Every FF&E project accumulates a deficiency list. Damaged pieces, missing components, wrong finishes. The list is not the problem — the list is normal, and a project with an empty one is usually a project that has not looked.
The problem is treating it as a backlog of open exceptions rather than as a live input to the installation schedule.
This assumes the exception process itself is in place; how a WMS should handle OS&D for furniture receiving covers that end to end — the typed record, the evidence, the four ways to hold affected stock, and what a system can and cannot claim about liability. What follows is the layer above it: the deficiency list as a project artefact, who owns each decision on it, and how it races the install date.
The three that survive a visual check
Visible damage is easy — a crushed carton corner gets noticed by anyone walking past. The deficiencies that decide schedules are the ones that pass a dock inspection cleanly.
Concealed damage. The carton is intact, the count is right, and the piece inside has a cracked veneer, a scratched top or a split joint. Nothing outside suggests it. Found at assembly months later, by which point the freight has moved twice and the carrier claim window has usually closed.
Missing hardware and components. The nightstand is present; the hardware pack taped inside the drawer is not, or the glass shelf was never packed, or the brackets went with a different carton. Invisible until somebody tries to assemble it — which, if nobody opened it earlier, is at the site.
Wrong finish, fabric or model. The right SKU count of the wrong thing, because a vendor substituted without telling the buyer. Worse than damage: it is not repairable, and the replacement is a full production cycle away.
The common property is that all three are cheap to catch while the carton is open and expensive at every later point. That is the entire argument for open-box inspection on the scopes that warrant it.
Disposition paths, and who owns each
A deficiency is not closed by being recorded. It is closed by a disposition — and the ownership differs in a way that matters, because two of the five decisions are not the warehouse's to make.
| Path | Owner | What it costs |
|---|---|---|
| Repair, warehouse or touch-up vendor | Warehouse | Hours. Cheapest when cosmetic and not a high-visibility scope |
| Replace from vendor | Procurement | A full lead time — the one that threatens the install date |
| Accept as-is | Designer or owner's representative | Nothing, but it is a design decision and must be recorded as theirs |
| Return to vendor | Procurement, warehouse executes | Return freight plus its own paperwork |
| Reject at receipt | Warehouse, at the dock | Only available while the carrier is still there |
Two consequences follow from that middle column.
The decisions that gate your install belong to people outside your building. "Accept as-is" and "replace" are client-side calls. A deficiency waiting on a designer is not warehouse work in progress; it is a question that has been asked and not answered. Tracking those two separately from the ones you own is the difference between a list you can act on and a list you can only read.
A recorded "accept as-is" protects everyone. It is the disposition most likely to be made verbally and the one most likely to be disputed later, when the piece is installed and somebody asks why. Written down against the piece, with who decided it, it stops being an argument.
The punch-list cycle
Deficiencies do not resolve once. They loop, and the loop has a rhythm worth planning for:
- Deficiency raised at receiving or inspection, evidenced, affected quantity held.
- Disposition decided — often needing the designer, so it needs client visibility.
- If replacing: ordered, with a lead time checked against the install date.
- Replacement arrives as new inbound freight against the same project.
- Original piece dispositioned — returned, repaired or written off — and its hold cleared.
- Replacement released into the wave it was always meant for.
Step 4 is the one people forget to model. A replacement is not an edit to the old record; it is a new receipt against the project, and it should be received and inspected like anything else. Replacements arrive damaged at roughly the same rate as originals, and a replacement that fails inspection on arrival is the failure mode that turns one late room into two.
Step 5 is where holds quietly accumulate. A project that finishes with twenty pieces still held usually did not have twenty unresolved problems. It had twenty resolved problems whose holds nobody cleared — and every one of them was invisible availability that somebody could have planned against.
Racing the install date
This is the part that makes a deficiency list a schedule document rather than a quality log.
Every deficiency has two dates attached: when it was raised, and when the piece is due to leave for site. The gap between them is your whole decision space, and it shrinks every day.
Working backwards from the release wave:
- Replacement lead time exceeds the remaining gap. The decision is already made — you are shipping the room incomplete or shipping a repaired piece. Escalate the day you know, not the week of.
- Lead time roughly equals the gap. The most dangerous case, because it looks survivable. It only works if the order goes today and the replacement clears inspection first time. Treat it as at-risk and tell the project side.
- Comfortable gap. Normal work. The only failure here is forgetting to order.
The practical instrument is simple: look at open deficiencies scoped to the next two release waves, not at the total. A project with eighty open deficiencies and none in the next two waves is in better shape than one with twelve, all of them on floor 4 which ships in nine days.
That is also the one number worth putting in front of the project side every week. Total open deficiencies is a vanity metric; open deficiencies inside the next two waves is a forecast.
Running the list as a shared artefact
Because the gating decisions are client-side, the deficiency list only works if the client can see it — with the same discipline that applies to the rest of the portal: read-only, scoped to their own records, no internal-only detail.
What the project side needs from it:
- The specific pieces, not a count
- The nature of each problem, with the photographs
- Which decisions are waiting on them, separated from the ones the warehouse owns
- What is held, so nothing is planned against unavailable stock
- Which waves are affected
What the warehouse still owes them on top of the list: the judgement calls. A vendor whose exception rate is climbing, a replacement that is not going to make its date, a staging zone filling faster than planned. A shared list makes routine questions self-serve; it does not make escalation self-serve.
The receiving workflow covers where deficiencies get captured, and the FF&E and project logistics page shows how holds, dispositions and release connect across the project.