Nobody Could Tell Me Where the Rug Was

A contents job split across a warehouse, a referring restorer, and two cleaning subs does not need another shared spreadsheet. It needs one named person who can state the whole truth of that job without asking somebody else — where every item is, what is not ready, and what date is real. Without that person, the work can all be getting done and the job can still be unanswerable. The cost that shows up first is not lost property. It is lost confidence, one status call at a time.

This is a typical shape, not a report on a real firm. Eighteen people. Thirty thousand square feet of warehouse. No mitigation crews, no rebuild division. Packout, cleaning, storage, and pack-back only.

Work arrives by referral from a dozen restorers and adjusters. A crew inventories and packs a house after a fire or water loss, brings what can be cleaned and stored back to the warehouse, sends electronics to one sub, textiles to another, and holds everything until the house is ready to receive it back, room by room.

A single job can run to 400 line items across three custodians at once. That spread, not the number, is the hard part.

Three systems, three answers

Ask “What’s the status of the contents job?” and watch what happens.

The warehouse count says 312 items on site. That count is accurate, for the warehouse. The cleaning sub has 41 pieces in process. That count is accurate too, for the sub’s floor. The referring restorer’s file says the homeowner has been told everything returns Friday. That date came from somewhere — a conversation, an optimistic estimate, a rebuild schedule that slipped on one end and not the other.

None of those answers is the job.

Seventeen items are still in deodorizing, so Friday was never real. And no count, in any of the three systems, cleanly includes the rug, because the rug went to a third-party cleaner under a separate ticket and sits in a fourth place in people’s heads: assumed.

Nobody lost the rug. Outright loss is rare in this kind of shop, and it gets remembered. What happens every week is smaller and more corrosive: nobody can say, in one breath, where the rug is, when it will be back, and whether the Friday promise needs to be withdrawn.

So every status call becomes a research project — warehouse system, sub, warehouse lead, restorer’s note, three partial truths reconciled into one sentence. Meanwhile the referring restorer, who is the specialist’s actual customer, learns that calling this shop costs him time and still does not get him a straight answer. He starts to dread the call, then makes it later, then wonders if another contents shop is easier to check on.

The property was never the problem. The unanswerability was.

The keeper, not the coordinator

An empty workshop with a single covered car in warm light.

Toyota has run a version of the answer since 1953. That year Kenya Nakamura became the first shusa — chief engineer — on the Crown. The system that grew from that appointment puts one chief engineer in total accountability for one whole vehicle program, from concept to market. Not for a department. Not for a phase. For the whole thing.

Two details matter here, and both are lost if you turn the role into a coordinator job.

First, the functional engineers do not report to the shusa. He does not own the org chart. What he owns is the truth of the program and the approval that lets work live. As Kosaku Wada put it: “If the shusa says no, that drawing does not live.” His power is a signature, not a staff.

Second, for his assigned vehicle, the shusa is effectively the president. When a function’s answer and the whole vehicle’s needs conflict, the whole wins, and he says so. The stress test came decades later with the Prius under Takeshi Uchiyamada, where no single department’s reasonable answer added up to the car Toyota had committed to build. Somebody had to hold the whole, against the parts, for years.

Toyota gives that holding a physical form too: the obeya, a single large room where all the project’s information is posted — one shared truth, in one place.

Translate that plainly: a shusa is not the person who forwards your question to whoever might know. He is the person who can answer it, and whose no stops a promise going out the door. A coordinator routes information. A keeper owns it.

What changed in the shop

The owner made a change that looks administrative and is not. Every job, at packout, gets a named contents keeper.

Not a team. Not a department inbox. A name.

That name goes in three places: on the master sheet that travels with the box labels, in the referring restorer’s update email, and on a single job board in the warehouse office. The board is the shop’s obeya move, scaled down: the whole job visible in one room, on one wall — custody by custodian, items out to subs with dates, items flagged not ready, and the pack-back date, stated only if it is real.

The discipline that gives the role its teeth is narrow. A Friday pack-back cannot be promised by sales, by the referring restorer, or by the warehouse lead. Only the keeper can promise it, and only after walking the wall.

That walk matters. Before answering, the keeper puts eyes on the actual state of the job, including what sits on somebody else’s floor, and folds the subs’ answers into one account she or he will stand behind. If the rug is still at the cleaner, the date moves — early, while it is still news, not Friday morning, when it is a failure.

Status calls changed shape almost immediately. The research project became a phone call, because there was a correct person to call who was expected to know. The referring restorer started quoting the keeper’s name to homeowners — “Our contents keeper on your job is — ” — and the name quietly became part of the specialist’s brand. Referrers were not selling square footage. They were selling the fact that someone could answer.

What the single point costs

Do not adopt this because it sounds clean. It is a bottleneck by design, and the bill arrives predictably.

The first bill is absence. When a job’s truth lives in one person, vacations and sick days stop being staffing problems and become truth problems. A keeper out for a week leaves a set of jobs nobody else can fully state. So the shop had to pay for something diffuse truth never required: a deputy system. Each keeper needs a named second who walks the same wall often enough to answer in her place — not as well, but honestly, including saying what is not known. That is real payroll spent maintaining a backup for a role you invented.

The second bill is power. A keeper who alone can promise a pack-back date, and whose no stops that promise, accumulates leverage whether she wants it or not. In the first year, two keepers became effectively un-fireable — not by threatening anyone, but because too many referrer relationships and too much unwritten job knowledge ran through them. The owner noticed at raise time, exactly when you would rather not discover it.

That is not an argument against the role. It is the role, priced honestly. Concentration is the mechanism — it is why the answers got good — and the same concentration is the exposure. Toyota lives with that trade with deep benches behind the shusa. An eighteen-person shop feels it faster.

The mitigation is not to diffuse the job again; diffusion is what made it unanswerable. It is unglamorous work at the edges: the wall carries the truth in a form a deputy can read, subs and dates live on it rather than in a phone, and the owner accepts deputy coverage and raise pressure as the standing cost of answering a customer in one call.

A shop doing a handful of large losses a year might rightly decide that cost is not worth it. It gets harder to defend once your customer — the referring restorer — starts choosing his next referral by who makes his own status call painless. The homeowner asks the restorer; the restorer asks the specialist. Somewhere in that chain, one person either can or cannot say where everything is and what happens next.

Two empty wooden chairs sit side by side in a sunlit office corner.

Give the job a keeper, and one person pays that cost on purpose, in advance — so nobody else pays it by surprise on a Friday.

The practice

  1. Name the keeper at packout, in three places. One person per job, on the master sheet, in the referrer’s update email, and on the job board. No name means no keeper yet — say so that day.
  2. Put the whole job on one wall. One board showing custody, subs out with dates, items not ready, and the pack-back date or “not set.” Update it from the keeper’s walk, not from three systems averaged at a desk.
  3. Reserve the promise. Only the keeper can commit a pack-back date, and only after checking the wall and the subs — the rug at the third-party cleaner included. Everyone else’s answer to a date question is the keeper’s name.
  4. Fund the deputy before you need one. A named second who walks the wall weekly and can state the job honestly in the keeper’s absence. An uncovered keeper is a known single point of failure, not a surprise.

From the Boyd & Toyota series at Restoration Intel — what two old disciplines, tempo and standard work, look like inside a restoration shop.

Scroll to Top