There's a specific moment every designer knows. A client asks — pleasantly, mid-walkthrough — "any word on the dining table?" And you hear yourself say "let me check on that," while somewhere behind your eyes you're already running the search: was it ordered? Did the deposit go out? Was that the vendor who emailed about a fabric delay, or was that the other project?
You're not disorganized. You're tracking two hundred moving items across five projects in a system that was never built to hold them. That's the whole FF&E tracking problem in one sentence.
What FF&E tracking has to cover
FF&E — furniture, fixtures, and equipment — sounds like a procurement term, but tracking it is really three jobs at once:
The item lifecycle. Every piece moves through the same stations: specified → presented → client-approved → quoted → purchase order → ordered → in production → shipped → received → delivered → installed. A tracking system's first job is to answer "where is this item?" for any item, instantly, without opening your email.
The money view. Each item carries numbers that change as it moves — estimated price, quoted price, deposit paid, balance due, freight, what the client has approved versus what's committed. If your item tracking and your budget live in different documents, one of them is wrong right now. You just don't know which.
The client view. Clients don't churn over aesthetics. When researchers asked past clients why they wouldn't rehire a designer, the answers were process answers: "Decisions took longer than expected," and wanting a better ordering and delivery experience. The client doesn't need vendor names and trade pricing — they need to see that things are approved, ordered, and moving. Silence reads as drift, even when everything's on schedule.
Why the spreadsheet version breaks
Nearly every studio starts with a spreadsheet, and nearly every studio hits the same four walls:
- Version chaos. The tracker on your laptop, the copy your assistant exported, the one attached to Tuesday's email. Three versions, three truths. (The restart that eats a week of sourcing tabs is the same failure wearing a different outfit.)
- Statuses live in your inbox. The spreadsheet says "ordered." The truth — backordered, new ETA, vendor waiting on a deposit — is in an email thread only you have read. The document you check isn't the place where reality happens.
- The budget doesn't move when the items do. A price change on row 40 doesn't ripple into the client budget, the deposit schedule, or anything else. Reconciliation becomes a weekly manual job that always happens later than it should.
- There's no client-safe layer. You can't hand the client the raw sheet — it has trade pricing and vendor names in it. So client updates become a separate weekly artifact you assemble by hand, which is why they slip.
None of this is a discipline failure. There's a whole cottage industry of FF&E tracker templates on Etsy — that market exists because the pain is universal, and because a better spreadsheet feels like it should fix it. It postpones the wall; it doesn't remove it.
What good FF&E tracking looks like
Whatever tool you use — including a spreadsheet, while it still fits — hold it to five requirements:
- One record per item, referenced everywhere. The board, the plan, the budget, and the PO all point at the same item — not four copies of it.
- Status changes update the money. When an item is approved or a quote lands, the budget view reflects it without a reconciliation session.
- Approvals are logged, not remembered. "You approved this on the 14th" should be a link, not an argument. Designers force communication into documented channels for a reason — clients deny conversations happened.
- A client view you don't have to sanitize. The client sees progress and approvals; they don't see trade pricing or your margin. And it updates itself.
- A cross-project view. "Everything awaiting approval, all projects" and "every order overdue, all projects" — the questions you ask Monday morning. Single-project tools make you open each project to find out; users of some popular design tools name exactly this complaint.
The honest tool landscape
A spreadsheet is fine for a solo designer with one or two projects and a couple dozen items each. Free, flexible, yours. It breaks at concurrency — multiple projects, multiple people, items in the hundreds. If you're reading this article, you're probably at or past that line.
Spec-only tools (Gather, Fohlio) do fast, deep FF&E specification — shared libraries, spec sheets, schedules. But they stop at the spec: users report pairing them with Basecamp or similar because approvals and project management aren't really there. You get a better spec sheet and keep the coordination problem.
Design-management platforms connect the item to the budget and the client. Programa's FF&E schedules are quick to build and present well (4.8/5 on Capterra); the trade-offs sit on the money side — no native accounting, and invoicing complaints in reviews. Studio Designer runs procurement plus full general-ledger accounting, the deepest in the industry — with a learning curve its own users describe as "a month of schooling." We compared the whole field on our Studio Designer alternatives page, payment fees included.
Mortar — ours — was built so the item, the budget, the order, and the client approval are the same record wearing four views. An item moves through its lifecycle; the budget updates itself; the client portal shows approval requests and progress without exposing trade pricing; and the studio dashboard answers the Monday-morning questions across every project at once. It's $59 per user per month, unlimited projects, and the payment fees are on the pricing page — including our share.
Start here this week
Even before you change tools: pick one source of truth per item and demote everything else to a pointer. Move status words out of your inbox and into that source the moment they arrive. And write down your item lifecycle stations — the list above is a start — because whatever system you adopt next, that list is the spine of it.
The dining-table question will come again. The goal isn't to know every answer from memory — it's to be one glance away from any of them.
