How to Track Interior Design Projects, Purchases, and Client Approvals

An interior design project is three projects pretending to be one. There is the design project, where you develop concepts, source items, and produce drawings. There is the procurement project, where every item you specify has to be quoted, ordered, acknowledged, produced, shipped, received, and installed. And there is the client approval project, where a separate parallel narrative runs in the client's head about what they agreed to, when, and at what price.

Those three tracks have to stay in lockstep. They almost never do without a tracking system designed for it.

The classic failure modes are familiar to anyone who has run a design firm: an item is approved but never ordered. Ordered but never acknowledged by the vendor. Acknowledged but the lead time slipped six weeks and nobody told the client. Received but damaged. Installed in the wrong room. Or the worst version — delivered, installed, invoiced, and the client says they never approved that color. There is no email trail. There is no signed sample. There is a $4,200 sofa and a fight.

The right tracking system gives every item a dual identity: an internal operations status and a client-facing approval status. The two move in parallel but they are not the same field. This guide walks through how to build that system, the seven workflow steps every item should pass through, the status fields you need on day one, and the approval patterns that protect both sides of the relationship.

Most project management advice was written for software teams or general contractors. Design firms have a few specific problems that those frameworks do not address well.

Item-level granularity. A residential project might have 80 to 300 individually tracked items — a sofa, two armchairs, a coffee table, a rug, three pendants, a console, twelve hardware pulls, and so on. Each item has its own vendor, lead time, price, tariff, sample status, and approval state. A project-level Gantt chart is useless at this resolution. You need a line-item ledger.

Dual state per item. Every item has an internal ops status (where is it in the procurement pipeline) and a client-facing status (has the client approved it, at what price, with what substitution allowance). These are different and they drift. The day you ship an item is not the day the client approved it.

Long, variable lead times. A custom upholstered sofa from a high-end vendor is 14 to 22 weeks. A stocked rug from a wholesaler is 4 to 7 business days. A made-to-order light fixture from Italy with current tariff exposure is 16 to 30 weeks and the date moves. You need lead time as a tracked field on every item, with the original quoted lead time and the current actual.

Vendor delays propagate. When a vendor misses a ship date on a single dining table, it does not just delay that one delivery — it pushes the install date for the whole dining room, which pushes the photography date, which pushes final payment. One slipped line item is a domino chain.

Change orders are constant. Clients change their minds. Items get discontinued. A finish shows up wrong and has to be reordered. Without a clean change-order log, the original budget bears no resemblance to the final invoice and the client feels nickel-and-dimed.

Approval is the audit trail. When something goes wrong, the only thing that matters is whether you can produce a signed or timestamped approval. "We discussed it in the meeting" does not survive a dispute. The tracking system is also the legal record.

Every project, regardless of scope, should move through the same seven steps. The work changes between a $50K e-design package and a $1.2M full-service renovation, but the workflow does not.

Before a single item is specified, the project is set up with its rooms as first-class objects. Living, dining, primary bedroom, primary bath, kitchen — whatever the scope covers. Every item that gets added later is tagged to a room. This is the structure that makes everything else work.

At the project level you set the master fields once: client name, billing terms (typical structures are cost-plus, fixed fee, hourly, or design fee plus product markup), the markup percentage if applicable, the target completion date, and the total project budget broken down by room. The room budgets are not aspirational — they become the rails you check every purchase against.

The other thing that lives at the project level is the team and access list. Who on your side can edit items. Who on the client's side can see and approve. For larger residential projects, this also includes the contractor and any sub-trades who need to see schedule milestones but not pricing.

Every item lives as a single row in the project FF&E ledger. Furniture, fixtures, and equipment is the traditional name — for residential it usually expands to FF&E plus art, accessories, and materials. The minimum fields every item needs:

- Item name and description - Room - Vendor and SKU - Quantity - Net cost, retail price, and markup - Lead time (original quoted, current actual) - Required by date - Internal status (the ops state) - Client status (the approval state) - Substitution allowance (yes, no, or designer's discretion) - Tear sheet or product image - Notes

This ledger is the source of truth. Every other view — the client approval document, the purchase orders, the budget tracker, the install checklist — is generated from it. If you have a designer maintaining a spec ledger in one system and a bookkeeper maintaining a purchase tracker in another, the two will drift, and your project will run on whichever one the person you ask last looked at.

Specification and approval are two different events. An item moves from Specified to Approved only when the client has affirmatively signed off — either by approving a batch document, individually checking off items in a portal, or returning a signed proposal.

Three patterns work in practice. Choose one and stay consistent across projects.

Batch approval by room. You send a room-level proposal with every item in that room, the client reviews and either approves the whole document or sends back red-lines. This works best for design-build packages where rooms get developed sequentially. The deliverable is one signed PDF per room, stored on the project record.

Individual item approval. Each item has its own approval state. The client sees a portal or shared list and approves item by item. This is more flexible — useful when you are sourcing in waves or replacing a single item — but it requires more administrative cycles and more discipline about following up on undecided items.

Schedule-based approval window. Items are presented and the client has a defined window (usually 5 to 10 business days) to object. After the window closes, items are deemed approved and procurement begins. This pattern is faster but only works when the contract explicitly authorizes it and the client signs off on the schedule terms up front.

Whichever pattern you choose, the approval has to leave a timestamped trail. A client saying "yes" in a meeting does not count. A signed proposal, a portal click with timestamp, or a return email saying "approved" — those count.

Once an item is approved, you cut a purchase order to the vendor. The PO references the project, the specific item, the agreed price and lead time, the ship-to address (which is usually a receiver, not the client's home — more on that in Step 6), and any custom specifications like fabric COM (customer's own material), finish, or dimensions.

A few non-obvious things to track at this step. Deposit terms. Most furniture vendors require 50% to 100% deposit at the time of order. The project ledger needs a field for deposit paid and balance due, because the balance is what gets billed before shipment. Acknowledgment. A PO is not confirmed until the vendor sends back an acknowledgment with a firm ship-by date. Until the acknowledgment lands, the item is in a fragile state — the vendor could come back saying the fabric is discontinued or the SKU is on a 30-week lead. Track Acknowledged as a distinct status. Change-order trail. If anything about the PO changes after issue — a finish swap, a quantity change, an upgrade — that is a change order and it needs its own document and client sign-off. Do not let change orders live in email threads.

From acknowledgment to ship date, the item is in vendor land. The job here is to surface delays before they cascade.

Set a check-in cadence with each vendor — typically every 3 to 4 weeks for items with long lead times, weekly when the item is within 30 days of expected ship. Log the check-in on the item record. If the vendor slips the date, update the actual lead time field and flag it. A flagged item triggers two downstream actions: re-evaluate the install schedule, and decide whether to tell the client now or wait until you have a confirmed new date.

Most designers err on the side of waiting, hoping the slip resolves. This is a mistake. The client almost always finds out at the worst possible moment — typically when they have already told their family the new dining room will be ready for Thanksgiving. A short, factual update at the moment of the slip — "the Bordeaux dining table has moved from a December 12 ship date to January 18 due to the vendor's container delay, here is the updated timeline" — protects the relationship even when the news is bad.

Items rarely ship to the client's home directly. They ship to a receiver — either a dedicated furniture receiving warehouse the designer has a relationship with, or a white-glove logistics provider. The receiver inspects the item on arrival, photographs it, checks against the PO, and stores it until the install date.

The receiving event is a status change on the item: Delivered (to receiver). Two fields update — date received, and inspection status. Damage discovered at the receiver is the cheapest place to discover damage. The vendor's freight claim window is typically 5 to 14 days, and the receiver's documentation is what supports the claim.

For projects without a receiver — usually smaller residential where items ship direct — you need to brief the client carefully about the inspection responsibility. The client signs for the item, the freight claim window starts, and any damage discovered after that window is on the client (or the project) to absorb. This is one of the more common sources of designer-client friction. A written inspection protocol, sent before the first delivery, prevents most of it.

Install day is the convergence point. All approved, received items move from the receiver to the home. Furniture is placed, art is hung, electronics are integrated, accessories are styled. The status of every item moves to Installed.

The last status — Punch — is for items that need follow-up. A scratch on the console that the receiver missed. A pendant that hangs slightly too low and needs the electrician back. A rug pad that is the wrong size. Punch items are tracked the same as any other item, with an assigned owner and a target close date, and the project does not close until punch is at zero.

The final walkthrough is also when you collect the final approval document — the client signs off that everything has been delivered, inspected, and installed to specification. Final payment releases against this signature. If you skip this step, you will end up chasing final balances 60 days after install while the client has moved on to their next priority.

On the internal ops side, an item moves through nine states. Each transition is logged with a timestamp and the user who made the change.

Run alongside this is the client-facing status, which is simpler — typically Proposed, Approved, Ordered, Arriving, Installed. The client does not need to see In Production or Acknowledged. They need to see whether something has been approved, whether their money has gone to the vendor, an arrival window, and whether it is in the house. Mapping the nine internal states to the five client states is one of the small operational tasks that separates a calm project from a chaotic one.

There are three reliable approval patterns. They are not interchangeable. Match the pattern to the project type, the contract structure, and the client's working style.

Batch approval by room. Best for design-build packages developed sequentially. You complete a room — every item specified, every price confirmed, every tear sheet attached — and present it as one document. The client approves the whole document with a signature, or sends back red-lines. The next room does not start until the prior one is approved. Pro: very few moving parts on the client's end, clean records, fewer change-order surprises. Con: a single hung-up decision blocks the whole room.

Individual item approval. Best when sourcing in waves, when items have wildly different lead times that need to start in parallel, or when the project is large enough that a room can't realistically be approved as one document. The client has a running portal or shared list of items in a Pending Approval state. Pro: items move through procurement as soon as approved, no item is held up by another. Con: more administrative cycles, more risk of items sitting in Pending Approval for weeks.

Change-order log. This is not a primary approval pattern — it is the supplemental system that runs alongside whichever one you choose. Every change after initial approval — a substitution, a quantity change, a discontinued SKU, an upgrade — gets logged as a numbered change order with the original item, the new item, the price delta, the lead-time delta, and a client signature line. A project with no change-order log will have client disputes. A project with a clean change-order log will not. This is the single highest-leverage piece of paperwork in a design firm.

Most interior design firms run this workflow across four to seven tools: a spreadsheet for the FF&E ledger, a separate purchasing tracker, a CRM for client communication, a portal for approvals, an accounting tool for deposits and invoices, and a file storage tool for tear sheets and signed documents. The cost runs $200 to $600 per month per designer once you total the subscriptions. The bigger cost is the time spent moving data between them.

Deelo replaces most of this stack inside a single platform. Projects holds the room structure and the FF&E ledger, with every item as a row carrying the full set of fields (vendor, SKU, lead time, internal status, client status, markup, room). CRM holds the client record, communication history, and the approval portal where clients can see their items in a clean, client-facing view. Invoicing handles deposit collection, vendor PO tracking, and the final payment schedule. Docs and ESign cover the signed proposals and change orders. The whole thing runs on one $19 per seat per month subscription, which for a four-person residential design firm is $76 per month — replacing roughly $1,500 per month in stacked single-purpose tools.

The operational gain is bigger than the cost gain. When the item record, the client communication, the approval document, and the invoice all live in the same project, there is no integration drift. An approval signed in ESign automatically updates the item status. A deposit collected in Invoicing automatically flags the PO as ready to issue. A vendor-acknowledged ship date updates the schedule view across the whole project. The designer spends time on design, not on copying line items between systems.

Imagine a typical full-service residential project: a 4,200-square-foot single-family home, six rooms in scope, an $850K total project budget with $620K in product and $230K in design fees. The FF&E ledger ends up with 187 line items across the six rooms. Lead times range from 5 days (a stocked wholesaler rug) to 26 weeks (a custom dining table from Italy with current tariff exposure).

The project runs 10 months from initial concept to final walkthrough. Over that period, the system records 187 specifications, 14 batches of room-level approvals, 142 purchase orders, 9 numbered change orders, 31 vendor acknowledgments with revised ship dates, 4 freight damage claims (3 resolved by the vendor, 1 absorbed by the project), and 187 install entries.

At close-out, the designer can pull a single project report that shows the original budget per room versus actual, the variance attributable to each change order, the lead-time accuracy by vendor (useful for next year's sourcing decisions), and a clean audit trail of every client approval. The client gets a final binder with signed proposals, change orders, warranties, and a digital inventory of every item with vendor contact for future service needs.

This is what "in control" looks like at the project end. None of it is exotic. All of it is what happens when the workflow has been set up with three concurrent tracks in mind and the right fields in place from day one.