BIM clash detection tests a federated 3D model for physical interference: a duct through a beam, a pipe through a footing, a clearance zone violated. 2D drawing review tests the documents themselves: a schedule that disagrees with a plan, a callout to a detail that does not exist, a level that differs between disciplines, a specification the drawings contradict. Clash detection needs coordinated models from every discipline and finds geometry problems. Drawing review needs only the issued PDFs and finds document problems, most of which have no geometry to clash. Projects that have both run both.
Two different questions
Clash detection asks a spatial question. Software loads each discipline's 3D model into one federated model, sets a tolerance, and reports every place two objects intersect (a hard clash), sit closer than a required clearance (a soft clash), or conflict in sequence (a workflow clash). The output is a clash list tied to model elements, worked through in coordination meetings until the model is clean.
Drawing review asks a documentary question. A reviewer, or a tool that reads the set, takes an element on one sheet and finds it on every other sheet, schedule, and specification that describes it, then checks that they agree. The output is a findings list tied to sheets and locations. Traditional 2D coordination did this by overlaying printed drawings, and its weakness was never the idea but the labor: incomplete overlays and missed cross-references let conflicts survive to the field.
How a federated model clash review runs
A federated model clash review follows the same loop on most projects. Each discipline publishes its model on an agreed schedule. The coordinator links them into one federated model on shared coordinates and levels, then defines clash tests between pairs of selection sets, such as ductwork against structural framing or sprinkler mains against cable tray, each with its own tolerance so that touching or insulated elements do not flood the report.
The software returns a clash list. The coordinator groups duplicates, filters out accepted conditions, assigns each group to the discipline that will move, and works through the list in a coordination meeting. After the next model drop the tests run again, and the count of open clashes becomes the progress measure. The quality of the review depends on the model: elements left out, modeled to a lower level of detail, or placed on the wrong level produce no clash at all.
How clearance zone checking works in BIM
Clearance checking looks for objects that do not touch but sit too close. It is set up in one of two ways. A clearance test reports any element within a set distance of another. A modeled clearance zone is an invisible solid attached to equipment, such as the access space in front of an electrical panel or the service space for a coil pull, which is then tested as an ordinary hard clash.
Either way, the distance is an input someone typed. It comes from the adopted code, the manufacturer’s installation data, or the owner’s maintenance standards, and a zone is only as good as the rule behind it. Drawing review checks that side of the problem: whether the clearance shown on the plans and equipment details agrees with the equipment schedule, the specifications, and the manufacturer data. A substituted unit with a larger service side, or a panel moved on the electrical plan but not on the architectural one, is a document finding before it is ever a clash.
Run the 2D drawing side of coordination
Find conflicts in sheets, schedules, and specs. Groundbook flags potential conflicts with links to the source sheets.
What each catches, and what each misses
| Problem | BIM clash detection | 2D drawing review |
|---|---|---|
| Duct routed through a beam | Yes, if both are modeled to the right level of detail | Yes, where the section or ceiling plan shows the conflict; a reviewer reads beam depth against duct route |
| Door scheduled at 60 minutes in a 90-minute wall | No. Ratings are attributes, not geometry, and often live only on the drawings | Yes. Schedule row against plan tag against wall type |
| Callout to a detail that does not exist | No. Sheet references are not in the model | Yes |
| Floor level 124'-6" architectural, 124'-0" structural | Only if both models were built to different datums and the difference produces an intersection | Yes. Level datums compared across disciplines |
| Opening shown on the mechanical plan, missing from the structural slab plan | Sometimes, as a duct-through-slab hard clash, if the slab is modeled solid | Yes, as a document gap: the opening exists in one discipline's sheets and not the other's |
| Equipment schedule says 460 V, spec says 208 V | No | Yes. Schedule against specification |
| Two structural sheets at different revisions with no statement of which governs | No | Yes |
| Clearance zone in front of a panel violated by a pipe | Yes, as a soft clash with a clearance rule | Only if a plan or detail shows both |
| Code requirement the drawings do not meet | No, unless a rule-checking add-on is configured | Yes, when the review checks against the code source |
The pattern: clash detection is strong on geometry and blind to attributes, references, revisions, specifications, and codes. Drawing review is strong on those and depends on what the drawings show for geometry.
What this looks like on a real set
Three anonymized findings from Groundbook AI's published reviews show the document side of the line:
- A required opening appeared in only one discipline. The plumbing sheets needed it; the structural slab plan did not show it. A model might have caught it as a clash if the slab were modeled solid, but the set as issued simply disagreed.
- Structural and mechanical floor elevations differed on the same level. No object collided; two disciplines described the same floor at two heights.
- Plans, schedules, and controls carried different equipment data. Nothing to clash. Three documents, three answers.
None of these is a 3D problem. All of them become field problems.
When you need both
On a project with coordinated models, run clash detection for geometry and drawing review for the documents, because the drawings are what gets permitted, priced, and built. On a project without models, which is still most small and mid-size work and nearly every renovation with archive sets, drawing review is the coordination check available.
Groundbook AI runs the document side. It reads the issued set, including scanned and hand-drawn sheets, connects every sheet, schedule, specification, checklist, and code source in a project knowledge graph, and returns findings linked to the sheet and the source. Teams can add a Revit model for spatial context, as described in 3D model-based plan review, but that does not replace clash detection where coordinated models exist. See the cross-discipline coordination review for the checks it runs.