Common Drawing Coordination Issues in Construction

Coordination problems are almost never caused by anyone doing their job badly.

That is the part people get wrong, and getting it wrong shapes how they respond. The mechanical engineer sized the unit correctly. The structural engineer designed the framing correctly for the load he was given, but that load schedule was superseded by a new one four weeks prior and was never informed. Three competent professionals, one uncoordinated set, and a framing revision that arrives after fabrication release.

Drawing coordination issues are artifacts of how design is produced: multiple firms, working asynchronously, exchanging backgrounds on a lag, each reviewing its own work internally and rarely reviewing across the boundary. That structure generates a predictable set of failures. Predictable is the useful word, because it means you can look for them specifically instead of hoping to notice them.

This article catalogs twelve coordination issue types, explains the mechanism that produces each one, identifies where each concentrates, and describes how to catch it. Then it covers the zones where coordination issues cluster, because coordination density is not uniform across a building and reviewer attention should not be either.

The framing throughout is diagnostic rather than accusatory. A coordination finding is information about a process, not a criticism of a consultant, and teams that treat it the second way get worse documents on their next project.

What Counts as a Coordination Issue

A drawing coordination issue is a conflict between two or more disciplines’ documents, where each discipline’s information is internally reasonable and the combination is not buildable, not consistent, or not adequate.

That definition excludes three things it gets confused with. It excludes errors inside one discipline’s own set, which are internal accuracy problems. It excludes conflicts between drawings and specifications, which are correlation problems. And it excludes obligations nobody has been assigned, which are scope problems.

Table 1. Coordination Issues Distinguished From Related Defects

The distinction matters operationally because each class needs a different reviewer and a different comment. Sending a coordination issue to one consultant produces a response that fixes half the conflict. Coordination findings need both parties in the conversation, which is why they belong in a coordination meeting rather than in a one-way comment log.

Core Terminology

Background. One discipline’s drawing used as the underlay for another’s. The mechanical engineer draws on an architectural background. Background currency is the single largest driver of coordination failure.

Hard clash. Two solid elements occupying the same space.

Soft clash. An element violating another’s required clearance envelope without physically touching it.

Installation clearance. Space required to get an element into position, as distinct from the space the finished element occupies.

Parameter mismatch. A numerical or descriptive attribute stated differently in two disciplines’ documents. Weights, voltages, loads, airflows, capacities, temperatures.

Datum. The reference elevation from which all vertical dimensions are measured. Divergent datums produce systematic, whole-building errors.

Coordination density. The concentration of elements from multiple disciplines within a given zone. High-density zones generate disproportionate findings.

Closed sequence loop. A drawn condition requiring trade A to precede trade B and trade B to precede trade A.

Stale background propagation. A revision to one discipline that is not reflected in the backgrounds other disciplines are drawing on, so the error spreads across the set.

Objectives

Recognize each issue type by its mechanism rather than by intuition

Direct review attention toward high-density zones instead of spreading it evenly

Write coordination comments that both affected consultants can act on

Distinguish issues resolvable by model coordination from those that are not, since most teams over-rely on the model

Understand the root causes well enough to prevent recurrence rather than only catch instances

Why Coordination Issues Are Structurally Inevitable

It is worth understanding the production process, because it explains the defect pattern and it tells you when to look.

A commercial building is designed by four to twelve separate entities under separate contracts. The architect holds coordination responsibility in most arrangements, but holds no authority over the consultants’ internal workflows and limited visibility into their working files. Each consultant works on its own schedule, publishes at milestones, and receives others’ work as backgrounds that are current as of publication rather than current as of now.

Four consequences follow directly, and they account for most of what a review finds.

Asynchronous currency. At any moment, each discipline is working from a snapshot of the others taken at different times. A change made Tuesday reaches other disciplines at the next background exchange, which may be three weeks out.

Discipline-siloed quality control. Each firm reviews its own work. Very few design teams have anyone whose job is to check across the boundary, and the ones who do usually assign it to a junior person late in the schedule.

