Design Project Delivery Tracking: A Step-by-Step Guide

Why Delivery Tracking Breaks Down in Spreadsheets

Most studios start the same way: one workbook per project, a tab per room, a column for "ordered," another for "expected date." That setup holds up for a single bathroom refresh. It falls apart once a project has dozens of vendors, each with its own lead time, its own confirmation email and its own habit of moving a ship date without telling anyone.

The problem is structural. A spreadsheet stores a date but never acts on it. Nobody gets a warning when an item's promised arrival slides past the day the installer is booked. Statuses depend on whoever remembered to update the cell, so two team members can end up with two different versions of the truth. And because pricing, markup and delivery notes live in the same file, sharing progress with a client usually means building a sanitised copy by hand.

Generic task tools don't fully solve this either. As Agiled's comparison of design software points out, a generic to-do app can't track vendor lead times, trade markup or client-approved selections with a price tag. Monday.com makes a similar observation: general project tools handle deadlines, then struggle once you need to manage visual assets or track 50 different vendor orders.

There's an outcomes argument too. Agiled reports that the 2025 ASID Interior Design Industry Outlook found firms using specialty project and procurement software had 61% fewer "failed delivery" incidents (wrong item, wrong finish, back-ordered) than firms running on spreadsheets. That figure reaches us through a third-party summary, so check the ASID outlook directly before quoting it to clients. Still, the direction matches what most studios experience: delivery problems are rarely mysterious. They're usually information that was never captured or never surfaced.

Good design project delivery tracking therefore needs three things: one record per item, a deadline attached to every order, and a way to see what's slipping without reading every row. The four steps below build exactly that.

Step 1: Build Your FF&E Schedule and Log Every Order

Delivery tracking starts with the specification. An FF&E schedule details every piece of furniture, fixture and equipment on a project, and it's the backbone you track deliveries against. If an item isn't in the schedule, it won't show up in your delivery view either.

Organise the schedule by room first. With a per-room structure, when the living room slips you can see at once which furniture, lighting and finishes belong to that space and what the delay does to your install sequence. In ArchiBoard, each project carries live estimates with per-room breakdowns, so the structure that drives your budget also drives your tracking.

Data entry is the slowest part of building a schedule, and it's also where errors creep in: a mistyped SKU becomes the wrong item on the pallet. The ArchiBoard Web Clipper cuts that risk by extracting product photos, prices and SKUs straight from a supplier's page, so the item lands in your project with the details the supplier published. If you're still sourcing, the shared product catalog gives you brand, price and dimension data across categories such as finishes, plumbing and lighting without leaving the workspace.

Once the client approves an item, log the order against it. Record, at minimum:

• the vendor and the order or confirmation reference
• the order date and the vendor's quoted lead time
• the expected delivery date
• the delivery destination (warehouse, site or client address)
• the person responsible for follow-up

That last field matters more than it seems. Expediting, meaning tracking order status, delivery dates and vendor follow-up, fails most often because everyone assumes someone else is chasing. One named owner per order removes the ambiguity.

If you're migrating from a spreadsheet, don't bother importing history for finished projects. Move active projects only, rebuild each as a room-by-room schedule, and log open orders with their current expected dates. Closed projects can stay in their archive.

Step 2: Set Vendor Lead-Time Deadlines in the Timeline

A quoted lead time only helps once it becomes a date on a calendar. Plenty of designers store "8 to 10 weeks" as text in a notes column. Convert it right away into two dates: the latest day the item can arrive without disrupting installation, and the latest day you can place the order to make that happen.

Work backward from the install. If the sofa must be on site the week before the photographer arrives, and the vendor quotes a long production window plus transit, the order deadline is simple arithmetic. In a timeline view, order deadlines and delivery dates sit side by side, so you can spot the item that needs ordering this week even though the install is months away. ArchiBoard's timeline tools are built for this: they track order deadlines and delivery dates in one place instead of scattering them across calendars, emails and cell comments.

A few habits keep the timeline reliable:

1. Add a buffer deliberately. Pick a standard cushion for freight and receiving and apply it consistently, rather than guessing per item.
2. Group by dependency. Tile must arrive before the tiler, plumbing fixtures before the plumber's second fix, and furniture last. Order deadlines for early-sequence items come first.
3. Separate long-lead items. Custom upholstery, stone and bespoke joinery deserve their own attention. The stone products and porcelain tile categories, for example, often involve cutting, batching or shipping considerations that standard stock items don't.
4. Confirm in writing. When a vendor confirms a date, attach or note the confirmation so the date has a source.

We don't have industry benchmarks for typical lead times or delay rates, and they vary enormously by vendor and category, so rely on each supplier's own quote rather than a rule of thumb. For a broader view of how tracking fits across a whole project, see our guide to design project tracking software for interior designers.

Step 3: Flag Late Items and Handle Backorders

Even a well-built timeline will meet late items. The goal isn't to prevent every slip. It's to catch each one early enough that you still have options.

Build a simple weekly review. Once a week, filter your orders to anything with an expected delivery date inside the next few weeks and confirm each with the vendor. Items without a fresh confirmation get flagged. This is the heart of expediting, and it goes much faster when the data already sits in one view instead of being reconstructed from inboxes.

When an item is flagged, classify the problem before you react:

• Delayed in transit: the product exists and a new date is available. Update the expected date and check what it touches downstream.
• Backordered: the vendor has no stock or no production slot. This is the high-risk case, because the new date may be uncertain.
• Wrong or damaged: a replacement or credit is needed, which restarts part of the clock.

For a backorder, work through the decision in order. First, ask whether the new date still fits the install sequence. If it does, update the record and carry on. If it doesn't, look at your options: a comparable in-stock alternative, a temporary solution, or resequencing trades so the delayed item goes in later. Substitutions need client sign-off, so having the original selection, its price and the proposed alternative side by side makes that conversation quick. If the alternative comes from a category you already source, such as lighting alternatives or a different paint or wallpaper option, the catalog can surface candidates with prices and dimensions to compare.

Record every status change with a date and a reason. A delivery log with history lets you tell a client precisely what happened, and it's your evidence if a vendor dispute follows.

Step 4: Update Clients Without Exposing Your Margins

Clients want to know where their things are. They don't need your cost price, your markup or your supplier discounts, and mixing the two in one shared file is how margin information leaks by accident.

The cleanest fix is permissions rather than careful copying. ArchiBoard uses role-based permissions that hide margins from clients while still letting them collaborate, so a client can see item names, images, approved selections and delivery status without ever seeing what you paid. Because the client view comes from the same project data as your internal one, you never maintain two versions.

Decide on a rhythm and stick to it. Many studios send a brief status summary on a fixed schedule, with an immediate message only when something changes the install date. A good update includes:

1. what has arrived and where it's stored
2. what's in transit, with expected dates
3. anything delayed, with the cause and your proposed fix
4. any decision you need from the client, and by when

Lead with solutions on delays. "The dining chairs are backordered; here are two alternatives that keep the install date" lands better than a bare notice of bad news. For estimates and approvals, export a clean PDF of the relevant schedule so the client has a record that excludes internal figures.

Finally, think about the whole team. Role-based access also lets a purchasing assistant update order statuses while a junior designer sees only the rooms they work on. If you want to try this workflow on a live project, the free Starter plan on ArchiBoard is enough to build one schedule and run it through these four steps. Done consistently, design project delivery tracking stops being a weekly scramble and becomes a routine you can trust.