Blog
Revit IFC Workflow for Architects: Coordination Guide
A Revit IFC workflow for architects is most useful when several disciplines need to exchange building information without working in the same native authoring software. Architects may develop the building design in Revit while structural or MEP engineers use another BIM platform. IFC provides a practical exchange format for sharing model information, but it should not be treated as a replacement for the native Revit project.
The most reliable approach is to maintain one controlled Revit model for architectural design and documentation, then create clearly identified IFC exports for specific coordination purposes. This separates design authoring from exchange, makes changes easier to track and gives engineers a model that is structured for review rather than simply a file produced at the end of a deadline.
When IFC exchange is useful in an architectural project
IFC exchange with engineers is useful when teams need to review geometry, locations and selected building information across different software environments. Typical examples include:
- Sharing architectural walls, slabs, roofs, doors, windows and spaces with structural engineers.
- Giving MEP consultants a reference model for levels, rooms, cores, shafts and other spatial constraints.
- Combining discipline models in a coordination or model-review application.
- Checking whether structural and service proposals fit the architectural design.
- Providing an open BIM deliverable for a tender, client review or project information requirement.
- Preserving a structured model exchange when a consultant cannot open the native Revit file.
IFC is more useful than a PDF or a collection of DWG files when the recipient needs to inspect model objects in three dimensions. A PDF remains appropriate for issued drawings, while DWG can still be practical for selected 2D drafting and detail exchanges. IFC sits between these uses: it carries a model with object categories and properties, but the result may not behave exactly like the original Revit model.
Before exporting, agree with the project team what the IFC is for. A coordination export, a tender exchange and an archive deliverable may require different content, naming and checking. Do not export every view, family and parameter simply because the information exists in Revit. A smaller, purposeful exchange is usually easier for engineers to review.
Keep Revit as the native project model
Revit connects design, documentation and building data in one model-based workflow. Plans, sections, elevations, schedules and sheets can be developed from coordinated building elements instead of disconnected drawings. This makes the native Revit model the appropriate place to author architectural changes.
IFC should normally be considered a published exchange version. It is not a round-trip editing format that guarantees every Revit object, family behaviour, view setting or parameter will return unchanged. An engineer may be able to reference the IFC, classify objects and coordinate against it, but the architectural team should continue making design changes in Revit.
This distinction prevents a common error: editing several exported files and then trying to determine which version is authoritative. Establish a simple rule at the start of the project:
- Revit: the native source for architectural design, documentation and revisions.
- IFC: an issued exchange file for coordination or another agreed purpose.
- PDF: a controlled drawing or document issue where visual output is required.
- DWG: a targeted 2D or detail exchange where the project requires it.
Use a consistent file naming method that identifies the project, discipline, zone or building, purpose, issue and date or revision. The exact convention should follow the project information requirements. The important point is that a recipient can identify what the file contains and whether it is current.
Prepare the Revit model before exporting IFC
Good IFC output begins with model management, not the export command. Before you export IFC from Revit, review the model using the same questions an engineer or coordinator will ask when opening it.
Check the project location and coordinate setup
Confirm the agreed project base point, survey point, orientation and shared coordinates. A model can look correct on its own but appear far away, rotated or misaligned when combined with another discipline model. Coordinate decisions should be made at project level and documented for the team.
Do not move the model to make one export look correct without understanding the effect on linked models, views, sheets and documentation. If the project uses separate buildings or zones, confirm whether each IFC should use the same overall coordinate system or a documented local system.
Review levels, grids and storeys
Check that levels have clear names and sensible elevations. Duplicate levels, temporary working levels and inconsistent naming can make coordination harder. Decide which levels and grids are intended for exchange. Engineers may use them to position structural elements, ducts, pipes and equipment, so an unclear vertical structure can create avoidable review questions.
Clean the model content
Remove or isolate elements that do not belong in the intended exchange. Examples may include temporary study geometry, demolished elements, linked reference content that the recipient does not need and highly detailed objects that do not support coordination. Review design options, phases and worksets so that the exported model represents the agreed project status.
Element categories and classifications also matter. A generic model used for a wall, equipment item or specialist component may not export with the meaning that the recipient expects. Use suitable native categories where possible, and check how important families appear in the target coordination software.
Review information before geometry
For each key element, check whether the information is useful and consistent. This can include type names, materials, fire or acoustic information where required by the project, manufacturer data where agreed, room or space relationships and design responsibility. Do not add unverified information just to make the export appear complete. An empty field is safer than a misleading value.
Choose what the IFC export should contain
Export settings vary by Revit version, project requirements and the receiving application. Use the IFC export options available in your installation and follow the exchange specification agreed with the engineers. Avoid assuming that one preset works for every project.
Before creating the file, decide:
- Which building, phase, design option or area is included.
- Whether linked Revit models are included or delivered separately.
- Which coordinate system and north orientation are required.
- Which level of geometric detail supports the coordination task.
- Whether spaces, rooms, zones, grids and reference elements are needed.
- Which property sets or project parameters are required by the recipient.
- Whether the exchange is for visual coordination, information review or a formal deliverable.
Including linked models in one export may be convenient for a combined reference file, but it can also make responsibility and revision tracking less clear. In many projects, separate discipline exports are easier to manage. Ask the coordinator how the files will be combined before selecting an approach.
Keep the export process repeatable. Record the Revit model version, export settings, included content and issue identifier. If a result must be recreated later, another team member should be able to understand how it was produced.
Review the IFC after export
Never assume that a successful export command means the exchange is correct. Open the IFC in the agreed coordination or model-review application and compare it with the Revit source. The review should cover both geometry and information.
Geometry checks
- Are the building, levels and main elements in the correct location?
- Is the model orientation correct?
- Do walls, floors, roofs, doors and windows appear in the expected categories?
- Are important openings, shafts and voids visible?
- Are elements duplicated, missing or unexpectedly fragmented?
- Is the model detail suitable for coordination without excessive file complexity?
Information checks
- Are storey names and element types readable?
- Are key properties present and assigned to the correct objects?
- Can the coordinator distinguish existing, proposed and demolished content where relevant?
- Are rooms or spaces included if the exchange requires them?
- Can the recipient identify the source discipline, issue and model status?
Compare a few known elements rather than checking only the overall appearance. Select a wall, door, slab, room and important façade or core element in both the Revit model and the IFC viewer. This small sample can reveal incorrect categories, missing properties or an offset coordinate system.
Keep a short export check record. Note the file name, export date, model revision, person responsible and any known limitations. If the engineer reports that a family or property is not visible, this record helps determine whether the problem comes from the Revit source, the export settings or the receiving application.
Coordinate efficiently with engineers
Architectural BIM coordination works best when the IFC is exchanged with a clear request. Do not send a model without explaining what the recipient should review. A useful transmittal can state the model status, included scope, coordinate system, intended use and known exclusions.
For example, an architectural exchange may ask the structural engineer to review slab edges, openings, cores, stair geometry and major wall positions. An MEP exchange may focus on ceiling zones, risers, plant areas, rooms and access routes. A tender exchange may require a broader set of object information but still needs a defined issue status.
Use the engineer’s comments to update the native Revit model, not the IFC file. After agreed changes are made, export a new IFC with a new revision or issue identifier. Avoid silently replacing a file with the same name, because coordinators may not know whether the model has changed.
For repeated exchanges, define a cycle:
- Update the approved architectural design in Revit.
- Run model checks for location, levels, phases and required information.
- Export the agreed architectural scope to IFC.
- Open and review the IFC independently.
- Issue the file with its revision and coordination notes.
- Receive and record engineer comments or clash findings.
- Resolve agreed changes in Revit and repeat the cycle.
This process is more reliable than exporting immediately after every small edit. The project team should agree exchange dates or milestones, especially when several disciplines need time to review the same issue.
Keep native Revit and IFC versions aligned
Version control is the main safeguard against coordination based on outdated information. A Revit coordination model should have a visible relationship to the native model and the issued IFC. Store the export with a clear revision, and keep a record of which Revit project state produced it.
Do not overwrite an IFC that is still being referenced in a coordination session. Issue a new file instead, then communicate what changed. Changes may include a revised core, altered floor-to-floor heights, moved shafts, updated façade geometry or changed room boundaries. A brief change summary helps engineers focus their review.
When a design is split into separate Revit files, coordinate their shared location and naming rules before export. If the architectural model is linked to another architectural or specialist model, verify whether that model should be issued separately. The goal is not to create one enormous file; it is to provide a predictable set of models that can be combined without ambiguity.
| Project need | Recommended exchange | Why |
|---|---|---|
| Architectural authoring and documentation | Native Revit model | Preserves parametric relationships, views, sheets and schedules. |
| Cross-platform 3D coordination | IFC export | Provides a structured model exchange for review in another BIM environment. |
| Issued drawing review | PDF from controlled views or sheets | Provides a stable visual record for the agreed issue. |
| Selected 2D drafting exchange | DWG export | Useful where the recipient needs compatible linework or details. |
| Formal information delivery | IFC plus the project-required documents | Supports an agreed open BIM delivery without assuming IFC contains every project document. |
The best tool depends on the task. IFC is not automatically better than Revit, DWG or PDF; it solves a different exchange problem. Use it when the recipient needs a coordinated, structured building model and when the project has agreed what the exchange must contain.
Which Revit setup fits an architecture studio?
Autodesk Revit is designed for architecture, structural engineering and MEP workflows in a shared building information model environment. For an architecture studio, it is suitable when the team needs connected plans, sections, elevations, schedules and sheets, together with model-based coordination and IFC exchange.
A studio should choose the Revit licence term and account arrangement that match its operational needs. Autodesk Revit is available for Windows, supports multiple languages including English, German, French, Italian, Spanish, Czech, Polish and Portuguese (Brazil), and the licence is assigned to an Autodesk account for one device. Check the current product page for the available term and licensing details.
Genuine Autodesk Revit licences are available from KEYFORREST with instant electronic delivery. Use the current product page to check the available option for your studio before purchase.
Frequently asked questions
Is IFC a replacement for the Revit model?
No. IFC is an exchange format for sharing agreed model content with other applications. Keep the native Revit model as the source for architectural design, documentation and revisions.
How often should an architect export IFC?
Export at agreed coordination milestones or issue dates. The right frequency depends on the project programme and the amount of design change. Always create a new identified issue rather than silently replacing a file.
Why does an IFC look different from the Revit model?
IFC export translates Revit geometry, categories and properties into an exchange structure. Some family behaviour, display settings, parameters or detailed geometry may not transfer exactly. Review the exported file in the target application.
Should linked Revit models be included in the architectural IFC?
It depends on the coordination agreement. Separate exports can make discipline responsibility and revisions clearer, while a combined reference export may be convenient for some reviews. Confirm the expected approach with the coordinator.
Can engineers edit the architectural IFC?
They may be able to reference, classify or coordinate against it, depending on their software. Architectural changes should normally be made in Revit and then issued through a new IFC export, rather than relying on edits to the exchange file.