Asymmetric information flow. Architecture publishes to everyone. Engineering publishes mostly to architecture. Structural rarely sees mechanical revisions directly. So a mechanical change reaches structural only if the architect notices it matters and forwards it, which requires the architect to know the structural implications of a mechanical change.

Compressed late-stage schedules. Coordination effort is needed most in the last third of construction documents and is available least, because that is when every discipline is finishing its own work.

Table 2. Root Causes and the Issue Types They Produce

The Twelve Coordination Issue Types

Table 3. Issue Types at a Glance

Seven of the twelve are not caught by model coordination, and they include the highest-severity types. That is the most important row in the table and the reason coordination cannot be delegated entirely to a clash detection process.

Issue 1: Spatial Interference

What it is. Two solid elements occupying the same space. Duct through beam, pipe through column, conduit through footing.

Mechanism. Almost always stale backgrounds, or two disciplines routing independently through the same congested zone without a coordination pass.

Where it concentrates. Corridor plenums, mechanical room ceilings, shaft walls, and anywhere trunk distribution crosses primary structure.

Cost. Individually modest and highly variable. In aggregate, large, and disproportionately schedule-driving because resolution usually requires a design decision rather than a field adjustment.

How to catch it. Model coordination handles this well and it is the one type where a clash detection process is genuinely sufficient. Where no model exists, overlay printed or PDF plans by zone and check trunk routing against primary structure.

Issue 2: Insufficient Installation Clearance

What it is. Space adequate for the finished element and inadequate for getting it there. A duct that fits the plenum by half an inch cannot be lifted into position. A pump that fits its housekeeping pad cannot be carried through the door drawn for the room.

Mechanism. Design represents the completed condition. Nothing in a drawing set or a model represents the swept volume required during installation.

Where it concentrates. Equipment rooms, ceiling plenums with tight structure, shafts, elevator machine rooms, and any space entered through a door narrower than its largest contained element.

Cost. High when discovered late, because the resolution is often to remove permanent construction. Cutting an opening in a completed masonry wall to admit a chiller is a real event that happens on real projects.

How to catch it. A rigging and delivery path review, done by a superintendent, tracing each major piece of equipment from the loading point to its final position. Ask whether the swept volume clears at every door, corner, and elevation change. This is a half-day exercise on a mid-size commercial project and it finds things nothing else finds.

Table 4. Issue 2, Recurring Conditions

Issue 3: Datum and Elevation Divergence

What it is. Disciplines measuring vertical dimensions from different references. Architectural finished floor versus structural top of slab is the classic pair, differing by the finish assembly thickness.

Mechanism. Different conventions, compounded when a datum is revised and not propagated. Civil adds a third convention, since site elevations typically use a survey datum rather than a building datum.

Where it concentrates. Everywhere at once, which is what makes it dangerous. This is a systematic error rather than a local one.

Cost. Potentially very high, because it affects every vertical dimension in the set. Discovered during structural coordination it is an annotation exercise. Discovered after slab placement, it is not.

How to catch it. Explicitly reconcile the datum statement on every discipline’s general notes at the first review. Confirm that architectural finished floor, structural top of slab, mechanical and plumbing invert references, and civil site elevations all relate through stated, consistent offsets. Then spot-check three or four specific elevations across disciplines to confirm the stated relationship actually holds in the drawn dimensions.

Issue 4: Grid and Dimensional Divergence

What it is. Gridlines at different spacings, differently labeled, or dimension strings that do not agree between disciplines.

Mechanism. A grid revision propagated to some disciplines and not others, or a consultant working from a background predating the change.

Where it concentrates. Perimeter conditions, areas revised late in design, and buildings with irregular geometry where grids shift between levels.

Cost. High, because layout depends on it. Field layout from a divergent grid produces installed work in the wrong place.

