How Public Adjusters Take On More Fire Files Without Hiring

Ask a public adjuster why they turned down work after a major fire and you will rarely hear "the claims weren't good." You will hear that they could not document them fast enough.

The arithmetic of the ceiling

A total-loss residential fire claim contains roughly 1,500–3,000 discrete personal property items. Documenting one properly means identifying each item, establishing quantity and condition, researching a current replacement value, sourcing that value, and organizing the result by room into a submittable schedule.

Done manually and honestly, that is 40–80 hours per file. A skilled contents specialist working full time completes somewhere between one and two total-loss inventories per week.

Contents staff	Total-loss files documented / month	Annual capacity
1	4–8	~50–95
3	12–24	~145–290
6	24–48	~290–575

Now overlay reality: fire losses are not evenly distributed across the year. They arrive in clusters. When 700 structures burn in one county over one weekend, the addressable market in your territory multiplies overnight and your capacity does not move at all. The firms that capture that work are the ones whose documentation throughput is not tied to headcount.

Why hiring into the surge rarely works

The instinct is to staff up. It usually disappoints, for reasons that are structural:

• Timing mismatch. Hiring, onboarding, and training a contents specialist to competence takes 60–90 days. The surge is happening now, and ALE clocks are already running on the files you're being called about.
• Consistency risk. New documenters produce variable methodology. On a single file that's a quality issue; across a cohort it's a credibility issue, because opposing counsel will find the inconsistency and argue from it.
• The cliff. Surge headcount becomes fixed overhead six months later when volume normalizes. Firms that staffed for the 2025 season and carried that payroll into a quiet stretch remember it clearly.

Three ways firms actually break the ceiling

1. Separate scoping from documentation

The two tasks require different skills and are usually performed by the same person, which is why both go slowly. Scoping — being on site, reading the loss, knowing what to look for and what the carrier will contest — is senior judgment that cannot be delegated. Documentation — turning a visual record into a sourced, priced, organized schedule — is production work.

Split them. Your adjusters capture the record and set strategy. Documentation runs in parallel elsewhere. The senior hour goes to the part that only a senior can do.

2. Standardize the deliverable format before volume arrives, not during

Every file should produce the same column structure, the same room taxonomy, the same sourcing convention, the same file naming. This sounds like housekeeping. It is actually leverage: standardized output is reviewable in a fraction of the time, comparable across files, and — when you are handling a cohort from a single event — defensible as a body of work rather than as a stack of individually-argued documents.

3. Move contents to variable cost

Outsourced documentation converts a fixed salary into a per-file cost that scales up during a surge and disappears when volume drops. The economics only work if three conditions hold: turnaround is fast enough not to become the new bottleneck, quality is defensible enough that you would put your own name on it, and cost is a small enough fraction of recovered value that it never changes whether you take a file.

The test for any contents solution: does it change which files you can say yes to?

What to demand from an outsourced documentation partner

1. Turnaround under 72 hours, held during a surge. A vendor whose capacity collapses in exactly the week you need it has not solved your problem; they have relocated it.
2. Live source URLs on every line. If you cannot click through to the price, you cannot defend it, and you will end up re-doing the research yourself.
3. Structured data, not a flat PDF. You need to sort, filter, re-price, and export. A locked report is a dead end.
4. Xactimate-compatible output. The schedule has to speak the language the carrier already reads.
5. Item-level visual traceability. Each line should point back to the photo or record it came from, location-tagged.
6. White-label option. The deliverable goes out under your firm's name. Your client hired you.
7. A free sample on a live file. Not a canned demo deck — your claim, their output, before any commitment.

The margin case

Contents documentation priced at under 1% of recovered value sits inside the fee on essentially any file. The relevant comparison is not vendor cost versus doing it in-house — it is vendor cost versus the files you decline, and versus the documented value that never makes it onto the schedule because the person building it ran out of hours.

A firm carrying 40 fire files a year that could carry 90 is not fee-constrained. It is throughput-constrained. That is a solvable problem.