What Revit model development actually involves
Development means progressing an existing Revit file from drawings, markups and a written brief — not taking over design authorship.
Published 24 August 2026 · 3 min read
Revit model development is production work on a file the practice already has. An early-stage model needs to be taken further. Drawings have moved on. Markups need to be built. The in-house team should not spend the next fortnight tracing rather than designing.
It is not the same as CAD to Revit
CAD to Revit rebuilds a model from drawings. Development assumes a Revit file already exists and then changes it. Mixing the two in one sentence is how scopes go wrong. If the current file is not usable, that should be said up front — the job may be closer to a new model than to an update.
What to send
- The current Revit file, in the version the office will keep using
- Drawings, PDFs or markups that show the required changes
- A written list of what is in and out of this package
- Templates or standards if the model should match in-house organisation
Outsourced Revit modelling of this kind only works when the instructions are specific enough to quote. “Develop the model” is not a scope. “Add the new wing shown on these markups, update levels 02 and 03, leave the existing core” is.
Who is still the architect
The practice remains responsible for design. Development follows the information supplied. Conflicts between the model and the drawings are referred back. That is slower than guessing, and it is how the office keeps control of the file.
Questions
No. CAD to Revit starts from drawings and builds a new model. Model development starts from a Revit file the practice already has.