Every ugly project dispute I've ever seen traced back to the same document, or rather, to the same missing document. The scope of work. Studios pour weeks into boards and drawings and then dash off the scope in two paragraphs, "design and execution of 3-BHK interiors as discussed", and six months later "as discussed" is doing battle with a client's memory, and the client's memory always favours the client. So here's the practical, step-by-step way to write a scope that actually holds when someone leans on it, which is the only test that matters.
What "holds" actually means
A scope holds when, at any point in the project, a disputed question can be answered by pointing at a sentence. Not by re-arguing, not by "what we meant was", by pointing. That's the design goal for the document, and it changes how you write it: you're not writing marketing, you're writing the referee's rulebook for a game that hasn't been played yet. Every vague phrase you leave in is a future argument you've pre-booked.
The second thing to understand is that a scope holds through structure, not length. A rambling ten-page scope with no exclusions list holds worse than a tight three-pager with one. So let's build the tight three-pager.
Step 1: Define the physical scope room by room
Never "interiors of the apartment". List every room, and for each room, the categories of work: false ceiling, wall finishes, wardrobes, loose furniture, lighting, soft furnishings. The clean way to do this is to write the scope from the same room-by-room structure you'll spec in, because then the scope, the specs, the quote and eventually the invoices all share one skeleton. In Designa this is literally the same data, the room-by-room breakdown with quantities and live costs feeds everything downstream, so the scope isn't a separate document that can drift from reality.
Step 2: Separate design scope from execution scope
Half of all scope disputes live on this line. Are you designing only, designing plus supervising, or doing turnkey execution? Write it explicitly, and write what supervision means in visits per week, because "we'll oversee the site" stretches from a weekly walkthrough to living there, depending on who's reading. If you're design-only, say who owns contractor errors. If you're turnkey, say which vendors are yours and which are the client's. Interior design as a service has fuzzy natural edges, and this step is where you draw them sharp.
Step 3: Write the exclusions list (the part that saves you)
The exclusions list is the highest-value section per word of anything you'll write this year. Civil structural changes, plumbing relocation, electrical load upgrades, appliances, curtains, deep cleaning, statutory approvals, whatever you are not doing, name it. The psychology matters here: clients don't read inclusions carefully because they assume everything is included, right, so the exclusions list is the only place their assumptions get corrected before they become expectations.
| Scope section | What it must pin down | The dispute it prevents |
|---|---|---|
| Room-by-room inclusions | Every room, every work category | "But the balcony was obviously included" |
| Design vs execution | Who builds, who supervises, visit frequency | "You were supposed to be watching the site" |
| Exclusions | Everything you're not doing, named | "I assumed appliances were in the price" |
| Revisions | How many rounds, what counts as a round | The endless-tweaks spiral |
| Timeline & dependencies | Duration, plus what pauses the clock | Delay blame when client decisions stall |
| Payments | Milestones, amounts, and what unlocks what | "I'll pay after everything is perfect" |
Step 4: Cap revisions, in numbers
"Reasonable revisions" is not a number. Two rounds of revisions per room, changes after approval treated as fresh chargeable work, that's a number. And this clause only works if approvals themselves are recorded, because a revision cap is meaningless if nobody can say what version was approved. This is exactly where a portal with one-tap, timestamped approvals earns its keep, and I've written up the approval mechanics in how to get interior design clients to approve faster.
Step 5: Tie money to milestones, and collect before you start
The scope should name the payment structure: a design advance before work begins (non-negotiable, and I've made the full case in how to collect a design advance before you start), then milestone payments tied to defined stages, and what happens if a payment stalls (work pauses, timeline shifts). Put the GST treatment in writing too, that fees attract 18% GST and how goods are billed, so the first invoice isn't a surprise. When the scope's milestones map onto your billing system, each milestone becomes an invoice in one click, and that flow is documented in how to turn a quote into a GST invoice in minutes.
Step 6: Version it, sign it, and store it where everyone can see it
A scope that lives in an email attachment from January holds worse than one pinned inside the client portal where both sides see the current version. Get it signed (digitally is fine for working purposes, keep wet ink if your lawyer insists for the contract itself), and when the scope changes mid-project, and it will, issue a scope amendment through the same approval flow rather than absorbing changes informally. Informal absorption is how studios end up doing 15% more work for 0% more fee.
A worked habit: the scope-to-system pipeline
Here's the operational trick that makes all six steps sustainable: stop treating the scope as a Word document and start treating it as the first entry in your project system. In Designa, the room-by-room structure you scope becomes the spec structure, the specs become the boards the client approves in the portal, the approved quote becomes the GST invoice, and the milestones become the billing schedule, so the scope isn't a promise sitting in a folder, it's the rails the whole project runs on. One flat founding price for the whole studio, billed in rupees, covers the whole pipeline, and I've explained the pricing philosophy separately in Designa pricing explained.
Professional bodies have pushed this discipline for years, the Institute of Indian Interior Designers on the interiors side, and the Council of Architecture with its formal conditions-of-engagement tradition in architecture, and they're right: the studios that document scope professionally get treated professionally.
The scope-that-holds checklist
- Every room listed, every work category named per room
- Design, supervision and execution responsibilities separated in writing
- An explicit exclusions list, minimum ten items
- Revision rounds capped with a number
- Payment milestones defined, advance collected before work starts
- Signed, versioned, and visible to both sides in the portal
Frequently asked questions
What should a scope of work include for an interior design project?
Room-by-room inclusions, a clear design-versus-execution line, an explicit exclusions list, a numbered revision cap, timeline with dependencies, and payment milestones with GST treatment stated.
How do I handle scope changes mid-project?
Through written scope amendments approved the same way as the original, ideally via your client portal so the change is timestamped. Never absorb changes informally, that's unpaid work by another name.
Is a WhatsApp confirmation enough to change scope?
It's evidence, but it's weak and hard to find later. A recorded approval in a portal, tied to the specific document version, is what actually holds when the disagreement gets serious.
How does Designa help a scope hold?
The scope's room-by-room structure becomes your specs, approvals are timestamped in the branded client portal, milestones become one-click GST invoices, and every change has a record, so pointing at the sentence takes seconds.
The bottom line
A scope of work is cheap insurance written in an hour and cashed in for the entire project. Write it room by room, draw the execution line, name the exclusions, cap the revisions, tie the money to milestones, and run it through a system where approvals leave a trail. Do that and the document holds, and so does the relationship, because the fastest way to keep a client friendly is to never need the argument. The end of the project deserves the same discipline, and that's covered in how to close a project cleanly. See the scope-to-invoice pipeline live at demo.designa.work, or pick up the founding offer at go.designa.work.