When the Audit Comes, You Open the Packet

The letter arrives. A notice of audit. A claim filed over work at a specific site. A demand to prove your crew was there, did what the contract called for, and followed the procedure. Your first instinct is to explain — to pick up the phone and tell your side.

That instinct is the trap. Audits and claims are not decided by whose explanation sounds better. They're decided by the record. And the moment you're explaining instead of showing, you've already lost the high ground.

The asymmetry nobody plans for

A traceable record gives the reviewer something concrete to examine: the original source, its available metadata, the requirement it supports, and the review history. It helps make questions specific. It does not determine the outcome of an audit or claim.

That's the entire game. The operations that handle audits and claims calmly aren't luckier or more honest than the ones that dread them. They're just defended — they built the record before anyone asked for it, so a challenge becomes a lookup instead of a fire drill.

What "defensible" actually requires

A folder or spreadsheet may contain important evidence. To make it easier to review, consider four properties:

• Contemporaneous. Preserve when each source was created. Keep that distinct from when it was received or organized into a packet.
• Complete. Check the available sources against the documented requirements. Keep missing or unclear information visible.
• Tamper-evident. Preserve originals and document changes and review decisions. State which integrity checks were actually performed; a label alone does not prove authenticity.
• Retrievable. Organize the sources and their references so a reviewer can find them. Confirm the receiving party’s format and submission requirements.

What reconstruction can and cannot do

Reconstruction can connect existing records to a documented requirement. It cannot manufacture a missing source or turn an unconfirmed account into verified evidence. Preserve original dates and distinguish them from the later assembly and review history.

It's the same failure that sinks disaster-recovery reimbursements. In a 2025 FEMA appeal, an applicant tried to support its costs with a general ledger produced for the appeal; FEMA found it couldn't validate the costs or tie them to eligible work, and the money came out. The work had been done. The record, built late, couldn't defend it. (We unpack that case in more detail in why FEMA claws back reimbursement you already earned.)

The tax you pay for being undefended

Being undefended doesn't only cost you the disputes you lose. It costs you the ones you settle to avoid the risk, the backcharges you can't contest, the liability exposure you can't quantify, and the unbudgeted hours your best people burn reconstructing the past instead of running the work. An operation without defensible records pays a quiet tax on every challenge — whether or not it was in the right.

The way out isn't to argue better. It's to stop treating documentation as a compliance chore and start treating it as your defense layer — built continuously, in the background, as the work happens. Do that, and the next audit or claim isn't an emergency. It's a file you open.

Source: FEMA, Public Assistance appeal decision, 2025.