Getting client approvals in writing — without making the client do paperwork

Every practice has lived it: the client approved the scheme in a meeting, the practice detailed it for six weeks, and then — with technical design nearly complete — the client "never liked the staircase". Without a written approval, the redesign is free, because the alternative is a fight with a client who still owes you the rest of the fee. Approvals are not administration; they are the fee's bodyguard.

Why practices don't get approvals in writing

Because asking feels adversarial, and because the mechanics are awkward. Email approval buries the decision in a thread; printed sign-off sheets make a design meeting feel like a mortgage closing; and chasing a busy client for a signature four times erodes exactly the relationship the approval is meant to protect. The problem is not willingness — it is friction.

What a working approval flow looks like

1. 1The practice presents a decision as a package: the drawings, the visual, the one-line question — "approve concept for development".
2. 2The client opens a link, sees exactly what they are approving, and clicks approve or requests changes — no login ceremony, no printing.
3. 3The decision is timestamped against the drawing REVISIONS it covered, so a later revision visibly reopens the question rather than inheriting the old yes.
4. 4The stage's fee milestone references the approval — the sign-off and the invoice trigger are the same fact.

This is how the client portal in Ofivio AEC works: read-only for the client, timestamped approvals attached to the exact revisions presented, visible to the whole practice team. The client experiences it as clarity — here is what we are deciding — and the practice quietly accumulates the record that makes stage boundaries mean something.