One framework. Every design, every model, every downstream system. A ground-up restructure of how a national volume home builder produces and consumes Revit data. Not a file reorganisation: an operating framework that made every subsequent automation possible. 120+ master home designs on one standard. 347+ active Revit models in live production. 1,000+ design options carried consistently. 258 pyRevit tools built on the framework.

​

The problem. Every automation, every integration, every piece of estimating confidence depends on one thing: models that behave the same way. At volume-builder scale, with hundreds of models, thousands of options and dozens of hands touching them, consistency does not happen by policy document. It has to be engineered.

​

The framework. CORE carries the shared geometry and structure every design starts from. KOP (kit of parts) carries the standardised, data-rich components that designs assemble from. Between them sits the rule set: naming, parameters, worksets and content governance, enforced by tooling rather than by memo. The framework is versioned and migrated like software: a dual-API compatibility layer carries the entire estate across Revit generations (39 scripts migrated in one pass), and 258 purpose-built pyRevit tools keep production on the rails daily.

​

What it unlocked. The framework is the input standard for everything downstream: the 5D takeoff pipeline reads it, the 4D scheduling system depends on it, and modular/DfMA thinking becomes possible because the product range finally behaves as a governed system rather than a folder of files.

​

Results. A single source of truth across the full product range. Model-derived quantities made viable (see Takeoff Automation). An estate-wide API migration executed as one governed change. Institutional knowledge moved from individuals into tooling.

 

How the restructure works. In the legacy structure, every master carried its full option set in one file: a dozen facade variants and a dozen internal options side by side. Every NCC update or specification change had to be applied across all of them. One change, applied up to twenty-four times, per master. At project time, drafters downloaded copies of the master, manually purged the options that did not apply, then merged and re-documented what was left.

 

CORE+KOP splits the master into two governed models. The CORE model carries one internal layout and the facade options, so internal maintenance drops from twelve variants to one. The KOP model carries the optional components (additional bedrooms, extended alfresco, swapped rooms, mirrored plans) as a standardised kit of parts, each maintained once. A change is now applied once to the CORE and once per affected part, and a project assembles what it needs instead of purging what it does not.

 

The downstream effect is the point: both models are takeoff-ready by construction. Components carry classification codes, so the 3D takeoff reads CORE and KOP directly. The model is inspected, coded and priced as it is built, not re-measured after the fact.