Two systems, one gate
The client sees the stage structure as a payment schedule: advance, working drawings, structural, MEP, supervision, closure. It is that. But the payment is the smaller half of what each gate does.
Every stage trigger is also a quality gate. The payment and the inspection are the same event because they check the same thing: that the work promised has actually been produced, at the level at which it can be built from. A client who understands this stops experiencing the stages as extraction and starts using them as control.
The gates, one by one
Take the advance gate. The client's payment releases the presentation drawings, and the inspection it performs is on the client's side: it verifies the project is real. The practice's recorded experience over thirty years is unambiguous here. The clients who hesitate at the advance are, with striking regularity, the clients whose projects do not finish; a practice that works without advances builds a portfolio of half-finished drawings for people who were never building anything. The gate protects the serious client most of all, because his project is not queued behind somebody's fantasy.
The working-drawings gate releases the construction set, and its inspection is one any client can perform: hand the set to his contractor before paying and ask what is missing. Does it answer every trade's questions, levels stated, dimensions at the wall, junctions detailed, as argued in [readable drawings](/journal/drawings-a-contractor-can- read/)? The structural and MEP gates then release the invisible correctness, load paths and beam sizing coordinated with the architecture, water, power, drainage. That inspection is usually outsourced trust, and it should not be: the client is entitled to drawings his engineer can check independently, and a practice that resists that check is telling him something.
Supervision works differently. Payment buys the visit schedule built into the fee, the drawing-against-site comparison walked in Two visits a week, and the gate is time-based rather than deliverable-based; its inspection is the visit itself. Closure releases the end state, the completed fixes, the handover, the documentation of the building as built, and its inspection is the client's own walk-through against the original brief.
What the gate system stops, in aggregate
Three failure modes, all recorded in district practice.
The drifting project: work continues without definitions until neither party can say what is included. Gates force definitions at fixed points.
The orphaned project. The trade reality, discussed plainly because every district architect knows it: a share of projects stall when a client stops paying mid-stream, and the drawings already delivered have already been used. The stage system is what makes that survivable rather than fatal: the practice loses a stage, not the practice. A client should read that the same way: pay to the stage, verify the stage, and neither party carries the other's risk.
The relationship collapse. Most client-architect disputes in the district are actually disputes about what was promised when. Gates convert memory into documents. Both parties sign at each stage; both remember the same project.
The full stage sequence and triggers are published on how we work, and the deliverables at each stage on what you receive.