Published
What Good Interior Design Specification Management Looks Like
There is no shortage of writing about what goes wrong with specification management. There is almost nothing about what right actually looks like. This post fixes that.
Author:
Ben D'Souza
Estimated reading time: 5 minutes
There is a great deal of writing about what goes wrong with interior design specification management. Version conflicts. Revision cascades. Procurement errors that trace back to a change nobody updated in the BOQ. The symptoms are well-documented and, for most studio directors reading them, depressingly familiar.
There is almost nothing written about what right looks like. What the specification workflow feels like in a studio where it is working properly. What the specific, observable markers are that tell you the system is sound rather than held together by individual vigilance and good fortune.
That gap is worth filling. Not because the diagnosis is wrong, but because knowing what is broken does not automatically tell you what to build instead. This post is about the target, not the problem.
The baseline: what a functioning spec system actually does
A specification system that is working properly does three things reliably. It maintains a single version of the truth that everyone is working from. It makes the downstream implications of product decisions visible before those decisions are finalised. And it produces client-ready outputs without requiring a designer to rebuild the document from scratch.
None of those are exotic requirements. They are the basic operational function of a specification workflow. The reason they are worth stating plainly is that most studios, if asked whether their current system does all three reliably, would pause before answering. The pause is the tell.
A functioning spec system maintains one version of the truth, makes cost implications visible before decisions are finalised, and produces outputs without manual rebuilding.
Seven markers of a specification workflow that is actually working
These are not aspirational. They are observable. A studio director who walks through a project mid-phase should be able to check each of these in under five minutes. If they cannot, the system has work to do.
1. One person can tell you the current status of every item in the spec without making calls.
In a working system, the spec is a live document. Anyone with access can see which items are approved, which are pending client sign-off, which have been revised since the last issue, and which are awaiting maker confirmation.
In .STUDIO: Item-level approvals + activity log + audit trail
Real-time concurrent editing — everyone sees the current state
Activity log and audit trail — every change recorded automatically
Item-level approval states — visible to the whole team without asking
→ See this in action: dotstudio.design/features/specification
2. A revision made on Tuesday is reflected in every document by Tuesday afternoon.
When a finish changes, the FF&E schedule, the cost plan, and the BOQ all reflect that change without manual cascade. In a spreadsheet system, this requires a human to trace the change through every document it affects.
In .STUDIO: Structured for how designers think — not rows and columns
Organise by Project → Area → Package — change a room type, every instance updates
FF&E and OS&E handled together — one change, both schedules
Automatic revision tracking — no manual cascade, no missed instances
→ See this in action: dotstudio.design/features/specification
3. The client approval history is attached to the spec, not to an email thread.
Sign-off records live inside the specification system, linked to the version they approved. When a question arises about what was agreed in week eight, the answer is in the spec — not in someone’s inbox.
In .STUDIO: Item-level approvals built into the workflow
Comments and mentions — discussions stay attached to the item
Item-level approvals — sign-off recorded against the specific version
Activity log — full traceable history without searching email
→ See this in action: dotstudio.design/features/specification
4. New team members can orient themselves in the spec without a handover session.
A designer joining mid-phase should be able to open the spec and understand the current state: what has been specified, what is still under review, what has changed recently, and what the package structure looks like.
In .STUDIO: Built around spaces, packages, and experience — not CSI codes
Switch view: By Area / By Category — find what you need immediately
Multiple packages per project — clear structure from day one
20,000+ Love That Design products with manufacturer, finishes, certifications attached
→ See this in action: dotstudio.design/features/specification
5. The cost implication of a product decision is visible before it is confirmed.
When a designer specifies a product, the margin impact is immediate and visible. The spec and the budget are not separate documents that need reconciling at the end of the phase.
In .STUDIO: Real product data. Real commercial impact.
Pricing + delivery timelines per item
Margin visibility per item — see the impact before confirming
Attach drawings, BIM, Revit families — full product records in one place
→ See this in action: dotstudio.design/features/specification
6. Generating a client-ready specification book takes less than an hour.
The specification book should be a generated output, not a designed document. A studio spending half a day in InDesign after every revision round is absorbing a cost that belongs to the system, not the project.
In .STUDIO: Generated directly from live specs
Specification books (PDF) — branded, ready to issue
Tear sheets and cut sheets
Submittal packages and presentation-ready outputs
Coming soon: room schedules, procurement lists
→ See this in action: dotstudio.design/features/specification
7. The principal can check project health without asking anyone.
A studio director should be able to see, across all live projects, which specs are at risk, which have open revision items, and which are approaching handover with outstanding approvals.
In .STUDIO: Secure collaboration beyond the studio
Granular permissions — the right people see the right things
External users only see approved items — controlled client and vendor access
Invite vendors securely — collaborate without losing control
→ See this in action: dotstudio.design/features/specification
One honest caveat
Reaching this standard requires more than the right software. It requires the studio to commit to a single system — which means retiring the parallel spreadsheets and email approval threads that currently sit alongside whatever tool is in use. Studios that adopt specification software but maintain Excel as a shadow system do not get the markers above. They get two systems, both partially maintained, with the familiar reconciliation problems running between them.
Specification software works when the studio commits to it. Half-commitment produces half the benefit and all of the switching friction.
free expert workflow audit
Book a Workflow Audit: See Exactly Where Your Studio Is Losing Time
LIMITED TIME OFFER FOR ARCHITECTURE AND DESIGN STUDIOS
Your audit is a tailored operational assessment designed specifically for interior design and architecture firms. Book your 30 minute session with our .STUDIO Consultant. Same-day slots usually available. Your audit report will:
Map your current specification and project workflows
Identify duplicate data entry and version-control risks
Highlight resource visibility gaps
Quantify potential time savings
Outline a phased plan to replace spreadsheets safely
This is not a generic demo. It is a tailored operational assessment designed specifically for interior design and architecture firms.
If you are considering architecture workflow software or looking for a serious alternative to Excel for your design firm, this is the first step.
Further reading
How to Replace Excel in Your Interior Design Studio — .STUDIO. The practical mechanics of committing to the system described in this post.
How to Prevent Errors in Interior Design Specification — .STUDIO. Tactical measures for markers 1–3 specifically.
