15 cross-discipline coordination errors in construction drawings
The same handful of patterns show up on almost every project. Here is where each one hides, and the check that catches it.
Cross-discipline coordination errors are conflicts between the architectural, structural, mechanical, electrical, plumbing, fire-protection, and civil documents of the same project: two sheets that describe the same element differently, or an element one discipline needs that another never drew. They survive review because each discipline's set is internally consistent; the error only appears when sheets from two sets are read together. In an anonymized Groundbook AI review of about 60 structural and mechanical pages, these patterns accounted for most of the 42 potential findings.
Why coordination errors survive review
Each discipline checks its own drawings against its own drawings. The mechanical engineer confirms the duct schedule matches the duct plan; the structural engineer confirms the beam schedule matches the framing plan. Neither is asked, sheet by sheet, whether the duct fits under the beam. On a large set, the number of cross-set relationships is far larger than the number of sheets, and nobody's fee covers reading all of them twice.
The errors below are grouped by the kind of relationship that breaks. For each: where it hides, and how to check.
Revisions and references
- Two governing revisions. A structural sheet carries revision 3 while the architectural plan it depends on is at revision 4, and the set does not say which controls. Check: compare the revision block on every sheet against the issue log; flag any sheet older than the sheets that reference it.
- Callouts to sheets that do not exist. A detail bubble references S5.12 after the structural set was renumbered to S5.11. Check: every callout, section marker, and "see" note resolves to a sheet and detail in the current index.
- Notes pointing to the wrong discipline. "See mechanical for louver size" when the louver is on the architectural elevations only. Check: trace every cross-discipline note to a drawn element.
Geometry and elevations
- Floor elevation mismatch. Architectural level 3 at 124'-6" and structural top of slab at 124'-0", with the difference never reconciled by a topping or finish. Check: compare level datums between the architectural building sections and structural framing plans at every floor.
- Grid offsets. A column grid shifted 6 inches in one discipline after a late plan change. Check: overlay grid dimensions across disciplines; confirm grid-to-grid strings match.
- Beam depth versus ceiling height. A transfer beam deepened in the structural set while the RCP still shows a 9'-0" ceiling that cannot exist under it. Check: beam bottom elevation against ceiling elevation along the beam's length, then against duct mains crossing it.
- Slab depressions and steps. Depressions for tile, showers, or equipment drawn on architectural plans but missing from the structural slab plan. Check: every finish change and threshold on the architectural set against the structural slab edge and depression plan.
Systems and openings
- Required opening shown in one discipline. A shaft, chase, or roof opening on the mechanical plan with no corresponding framed opening in the structural set, or no rated shaft wall in the architectural set. Check: list every penetration larger than a sleeve and confirm it appears in all three sets.
- Duct or pipe route through a structural member. The classic duct-crosses-beam conflict at a corridor, or a drain line through a grade beam. Check: mains and risers against framing and foundation plans wherever they change level or direction.
- Equipment without support. Rooftop units, transformers, or a generator on the MEP plans with no pad, dunnage, or reinforced slab in the structural set. Check: every scheduled piece of equipment against the structural drawings for a support or load note.
- Rated assemblies that stop. A rated corridor on the life-safety plan whose wall type changes to non-rated on the enlarged plan, or a rated shaft that loses its rating at the roof. Check: trace every rated line through plans, wall types, and details from foundation to roof.
Schedules and specifications
- Schedule drift. Door 204 scheduled at 60 minutes, tagged on the plan with a 90-minute wall type. Check: every scheduled item against its plan tag and the assembly it sits in.
- Equipment schedule versus specification. A schedule lists a 460 V unit while the spec section describes a 208 V product, or the mechanical schedule shows a capacity the electrical panel schedule cannot serve. Check: capacities, voltages, and product references across mechanical, electrical, and specification sections.
Calculations and units
- Unit-conversion errors. A schedule that mixes metric and imperial, or a calculation that carries a value in the wrong unit into a schedule. Check: spot-check any schedule that reports capacities, flows, or loads against its calculation and against the units used on the plan.
- Inconsistent design criteria. Structural general notes citing one snow or wind value while the calculations or the specifications cite another. Check: design criteria in general notes, specifications, and calculation cover sheets against each other.
How to catch them systematically
Every check above has the same shape: take an element on one sheet and find it on another. That is a tractable job for a person on a small set and an impossible one on a large set, which is why Groundbook AI builds a project knowledge graph across drawings, specifications, checklists, and uploaded code sources and cross-checks the relationships for you. Findings come back with the exact sheet and location on both sides of the conflict, so the responsible engineer or architect can decide which is right. See the mixed-use residential case study for what that looked like on a real set.
Related pages
Frequently asked questions
What is the most common coordination error in construction drawings?
Consistency failures between a plan and its schedule, and between two disciplines describing the same element—floor elevations, openings, and beam-versus-duct conflicts—are the patterns that appear on almost every project.
Does clash detection catch these?
Clash detection finds physical interferences in a 3D model. Many of the errors above have no geometry to clash: a wrong revision, a missing callout, a schedule that disagrees with a spec. Those are document-review problems, not model problems.
Who is responsible for fixing coordination errors?
The architect or engineer of record for each discipline resolves the conflict in their documents. A review tool or a checklist surfaces the question; the professionals decide the answer.
Find these on your set before the field does
Set up a review yourself, or book time to talk through your project.