Handling client variations — without becoming the difficult one

Scope creep in architecture rarely arrives as a demand. It arrives as "could we just look at" — reasonable, small, and said by someone you want to keep working with. Twenty of those is a stage of unpaid work, and the practice that raises it at number twenty looks difficult, because it did not raise it at number one.

What is actually a variation

The test is not size and it is not effort. It is whether the work was in the agreed scope. Three specific patterns account for most of them:

• —**A revisited decision.** Something previously agreed is reopened. The original work was in scope; doing it again is not.
• —**An added element.** A new room, a new discipline, a second option to be developed rather than sketched.
• —**A changed constraint.** A different site boundary, a new authority requirement, a budget cut requiring redesign rather than specification change.

Everything else — a longer meeting, a difficult conversation, a slow response — is the cost of doing business and should be priced into the fee rather than claimed.

The sentence that makes this easy

Put this in the appointment, in the client's language, at signing: *"Design work following a change to previously agreed decisions is charged additionally, at the rates in Appendix X. We will tell you before we start."*

The value is not the clause. It is that you have said it once, calmly, at a moment when nothing is at stake — so raising it later is a reminder rather than a confrontation.

Say it before the work, always

A variation claimed after the work is done reads as a bill for something the client thought was free. The same variation flagged before — "happy to explore that; it's outside the current stage, so I'll send a short note on the additional fee before we start" — is a normal professional exchange, and clients accept it far more often than practices expect.

Practices consistently over-estimate how badly this lands. In our experience the client who says no simply proceeds without the change, which is also a good outcome: you have just avoided doing unpaid work.

Record it even when you do not bill it

This is the part almost nobody does, and it is the highest-value habit in the article. When you decide to absorb a change — and you will, often, for good reasons — log it anyway, with a rough hours figure.

At year end that log tells you which clients and which project types consume unbilled effort, and by how much. That is not a debt-collection exercise. It is a pricing input for the next appointment, and it turns "they're a bit demanding" into a number you can put in a fee.

Attach the variation to the record

A variation is an instruction, and like any instruction it needs a date, an author and the drawings it affects. Kept in the project rather than in a mailbox, it is also the evidence for the final account. See getting client approvals in writing.