How to structure architect fees by stage — and get paid on time

Architects bill by stage because the work arrives in stages: nobody can price detailed design before concept is agreed, and nobody should be asked to. The instrument is old, well understood, and — in most small practices — applied so loosely that the firm becomes its own worst debtor.

This is the practical version: how much of the fee each stage carries, what actually triggers the invoice, and the two mistakes that turn a stage fee into an argument.

What a stage fee is meant to do

A stage fee does three things at once, and the reason it goes wrong is that most practices only remember the first. It prices the work. It caps the practice's exposure if the project stops. And it defines what has to exist before the client owes money.

That third one is the whole game. If "concept design" is not a defined set of deliverables, then the end of concept design is a matter of opinion, and an invoice raised against an opinion is an invoice that gets queried.

A workable split

The first mistake: a stage with no deliverable list

If the appointment says "Stage 2 — Design Development, 25%" and nothing else, then Stage 2 ends when the client agrees it has ended. That is not a fee structure, it is a negotiation scheduled for a date when you have already done the work.

The fix costs one paragraph per stage in the appointment: the drawings issued, the documents produced, and the decision the client is asked to make. When the last item on that list is issued, the stage is complete and the invoice is a fact rather than a proposal. The design stages, and why your software should know them sets out the sequence in full.

The second mistake: no record of the approval

The stage ends on the client's acceptance. In most practices that acceptance happens in a meeting, gets confirmed in an email that is later buried, and is remembered differently by the two parties four months on when the client asks why they are paying for a revision to something "we never signed off".

A dated approval attached to the exact revision it approved ends that conversation in thirty seconds. It does not need software to exist — an email with the drawing numbers and revision letters in it is a record. It needs somebody to have decided that it is required. See getting client approvals in writing.

Bill the stage, not the calendar

Practices that invoice monthly regardless of progress train their clients to treat the invoice as a subscription and query it accordingly. Practices that invoice on stage completion get paid for events the client can see. The exception, again, is construction administration, where the event genuinely is the passage of time.

What this looks like when it is running properly

• —Every project carries its stages and the fee instalment attached to each
• —Every stage carries the deliverables it owes
• —A stage closes on a recorded approval, not on somebody's judgement
• —Closing the stage raises the receivable — the invoice does not depend on anyone remembering
• —The practice can see, today, how much fee is earned and unbilled across every live project

That last line is the one most practices cannot answer, and it is the number that decides whether the firm is short of cash or short of invoicing discipline. It is also, straightforwardly, why architecture practice management software exists as a category: a spreadsheet can hold the fee, but it cannot notice that a stage closed three weeks ago and nobody billed it.