How to catch it. Overlay gridlines from every discipline for each level and confirm identity. This is fast, mechanical, and finds a systematic problem when it exists. Also confirm grid labels match, because relabeled grids produce coordination failures even when spacing is identical.

Issue 5: Parameter Mismatch

What it is. A numerical or descriptive attribute stated differently in two disciplines’ documents. This is the type model coordination cannot see at all, and it is where the highest-severity findings tend to live.

Mechanism. A value changes in one discipline late in design and does not propagate. Equipment gets resized, loads get recalculated, a system gets rezoned, and the downstream discipline never learns.

Where it concentrates. Equipment schedules and their consumers.

Table 5. Issue 5, Parameter Pairs to Reconcile

How to catch it. Take each pair in that table, retrieve both values, and compare. This is a reading exercise rather than a geometric one, and it is the single highest-value coordination check available. On any set produced by more than three firms, expect findings.

Issue 6: Stale Background Propagation

What it is. A discipline drew on a superseded underlay, so its entire sheet is coordinated to a building that no longer exists.

Mechanism. Background exchange lag combined with a significant revision.

Where it concentrates. Whichever areas were revised. The tell is a cluster of unrelated conflicts in one zone, all of which resolve if you assume one discipline is working from an older version.

Cost. Variable and often high, because it is many conflicts with one cause and each gets logged and resolved separately if nobody spots the pattern.

How to catch it. Review coordination findings as a batch by zone rather than individually. When ten findings in one area all point the same direction, stop writing comments and ask which background that discipline used. Then request a coordinated reissue rather than ten individual corrections. This distinction is worth real time: ten comments produce ten responses and probably three new conflicts. One background question produces a coordinated sheet.

Issue 7: Rated Assembly and Penetration Coordination Failure

What it is. Penetrations of fire-rated or smoke-rated construction that are not coordinated with the protection the rating requires. Ductwork through a rated wall without a damper. Cable tray through a shaft without a firestop detail. A rated corridor whose assembly does not continue to structure above.

Mechanism. Rating information lives in the architectural set and the life safety plans. Penetrations live in the engineering sets. Nobody’s discipline covers the intersection, and the specification for firestopping sits in a division none of the penetrating trades read.

Where it concentrates. Corridor walls, shaft walls, stair enclosures, exit passageways, smoke barriers, and the horizontal assemblies at floor penetrations.

Cost. High severity rather than high frequency, because rated construction is inspected and inspection gates occupancy. This is a schedule risk category.

How to catch it. A dedicated consolidation pass: take the life safety plans as the base, overlay every discipline’s penetrations of every rated assembly, and confirm each has a protection method shown or specified. Then confirm rated assembly continuity to structure, including head-of-wall conditions above accessible ceilings, which is where continuity most often fails.

Issue 8: Opening and Penetration Mismatch

What it is. The opening provided does not match what passes through it. A sleeve too small for the pipe plus its insulation. A slab opening in the wrong location. A masonry opening that does not accommodate the duct plus its lining and required clearance.

Mechanism. One discipline sizes for the bare element and another for the assembled element with insulation, lining, and clearance. Or a routing revision moved the element and not the opening.

Where it concentrates. Slab penetrations, shaft wall penetrations, foundation wall penetrations, and rated assembly penetrations where the protection device itself needs space.

Cost. Moderate individually. High when the opening is in placed concrete, because the resolution is coring, and coring near reinforcement requires structural engagement.

How to catch it. For each penetration schedule, confirm the opening dimension against the element outside diameter plus insulation plus required annular space plus the protection device. Then confirm location against the current routing rather than the routing on the background.

Issue 9: Ceiling Plane Congestion

What it is. More elements assigned to one plane than the plane can hold. Reflected ceiling plans concentrate lights, diffusers, sprinkler heads, speakers, detectors, access panels, and specialty devices from five or six disciplines onto a single surface.

Mechanism. Each discipline places its elements on its own drawing. Only the reflected ceiling plan shows them together, and it is typically produced by the architect from backgrounds of varying currency.

