"I never approved that": getting client sign-off on drawings you can prove
Why a client's approval so often leaves no trace, the four things a provable approval has to pin down, how to settle who approves before the first sketch, a ninety-second routine for every stage, and what to do when the dispute has already started.
- Most disputes of the form "I never approved that" are not about bad faith. The approval did happen, in a meeting, on a call or as a thumbs-up, and nothing durable recorded which drawing it applied to.
- A provable approval pins down four things: the sheet and revision, the person with authority to approve it, exactly what is now fixed, and the date.
- The approver is a decision you take at appointment, not at the dispute. When a family is the client, name who signs off before the first sketch.
- Software does not create the approval. It keeps the approval, the revision it referred to and the fact that the client opened that revision in one place, so you are not reconstructing it from three apps.
The call comes in the week the shuttering goes up. The client has seen the first-floor plan on site and the staircase is not where they thought it would be. "We never agreed to this." You remember agreeing to it, in the drawing room, six weeks ago, with both of them nodding. You also remember that no one wrote it down.
This is one of the most expensive conversations in a practice, and it is almost always avoidable. It is rarely a character flaw in the client or in you. It is a record problem: the decision was made in a place that keeps nothing. This guide is about how an approval is actually given on an Indian residential or small commercial project, why it so often leaves no trace, and how to build a short routine that makes "approved" something you can show.
Why "approved" is rarely on the record
Approval happens wherever the client happens to be when they feel sure. That is a strength of how people work and a weakness for evidence. Look at the common routes and what each one leaves behind.
| How it was given | What survives | What it fails to show |
|---|---|---|
| Agreed in a meeting or on a site visit | Your memory, possibly a line in your own notes | Which sheet was on the table, and who in the room had the authority |
| A phone call | Nothing, unless you wrote it up the same day | Almost everything |
| A thumbs-up or "ok" on WhatsApp | A message in a long thread | Which attachment it answered, once newer files arrive below it |
| "Looks good" by email | A dated email | Whether the attachment was the final revision, and who else needed to agree |
| One spouse says yes, the other was not told | A decision that may not bind the household | That the person who approved is the person who decides |
None of these is dishonest. The pattern is that the approval is attached to a conversation, not to a drawing, so it cannot be traced to the revision it covered.
The WhatsApp row deserves a second look because it is the one most practices lean on. A thumbs-up is a reply to a message, and a message is a position in a stream. Two days later three more drawings arrive underneath it. Six months later, scrolling back, nobody can say with confidence what that thumbs-up was agreeing to, including the person who sent it.
What a provable approval has to pin down
An approval you can stand behind answers four questions without any help from memory. If a record answers all four, it will hold up with an unhappy client and with a mediator. If it misses one, that is where the argument will happen.
Which drawing, at which revision
By sheet number and revision, not "the latest plan". "A-102, Rev 2" means one thing for ever. "The plan we discussed" means something different each week.
Who approved
A named person who has the authority to decide for the household or the company. A relative who is cheerful in meetings but not the decision-maker is a trap for both sides.
What is now fixed
Say what the approval locks. "Layout and room sizes are approved; finishes and furniture positions remain open" lets the client keep changing things you never meant to freeze, and stops you freezing things they did not realise were closing.
When
A date, because later changes are priced against it. An approval with no date cannot tell you which changes came before it and which after.
The decision-maker problem
On an Indian house project the person paying, the person living in the house, the person who will have opinions at the last moment and the person who is abroad but must be consulted are often four different people. They do not all attend the meeting. Any of them may say later that they were never asked.
The fix is to settle it once, at appointment, in writing: who gives stage approvals for this project, and that the studio may rely on that person's approval as the household's. If two people must agree, say so and name both. It feels formal when you propose it and ordinary once it is in the appointment letter. It is also the single cheapest dispute prevention in this guide, because it is done before anything is at stake.
The payment stages guide covers the clauses that belong in an appointment letter. An approver clause fits alongside them.
Approval and the change that follows it
An approval is a boundary. Everything before it is design; everything after it is a change, and changes after approval are what most studios under-price. If you can show the date and revision that were approved, you can show that a later request is a variation rather than a continuation.
That is the bridge to the scope creep and revision guide, which deals with the other half: deciding what counts as a variation and what to charge for it. Read together, they give you a sequence the client can see: draft, approved at Rev 2 on a date, then change requested on a later date, priced and agreed before the work starts.
Where a client portal helps, and where it does not
A tool cannot give your client the authority to approve, and it should not pretend to. It can reduce the amount of reconstruction you do afterwards. Three things matter, and each of them is a specific, modest behaviour.
- The conversation sits beside the drawing. In AtelierLab each client has one thread tied to their workspace, next to the drawings they are discussing, so "approved" is written in the same place the sheet lives rather than in a stream of other messages.
- The revision cannot quietly change underneath the approval. Versioned document sets keep every prior revision when a drawing is replaced, so "Rev 2" still refers to the same file in six months.
- There is a record that the client opened what they approved. The audit log records views and downloads, who and when, in an append-only log. That does not prove the client understood the drawing. It does show that the revision named in the approval was available to them and was opened.
A note on evidence generally: electronic records can be relied on in a dispute, but how a record is produced and who can vouch for it matters, and the rules are specific. If you expect a real dispute, take legal advice about preserving your records before you tidy them. This guide is about prevention, not about running a case.
A ninety-second approval routine
The routine below fits the end of any stage and does not require a meeting. It is deliberately short, because a routine that takes ten minutes is the one that gets skipped on the busy week.
Issue the stage set with revisions in the sheet titles
Make sure every sheet carries its number and revision before it leaves. The drawing issue register guide covers numbering that holds up through a long job.
Say in the covering note what approval would fix
Two lines: what is being asked for sign-off, and what stays open. This is the "what is now fixed" answer, written before the client answers rather than argued after.
Ask for the one-sentence reply
From the named approver, in the same thread. Give them the sentence to paste if it helps; people comply more readily with a form than with an instruction.
Log it against the sheet, not the conversation
Add the approval date and the approver to your own register or variation log against that sheet and revision. In a workspace, the reply already sits beside the sheet it names.
Treat anything later as a change
When the next request arrives, answer with the approved revision and date, and move to pricing it the way the scope creep guide describes. You are not accusing anyone; you are pointing at a date.
When the dispute has already happened
If you are reading this because the call has already come, the advice is different and mostly about restraint.
- Do not edit, delete or rearrange anything. A tidy record that has been touched is weaker than a messy one that has not.
- Collect what exists: the dated drawings and their revisions, any covering notes, WhatsApp and email threads, your own meeting notes, and photographs from the site visit.
- Reconstruct the sequence in a plain document: what was sent, on what date, at what revision, and what each reply said. Mark clearly which entries are firm and which are your recollection.
- Start the conversation with the sequence, not with a verdict. Most clients who have forgotten, or who were not the person who approved, respond to a calm timeline far better than to being told they agreed.
- If it is going to cost real money either way, speak to your lawyer before you reply in writing, and consider a neutral third party before positions harden.
The aim afterwards is to make sure it is the last time. Add the approver clause to the appointment letter template and the one-sentence reply to your stage routine, and most of the exposure goes.
Does it matter on a small job?
On a single-room interior with one decision-maker and one sitting, you can reasonably rely on a clear email. The routine earns its time as soon as there are several stages, several people with opinions, or a fee that depends on a stage being treated as complete. Those are exactly the jobs where the staircase conversation is expensive.
There is also a point that is easy to miss: a clear approval protects the client as much as you. It is the thing that lets them say, honestly, that nothing was built that they did not see. Framed that way, most clients are glad to give it.
Keep the approval where the drawing is
AtelierLab is in early access and onboarding our first studios personally. Each client gets a private workspace with versioned drawings, a thread beside them and a record of what was opened. It will not sign for your client, and it will make the sequence easy to show. Tell us how you handle sign-off today and we will say honestly whether it fits.
Questions, answered
The questions architects ask most about this, in plain language.
Ask us anythingAsk for a one-sentence reply from the named decision-maker that states the sheet and revision, what the approval fixes, and the date, for example "Approved: A-102 Rev 2, layout and room sizes only. Finishes open." Do it at the end of every stage, in the same place the drawing is shared, so the reply and the sheet sit together.
Do not alter any record. Collect the dated drawings, covering notes, message threads and your own meeting notes, and build a plain timeline of what was sent and said. Open the conversation with that timeline rather than a verdict. If significant money depends on the outcome, get legal advice before replying in writing.
It can be evidence, but it is weak on the one thing you need: which drawing it referred to. A thumbs-up answers a message, and newer attachments pushing it up the thread make it ambiguous. A reply that names the sheet, revision and what is fixed, written where the drawing lives, is far stronger.
Decide it at appointment and put it in the appointment letter: who gives stage approvals, and that the studio may rely on that person's approval for the household. If two people must agree, name both. Settling this before any drawing exists is the cheapest way to avoid a later claim that someone was never consulted.
No. It keeps a private thread beside each client's drawings, preserves every revision when a drawing is replaced, and records views and downloads in an append-only audit log. The approval itself is a message the client writes. If you need a signed document, keep issuing and countersigning it as you do now.
No, and it should not. It fixes the date and revision from which a request counts as a change, so the cost of that change can be agreed before the work begins. How to decide what counts as a variation and how to price it is covered in the scope creep and revisions guide.