v7.3.0 - A desktop install that heals itself,
and an estimator that never fakes a price.

v7.1.0 connected the modules. The two releases folded in here are about trust: the parts of the app that should have just worked, working. A desktop install that finishes on every machine and quietly repairs a broken one. An estimator that never shows you a number it cannot stand behind. A BIM viewer where filtering a model actually filters it and stays put. Schedules that get checked like everything else. None of this is glamorous, all of it is the difference between a tool you reach for and one you work around. Everything here was verified against the live backend and on real installs, the Alembic head is a single revision, the frontend type-checks clean and the backend is ruff clean.

What landed

A desktop install you can trust

The desktop app is meant to be the easy way in: download one installer, open it, and you have the whole platform running locally with its own database, no Docker and no separate server. Most of the time that is exactly what happens. But a fresh install sets up a local PostgreSQL on first launch, and on Windows PCs whose regional format was set to Turkish that step could hang on "Recovering the local database" and never finish. The bundled database tool refused the non-ASCII locale name the system handed it during setup, so the database stayed half-built. Setup now always creates the database with a neutral locale, which sidesteps the problem entirely. On top of that, if an earlier attempt left a half-finished database folder behind, the next launch clears it and starts clean, so a machine that was already stuck on a broken install heals itself instead of failing the same way again. Both paths were verified end to end against a real local PostgreSQL: a fresh install, and an upgrade from a folder that a previous run had left broken.

An estimator that never fakes a price

The AI Estimate Builder matches your work against a cost catalogue, and sometimes it finds the right code but that code has no price recorded. Before, the match step would show a $0.00 in that case, which reads like a real, free line and is exactly the kind of number that slips into a total unnoticed. Now the match step and the alternatives list say "matched, no price in catalogue" instead. An unpriced code reads honestly, you can pick a priced alternative from the list, and the line stays flagged for review. The rollup still treats the missing price as zero, so the totals you see stay correct, but nothing pretends the work is free. Around it, the estimator got clearer end to end: parameter names read as plain words instead of code-style snake_case, the match step shows a live progress bar so a long run no longer looks frozen, and matched rates are grouped by trade instead of one long list. Element matching can also use your own AI key to re-rank candidates for better results, turned on at the match step, with the key scoped to your own workspace so it is never shared across tenants.

BIM filtering that stays put, in every language

Loading an IFC or other BIM model and then filtering it should be simple: pick a storey, a category or an entity type and see just those elements. For larger models that briefly worked and then the whole project would reappear a moment later, because the geometry finished loading and the camera reset to fit everything. Grouping and filtering now line up with the geometry reliably. Each shape is matched to its element by a stable id, so the selection isolates exactly the right elements and the view holds that selection rather than snapping back to the full model. It was verified end to end on a real IFC model: a wall, a member or a storey filter keeps just that subset on screen and stays there. The panel that drives all this is now fully translated in all 26 app languages. The search box, the category, level and grouping controls, and the property-search operators had been showing in English everywhere because their text lived only in code, never in the translation catalogue. That text is now in the catalogue and translated, and the remaining stage-2 translation gaps were closed in the same pass.

Schedules join the validation pipeline

Validation has always been a first-class step for a bill of quantities and a BIM import: data comes in, it is checked against a configurable rule set, and the result is a traffic-light report you can act on. A project schedule is just as easy to get wrong, and until now it was trusted by default. The new schedule-quality pack brings it into the same pipeline with seven checks: missing logic links, dangling activities, negative or excessive lag, hard date constraints that fight the logic, and out-of-sequence progress among them. A weak schedule now shows up as warnings and errors you can resolve, not a plan you assumed was sound. Alongside it, modules across the platform now explain themselves with a shared set of guidance pieces: confidence badges, suggestion chips, plain-language error states, an inline glossary tooltip and consistent grid headers. The first wave of construction glossary terms shipped in every language, so a term means the same thing wherever it appears.

Faster, tidier, and honest fixes

Moving between modules is faster now. The sidebar and header stay mounted as you navigate instead of being rebuilt on every page, so switching modules no longer tears down and re-creates the whole shell each time. The BIM upload picker accepts RVT, IFC and DWG only, and a dropped DWG is routed straight to the Drawings takeoff where it belongs instead of failing as an unsupported 3D model. The RVT converter stopped reporting "Converter is out of date" when it was actually current. Module badges were tidied so a well-developed module no longer wears a BETA tag it has outgrown, rougher ones keep it, and the old NEW tag is gone. The DWG takeoff drawing card reads clearly on the dark canvas, and the PDF takeoff toolbar wraps to two rows instead of showing a scrollbar. On the security side, appending a maintenance entry to an asset now verifies you have access to that asset's project first, closing a gap where that one endpoint skipped the per-project access check. And more interface text was translated, including the converter install progress labels and a validation page introduction that were still showing in English.

Upgrade

pip install --upgrade openconstructionerp

The Alembic head is a single revision and the normal install path creates the schema from the models and stamps it at the latest version. The desktop installers for Windows, macOS and Linux carry the install-reliability fixes, so a fresh install sets up its local database with a neutral locale and a machine left in a broken state from an earlier attempt repairs itself on the next launch. You can grab the latest installers from openconstructionerp.com/download. If you run an external PostgreSQL through DATABASE_URL, nothing about that connection changes. Questions or trouble upgrading, write to info@datadrivenconstruction.io.