Building a Claims File Before You Ever Need One

Why this matters

The shops that come out of a claim against them cleanly are almost never the ones that scramble to remember details after the fact. They are the ones with a habit of documenting jobs, incidents, and near-misses as a matter of routine, long before any specific claim exists. When something does happen, that habit turns into a file that supports your position instead of a memory that fades and gets picked apart. Building this habit costs a few minutes a week. Not having it costs a claim you cannot fully defend.

Step 1: Decide what gets a record, not just the big stuff

Most owners only think to document the obvious incidents: an injury, a fire, a major property loss. But the file that actually protects you includes the small and the near-miss too.

• Every incident involving injury, no matter how minor it seems at the time.
• Every incident involving property damage, including damage the customer says "not a big deal, do not worry about it." Document it anyway; opinions change.
• Near-misses: a ladder that slipped but no one was hurt, a fitting that let go before anyone was in the splash zone, a customer who seemed upset but did not file a complaint. These are free information about where your risk actually lives.
• Any interaction where a customer, subcontractor, or bystander expresses a concern about safety or damage, even informally.

Step 2: Capture the same core facts every time

Consistency is what makes a file useful under scrutiny. Build a habit around the same short list every time, so nothing depends on memory later:

1. Date, time, and location.
2. Who was involved: your crew, the customer, any subcontractor, any third party.
3. What happened, in plain factual language. Describe what you observed, not your interpretation of who was at fault.
4. Photos, taken before anything is moved, cleaned, or repaired.
5. Who was notified and when (the customer, your office, your broker).
6. What was done immediately after (first aid rendered, area secured, work stopped).

Write the account the same day. Details that feel obvious in the moment blur within a week and are gone within a month.

Step 3: Separate the incident log from the general job notes

A jobsite photo dropped into a general job file is easy to lose track of later. Keep a separate incident log, even a simple one, that any office staffer can pull up and search by date, customer, or crew member. The goal is that six months from now, when a claim surfaces, you can find every relevant fact in minutes, not by trying to remember which job it was and scrolling through unrelated photos.

Step 4: Report to your broker or carrier as a routine step, not a last resort

Many owners hesitate to report anything that has not become a formal claim yet, worried about the effect on their premium. This usually gets the risk backward. See related: What Raises Your Premium and What Doesn't. Reporting an incident promptly, even one that never turns into a paid claim, does two things:

• It puts your carrier on notice while facts are fresh, which strengthens your position if the situation develops later.
• It creates a paper trail showing you acted responsibly and promptly, which matters if a dispute ever arises over how quickly you responded.

Waiting to report until you are sure it will become "a real claim" means reporting late, with a weaker file, on the exact incidents most likely to actually cost you.

Step 5: Keep certificates, contracts, and permits in the same discipline

A claims file is not just incident records. It is also:

• Current, verified certificates of insurance for every subcontractor you use. See related: The Certificate of Insurance a Customer or GC Asks For.
• Signed contracts and scopes of work, which define what you agreed to do and what you did not.
• Permits and inspection records, which show the work was done under proper oversight.

When a claim touches a job, the adjuster or attorney on the other side will ask for all of this. Having it organized and ready is the difference between a claim that resolves in weeks and one that drags for months while you dig through old emails.

Step 6: Review the file periodically, not just when something happens

Set a recurring habit, monthly or quarterly, to skim the incident log for patterns. Three near-misses on the same type of job, or two minor injuries with the same root cause, are a signal to fix a process before it becomes a real claim. This is the same discipline that keeps your experience modifier and claim frequency low over time, not just your individual claim outcomes clean.

References

• OSHA recordkeeping requirements for workplace injuries (29 CFR 1904) as a model for consistent incident documentation
• Insurance Information Institute, small business claims reporting guidance
• See related: What Raises Your Premium and What Doesn't, The Certificate of Insurance a Customer or GC Asks For