Where it concentrates. Corridors, lobbies, and any area with a symmetrical grid pattern where alignment matters visually as well as functionally.

Cost. Moderate cost, high visibility, and high rework probability, because the finished ceiling is what the owner looks at.

How to catch it. Overlay every discipline’s ceiling-mounted elements against the reflected ceiling plan and against each other. Check both conflict and alignment, since a sprinkler head 4 inches off the tile center is not a clash and will still be rejected. Verify that fixture types are compatible with the ceiling types they occur in, which is a separate and frequently missed check.

Issue 10: Service and Maintenance Clearance Failure

What it is. No space to operate, service, or replace equipment after construction. Valve handles against walls. Filter access blocked by piping. Electrical working clearance occupied by ductwork. Coil pull space unavailable.

Mechanism. Clearance requirements are stated in specifications and codes rather than drawn as geometry, so nothing in the coordination process represents them unless somebody models clearance envelopes deliberately.

Where it concentrates. Mechanical and electrical rooms, above accessible ceilings, and equipment yards.

Cost. Frequently absorbed as an operational nuisance, which is why it recurs. Where code working clearance is violated it becomes an inspection issue with occupancy implications.

How to catch it. Model clearance envelopes where you have a model, and where you do not, walk the equipment rooms on paper with a superintendent asking how each device gets serviced and how it eventually gets replaced. Electrical working clearance is a code requirement and deserves an explicit check.

Issue 11: Sequence Conflict

What it is. A drawn condition that cannot be built in any valid order. Trade A must precede trade B and trade B must precede trade A.

Mechanism. Design represents a completed state. Nothing in the documents or the model represents the order of assembly.

Where it concentrates. Congested plenums, shaft walls, exterior wall assemblies with multiple layers and embedded elements, and anywhere concealed structure must support systems installed after the concealment.

Cost. High schedule impact. Resolution during construction usually means either a design change or a sequence workaround with added labor.

How to catch it. This one requires people, not tools. Walk the congested zones with a superintendent and the relevant trade foremen and ask two questions repeatedly. What has to be finished before you can start? And can your work be installed after the thing that conceals it? Closed loops become obvious in minutes to the people who install the work and are essentially invisible to anyone else.

Issue 12: Interface and Transition Detail Failure

What it is. The boundary between two systems is detailed by neither consultant, or detailed by both differently. Curtain wall to roof. Slab edge to exterior wall. Rated wall to structural deck. Existing construction to new.

Mechanism. Each consultant details up to its scope boundary and stops. The transition belongs to the architect in principle, and in practice it belongs to whoever notices.

Where it concentrates. Exterior wall transitions, roof edges and penetrations, below-grade waterproofing terminations, expansion joints, and every interface with existing construction on renovation work.

Cost. High, and disproportionately associated with water intrusion, which is the most expensive defect category in commercial building over the life of the asset.

How to catch it. Trace continuity of each control layer, meaning water, air, thermal, and vapor, around the entire building envelope, through every transition, and confirm a detail exists at each. Where a detail exists, confirm it is buildable in sequence. This is the most productive review activity on the building envelope and it is regularly skipped because it crosses every discipline boundary at once.

Coordination Density: Where to Concentrate

Coordination issues are not uniformly distributed. A small proportion of a building’s volume generates most of the findings, and reviewer attention should follow.

Table 6. Coordination Hot Spots by Density and Severity

Two zones deserve emphasis for opposite reasons. Corridor plenums have the highest density and are where most teams already look, because that is where clash detection reports concentrate. Exterior wall transitions have only moderate density and the highest long-term severity, and almost nobody reviews them systematically, because the review requires tracing continuity across every discipline rather than examining a congested volume.

Detection by Method

Table 7. Issue Types Against Detection Methods

