Reviewing an IFC delivery without losing context
An IFC review should test whether the exchanged model supports the agreed collaboration task. It is easy to lose context when a reviewer sees only isolated objects or attractive exterior views. Keep the brief, source references and current issue information nearby so observations can be assessed against the building and the purpose of the exchange.
Open the actual delivered file
Use the viewer or receiving application intended for the project. Confirm the file identity, issue date and relationship to any accompanying native model. Check that the expected building and floors are present before investigating individual elements. If the file displays differently from another application, distinguish a display issue from missing information. Record the environment used for review so any problem can be described reproducibly. The provider needs more than a screenshot saying that the model looks wrong on one computer.
Follow a structured route
Start with the overall building, then inspect level organization and a representative selection of architectural elements. Use sections to check relationships that are hard to judge in an exterior view. Select a few elements and examine the properties relevant to the receiving team's task. Check names, categories and any required project reference information. Review complex interfaces and known source uncertainties early. These areas are more informative than repeatedly inspecting straightforward rooms that were already clear in the original drawings.
Give feedback with the exchange purpose
State the element or location, the observed issue and the information expected under the agreed brief. Include a view showing context as well as the close-up if needed. Identify whether the concern is missing geometry, confusing classification, an absent property or a question about the underlying design. Refer architectural and specialist decisions to their owners. An IFC file does not automatically prove that the project has been fully coordinated, structurally assessed or checked against regulations simply because multiple people can view it.
A structured IFC review
- Confirm the issue and receiving environment first, then follow a repeatable route through overall geometry, levels, representative elements and the most uncertain connections.
- Inspect useful properties alongside appearance and distinguish missing information from application display differences before reporting a problem to the provider or project team.
- Describe each issue with a location, expected information and exchange purpose, then retain the accepted file reference with its recorded limitations and review status.
Save the accepted file reference and a short review record with any remaining limitations. If the provider reissues the IFC, confirm the reported fixes and any connected changes. A repeatable review route makes future exchanges easier: the practice knows what was checked, the recipient knows what the file supports and outstanding questions remain attached to the correct issue.
Sources and technical reading
General guidance: each project's scope is confirmed before commissioning.