Ask a studio owner for the approved spec of a project that closed eight months ago and watch what happens. Someone scrolls WhatsApp, someone opens a Drive folder with four files named "FINAL", someone calls the designer who left in January. Documentation is the least glamorous subject in this whole business, and it's also the thing that decides who wins the dispute, who passes the tax scrutiny, and who actually learns from finished projects. So here's the complete inventory, what to keep, why, for how long, and how to make keeping it automatic instead of heroic.
The three reasons you keep records (know which one you're serving)
Every document earns its place by serving at least one of three masters. Defence: when a client, vendor or contractor disputes something, the record is your case, and the side with the timestamped trail generally wins politely without lawyers. Compliance: GST scrutiny wants a continuous invoice series, POs matching bills, and books that reconcile, and "we were busy with design" is not a recognised defence. Learning: the only way to know your real margin per project type, your real vendor performance, your real estimation accuracy, is records, and studios that keep them quote sharper every year while everyone else re-guesses.
Keep this trio in mind because it answers every "do we really need to keep this?" argument inside the team, right, if a document serves none of the three, drop it, and if it serves any, it needs a home that isn't somebody's phone.
The inventory, phase by phase
| Phase | Documents to keep | Serves |
|---|---|---|
| Enquiry & closing | Enquiry record, consultation notes, scope of work, fee agreement | Defence, learning |
| Design | Room-by-room specs with costs, board versions, client approvals with timestamps | Defence |
| Commercial | Quotes and revisions, GST invoices, payment receipts | Compliance, defence |
| Procurement | Vendor quotes compared, POs, delivery records, vendor bills, payment approvals | Compliance, defence, learning |
| Site | Dated site updates with photos, drawing versions with pinned issues, snag lists | Defence |
| Closure | Handover packet, as-built drawings, warranties, final settlement | Defence, learning |
| Post-project | Actual vs budget summary, vendor performance notes | Learning |
Two rows get underestimated constantly. The approvals row: a client approval is only a record if it's tied to the exact version approved and timestamped, a WhatsApp "ok" three messages below a photo is evidence-shaped noise. And the procurement row: the spec-to-PO-to-bill chain is simultaneously your GST compliance backbone and your margin-leak detector, and I've walked the money half of it in how to turn a quote into a GST invoice in minutes.
What "keeping" actually means (the three tests)
A document is kept when it passes three tests. Findable: anyone on the team locates it in under a minute without asking anyone. Trustable: it's obviously the current version, timestamped, with its approval state visible. Connected: it links to its neighbours, the PO points at the spec it was raised against, the invoice points at the quote, the snag points at the drawing. A Drive full of PDFs passes none of these, honestly, it's a shredder with a search bar. This is why documentation is really a systems question wearing a filing costume: when the work itself happens in one connected workspace, the record is a by-product, the approval exists because the client tapped approve in the portal, the PO trail exists because the PO was raised there, and nobody "does documentation" as a separate chore, which is the only version of documentation discipline that survives a busy quarter.
Retention: how long is long enough
For the commercial and tax records, GST invoices, POs, vendor bills, ledgers, keep them a minimum of six years, and practically speaking eight, since assessments and appeals stretch. For design and site records, drawings, approvals, snag lists, handover packets, I'd argue you keep them effectively forever, because storage is nearly free and the value curve is strange: a client calls four years later needing the paint code, a redevelopment enquiry arrives for a building you documented, a warranty dispute surfaces in year three. The Council of Architecture tradition treats project records as part of professional practice itself, and bodies like the Institute of Indian Interior Designers push the same discipline on the interiors side, and they're right, your archive is quietly an asset.
The special cases that need extra care
Contractor interfaces. Where your work meets the civil contractor's, measurements taken jointly, work-readiness confirmations, damage observations, document the handoffs, because that boundary is where blame games are born, and I've covered it properly in coordinating with civil contractors.
Variations. Every mid-project change needs its own mini-record: what changed, who approved, cost impact, date. Firms that absorb variations informally lose twice, the margin now and the argument later.
Design-build firms. If you run execution too, your documentation load roughly doubles and the payment-approval trail becomes critical, the full treatment is in managing a design-build firm, and architecture practices with long arcs have their own version of this in project management software for architecture firms in India.
How Designa makes this automatic
I'll describe it in documentation terms, since that's today's lens. Every interior design project in Designa accumulates its record as a side effect of running: enquiries logged in leads, specs versioned room by room with live costs, client approvals timestamped in the branded portal (unlimited free client logins, so every approver is on the record), quotes becoming compliant GST invoices with a continuous series, Razorpay payments reconciling against invoices, POs chained to specs and bills, site updates and snags pinned to drawings, payment approvals and an org-wide transactions ledger, all syncing to Tally or Zoho Books so the books agree with the record. When the dispute, the scrutiny or the "what was our real margin" question arrives, the answer is a search, not an excavation. One flat founding price for the whole studio, billed in rupees, covers all of it.
If you're assembling your stack more broadly, every tool a design studio needs (and which you can skip) sorts the market with this record-keeping lens applied.
The documentation audit, run it on your last finished project
- Scope of work and fee agreement findable in under a minute
- Every client approval tied to the exact version, with a timestamp
- Complete spec → PO → vendor bill chain for five random purchases
- Continuous GST invoice series with payments reconciled
- Snag list with photo-verified closures and handover packet delivered
- Budget versus actuals summary saved for future quoting
Frequently asked questions
What documents should an interior design studio keep for every project?
The full trail: scope and fee agreement, versioned specs, timestamped client approvals, quotes and GST invoices, vendor quotes, POs and bills, dated site updates and snag lists, and the handover packet, connected so each document points to its neighbours.
How long should studios keep project records in India?
Tax-relevant records (invoices, POs, ledgers) for at least six years, practically eight. Design and site records are worth keeping indefinitely, since storage is cheap and old projects generate warranty questions, referrals and repeat work.
Is WhatsApp approval enough as a record?
It's weak evidence, hard to find and not tied to a version. A portal approval, timestamped against the exact board or quote approved, is what holds up when the disagreement gets serious.
How do I keep documentation without hiring an admin?
Run the work in one connected system so the record is a by-product: approvals, POs, invoices and snags document themselves as they happen. Documentation as a separate chore always loses to deadlines.
The bottom line
Documentation isn't filing, it's the studio's memory, defence and tuition rolled into one, and the only sustainable way to keep it is to make the record a by-product of the work itself. Run one project through a connected workspace and watch the archive build itself at demo.designa.work, and the founding offer is at go.designa.work.