The pattern is worth stating plainly. Model coordination is excellent at exactly one issue type and good at one more. Field and trade walkthroughs are the only reliable method for two of the highest-cost types. Parameter reading is the only method for the type with the worst late-discovery profile. A coordination process built only on clash detection covers a small fraction of the territory while feeling thorough, which is the most dangerous combination available.

Stakeholders

Table 8. Coordination Issue Detection Responsibility

The distribution matters. Four of the twelve are best caught by field people, three by parameter readers, and only three primarily by VDC. Organizations that assign coordination review entirely to VDC are structurally covering a quarter of the taxonomy.

Required Documentation

Table 9. Documents Required to Find Coordination Issues

Technology Integration and Its Limits

Table 10. Coordination Technology and Coverage

Two honest observations. First, no combination of tools covers Issue 11, sequence conflict, and Issue 12, interface details, both of which carry high cost. Those require experienced people looking deliberately. Second, model coordination’s coverage is narrower than its prominence in industry conversation suggests, and teams routinely conclude a project is coordinated because the clash report is clean.

AI-Assisted Opportunities

The coordination type that automation genuinely addresses is Issue 5, parameter mismatch, and it does so decisively. Reconciling equipment weights against structural design loads, voltages against panel schedules, connected loads against service capacity, and airflows against duct sizing is a reading and comparison exercise across hundreds of schedule rows spread across four or five disciplines. It is the type with the worst late-discovery profile and the one no model catches, and it is a volume problem.

Platforms that index construction documents and support direct interrogation, iFieldSmart AI among them, make this practical. A reviewer asks where equipment weights appear across all disciplines, or which equipment schedule entries state voltages that do not appear in any panel schedule, or which rated assemblies have penetrations shown on engineering drawings, and gets a sourced answer linked back to the sheet location. The same capability supports Issue 6 by differencing revisions to identify what changed and which disciplines’ backgrounds predate it.

Table 11. AI Use Case Matrix for Coordination

Implementation

Inquire with the design team about how and when backgrounds are interchange. It helps you identify the focus areas for issue types 1, 3, 4, 6, 8, and 9, and helps you schedule your review for shortly after a background interchange.

Run the parameter reconciliation from Table 5 at design development and again at 90 percent construction documents. An hour or two per pair, and it addresses the type with the worst discovery profile.

Reconcile datums and grids once, early. Both are systematic errors and both are cheap to check.

Schedule the trade walkthrough for the hot spots in Table 6 rather than for the building. Corridor plenums, mechanical rooms, shafts, roof, and any lab or kitchen. Half a day with a superintendent and three foremen.

Run the rated assembly consolidation pass with the life safety plans as the base. This is the highest-severity type and nobody’s discipline owns it.

Trace envelope control layer continuity through every transition. Assign it to someone with envelope experience, or engage a consultant on projects where water intrusion exposure justifies it.

Batch findings by zone before writing comments, so stale background patterns get caught as one issue rather than ten.

At closeout, categorize every coordination-driven change order by issue type. The distribution tells you which check to strengthen, and it is usually not the one people expect.

Table 12. Implementation Roadmap

Best Practices

Table 13. Coordination Review Best Practices

Common Mistakes

Table 14. Common Failures in Coordination Review

How These Issues Appear Across Sectors

Class A office tower, 340,000 square feet, core and shell. Most common form of Issue 5. Rooftop unit weights increased through design development and the penthouse framing still reflected the earlier schedule. One hour reconciling equipment schedules against structural general notes found it. After fabrication release it becomes a long-lead schedule event, and on a core and shell project with a signed anchor tenant that is the worst category of delay.

Regional hospital expansion, 190 beds, occupied campus. Combining Issues 7 and 12. The rated corridor assemblies included mechanical penetrations missing dampers on two levels and did not provide a detail to ensure the smoke barrier continues through the connector at the interface between the new construction and the existing building. Healthcare concentrates Issue 7 because rated compartmentation is dense and inspected rigorously, and both findings gated occupancy rather than cost.

