Scope creep and the endless revision: price it, log it, stop it
Unpriced revisions are what cost you, and they arrive one reasonable request at a time. How to state what is included before it is tested, keep a variation log that turns an argument into arithmetic, and raise a fee without souring the relationship.
- Revisions aren't the problem. Unpriced revisions are, and so is the silence that lets them pile up.
- State the number of included rounds per stage in the appointment letter, before anyone has a reason to argue about it.
- Keep a variation log. It turns an argument about memory into a piece of arithmetic.
- Raise it at the request, never at the invoice. A charge that surfaces three months later reads as a penalty.
Nobody loses money on the fourth revision. They lose it on the fourteenth, having never mentioned the fourth. Scope creep in an architecture practice is almost never one outrageous demand. It's a long sequence of individually reasonable requests, each of which would have been petty to charge for, arriving over eight months until the project has eaten twice the hours it was priced at.
The client usually isn't being difficult. From where they sit each request is small, and the previous eleven were absorbed without comment, which they've quite reasonably read as those requests being normal. You taught them that. The answer isn't to become harder to work with; it's to make the boundary visible early, while drawing it still costs nothing.
Say what is included before it is tested
The appointment letter states the fee, the stages and the deliverables. Very few state how many revision rounds each stage includes, and that omission does most of the damage.
A round is one consolidated set of comments and one revised issue in response. Not one comment. Spell that out, because a client who sends four separate emails over a fortnight doesn't think of it as four rounds, and they aren't wrong to be confused if nobody told them.
| Stage | Included rounds | What a round means here |
|---|---|---|
| Concept design | 2 | One consolidated set of comments, one revised concept in response. |
| Preliminary design | 2 | Comments on the scheme, not a reopening of the concept. |
| Drawings for approval | 1 | Plus any revisions required by the sanctioning authority, at no charge. |
| Working drawings | 1 | Coordination changes arising from consultants are included; design changes are not. |
Authority-driven changes should always be free. They aren't the client's doing, and charging for them reads as opportunism.
Two things make this clause work rather than merely exist. It has to be generous enough to be credible: two concept rounds is a real allowance, whereas a client who reads "one round" will assume you intend to be difficult. And it has to distinguish between changing a decision and refining one. Moving a wall is refinement. Moving the staircase after the plan was signed off is a new decision.
What is a variation and what is just Tuesday
Not every request is a variation, and a practice that bills them all becomes exhausting to deal with. The test is whether the request changes a decision that was already made and paid for, or refines one that's still open.
| The request | Verdict |
|---|---|
| "Can the kitchen window be a bit wider?" during concept | Included. This is what the concept stage is for. |
| "Can we look at the whole thing with the entrance on the east?" after preliminary sign-off | Variation. A signed decision is being reopened. |
| The sanctioning authority requires a setback change | Included, and free. Not the client's doing. |
| "My brother-in-law is an engineer and has some thoughts" | Depends entirely on the thoughts. Judge the change, not its source. |
| "Could you also do the landscape?" | Additional services. A separate scope with its own fee, not a revision at all. |
| Third round of comments at concept, when two were included | Variation, but a small one. Often worth absorbing while noting it. |
That last row carries more weight than it looks. The point of this discipline isn't to bill every deviation, it's to know. A studio that absorbs the third round deliberately, having logged it, is in a completely different position from one that absorbs it because it never noticed. The first is being generous. The second is being drained.
The variation log
The log is small and it does one job: it converts an argument about what happened into a document about what happened. Date, request, who asked, which signed decision it changes, the hours, whether it's charged or absorbed, and the client's acknowledgement.
Keep it where the conversation is, not in a separate file nobody opens. If the back-and-forth about a drawing sits beside the drawing itself, in one thread per client, the log summarises a record that already exists instead of being a second thing to maintain. Where the discussion is scattered across WhatsApp, email and two phone calls, you'll be reconstructing it from memory, and memory is the thing the log was supposed to replace.
A variation log turns a disagreement about memory into a piece of arithmetic. Nobody argues with arithmetic for very long.
The three sentences
Most architects know when a request has crossed the line and say nothing, because the alternative feels like starting a fight over something minor. It doesn't have to. Three sentences, sent at the moment of the request rather than three months later on an invoice, do the whole job.
- Confirm you can do it. "Yes, we can move the staircase to the north wall." Lead with the answer they want. You aren't refusing anything.
- Name what it changes. "That reopens the preliminary plan, which was signed off on 14 April, and it will affect the structural grid." Factual, dated, no editorialising.
- State the consequence. "It's about twelve hours of work and roughly two weeks on the programme. Shall I send a variation note so we have it on record?"
That last question does the real work. You're not demanding a decision, you're offering to document one, and clients agree to variation notes far more readily than they agree to charges. The note is what makes the charge unarguable later.
Pricing the round that is not included
Two mechanisms cover almost everything. An hourly rate, stated in the appointment letter, for work that's genuinely incremental. And a percentage-of-cost fee for additional services that amount to a new scope, priced the way the main fee is priced.
What separates them is kind, not size. Redrawing a facade is incremental, however many hours it takes. Adding the landscape is a new scope even if it's small. Charge the second by the hour and it looks like a favour, and you'll find it hard to price properly. Charge the first as a percentage and you won't be able to justify it at all.
State the hourly rate up front, before there's any occasion to use it. A rate that appears in an appointment letter is a term. The same rate quoted for the first time in month seven, in response to a request, is a negotiation you will lose.
Then treat the variation like any other stage: the revised drawings go out when the variation is settled. If the revised set leaves first, you're back to chasing, which is the position the whole stage-wise schedule exists to keep you out of. Attaching an invoice to the revised set makes that automatic rather than something you have to remember to be firm about.
When to absorb it anyway
Sometimes the right answer is to do it for nothing, and a piece about scope creep that won't say so is dishonest. Absorb it when the change came from something you missed. Absorb it when it's trivial and the relationship is worth more than the hours. Absorb it when the client has been straightforward about fees all year and this is the first ask.
But log it either way, and say that you're absorbing it. "That's outside the two included rounds, but it's small and I'm not going to charge for it" costs you the same hours as saying nothing, and it buys something silence doesn't: the client now knows the boundary exists and that you chose not to enforce it. The next request arrives with that knowledge attached.
Write the allowance into the letter
Rounds per stage, what a round means, and sign-off before the next stage begins. Do this once and it protects every project after it.
Log every request, charged or not
Date, what it changes, hours, decision. The log's value is in its completeness, not in its billing.
Raise it in the moment, in three sentences
Yes, here's what it changes, here's the consequence, shall I document it. Never at invoice time.
Issue the revision when the variation is settled
Same discipline as the main fee. The drawing follows the money, not the other way round.
Review the log at each stage close
Absorbed hours are real hours. If a project has absorbed forty of them, you want to know that before you price the next one like it.
One habit underpins all five: having a single place where the conversation, the drawings and the invoices sit together. Scattered across three apps, reconstructing what was agreed is a half-day's work and you won't do it. In one place, the log almost writes itself. That's less a discipline problem than a question of what the practice runs on.
The conversation, kept with the work
AtelierLab keeps the back-and-forth about a drawing beside the drawing itself, in one ordered thread per client, alongside the invoices that release each set. One record of what was asked, what was agreed, and what it cost.
Questions, answered
The questions architects ask most about this, in plain language.
Ask us anythingTwo at concept, two at preliminary, one at approval stage and one at working drawings is a defensible allowance that most clients read as generous rather than restrictive. What matters more than the numbers is defining what a round is: one consolidated set of comments and one revised issue in response, not one comment. Authority-driven changes should sit outside the count and be made free, because they are not the client's doing.
State an hourly rate in the appointment letter, before there is any occasion to use it, and apply it to work that is genuinely incremental. Anything amounting to a new scope, such as adding landscape or interiors, should be priced as additional services on the same percentage-of-cost basis as your main fee rather than by the hour. Issue the revised drawings once the variation is settled, exactly as you would for a stage payment.
A revision refines a decision that is still open within the current scope. Additional services introduce work that was never in the scope at all: a new discipline like landscape or interiors, a second building, a feasibility study, or a submission the appointment never contemplated. The test is not how many hours it takes but whether the same job is being improved or a different job is being started, because the two are priced on completely different bases.
Raise it at the moment of the request rather than at invoice time, and lead with agreement. Confirm you can do it, name the signed decision it changes and the date it was signed, state the hours and the programme effect, then offer to send a variation note for the record. You are documenting a decision rather than demanding one, and clients agree to notes far more readily than to charges. The same words at the end of a stage read as an ambush.
This is what the log and the sign-offs are for. If each stage was signed off before the next began, and every request was recorded with its date and what it changed, the question becomes a comparison of documents rather than a contest of recollections. Where you have no record you will usually lose the argument regardless of who is right, which is the strongest practical case for keeping the log even on the requests you intend to absorb.