BIM and IFC: What Checking the Model Against the Drawings Adds, and What It Cannot Tell You
On many projects today the drawings are produced from a model. In theory that means the drawings and the model always agree. In practice they drift: a sheet is edited by hand after export, a schedule is overridden, a storey is renamed in one place, a consultant works from an older model. When the model is submitted alongside the drawings, it becomes a second source of truth, and comparing the two is one of the most effective ways to find errors that neither source shows on its own.
This article explains what checking an IFC model against the drawings adds, what such a check cannot tell you, and how to prepare models so the comparison is meaningful.
IFC in brief
IFC (Industry Foundation Classes) is an open, vendor-neutral data format for building models, maintained by buildingSMART and published as an ISO standard. Most BIM authoring tools can export it. IFC files describe a building as typed objects with properties: a site containing a building, the building containing storeys, storeys containing spaces, walls, slabs, doors, windows, columns, beams, ducts and so on. Several schema versions are in use (IFC2x3 and IFC4 are the most common), and what a file contains depends heavily on the export settings chosen in the authoring tool.
The useful property of IFC for review is that it is structured. A storey is a storey with an elevation, a space is a space with a name and a computed area, a door is a door with dimensions. That makes comparison with drawings and schedules a matter of reading values rather than interpreting lines.
What a model-versus-drawings check adds
Heights and elevations
The model holds storey elevations and the geometry of slabs and roofs. The drawings state floor-to-floor heights in sections, a total building height on elevations, and often a height in the code summary. A check can compare all of these. A building height that differs between the narrative, the sections and the model is not cosmetic: height often drives code classification, fire requirements and zoning limits.
Storey counts and names
The number of storeys above and below grade, and how they are named, should match across the model, the plans, the sections and the code summary. Mezzanines, plant levels and basement levels are where mismatches appear most often, because one source counts them and another does not.
Room areas versus schedules
Spaces in the model carry names, numbers and areas. The room schedule on the drawings, the area table on the cover sheet and the figures used in the estimate should match them. A difference may be legitimate (gross versus net, different measurement rules) or may reveal a schedule that was not updated after a design change. Either way it should be explained, because everything priced per square foot inherits it. See how to check a quantity takeoff for the cost side.
Element counts and types
The number of doors, windows, columns or plumbing fixtures in the model can be compared with the counts in the drawing schedules. A door type that exists in the model but not in the schedule, or the reverse, is a coordination gap.
Identifiers and references
Room numbers, door marks and level names should be the same in the model and on the sheets. When they differ, every cross-reference between drawings, specifications and the estimate becomes harder to follow.
What an IFC check cannot tell you
Being honest about limits matters here, because a model looks complete in a viewer even when important information is missing.
- Whether the model is complete. A check reads what is in the file. If a discipline was not modelled, a floor was excluded from the export, or elements were modelled as generic objects, the check will not invent them. Missing content shows up only where the drawings or schedules mention something the model lacks.
- Whether the design is compliant. Matching numbers between model and drawings means the documents agree with each other. It does not mean they meet the code. Compliance requires checking the agreed values against the requirements in force, and final decisions rest with plan review and licensed professionals.
- Information that lives only on the sheets. General notes, specifications, many details, and annotations added after export are typically not in the IFC file. The drawings remain the contract documents in most projects; the model supports them.
- Correctness of properties. A wall can be tagged with a fire rating property that is wrong, outdated or simply a default value. A check can compare the property with the drawings, not confirm the assembly will perform.
- Structural or system adequacy. A model shows geometry and properties, not whether a beam is strong enough or a duct is sized correctly. That is engineering, not data comparison.
- Content lost in export. Depending on the schema and settings, export can drop properties, simplify geometry or misclassify objects. If something is missing in IFC but present in the native model, the problem is in the export, and the check sees only the export.
Why each discipline should be a separate model
It is tempting to merge architecture, structure and MEP into one IFC file before submitting. Usually it is better not to.
- Differences stay visible. If architecture and structure use different level elevations, two separate models show the conflict. A merged model may contain duplicate storeys or have one discipline's levels silently adopted by the other.
- Responsibility stays clear. Each model has an author and a revision. Findings can be traced to the discipline that needs to act on them.
- File sizes stay manageable. Federated models grow large quickly. Separate files are easier to transfer and read, and more likely to stay within upload limits.
- Revisions can be compared. When one consultant issues a new model, only that file changes, and you can see what changed in that discipline.
Name each file with the project, discipline and revision, for example a code for architecture, structure or mechanical followed by the revision and date, and keep the same storey names and project base point across disciplines.
How to prepare IFC files for a check
- Export from the current model state and record the date and the drawing revision it corresponds to.
- Use a supported schema (IFC2x3 or IFC4 are the common choices) and the same schema for all disciplines if possible.
- Include spaces. Many exports leave rooms out by default. Without space objects there are no room areas to compare.
- Map categories properly so walls are walls and doors are doors, not generic building elements.
- Include the property sets you rely on, such as fire ratings, door types and room numbers.
- Keep storey names and elevations consistent with the drawings and across disciplines.
- Open the export in an independent viewer before sending, to confirm that floors, spaces and key properties came through.
- Send the drawings too. The comparison is the point; a model without drawings can only be checked against itself.
Typical findings from a model-versus-drawings comparison
| What differs | Where it usually comes from |
|---|---|
| Storey count or names | Mezzanines and plant levels counted in one source only |
| Building height | Code summary not updated after a section change |
| Room area vs schedule | Schedule overridden by hand, or different measurement rules |
| Door or window counts | Late design changes not carried into schedules |
| Level elevations between disciplines | Consultants working from different base points or older models |
For the full list of places where document sets go wrong, see the construction document review checklist. Lenders and owners who rely on area figures for budgets will also find useful context in what to verify in a borrower's budget before closing.
Where MEXUM fits
MEXUM reads IFC models up to 25 MB alongside drawings, specifications, estimates and contracts, and checks them against each other and against the codes of the project region. The conclusion arrives as a PDF within 24 hours, with each finding carrying a quote and a page reference. Larger federated models are best split by discipline before upload. The check does not replace model coordination by the design team, plan review or the judgment of a licensed architect or engineer.
Frequently asked questions
Does a matching model and drawing set mean the design is compliant?
No. Agreement between model and drawings shows that the documents are consistent with each other. Whether the agreed values meet the code is a separate question, and the final decision rests with plan review and the licensed professionals responsible for the design.
Why are room areas missing when my IFC file is checked?
Most often the export did not include space objects. Many authoring tools leave rooms out of IFC unless you enable them. Without spaces, there are no room areas in the file to compare with the schedule.
Should I merge all disciplines into one IFC file?
Usually not. Separate models keep conflicts between disciplines visible, keep responsibility and revisions clear, and keep file sizes manageable. Use consistent storey names and the same base point across them.
Which IFC version should I export?
IFC2x3 and IFC4 are the most widely used. Use one supported by the recipient, and ideally the same schema for every discipline, so that the files can be read and compared consistently.
