Who Is Responsible for Coordinating Consultant Drawings — the Architect or the Owner's Consultants?

The coordination question is really a liability question — and the answer is in your contract, not your org chart

It usually surfaces at 90% CDs: a beam from structural clashes with a duct run, the ceiling height won't hold, and the question that decides whose fee absorbs the rework is 'whose job was it to catch this?' The instinct is to answer by discipline — 'the architect coordinates everyone.' That instinct is wrong, and acting on it can quietly pull professional-liability exposure onto your firm that your contract never assigned to you. Who is responsible for coordinating consultant drawings is determined by who holds the consultant's contract. There are two fundamentally different structures, and they allocate coordination duty — and the liability that rides with it — to different parties. Before you spend another billable hour reconciling someone else's drawings, confirm which structure you're actually in. The phase pressure is real, but absorbing coordination you didn't contract for is how firms erode margin and expand their standard of care without realizing it.

Architect-led (prime/sub structure): the architect coordinates and carries it

In the most common structure, the architect is the prime design professional and retains the engineering and specialty consultants — structural, MEP, civil, sometimes landscape and lighting — as the architect's own subconsultants. Their fees flow through the architect's contract; the owner sees one design team. Under this structure the coordination duty sits squarely with the architect. The architect's basic services include coordinating the design services of its consultants so the construction documents are reasonably consistent across disciplines, and the architect is responsible to the owner for that work product as if produced in-house. Practically, that means: - The architect runs interdisciplinary coordination — drawing overlays, clash checks, RFstyle conflict resolution — across its consultants. - The architect is accountable to the owner for consistency between the architectural drawings and the consultant drawings it commissioned. - The consultants' errors and omissions flow up: the architect carries first-line responsibility to the owner and pursues its own consultants under the subconsultant agreements. This is the default mental model most teams carry — and it's correct, but only when the architect actually holds the contracts.

Owner's separate consultants: coordination duty and liability shift away from the architect

The picture changes materially when the owner contracts directly with consultants — a geotechnical engineer, a code consultant, an existing-conditions surveyor, an owner's commissioning agent, or a separately retained civil or MEP firm. These are the owner's 'separate consultants,' and they are not the architect's subs. When the owner holds the contract, the owner — not the architect — owns the coordination and reliance chain for that scope: - The owner is responsible for furnishing the services and information produced by its separate consultants, in a timely manner and with reasonable accuracy. - The architect is generally entitled to rely on the accuracy and completeness of that information and is not obligated to independently verify it. - The architect incorporates the separate consultants' work into the documents; it does not guarantee, warrant, or assume responsibility for the adequacy of that work. The distinction that protects you is incorporate vs. guarantee. Pulling a survey datum or a code-consultant occupancy figure into your drawings is incorporation — a coordination act. Standing behind whether that datum or figure is correct is a guarantee — and on owner-held consultants, that guarantee is not yours unless you contract into it or assume it by conduct.

The AIA B101 language pattern that draws the line

The AIA B101 Owner–Architect Agreement is the standard reference because it codifies exactly this split, and most negotiated agreements echo its pattern even when they aren't B101 verbatim. Two language patterns do the work: - On the architect's consultants, B101 frames the architect's basic services as including coordination of the services of the consultants the architect retains, making the architect responsible to the owner for that coordinated design. - On the owner's side, B101 obligates the owner to furnish the services of its own consultants and the information they produce, and establishes that the architect may rely on that information's accuracy and completeness without a duty to verify it independently — i.e., the architect incorporates but does not guarantee. The practical test, regardless of which form you're on: trace the contract privity. Privity to the architect = the architect coordinates and is responsible. Privity to the owner = the owner coordinates and bears the reliance risk; the architect's duty is limited to reasonable incorporation. Caveat worth holding: edition language evolves and owner riders routinely rewrite these clauses — a rider can quietly push owner-consultant verification duties onto the architect, or name the architect as overall coordinator of the owner's separate consultants without a corresponding fee or limitation of liability. Read the executed agreement and its supplementary conditions; do not rely on the standard form from memory. This is general practice context, not legal advice — confirm allocations with your own counsel and PL carrier.

Where this lands in the deliverable chain — and how the principal should scope it

This is a principal-level scoping decision made before the agreement is signed, then enforced through the documents at every phase milestone: - SD/DD: Establish in the proposal and contract which consultants the architect retains and which the owner holds separately. Every owner-held consultant is a coordination interface you incorporate but don't guarantee — define the information handoff and timing for each in the agreement. - CDs: At each milestone set (50/90/100%), run coordination across the consultants you contract — that's your duty — and explicitly mark the boundary where owner-furnished information is incorporated by reference. Annotate drawings and the basis-of-design so the reliance boundary is legible to the contractor and the owner. - Liability hygiene: Confirm your PL exposure matches your coordination scope. If a rider names you as overall coordinator of the owner's separate consultants, scope the fee and the limitation of liability to match, or push the duty back to the owner. The deliverable that makes this defensible is a clean responsibility map: a single diagram showing each consultant, their contract privity, and the coordination/reliance boundary — circulated to the owner and updated as the team changes. When a clash surfaces at 90%, that diagram is what determines whose fee absorbs the rework, instead of a fee-eroding argument.