The Cross-Discipline Coordination Checklist Every Drawing Set Needs
Short answer: A drawing coordination checklist is a structured set of checks that confirm the architectural, structural, and MEP drawings of a set agree with each other before they go to site. You work interface by interface — grids and levels first, then structure against architecture, then MEP routes against structure and ceilings, then risers, penetrations, and drainage falls — and you record every clash you find as a tracked item. Archi Check supports this on the drawings themselves: you put two disciplines side by side on a full-size monitor and mark each coordination issue as a tracked comment that someone has to resolve and close.
Most of the expensive problems on a construction site are not design failures. They are coordination failures — a duct that needs 450mm of ceiling void where the structure leaves 300mm, a column that lands in a doorway, a drainage run that cannot achieve its fall because a beam is in the way. Each discipline drew something reasonable in isolation. The drawings simply never agreed with one another, and nobody caught the disagreement on paper.
Coordination is the discipline of making those drawings agree before anyone builds from them. On a fully modelled project, a BIM clash-detection engine finds many of these conflicts automatically. But plenty of sets are still coordinated by people reading drawings against one another, and even on modelled jobs the human review of the issued drawing set is where the last and most consequential errors are caught. This guide is a practical checklist for that review, organised by the interfaces where clashes actually happen.
Why cross-discipline coordination is a drawing problem, not just a model problem
It is tempting to assume that coordination is solved the moment a project goes to BIM. Federate the models, run clash detection, resolve the hard clashes, and the drawings that fall out are coordinated by definition. In practice it is rarely that clean.
Models and drawings drift. A clash gets resolved in the model but the change does not propagate to every affected sheet, or a 2D detail is drawn over the top of a region the model never described. Tolerances that a clash engine treats as "soft" — a pipe passing within 50mm of a beam — are exactly the ones a human needs to judge, because whether they matter depends on insulation, supports, and access that the geometry alone does not capture. And a great many projects, particularly refurbishments, fit-outs, and smaller works, are never fully modelled in the first place. The coordination happens on the drawings or it does not happen at all.
So the drawing set remains the document everyone actually builds from, and the coordination review of that set is a distinct activity from running a clash report. It asks a different question: not "do these two solids intersect in the model" but "do these two drawings, as issued, describe a building that can be constructed". That question is answered by a person reading one discipline against another, which is what the rest of this article is about.
How to run a coordination review
Before the checklist itself, a word on method, because the order you work in determines how much you find. Coordination is layered: the lower layers constrain the upper ones, so a disagreement at the bottom invalidates everything above it. Checking in the wrong order means re-checking.
Work from the datum outward
Start with the things every discipline shares: the grid and the levels. If the architectural and structural grids do not agree, nothing else can be trusted, because every element on every drawing is positioned relative to that grid. Confirm the shared datum first, then move outward to the elements that hang off it.
Compare two disciplines at a time
Coordination is pairwise. You are always reading one discipline against one other — architecture against structure, then MEP against structure, then MEP against the ceiling. Trying to hold three disciplines in your head at once is how things get missed. Take the pairs in turn, on the same area of the building, at the same scale.
Record every clash as a tracked item, not a note to self
A coordination review produces findings, and a finding that is not recorded against an owner is a finding that will be forgotten. Each clash needs to become an item with a location, a description, the disciplines involved, and someone responsible for resolving it. A mental note or a mark on a printout that nobody else can see is not coordination — it is the appearance of coordination.
The cross-discipline coordination checklist
The checklist below is organised by interface — the boundary between two disciplines where clashes occur. Work down it roughly in order, because each row depends on the rows above it being clear. The disciplines are abbreviated A (architectural), S (structural), and M (mechanical, electrical, and plumbing, taken together as MEP).
| Interface | What to check | Disciplines | Typical clash it catches |
|---|---|---|---|
| Grids and levels | Grid lines, spacing, and reference letters match across every discipline; finished floor levels and structural slab levels are consistent and clearly distinguished | A / S / M | Drawings positioned to different datums; FFL confused with structural level |
| Structure vs architecture | Columns, beams, and walls land where the architecture expects; no structure in doorways, windows, or circulation; structural depths fit the architectural zones | A / S | Column in a doorway; downstand beam below a head height |
| MEP routes vs structure | Primary duct, pipe, and cable-tray routes have a clear path through or around beams and walls; penetrations are coordinated with the structural engineer | S / M | Main duct run blocked by a transfer beam |
| Ceiling void depth | The space between structural soffit and finished ceiling accommodates the deepest service plus insulation, supports, and crossings, with tolerance | A / S / M | Services deeper than the available void; clashing crossings |
| Risers and plant rooms | Riser dimensions accommodate all the services routed through them; plant-room layouts give equipment its required clearances and maintenance access | A / S / M | Riser too small for the riser schedule; no access to a valve |
| Penetrations and openings | Every service penetration through a wall, slab, or beam appears on the structural drawings with the correct size, position, and any required support or lintel | S / M | Slab penetration missing from the structural drawing |
| Drainage falls | Gravity drainage achieves its required fall along the full run without a beam, slab, or level change interrupting it; invert levels are consistent | S / M | Drain cannot achieve fall because a beam is in the way |
| Fire and acoustic interfaces | Fire and acoustic compartment lines align across disciplines; penetrations through rated elements are detailed and sealed | A / S / M | Duct crossing a fire line with no damper or seal detailed |
The table is a starting framework, not an exhaustive list. Every project has its own critical interfaces — a hospital adds medical-gas and pneumatic-tube coordination, a lab adds extract and containment, a tall building adds movement and tolerance at every floor. Adapt the rows to the project, but keep the order: datum first, then the heavy elements, then the services that have to fit around them.
The interfaces where clashes actually happen
Some of the rows above deserve a closer look, because they account for the majority of coordination failures that reach site.
Grids and levels: the datum everything else depends on
This is the cheapest check to perform and the most expensive to get wrong. If the structural grid is labelled differently from the architectural grid, or the two are offset, every subsequent comparison is built on sand. The level question is just as important and more often muddled: finished floor level and structural slab level differ by the floor build-up, and a drawing that conflates them sends services to the wrong height. Confirm that every discipline references the same grid and that levels are labelled unambiguously before you check anything else.
Ceiling void depth: the most contested 300 millimetres on the job
The ceiling void is where structure, architecture, and every mechanical and electrical service compete for the same vertical space. The structure sets the soffit, the architecture sets the finished ceiling, and the difference is all the room the services have — minus insulation, minus supports, minus the depth lost where two services cross. Coordinating the void means confirming the deepest service plus its allowances fits in the available zone along its whole route, not just at the easy points. This single interface generates more on-site rework than any other, because it is invisible until someone tries to install into it.
Penetrations: the holes that have to be in two drawings at once
A service penetration is a coordination problem by definition: a hole the MEP engineer needs and the structural engineer has to permit. Every penetration through a slab, beam, or structural wall must appear on the structural drawing with the right size and position, and with any lintel or trimming the structure requires. The classic failure is a penetration that exists on the MEP drawing and not the structural one, discovered when the slab is already poured and someone has to core through it — or worse, cannot.
Drainage falls: where gravity refuses to negotiate
Gravity drainage cannot be rerouted around a clash the way a pressurised pipe can, because it has to fall continuously to work. A beam, an up-stand, or a level change in the wrong place does not inconvenience a drainage run, it stops it. Coordinating drainage means tracing each run against the structure along its full length, confirming the fall is achievable and the invert levels are consistent at every junction. It is the interface where a clash is least forgiving and a late fix is most disruptive.
A worked example: coordinating a typical office floor
To make the checklist concrete, here is the kind of sequence a checker works through on a single office floor plate, reading one pair of disciplines at a time.
- Grids and levels. Confirm the structural and architectural grids share letters, spacing, and origin, and that the slab level and finished floor level are separately and consistently labelled. One offset here would invalidate everything below.
- Structure against architecture. Lay the structural plan over the architectural plan and check no column lands in a doorway, corridor, or glazing line, and that downstand beams clear the required head heights in occupied space.
- MEP routes against structure. Trace the primary duct and the main pipe runs across the plan and confirm each has a clear path, flagging where a run meets a transfer beam or a structural wall and needs a coordinated penetration.
- Ceiling void. At the tightest crossing — typically a corridor where a duct, a sprinkler main, and a cable tray all run together — confirm the deepest service plus insulation and supports fits below the structural soffit and above the finished ceiling.
- Riser. Check the riser drawn on the architectural plan is large enough for everything the riser schedule routes through it, with room for connections and access.
- Penetrations and drainage. Confirm every penetration the MEP drawings need is shown on the structural drawings, and trace the WC drainage run to confirm it holds its fall to the stack without meeting a beam.
Each disagreement found becomes a tracked item with a location and an owner — the duct that does not fit, the missing penetration, the column in the corridor — and the floor is not coordinated until every one of those items is resolved and confirmed.
Where Archi Check fits
Archi Check is purpose-built QC software for architectural drawing sets, and coordination review is one of the things it is built to support — with an important honest caveat. Archi Check is a drawing-review and markup tool, not a 3D clash-detection engine. It does not federate models or compute geometric intersections. What it does is make the human coordination review of the issued drawings faster, more thorough, and fully tracked.
The core of that is the two-screen workflow. Coordination is pairwise, and the natural way to do it is to put two disciplines next to each other and read one against the other. Archi Check lets you open the architectural drawing and the structural drawing side by side on a full-size monitor, with the register on the second screen, so you are comparing real drawings at a real scale rather than squinting at thumbnails. When you spot a clash — a column in a doorway, a duct that will not fit the void — you mark it directly on the drawing, and that markup becomes a tracked comment with an owner, a discipline, a location, and a status.
From there the coordination finding moves through the same loop as every other QC item: Check → Correct → Verify → Close. The clash is raised, assigned to whoever owns the fix, corrected, verified by someone other than the person who made the change, and only then closed. A coordination issue cannot quietly disappear, because it stays open until it is resolved and confirmed. And because Archi Check keeps your QC data in your own project folders rather than a vendor cloud, the full audit trail of what was found, who fixed it, and who signed it off belongs to you. Archi Check runs on Windows today, with macOS coming soon, and there is a 14-day free trial.
FAQ
What is a drawing coordination checklist?
A drawing coordination checklist is a structured set of checks that confirm the architectural, structural, and MEP drawings of a set agree with one another before construction. It is organised by interface — grids and levels, structure versus architecture, MEP routes versus structure, ceiling void depth, risers and plant rooms, penetrations, and drainage falls — so that each clash between disciplines is caught on paper rather than on site.
How do you coordinate architectural, structural, and MEP drawings?
Coordinate pairwise and in order. Confirm the shared grid and levels first, because every element is positioned relative to them. Then read structure against architecture, then MEP routes against structure, then services against the ceiling void, and finally risers, penetrations, and drainage falls. Take two disciplines at a time on the same area, and record every disagreement you find as a tracked item with an owner.
Is coordination on drawings the same as BIM clash detection?
No. BIM clash detection finds geometric intersections automatically in a federated 3D model. Coordination on drawings is a human review of the issued 2D set, which is a different and complementary activity. It catches the soft clashes a person has to judge, the changes that did not propagate from model to sheet, and the conflicts on projects that were never fully modelled. Many sets need both.
Which interface causes the most coordination problems?
The ceiling void is the most common source of on-site rework, because structure, architecture, and every mechanical and electrical service compete for the same vertical space and the conflict stays invisible until installation. Penetrations and drainage falls are close behind, because a missing penetration or an interrupted fall is expensive and disruptive to fix once the structure is built.
Can Archi Check do clash detection?
Archi Check is a drawing-review and markup tool, not a 3D clash-detection engine, so it does not federate models or compute geometric intersections. It supports the human coordination review of the drawings: you put two disciplines side by side on a full-size monitor, mark each clash as a tracked comment with an owner and a status, and move it through Check → Correct → Verify → Close until it is resolved.
Coordinate the set before it reaches site
A coordination review only protects a project if every clash it finds is recorded and followed through to resolution. If your coordination still lives as marks on a printout, see how Archi Check turns each finding into a tracked item with a full audit trail: Try Archi Check free for 14 days.
Related guides
Keep building out your drawing QC process with Archi Check and these related guides:
- How to check construction drawings
- How to set up a shop drawing review process
- The drawing QA/QC process in 4 stages
- Drawing markup symbols explained
Archi Check is an independent product by Archi for architectural drawing QA/QC. Product names and trademarks referenced belong to their respective owners and are used for identification only.