Hyperscale data center, 60 MW. Issues 5 and 10. Connected loads on mechanical equipment schedules did not reconcile with electrical panel schedules across roughly a dozen units, and electrical room cooling had been sized against an earlier heat rejection figure. Separately, working clearance in front of switchgear was occupied by overhead piping in three rooms. At data center density, both types compound.

Advanced manufacturing facility, food grade. Issue 11, a textbook closed loop. The hygienic wall panel system required installation before overhead process piping, and the piping needed support from structure the panels concealed. Invisible in the model, invisible on paper, obvious to the panel installer in about four minutes. Sequence conflicts are why trade walkthroughs cannot be replaced.

University science building, 11 floors. Issues 1, 5, and 10 in laboratory zones. Lab spaces converge more disciplines per square foot than anything else in commercial construction, and this set had fume hood exhaust conflicting with structure, makeup air quantities inconsistent between the mechanical schedules and the lab equipment documents, and no service access to valves above the ceiling in two lab modules.

Multifamily podium, 240 units. Issue 6, with the multiplier that makes residential distinctive. Two unit type plans were revised by addendum and the mechanical and electrical sheets continued from the earlier background, so every instance of those two unit types carried the same set of conflicts. On repetitive work a single stale background error multiplies by the unit count, which makes revision propagation checking unusually valuable.

Highway interchange, design-bid-build. Issues 3 and 8. Signal conduit depths conflicted with drainage structure inverts, and the underlying cause was a datum inconsistency between the civil survey datum and the structural drawings for the retaining walls. Infrastructure work concentrates datum problems because survey and structural conventions differ by default.

Historic warehouse conversion to hotel, 140 keys. Issues 3, 8, and 12, which is the standard adaptive reuse profile. Record drawing elevations differed from field-measured conditions by three inches in one structural bay, penetrations through existing masonry had been located from the record drawings, and the interface between the new envelope and the retained facade had no detail for water management. Source-end types of renovation work combine every interface type, thus field verification must be conducted during coordination verification.

Frequently Asked Questions

Who Handles Project Coordination in Construction?

Design coordination among consultants is generally the architect’s responsibility under most standard agreements, and construction coordination among trades is the contractor’s. In practice, the contractor’s review finds design coordination issues the design team missed, and reporting them is both a contractual duty in most forms and plainly in the contractor’s interest. Reporting a condition is different from directing a solution, and keeping that line clear matters legally as well as diplomatically.

Does BIM coordination solve coordination issues?

It solves one of the twelve types thoroughly and one more partially. Spatial interference is genuinely well handled by a federated model, and that is real value. Parameter mismatch, rated assembly penetrations, sequence conflicts, and interface details are entirely outside what geometry represents, and those four include the highest-severity types. A clean clash report is evidence about geometry and about nothing else.

Which coordination issue costs the most?

Issue 12, interface and transition details, has the highest cost over the life of the building, because it drives water intrusion, which is the most expensive commercial building defect category. Issue 5, parameter mismatch, has the worst late-discovery profile, because equipment weight and load errors surface after fabrication or procurement. Issue 11, sequence conflict, generates the largest work scheduling issues. Given the nature of the issues, different metrics may provide different answers. Thus, the taxonomy is a more valuable tool than a single ranking in this case.

When should coordination review happen?

Design development for issues 3,4,5,11, and 12, as the changes there affect design not price. Ninety percent construction documents for the comprehensive pass across all twelve. Then difference every subsequent addendum, because revisions issued to fix one condition create new coordination conflicts often enough that it should be routine.

How do I know a discipline is working from a stale background?

The signature is a cluster of unrelated conflicts in one zone that all resolve if you assume one discipline is working from an older version. When you see that pattern, stop writing individual comments and ask which background that discipline used and on what date. It is a much better question than ten comments, and it produces a coordinated sheet instead of ten patches.

What is the difference between a hard clash and a coordination issue?

