Why Do Indian Architecture Clients Always Ask for One More Change?
Every Indian architect knows the feeling — the design is approved, then comes "just one small change." Here's why it happens and exactly how to stop the revision cycle.
You have been here before.
The concept was presented. The client loved it. They said — and you remember this clearly — "Yes, this is exactly what we wanted." You went away and developed it further. Working drawings started. And then the message arrived.
"Just one small change. Can we shift the master bedroom to the other side?"
One small change. The phrase every Indian architect has learned to dread — not because the change itself is always significant, but because of what follows it. The shift that affects three walls. The walls that affect the structural grid. The structural grid that affects the MEP layout. The MEP layout that requires three new drawings. And the client who, when shown the implications, says: "Oh, I didn't realise it would affect so much. While we are doing this anyway, can we also look at the kitchen?"
This is not bad luck. It is not a difficult client. It is a pattern — predictable, preventable, and in most cases caused by decisions made at the very beginning of the project, long before the revision request arrived.
Why the Revision Cycle Happens
Understanding why Indian architecture clients ask for constant changes is the prerequisite for stopping it. There are five reasons, and they are almost never the client's fault.
1. The Design Was Not Fully Resolved Before Approval Was Taken
The most common cause of endless revisions is a concept approval taken before the concept was actually finished.
The pressure to show something — to keep momentum, to reassure the client that work is progressing — leads many Indian architects to present concepts before they are confident in them. The client approves something that the architect was not fully satisfied with, and both parties proceed on a foundation that neither entirely trusts.
When the client later asks for a change, they are often — without knowing it — responding to the same discomfort the architect felt when they presented the design. The revision is the client's attempt to fix something that was not right, without the vocabulary to say precisely what.
The fix: Do not seek approval until you are satisfied with the design. A client who approves a design you believe in is far less likely to request significant revisions than a client who approves a design you were still working through.
2. The Brief Was Incomplete or Ambiguous
A design can only be as resolved as the brief it comes from. When the brief is vague — "modern," "open," "not too dark" — the design is built on assumptions. Every assumption is a future revision request waiting to be discovered.
Indian residential clients frequently arrive at the briefing stage without having thought through their spatial requirements in specific terms. How many people use the kitchen simultaneously? Does the client work from home — and if so, where? What is the family's approach to entertaining — formal dining, or informal living area gatherings? Does anyone have mobility requirements? What is the client's actual storage behaviour?
These questions feel detailed and tedious at briefing stage. They feel essential at revision stage, when the kitchen turns out to be too small for two people cooking together, or when the home office turns out to be missing.
The fix: Run a structured briefing process — written, not verbal — that covers room-by-room requirements before any design begins. A brief that takes two hours to complete properly prevents ten hours of revision.
3. The Client Cannot Visualise From Drawings
This is the most under acknowledged cause of revision requests in Indian architecture, and it is entirely the profession's communication problem rather than the client's limitation.
Most clients cannot spatially read a floor plan. They approve a plan because they trust the architect, because the spaces look logical on paper, and because they cannot yet see what the space will actually feel like. When they walk the partially built space — or when they see a 3D render that reveals what the plan meant in three dimensions — they respond to the reality rather than the abstract.
"I didn't realise the bedroom window would look directly into the neighbour's wall."
"I thought the living room would feel bigger."
"I didn't understand that the bathroom door would open into the bedroom this way."
These are not unreasonable complaints. They are the discovery of things that were always in the drawings but never visible to the client.
The fix: Do not take plan approval as design approval. Show clients 3D visualisations, walkthroughs, or physical models before finalising plans. The cost of a render is far lower than the cost of a structural change after working drawings are done.
4. There Was No Agreed Revision Limit
If the contract — or the verbal understanding — does not specify how many rounds of revision are included in the design fee, the implicit message to the client is that revisions are unlimited.
Unlimited revisions produce unlimited revision requests. Not because the client is exploitative, but because the absence of a limit removes the natural discipline that a limit creates. When there is no cost to asking for another change, there is no reason not to ask.
The fix: State the revision limit in writing at the start of the engagement. "The design fee includes two rounds of concept revisions and one round of design development revisions. Additional revision rounds will be billed at ₹X per round." This does not make clients hostile. It makes them deliberate — which produces better, more considered feedback, not less.
5. The Spouse, Parent, or Relative Who Was Not in the Room
This deserves its own category in Indian residential architecture. The project brief was taken with the primary client. The concept was developed and approved with the primary client. And then — at design development, or at working drawing stage, or at the site visit — a spouse, parent, or relative sees the drawings for the first time and has strong opinions.
This is not a client problem. It is a stakeholder management problem. The people who will live in or use the space have a legitimate interest in the design, and if they were not involved in the brief and approval process, their feedback will arrive as revisions rather than inputs.
The fix: Identify all decision-makers at the very first meeting and ensure they are present at every significant approval moment. A concept approval signed off by only one half of a couple is not a concept approval — it is a pending revision.
How to Stop the Revision Cycle — Practically
Write Everything Down
Every brief, every approval, every decision, every change request — in writing, confirmed by the client. Not because clients are dishonest, but because memory is unreliable and projects are long.
When a client says "we approved this six weeks ago," the written record either confirms or clarifies. When a client says "I never asked for that," the written change request tells both of you exactly what happened.
The discipline of written documentation also subtly changes client behaviour. A client who knows that their change requests are logged and tracked is more considered about making them than a client who believes changes are free and unrecorded.
Charge for Out-of-Scope Changes
The moment a client understands that a change request has a cost — even a modest one — the quality of change requests improves dramatically. Requests stop being impulsive and become considered.
This does not mean charging for every small clarification. It means clearly defining what is within scope, having a written agreement about revision rounds, and issuing a variation note — with a cost — when a request goes beyond that scope.
Most clients, when shown a variation note, will either proceed with the change (accepting the cost) or reconsider whether it is genuinely necessary. Both outcomes are better than the revision cycle.
Use a Design Sign-Off Document
At every design stage — concept, design development, working drawings — have the client sign a document that records what was presented, what was approved, and what the next stage will cover.
This document does two things. It creates a clear record of the design progression. And it asks the client to be deliberate about approval — to read what they are signing rather than verbally agreeing and moving on.
A signed design approval is not a guarantee against future change requests. But it changes the conversation from "I don't remember approving that" to "here is what you approved and when."
Brief Every Stakeholder Yourself
Do not rely on the primary client to brief their spouse, parents, or business partners. Brief them yourself — directly, in the same meeting, with the same drawings and the same explanation.
Two minutes spent ensuring that every person who will influence the project understands the design at approval stage saves hours of revision management later.
The Client Who Keeps Changing Their Mind
There is a category of client for whom the above measures help but do not fully solve the problem — the client who is genuinely uncertain about what they want and processes that uncertainty through revision requests.
This client is not being difficult intentionally. They are making spatial decisions — decisions about how they will live, work, and feel in a space for the next decade — and they do not yet have the clarity to commit.
The most effective response to this client is not stricter contract terms or firmer revision limits. It is more design work upfront — more options presented at concept stage, more 3D visualisation before plan approval, more detailed brief development before design begins.
The revision cost of a client who was not ready to commit at approval stage is always higher than the investment of ensuring they were ready. Slowing down the front of the process is almost always faster than managing the revisions it prevents.
Documentation Makes the Difference
Every change request, every approval, every variation note lives in a project record that needs to be accessible — to the architect, the design team, the contractor, and the client — throughout the project.
Wallxy keeps every drawing revision, client approval, and change request documented in one organised project workspace. When a client says "I never asked for that," or when a contractor claims the drawing they have is current, the complete project record is immediately accessible to everyone. See how Wallxy works →
Free plan available. Go at ₹1,799/month. Pro at ₹4,399/month (7-day free trial on Pro).
Built for Indian architecture and construction professionals.
The Change That Was Coming Anyway
Here is the uncomfortable truth about the Indian architecture revision cycle: many of the changes that arrive at working drawing stage were always coming. They were visible in the brief, in the first concept, in the client's hesitation during approval.
The architects who have the fewest revisions are not the ones with the strictest contracts. They are the ones who see the coming change before the client does — who address the uncertainty before it becomes a revision request, who ask the question the client had not yet thought to ask, who present the option the client was going to discover at site.
That quality of attention — to the client, the brief, and the design simultaneously — is what separates the practices that spend their time designing from the ones that spend their time revising.
Keep every project approval documented on Wallxy →
Resources
Explore more at wallxy.com/blogs
No Wallxy comments yet
Be the first to share your thoughts on this article!