Skip to content

    Interior Design Approvals Workflow: A Stage-by-Stage Guide

    By Faura ·

    Interior Design Approvals Workflow: A Stage-by-Stage Guide

    An interior design approvals workflow is the set sequence in which a client reviews, comments on and signs off each decision, with every approval recorded before the next stage starts. The version that holds up on London projects has four parts: approvals split by stage, one place for feedback, deadlines and revision limits written into the contract, and a change order for anything altered after sign-off. This guide sets out each part in the order you will use it.

    Faura
    Present Material Choices With Confidence
    Faura gives designers a place to present schemes to clients, with samples and a materials library across more than 200 brands.
    Arrange an appointment

    TL;DR

    • Approve in stages (brief, layout, concept, specification, procurement, handover), so that earlier decisions are locked before later ones depend on them.
    • Keep feedback in one place and record each decision with the document, version, date, response and any conditions.
    • Put revision rounds, decision windows and the rate for extra work in the contract, then repeat them at every presentation.
    • Treat changes after sign-off as change orders that state scope, cost and programme impact before any work starts.
    • Keep the issued proposal as the contractual record, and use any portal or app status only as workflow.

    Table of Contents

    What an approvals workflow is, and why it matters

    An approvals workflow is the structured process of requesting, tracking and confirming client decisions on layouts, materials and quotations so the project can move forward. One practitioner guide says it creates accountability, reduces misunderstandings and replaces scattered, informal communication with a documented record. Another describes the core event as the point where an item moves from specified to approved, whether through a signed proposal, a batch document or a portal click.

    The commercial reason is simple. In a trade project, an approval is the trigger for spending: drawings go to site, samples become orders, and orders become manufacturing slots. A vague “that looks lovely” in a message thread is not a trigger you want to rely on when a bespoke piece is in production.

    One design studio makes a point worth keeping in mind: clients rarely complain about mood boards or palettes. They complain about delays, confusion, silence and surprises. A clear workflow addresses all four, because the client always knows what is being asked, by when, and what happens next.

    What an approvals workflow is, and why it matters — overview diagram

    The approval stages, from brief to handover

    A full-service UK project typically runs through enquiry and scope, briefing, concept design, spatial coordination, technical specification, procurement, construction, and handover with aftercare. Not every stage needs a formal sign-off, but several do. Clients are usually asked to approve final layouts, designs, finishes and furniture before manufacture or before drawings are issued to site.

    A practical sequence of approval gates looks like this:

    Gate What the client approves What it unlocks
    1. Contract and brief Scope, revision rounds, decision windows, fee basis for extra work Concept work
    2. Layout Space plan, room use, furniture positions Concept development and technical drawings
    3. Concept Direction, palette, material families Detailed product selection
    4. Specification Named products, finishes, quantities, budget Quotations and orders
    5. Procurement Final quotation or purchase order Manufacture and delivery
    6. Handover Snag list and sign-off on completion Final invoice and aftercare

    The order matters. Moving sign-offs earlier, for example approving the layout before any sourcing begins, reduces the volume of later revisions. The reason is mechanical: a changed layout alters furniture sizes, lighting positions and joinery drawings, and every one of those has already been paid for in time if sourcing started first.

    Gate 1: the contract and brief

    The first approval is of the terms themselves. The contract should set the number of revision rounds, the deadline for submitting them, the rate for additional work and what falls outside scope. If you use a standard letter of appointment, this is where your approvals process becomes part of it rather than a courtesy.

    The brief approval is the one most often skipped. Have the client confirm the brief in writing, including budget range, who the decision-makers are and any fixed constraints such as listed-building status or a landlord’s licence for alterations. For a repeatable way to capture this, see our guide to client onboarding and briefs for trade designers.

    Gate 2 and 3: layout and concept

    Present one strong recommendation based on the approved brief, rather than three half-developed routes. One workflow guide suggests supporting it with a realistic 3D visualisation so clients can judge placement, colour, materials, lighting and atmosphere before purchase. Offering a single direction does not remove the client’s say. It makes the feedback specific: they respond to something concrete.

    Sequence also helps. One presentation guide suggests moving from goals and mood to layout, then materials, and finally products, so that value and risk are addressed before the client sees a price. Treat that as a view from a software vendor, not a rule, but the logic is sound: money questions land better when the client already trusts the direction.

    Gate 4: specification

    This is the approval with the most consequences. Each line should name the product, finish, dimensions, quantity and budget, so that what the client approves is exactly what is ordered. Writing those lines well is a skill in itself; our specification writing guide covers the fields to include.

    Presentation format shapes the quality of the decision. Clients decide faster when they can see the real thing. Our own view is that a finish board in daylight, a cutting of fabric against the actual paint colour or a stone slab beside the brassware will settle in ten minutes what a week of emailed images will not. That is the case for presenting selections at a trade showroom, covered in more detail in our guide to client presentation space.

    Gate 5: procurement

    Before you place orders, confirm that the approved specification, verified dimensions, supplier lead times and installation dependencies all line up. Procurement planning should track exactly these four things. A purchase order should follow only from an approved item, never from a conversation.

    Lead times drive the approval deadlines upstream. If the install date is fixed, work backwards from it to find the last day each approval can happen. Our article on FF&E lead times and backward scheduling shows the method, and the FF&E procurement process explains how orders then move to delivery.

    Gate 6: handover

    After installation, the designer walks through with the client, notes adjustments, addresses minor issues and completes final tweaks. Record this as a short snag list and have the client confirm it. Completion is an approval like any other and deserves the same written trail.

    Keep feedback in one place

    Scattered comments are the most common reason approvals drift. Feedback spread across email, messages and phone calls creates ambiguity, while a centralised, structured system keeps all parties aligned on the final version. Some presentation tools let clients view items, see alternatives and comment on specific selections in one place, which avoids the email and WhatsApp split.

    The tool matters less than the discipline. Whatever you use, apply four habits:

    1. One channel. Tell the client at onboarding where feedback goes, and politely redirect anything sent elsewhere.
    2. One voice per household or company. Name the person whose answer counts. With couples, boards and developers, agree this before the first presentation.
    3. Specific requests. Ask “approve the oak veneer finish on the joinery, yes or no” rather than “any thoughts?”.
    4. A log. For each decision, record the document or specification, version, date, response and any conditions or comments.

    Choose one approval pattern

    Clients get confused when the rules change from room to room. One project-management guide suggests choosing one approval pattern and keeping to it: batch approval by room, individual item approval, or a schedule-based approval window. Batch by room suits residential schemes with a clear room sequence. Item-by-item suits hospitality or commercial fit-outs where each product has its own supplier and lead time. A scheduled window suits busy clients who prefer to decide on a set day.

    Deadlines, revision limits and change orders

    Revision limits and decision deadlines need to be defined in the initial contract and reinforced at every presentation. Reminding the client in the presentation itself, not only in a contract they signed weeks ago, is what makes the limits workable.

    Setting decision windows

    A window needs a length and a reason. The Interior Designers Hub suggests seven to ten working days is the sweet spot for most design decisions. Treat this as a starting point to adjust, not a standard. Shorten it where a supplier’s price is held for a limited period or a lead time is tight, and lengthen it for decisions involving several stakeholders.

    The same source warns that delayed decisions cause calendar disruption, stalled invoicing and exposure to supply chain risks such as discontinued fabrics or price changes. It helps to say this to clients plainly. Explain how each decision affects the project schedule, and a deadline reads as information instead of pressure.

    Handling changes after sign-off

    Once an item is approved, a later change is a variation. Handle it through a formal change order that captures the scope, cost and schedule impact before any new work begins. A workable change order includes:

    • the approved item and version being changed;
    • what the client now wants, and why it is needed;
    • the cost effect, including any cancellation or restocking charges the supplier has confirmed;
    • the effect on the programme and the install date;
    • the client’s signature or written confirmation.

    Many late change orders start as a client seeing something for the first time after approval. Seeing and handling materials before the specification is signed removes a good share of them. Our article on using a trade showroom to reduce late change orders goes into this.

    On projects involving architects, developers or contractors, change control also has to match the main contract, so check how variations are instructed there. Where a project involves building regulations matters such as fire performance of finishes, confirm requirements with the building control body or your fire adviser before approval, not after.

    What counts as evidence of approval

    Approval can be recorded as a signed proposal, a timestamped portal click or an email saying “approved”, after which the item can proceed to a purchase order. Of the three, the signed proposal is the strongest, and the sensible approach is to layer them.

    One software provider recommends treating in-app approval status as workflow, and the issued proposal that records the agreed scope, products and prices as the contractual record. That separation is useful whatever tool you use. The status tells you where an item is. The proposal tells you what was agreed at a particular time.

    The gap many studios leave is the approval stage itself: some skip a dedicated sign-off, leaving no clean record of what was approved and when. A minimal record for each approval:

    1. Item or drawing reference and version number.
    2. Date and time of approval.
    3. Who approved it, in what capacity.
    4. The exact response, with any conditions.
    5. A link to the issued proposal or specification sheet.

    If your contract or professional indemnity cover has requirements about record-keeping, ask your insurer or solicitor. Do not assume a trade body guideline sets them.

    Making the workflow repeatable

    A workflow only saves time if you do not rebuild it for each job. Standardise templates for briefs, presentations, feedback requests and approval confirmations, and adapt them where a project needs it. A consistent process also gives clients a more professional experience, because they know what to expect at each stage.

    A simple starter kit:

    • a brief and budget confirmation form;
    • a layout approval sheet;
    • a specification schedule with a sign-off block;
    • a change order form;
    • a handover snag list.

    Review the kit after each project. Note which approvals took longest and why, then move that question earlier in the next job.

    Perspective: where approvals break in London projects

    From our position at a trade showroom, the same pattern appears often. Approvals rarely fail at concept stage. They fail at specification, when the client signs off from images and then sees the finish, scale or colour in person for the first time. Moving that moment of seeing earlier is usually the most effective change a designer can make to the workflow.

    We built the Faura residency in Westminster around that idea. Designers can specify from over 200 brands across two floors of finished interiors, with samples, technical files and a materials library on site, and present schemes to clients at the residency. Once the client approves, our team can handle procurement, logistics and delivery as one order and one invoice, so the approved specification is the one that is ordered. Trade terms are agreed individually with each approved trade account.

    — Faura Editorial

    Using a trade showroom inside the workflow

    A showroom does not replace your approvals process. It strengthens two gates: specification, where clients see real materials, and procurement, where an approved schedule becomes orders. Faura is a trade-only showroom and residency in Westminster, open by appointment Monday to Friday, 09:00 to 18:00, for interior designers, architects, developers and contractors.

    If you are mapping where this fits, start with the trade account and client hosting for presenting schemes. Architects and developers can look at specification support and FF&E procurement. For product-specific visits, we cover lighting, bathrooms and stone, tiles and finishes separately.

    FAQ

    How many approval stages should an interior design project have?

    There is no fixed number, but most projects need at least six gates: contract and brief, layout, concept, specification, procurement and handover. Add more for large or phased schemes, such as an approval per room or per package. What matters is that each gate unlocks a defined next step.

    What is the best way to record client approval?

    Use a signed proposal or specification schedule as the contractual record, and support it with an email or portal confirmation showing date and version. Keep the status in any app as workflow only. Note any conditions the client attached.

    How do I stop clients changing their minds after sign-off?

    You cannot stop it, but you can price it. Set revision rounds in the contract, remind the client at each presentation, and handle later changes through a change order showing cost and programme impact. Letting clients see and handle materials before sign-off also reduces second thoughts.

    How long should clients have to decide?

    The Interior Designers Hub suggests seven to ten working days for most decisions. Shorten it where supplier pricing or lead times are tight, and say so to the client. Put the window in the contract so it is not a surprise.

    Who approves on a project with an architect and a contractor?

    Agree it at the start and write it down: who the client’s decision-maker is, who issues drawings, and who instructs variations. Your design approvals should feed the main contract’s change process, not run beside it. Confirm the contractual route with the architect or contract administrator.

    Sources

    Related on Faura

    More from the journal