Your Supplement Is Perfect and Three Weeks Late

What happens is simple, and not flattering: the money starts moving about a week sooner, and the file gets a little less perfect. When a shop stops building supplements to prove it was right and starts building them to land inside the review cycle that actually releases payment, the work does not get sloppier. It gets timed. The thoroughness meant to protect the shop was keeping its jobs open.

This is a franchise unit, busy enough, good reputation, with one large program relationship that matters more than the rest. That program does not pay when the work is done. It pays after a file moves through a batch on the carrier side: files are batched, reviewed on Thursdays, and supplement questions come back the following Tuesday.

The office manager is excellent. Every supplement she builds is a complete package — scope tied to photos, photos tied to notes, labor and materials documented, the question the adjuster might ask already answered two pages before he would have asked it. Unanswerable, if you give her time to finish it.

It takes her nine days to build one.

The file that kept missing the train

Picture a job that is physically done. Dry, rebuilt, homeowner back in the kitchen. The only thing left is the supplement — a legitimate difference between what was approved and what the job required once walls were open. She starts on a Monday. By the time she has chased the last invoice and matched the last photo, it is the Wednesday of the following week. Sometimes Friday.

Friday is the problem, not the quality.

A supplement finished on Friday has missed Thursday’s batch. It waits almost a full week for the next review, then until Tuesday for an answer. If that answer contains one question — and there is almost always one — the reply, however perfect, cannot be reviewed until the Thursday after that. One question costs a full loop.

Do that on a handful of jobs at once, which is normal, and receivables age in a way that has nothing to do with how well the shop does restoration work. Jobs sit open 30-plus days past physical completion. The homeowner, who sees none of this machinery, experiences the delay as the shop’s slowness. The competitor across town, whose files are not better, gets paid about three weeks faster because his paper lands on time.

The owner kept asking for a better file. What he had was a timing problem wearing a quality costume.

That is the mismatch Boyd would point at first. John Boyd, the fighter pilot who worked out the Observation-Orientation-Decision-Action cycle, held that when your picture of a situation no longer matches reality, you cannot patch it from inside the picture. You have to build a new one. This shop’s picture was: completeness gets us paid and protects us. Reality demonstrated something else every week: completeness on a nine-day rhythm guarantees we miss the only review that pays us. More documentation inside that picture just made the package heavier while it waited.

Tempo is relative, not fast

Boyd’s word for this is tempo, and it is easy to get wrong. Tempo is not speed, not hustle, and not a date on a calendar. It means operating at a rhythm that fits — and gets inside — the rhythm of the situation around you. Relative, not absolute. Measured from demonstrated reality, never from what the schedule was supposed to be.

This shop kept its own rhythm: nine days, same process every time. The carrier kept a different one. The mismatched one decides how long you wait.

Getting inside another party’s cycle, in Boyd’s sense, does not have to mean beating anyone. There is no enemy here. An adjuster working a Thursday batch is not an opponent to be disoriented. He is a person carrying a stack of files, with limited time on each one. The file is something being carried through his process. The useful question is: what does his Thursday actually look like, and what kind of file moves through it in one pass?

That question turns on orientation. For Boyd, orientation was the decisive part of the cycle — shaped by experience, by the culture you were trained in, by new information, and by pulling things apart and putting them back together differently. The office manager’s orientation was formed, for good reasons, around thoroughness as protection: if a line is documented completely, no one can take it away. It also filtered out the fact that mattered most: a complete package that arrives after the batch might as well not exist until next week.

Changing the file required changing the orientation first. Not her competence — her picture of what a good supplement is for. Under the new picture, a good supplement is one an adjuster can say yes to on Thursday without starting a second file in his head.

The Wednesday file

So she rebuilt her week around Thursday, not around completion.

Supplements are now scoped to be reviewable in one pass. The headline number is at the top. Three photos — not thirty — showing the condition, the cause, and the finished result. One question maximum for the adjuster, if a question has to be asked at all. If a line is still pending — a subcontractor invoice that has not landed, a material cost not yet final — she does not hold the whole supplement hostage to it. She submits Wednesday, incomplete but honest, with the pending line flagged rather than guessed or buried.

Wednesday matters. It puts the file in the batch with a day to spare, and it makes the shop’s rhythm usefully irregular: small files sometimes go in three days, a larger one in five, but all orient to the same Thursday reality instead of a nine-day standard that had nothing to do with payment.

Boyd treated a decision as a hypothesis and an action as a test. The hypothesis here was narrow: a shorter, reviewable file submitted before the batch will come back with fewer full-cycle delays than a complete file submitted after it. The test was the next three Tuesdays. Count days from completion to payment, not pages in the package.

It held. Completion-to-payment dropped by roughly one full review loop. Nobody worked frantic hours or added staff. The same office manager stopped answering questions no one had asked yet and made the one question that mattered impossible to miss. When a file moves in one pass, the Tuesday answer is usually a decision, not a new round of discovery — the job closes while the crew still remembers it.

What it costs

Boyd’s tempo is always paid for in comfort with imperfection, and this shop paid it in the exact place you would expect.

The unanswerable package was armor. Giving it up feels exposed. A flagged pending line, sent honestly before the final number is nailed down, occasionally gets denied in a way a buried, fully documented line probably would not have. That has happened. It is not theoretical. The shop had to weigh the week saved across ten jobs against the line lost on one. So far the math says yes, clearly. The feeling still says be careful.

The second cost landed on the office manager herself. Thoroughness was not just her method; it was her professional identity — the person who never missed anything. Sending a file she knows is incomplete, even flagged and honest, felt at first like doing worse work in public. It helped that the new standard was hers to shape: she designed the one-pass format, chose which three photos tell the story, and wrote how pending lines get flagged. The rhythm changed. The ownership did not.

Rhythm-matched does not mean thin. A file that leaves out the photo that proves the condition, or guesses at a number to make a Wednesday deadline, is just fast and wrong. Keep what a reviewer needs to decide, in the order he needs it, and be explicit about what is not yet in the file.

If you are paid directly by homeowners, translate the principle, not the Thursday. Every business paid through someone else’s batch — a property manager’s monthly approvals, a GC’s pay-app cycle, a corporate accounts-payable run — has a Thursday somewhere. Most shops never ask when it is. That rhythm is the other party’s observation, orientation, decision, and action cycle, running on its own clock. Your file either lands inside it or waits outside it, complete and correct and unpaid.

The practice

1. Find your Thursday. For every payer, program, or GC that matters, ask when files are actually batched and reviewed — and when answers come back. Write those two days down. That is your real payment schedule.
2. Redesign one file for one pass. Rebuild next week’s supplement to be decided in a single review: headline number first, the few photos that prove the condition, one clear question at most. Submit it the day before the batch, as a test.
3. Flag, don’t hold. If one line is still pending, submit the rest on rhythm and flag that line. Do not let one missing invoice move the whole job into the next cycle.
4. Measure days, not pages. Track completion-to-payment days for a month. If they do not fall after three cycles, the hypothesis was wrong — change the file again, based on what Tuesday brought back.

From the Boyd & Toyota series. The operator-side pieces run at Restoration Intel — start with The Cord Nobody Pulls and Salvage Is a Window, Not a Service. Want this thinking applied to your own shop? Book a call with Will Tygart — 30 minutes, and we start from your receipts, not a pitch deck.