Every studio owner has had this conversation, and it always goes the same way. Three weeks after the client approved the Italian marble, the tiles arrive, and the client stands in the room and says, calm as anything, "no, I never agreed to this one, I wanted the other option". And you know they did agree, you remember the call, but you cannot prove it, so you eat the cost of re-ordering or you have an ugly argument that sours the whole project. This post is about the boring, unglamorous fix that makes that conversation disappear, which is making sure every approval on your project carries a timestamp and a record.
Let me be honest, this sounds like a small administrative thing, and it is, but small administrative things are exactly where Indian studios lose money and goodwill, quietly, month after month. If you have ever lost an argument you were actually right about, this one is for you.
Memory is not a record, and clients are not lying
Here is the thing I want to say gently, because it matters. When a client says they never approved something, they are usually not lying. Human memory genuinely rewrites itself, especially over the eight or ten weeks of a project, and especially when someone has since seen a nicer option on Instagram. So the goal is not to catch anyone out, the goal is to have a shared record that neither of you has to remember, because the record remembers for both of you.
A verbal yes on a phone call is not a record. A "haan theek hai" on WhatsApp buried in four hundred messages is barely a record. What you want is a specific approval, tied to a specific option, on a specific date, that both sides can see. That is what a timestamp gives you, and it is the difference between a five-minute reference and a two-hour argument.
What a timestamped approval actually looks like
A proper approval record is not complicated. It just needs to answer four questions without anyone having to scroll through chat history.
| Question | What the record shows |
|---|---|
| Who approved it | The client, logged into their own portal |
| What exactly they approved | The specific mood board or finish option |
| When they approved it | The date and time, fixed |
| What it cost at that moment | The rate and quantity as approved |
When all four are captured in one place, the conversation three weeks later takes ten seconds. You open the record, you show them, and you both move on. No blame, no re-order at your expense, no cold feeling in the room. This is really an extension of keeping one source of truth for the studio, because an approval is only useful if there is exactly one authoritative version of it.
The money that timestamps quietly protect
Approvals are not just about taste, they are about money, and this is where the timestamp earns its keep. Think about the last few times a project went over on cost or time. There is a very good chance the root cause was an approval that was fuzzy, so the wrong thing got ordered, or a change the client asked for verbally that never made it into the quote.
That middle number is the one that matters. Every re-order you eat because you could not prove the client signed off is pure margin gone, and it never shows up as a line item anywhere, which is exactly why it survives for years. I traced how this kind of leak works end to end in why studios lose money between quote and invoice, and the fuzzy approval is very often the first domino.
Timestamps and scope creep are the same story
When a client keeps asking for "just one small change", the reason it eats your margin is almost never the change itself, it is that the changes are never recorded as decisions, so they pile up invisibly until the project is three weeks late and you cannot point to why. A timestamped approval flips this. The moment a change is a recorded, dated approval with a cost attached, it stops being a favour and becomes a decision the client can see they made.
That record is what lets you have the grown-up conversation, "you approved these four additions on these dates, which is why we are two weeks past the original plan", without it turning into a fight. The approval log is your calm, factual backup, and it works precisely because it is not your word against theirs.
Where the record should live
A timestamp is only as good as the place it lives. If your approvals are scattered across WhatsApp, email, and a couple of phone calls you half-remember, you technically have timestamps but no usable record, because you cannot find them when you need them. The record has to live in the same place the client approved, which is why the branded portal matters so much, and why I keep coming back to why your client portal should be branded. The client logs in, approves the option, and the timestamp is captured right there, next to the thing they approved.
And because the approval is tied to the quote, the same record carries through to billing. When the approved board becomes the invoice, the sign-off and the bill reference the same decision, which I walked through in how a quote turns into a GST invoice in minutes. No gap, no "which version", no argument at payment time.
Key takeaways
- Clients who deny approving something are usually misremembering, not lying, so you need a record, not a better memory
- A useful approval record captures who, what, when, and at what cost, in one place
- Every re-order you eat for lack of proof is pure margin gone, and it hides forever
- Timestamps turn scope creep from a vague grievance into a list of dated decisions the client can see
The profession has been moving toward this kind of formality for years, the same push toward documented, accountable practice that bodies like the Council of Architecture and the Institute of Indian Interior Designers have championed. Treating an approval as a real, recorded decision is simply what serious interior design practice looks like now, and clients increasingly expect it.
The cost of not having it is invisible until it is not
The reason studios put off fixing this is that the cost is invisible right up until the day it is very visible. You do not feel the missing timestamp on the ninety-nine projects where nobody disputes anything, you feel it hard on the one where a client digs in and you have nothing to show. I added up these quiet, invisible costs across a whole studio in the true cost of running a studio on five tools, and the disputed-approval line is one of the ugliest, because it costs money and goodwill at the same time.
Frequently asked questions
Why should design approvals be timestamped?
Because memory is not a record. When a client later disputes a finish or a scope change, a timestamped approval showing who approved what, when, and at what cost settles it in seconds instead of turning into an argument you cannot win.
Is a WhatsApp "yes" good enough as an approval?
Not really. It is technically dated, but it is unfindable in a four-hundred-message thread and it is not tied to the specific option or its cost, so it fails you exactly when you need it. A portal approval keeps the record next to the thing approved.
How does this help with scope creep?
A timestamped approval turns each "small change" into a dated decision with a cost attached, so instead of a vague grievance you have a clear list you can show the client to explain the extra time and money.
Does Designa record approvals automatically?
Yes. Clients approve mood boards and options in a branded portal with unlimited free logins, and each approval is captured with a timestamp and carried through to the quote and invoice.
If you have ever lost an argument you were factually right about, the fix is not a better memory or a firmer tone, it is a record that neither of you has to remember. You can see timestamped approvals working on real projects at demo.designa.work, and the founding offer, one flat price for the whole studio in rupees with unlimited free client logins, is at go.designa.work.