Claim File Management Guide
Principles for organizing claim files across an operation — naming, structure, ownership, status, retention — and how to tell whether your current system is actually working.
The test
There is one useful test of a claim file system. Pick a file closed eight months ago, worked by someone who has since left. Can a colleague open it and answer, without asking anyone: what were we asked to do, what did we observe, what did we conclude, what did we tell the client, and when?
Most operations fail that test, and they fail it for structural reasons rather than careless ones. The information exists; it is just distributed across a mailbox, a drive, a phone's camera roll, and someone's memory.
Principle 1 — One record per claim, and it is the file
Not a folder that documents live in. A record that owns the documents, the correspondence, the photographs, the tasks, the status, and the history — so that opening the record is the complete answer rather than the first of five places to look.
Principle 2 — Identify files the same way every time
- Pick one internal reference format and never deviate from it
- Include the client's own reference as a searchable field, not as part of your identifier
- Never encode status into the identifier — status changes, identifiers must not
- Never reuse an identifier, even for a file opened in error
Principle 3 — Every file has an owner and a next action
A file without a named owner is a file nobody is working. A file without a next action is a file that will be discovered late. These two fields do more for throughput than any amount of process documentation.
Principle 4 — Status means the same thing to everyone
Status values should describe where the file is, not how someone feels about it. 'Pending' is not a status; 'awaiting policy documents from client' is. If two people would categorize the same file differently, the status set needs work.
- Keep the list short enough to remember
- Make each value mutually exclusive
- Make it obvious what has to happen to leave each status
- Record when the status last changed — an unchanged status is the earliest signal of a stalled file
Principle 5 — Different work gets different workflows
A carrier assignment, an appraisal demand, and a homeowner referral have different stages, different deadlines, and different documentation requirements. Forcing them through one pipeline means the pipeline fits none of them, and the mismatch is absorbed by people remembering exceptions.
Principle 6 — Correspondence belongs to the file
The single most common gap in claim records is correspondence that lives in an individual mailbox. It is invisible to everyone else, it leaves with the employee, and it is the first thing anyone asks for when a file is questioned.
Principle 7 — Photographs are evidence, so organize them like evidence
- Associate every photograph with a claim at capture, not afterward
- Group by elevation, roof section, and room rather than by date taken
- Preserve originals; keep annotations separate from the original image
- Never let a phone's camera roll be the only copy
Principle 8 — Decide retention before you need it
Claim files hold personal information about insureds. Decide how long you keep closed files, who can open them after close, and how they are disposed of — and write it down. Client agreements and state law may set requirements; those control.
Signals your current system isn't working
- Anyone asks 'who has the file on…' out loud
- Documents are requested twice from the same party
- Photographs are matched to files by looking at timestamps
- The count of open files depends on who you ask
- A missed deadline is discovered by the client rather than by you
- Onboarding a new hire means teaching them where things happen to be