A hard clash is one type of coordination issue, specifically Issue 1. The broader category includes conflicts with no geometric expression at all: a voltage mismatch between two schedules is a coordination issue and can never be a clash. Treating the two terms as synonyms is the main reason teams overestimate their coordination coverage.

Who should attend a coordination review walkthrough?

A superintendent leading, plus foremen from mechanical, electrical, and whichever trade dominates the congested zones, which is usually sheet metal. Add fire protection where ceilings are tight and add the panel or envelope installer where the exterior wall is complex. Four to six people, half a day, with a defined zone list rather than an open invitation to comment.

How many coordination findings should a review produce?

It varies too much by set maturity and delivery method for a firm number, but the distribution is more diagnostic than the total. If nearly all your findings are Issue 1, your process is a clash detection process rather than a coordination process, and seven types are going unexamined regardless of how many clashes you found.

How should coordination comments be written?

State the condition, cite both disciplines’ sheets, and address it to both consultants plus the coordinating architect. “M-301 shows RTU-4 at 4,200 lb operating weight; S-201 general note 6 states roof framing designed for 2,800 lb maximum unit weight at this location. Please confirm which governs and advise.” That is actionable. A comment to one consultant alone gets a response that fixes one side.

Does the model or the drawing govern when they disagree?

Whatever the contract documents say, and it is worth checking rather than assuming, because practice varies. Many projects still designate the published two-dimensional sheets as the contract documents with the model provided for coordination and information only. Others give the model contractual status. The answer changes what a model-to-drawing divergence means, so establish it early.

How does coordination review differ on renovation work?

Existing conditions become the dominant variable. Record drawings are frequently wrong, so field verification belongs inside the coordination process rather than after it, and issues 3, 8, and 12 all spike. On adaptive reuse I would spend the first day of coordination review measuring rather than reading, because every subsequent finding depends on whether the existing dimensions are what the documents claim.

What single change most improves coordination outcomes?

Reconciling parameters at design development, from Table 5. It costs a few hours, it addresses the type no model catches, and it catches errors while they are still design decisions. If you want a second, it is timing your review to just after a background exchange rather than just before, which costs nothing at all and changes what you are looking at.

Expert Recommendations

For the VDC or BIM manager: publish the coordination density map to the whole team before review. The rest of the organization does not know which zones concentrate findings, and you are the only person who does.

For the preconstruction manager: own the parameter reconciliation. It is a reading exercise across schedules, it does not require modeling skill, and it addresses the type with the worst late-discovery profile in commercial construction.

For the superintendent: lead the hot spot walkthrough with an agenda and a zone list. Ask two questions repeatedly. How would your crew install this? And what has to be finished before you can start?

For the project manager: run the rated assembly consolidation pass yourself or assign it explicitly. It is the highest-severity type, no discipline owns the intersection, and it gates occupancy rather than payment.

For the project engineer: reconcile datums and grids in the first week you have the set. Two systematic error types, both cheap to check, both catastrophic if they survive to layout.

For the project executive: ask what proportion of your coordination findings are hard clashes. If the answer is most of them, your organization is running a clash detection process and calling it coordination, and seven issue types are unexamined on every project.

For the owner or owner’s representative: ask how often the design consultants exchange backgrounds. It is an unusual question and the answer tells you more about the coordination quality you will receive than any progress report will.

Where the Taxonomy Leaves You

Coordination issues look like a series of unrelated surprises and they are not. Twelve mechanisms, each with a predictable cause, each concentrating in identifiable zones, and each detectable by a specific method. Five of the twelve trace largely to one root cause, which is a discipline working from information that changed after they received it.

The reason coordination review produces such uneven results across the industry is that the dominant tool addresses one issue type extremely well. That creates a false sense of completeness, and it directs attention toward congested volumes and away from schedules, life safety plans, envelope transitions, and installation sequence, which is where the expensive findings live.

Start by categorizing your last three projects’ coordination change orders against these twelve types. Almost every team that runs that exercise finds the distribution is not what they assumed, and that the type costing them the most is one they were not checking for at all.