Guide · Coordination · 3 min read · Updated September 10, 2026
2D drawing review vs BIM clash detection
They are often mentioned together and they answer different questions. One asks whether two modeled objects occupy the same space. The other asks whether the documents that describe the building agree with each other.
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.
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. It does not read models and does not replace clash detection where models exist. See the cross-discipline coordination review for the checks it runs.
Keep reading
Related pages
Questions, answered
Frequently asked questions
Do I need BIM for clash detection?
Yes. Clash detection tests a federated 3D model, so every discipline involved has to have modeled its work to a compatible level of detail. Without models there is nothing to clash; coordination then falls to drawing review.
Can 2D drawing review find clashes?
It finds the clashes the drawings show: a duct route drawn through a beam on a section, a pipe crossing a footing on a plan. It cannot find an interference that appears only in three dimensions and on no sheet. That is what models are for.
Does AI plan review replace clash detection?
No. AI plan review of PDFs, including Groundbook AI, checks documents against documents, specifications, checklists, and codes. It does not read models. Where models exist, run both.
What is a soft clash?
A clearance violation rather than an intersection: an object sitting inside the access or maintenance zone another object requires. Clash software finds it when the clearance rule is set; a drawing reviewer finds it when a plan or detail shows both objects and the required clearance.
Why do coordination errors survive clash detection?
Because most of them are not geometric. Ratings, references, revisions, levels, schedule values, and specification requirements live on the drawings and in the project manual, not in the model. A clean clash report says nothing about whether those agree.
Run the document side of coordination on your set
Set up a review yourself, or book time to talk through your project.