A contents line is built to travel. It starts on the claim record, rides to the field sheet, crosses into the estimate, and lands on the carrier’s form. Name, quantity, price — that’s the whole passport, and for most of what comes out of a building, it’s enough.
For some lines, it isn’t. Not because the item is expensive. Because the item’s real need was never a price.
Picture a day of commercial contents work: a medical clinic, a research lab, a data center, a packing plant’s equipment room. Thirty boxes of water-damaged medical records. A painting, off the wall, with smoke on the frame. A backup tape library — worthless as hardware, holding years of a business’s records. Precision instruments that need a certified service, not a replacement. Every one of those lines has a name. Every one can be handed a number. And every one will be handled wrong if the name and the number are all that travels, because what each line actually needs is for its situation to survive the trip. The paper needs a freeze-dry specialist before the mold takes it. The painting needs a conservator before anyone guesses what it’s worth. The tapes need a recovery lab’s evaluation, and the evaluation fee is the only honest money on that line today.
There is no field for any of that. Not on the claim record, not on the field sheet, not in the estimate. We know, because we went looking for the place where the specialist’s name is supposed to live — surface by surface, form by form — and it isn’t there. So the situation gets typed into a note, or said out loud in a room full of people who all nod. Notes don’t travel. At the next hand-off, the line arrives as a bare name and a price, and it gets treated as what it appears to be: an ordinary line. It gets priced as the wrong kind of thing — a service carried as a product, a component carried as a whole unit, an evaluation carried as nothing at all. Or it gets skipped, because nobody downstream can see what it was waiting for.
That’s the work these codes are about. The boxes are what the paperwork sees. The work is what’s inside them — and in the seams between pack-out and estimate, between the claim and the carrier’s form, where a specialty situation can fall out of the file without anyone dropping it on purpose.
What a specialty code is
A specialty code is a short label that rides with the line and carries the situation across. Written on whatever paperwork the line touches, it says: this line is a specialty situation, this is the kind of expert it routes to, and this is what has to still be true when the line arrives.
The first set — thirteen codes — was drafted from one day of commercial contents work, and only from what that day actually did. Every code on the list exists because a real line hit the wall described above: priced as the wrong species, skipped with its need recognized and entered nowhere, or carried across a border with its meaning stripped off. Situations that were planned but never run — a pharmacy’s dispensing robot, a hotel’s key-card system, a bakery’s deck ovens — were refused codes. They sit in an annex, unearned, until a day’s work measures them. That’s the methodology, and it’s the whole credibility of the set: no code without a situation that actually happened.
What a code carries
The string is only the label. The substance is eight fields that travel with the line, written out on the paperwork in plain language:
1. Identity. What it is, how many, and whether it’s a set. The one thing ordinary paperwork already carries well.
2. Price species. What the dollar figure on the line actually is: a replacement product, a recurring service, a one-time service, a component, an evaluation fee — or a prose estimate that isn’t a price yet. More specialty lines die here than anywhere else. The number survives the trip; its meaning doesn’t.
3. Periodicity. Once, per year, or per visit. A yearly service that arrives as a plain one-time price has already been misread.
4. Scope qualifier. Component only. Evaluation only. The unit, but not the contents inside it. The qualifier is small print with large consequences, and it’s the first thing a bare line loses.
5. Expert kind. The class of specialist the line routes to — and their name, when it’s known. This field exists because nothing else in the chain holds it. The code carries it because nothing else will.
6. Custody expectation. Does the item leave with the expert, get serviced where it sits, or stay in the pack-out chain? Anyone who picks up the file should be able to answer that from the line.
7. Estimate destination and markup. Where the money lands in the estimate, and whether a markup applies — set deliberately, by a person, never inherited silently from a default nobody chose.
8. Disposition state. The repair / replace / total-loss state the line was in when its figure was produced. The same item prices as different species under different states; a figure recorded without its state can’t be reproduced or defended.
The routing rule
Anyone who has watched Pawn Stars knows the move. Something comes over the counter that’s beyond the shop — a manuscript, a rare instrument, a signature nobody at the counter can authenticate — and nobody guesses. They call their expert. And here’s the part that matters: the expert doesn’t just offer an opinion from across town. He comes down to the shop, or the item goes to him. The evaluation happens with the thing in his hands.
Specialty routing works the same way, and the codes are written to that rule: the expert doesn’t just opine — they come get it, or they come do it. A document-recovery specialist takes the boxes and returns treated records. A conservator takes custody of the painting and returns a written assessment. A recovery lab receives the media and returns a report. If the “routing” on a line is a note saying someone should probably look at it someday, nothing has been routed. Custody moved, or it didn’t happen.
Published to be used
These codes are published here, on Restoration Intel, to be used. Copy the strings verbatim onto your own paperwork. Adapt the fields to your forms. Rename the strings to fit your shop if that makes them stick. There is no permission to ask for, no license to sign, no registry to join. If a code helps a file close cleaner, it did its job. If it doesn’t fit your work, leave it — nobody is keeping score.
And if your work runs into a specialty situation this set doesn’t cover, write the code your situation earned — from what actually happened, the same way these were written — and publish yours too. A shared language doesn’t need an owner. It needs people willing to write the situation down where the line can carry it.
The practice
Take the next specialty line on a file you’re working — the one currently riding as a bare name and a price — and write its eight fields onto the paperwork by hand. Identity, price species, periodicity, scope, expert, custody, destination, disposition. One line, fully carried, will show you exactly where your own forms drop the situation. That spot is where the code goes.