SOP Management & Workflow Documentation3 min readUpdated September 2026

Design-Phase Gates That Catch Coordination Clashes Early

A design-phase gate is a checklist at each phase transition that requires open items, such as code questions, consultant clash checks and written client approval, to be confirmed before work continues. Without one, an unresolved code question can resurface at permit review, and a beam location can conflict with the structural engineer's drawings once construction documents are underway.

Architecture firms already work in phases with natural checkpoints, schematic design, design development, construction documents. The firms that avoid these problems treat each phase transition as a gate that requires specific items to be confirmed before work proceeds, not just a calendar milestone.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Gating Schematic Design Before Design Development Starts

Moving into design development with an unresolved zoning question, an unconfirmed code path, or a client approval that was verbal but never documented sets the whole next phase on an assumption that might not hold. A checklist requiring each of those items to be explicitly confirmed, with the confirmation attached rather than remembered, before design development begins prevents the team from building on a foundation that shifts later.

This is also the point to confirm the client has actually seen and approved the schematic direction in writing, not just nodded along in a meeting. A verbal approval that a client later disputes is an expensive argument to have once design development work is already underway, and it is far easier to resolve before real fee has gone into the next phase than after. A brief, specific follow-up costs a few minutes; unwinding a phase's worth of work built on a misunderstood approval costs a great deal more, in both fee and trust with a client who is now questioning the whole engagement.

A gate checklist for the move into design development should confirm that:

  • Any open zoning question is resolved and the answer is documented, not assumed by whoever last discussed it.
  • The code path is confirmed in writing, with the confirmation attached to the project record.
  • The client has approved the schematic direction in writing, with the approved materials attached rather than a verbal nod from a meeting.
  • A documented overlay or clash check against the consultants' latest drawings is complete, with any conflict logged and assigned an owner.

Running a Real Consultant Coordination Check, Not an Assumed One

Structural, mechanical, and electrical consultants each update their own drawings on their own schedule, and assuming everything still lines up because it did at the last coordination meeting is how a beam and a duct end up wanting the same space. A checklist requiring a documented overlay or clash check at each phase transition, with any conflict logged and assigned an owner, catches this before it reaches construction documents, where fixing it costs far more in redrawn sheets and consultant fees.

Require the check to happen against the current drawings, dated, not against whichever version happened to be the latest one someone had open. Note the exact drawing version each consultant was working from at the time of the check, so a later dispute about whose version was current has an actual, documented answer rather than two competing memories of the same meeting.

Confirming Code Compliance Before It's a Permit Rejection

A code question that seems minor early on, an egress path, an accessibility clearance, an occupancy classification, can force a significant redesign if it surfaces for the first time during permit review. A checklist requiring a documented code-compliance confirmation at each phase gate, covering the specific items most likely to be missed for that project type, catches the question while it's still cheap to answer.

Assign this check to someone other than the project architect who's been immersed in the design, since a person close to the work is more likely to see what they intended rather than what's actually on the sheet.

Getting Client Sign-Off in a Form That Actually Holds Up

A client who approves a design direction in a meeting, then asks for a significant change two weeks later, creates a dispute about whether that change is a revision within scope or a change order. A checklist requiring a specific, documented sign-off at each phase gate, with the approved materials attached, gives the firm a clear record of what was actually approved and when, rather than a memory of a conversation that both sides now remember differently.

What a Late-Discovered Clash Actually Costs a Firm

A commercial architecture practice runs on fee structures that assume a design proceeds roughly as planned through each phase, and an operations lead senior enough to own phase-gate discipline and consultant coordination across active projects is a real position, not a task added to a project architect's plate. National pay for that kind of operations role spans roughly $50,090 to $253,390, with a median near $105,7701, and a firm that avoids even one significant late-stage redesign in a year has usually already paid for that role several times over.

Executive Capability Standard

What Good Looks Like

A disciplined architecture firm requires a documented code-compliance confirmation, a consultant coordination check, and a specific client sign-off at every phase gate, so nothing carries forward on an assumption that turns out to be wrong.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Review the last several projects for any code issue or consultant clash discovered late, and trace each back to the phase gate that should have caught it.
2. Do Manually:Rely on the project architect to informally confirm code compliance and consultant coordination before moving to the next phase.
3. Delegate:Assign a QC principal to review and sign off on every phase-gate checklist across active projects, separate from the project architect.
4. Automate:Run phase-gate confirmation, consultant coordination checks, and client sign-off as tracked workflows that block the next phase until each is complete.
5. Buy:Connect the coordination-check workflow to your BIM model version history so a clash check runs against the current drawings automatically rather than a version someone remembered to pull.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Process Street

Use it to gate schematic design, design development, and construction documents behind documented code-compliance and coordination checks.

Visit Process Street→
Every

Use it to keep contractor and consultant payments organized across active projects.

Visit Every→

Frequently Asked Questions

Who should sign off on a phase-gate checklist, the project architect or a principal?

The project architect should complete it, since they know the project, but someone with less day-to-day investment in the design, a principal or a QC lead, should confirm it before the next phase begins. That separation catches what a person close to the work tends to overlook.

How often should a consultant coordination check run?

At minimum, at every phase gate, but a project with a compressed schedule or a complex structural and mechanical scope may need it more often. Base the frequency on how quickly the consultants' drawings are actually changing, not a fixed calendar interval that might be too slow for a fast-moving project.

What's the best way to document a verbal client approval?

Follow it with a written confirmation the same day, referencing the specific materials shown, and ask the client to acknowledge it rather than assuming silence means agreement. Build that follow-up into the phase-gate checklist itself so it isn't left to whoever remembers to send the email. A short summary email with the actual drawings attached, asking for a reply confirming approval, works better than a general recap that never specifies exactly what was shown.

Sources

Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.

  1. Annual wage, General and Operations Managers (SOC 11-1021), US all industries. BLS OEWS May 2025, 2025.

Related Guides