Revit compatibility: what to agree before starting
The requested Revit version is an operational requirement that belongs in the initial brief. Discovering a mismatch at handover can interrupt continued work even when the modeled geometry is acceptable. Agree the intended authoring environment, office requirements and receiving workflow before production begins, then test any unfamiliar arrangement with a representative file.
Identify the receiving environment
Ask the colleague who will continue the work which Revit version the practice requires. Record that requirement in the commission and confirm it with the provider. Identify any office templates, component libraries or linked references that matter to the agreed task. Avoid assuming that every project in the practice uses the same setup. If consultants have separate requirements, describe those as distinct exchanges rather than expecting one file to satisfy several unexamined workflows at once.
Clarify the continuation task
Explain what the practice needs to do after receiving the model. Continuing architectural authoring has different requirements from simply reviewing the building. Confirm the expected organization, names and delivery contents alongside the version. If an IFC is also required for exchange, define its purpose and review it separately. Do not treat another file format as an automatic replacement for the native editing workflow the practice originally requested. Agree any change to the handover before the model is developed around different assumptions.
Test the handover early
For a new provider or unusual office setup, request a small representative sample and open it in the receiving environment. Check that the team can identify levels, inspect elements and perform the intended next steps. Record any issues with references or office conventions while they are still inexpensive to resolve. At final delivery, repeat the practical opening and usability check on the issued package. Keep a clear issue reference linking the tested native model to any accompanying exports or review notes.
A compatibility check
- Ask the actual receiving author to confirm the required Revit environment and continuation task instead of relying on a general office software assumption.
- Open a representative sample in that environment and check whether the team can identify levels, understand element names and continue its intended architectural work.
- Repeat the practical opening check on the formally issued package and link its issue to any accompanying exports, review comments and source references provided.
Add the required version and handover workflow to the practice's standard request template. Reconfirm them when a new project uses a different environment. A compatibility agreement is successful when the receiving team can use the delivered architectural base for its planned work, with any limitations understood before the deadline rather than discovered when production is supposed to resume.
General guidance: each project's scope is confirmed before commissioning.