A Filing System for an Independent Insurance Agency
Every agency has a filing system. Most of them exist as an agreement between the two people who have been there longest, and neither of them can say what happens to a certificate for a policyholder who is also a claimant on somebody else’s claim.
The short answer
An independent agency files in three levels: the policyholder, then the policy under them, then the claim under the policy. Documents that belong to the relationship rather than to any one policy — the application, correspondence, signed authorisations — sit at the policyholder level, and everything else sits under the policy or claim it concerns. A workflow makes the structure hold: the Read Details from File step identifies the policyholder and the policy or claim number from each document, and the Move step files it accordingly, so the structure is applied at the moment a document arrives rather than remembered by whoever saves it.
Steps this uses
Before and after
What actually changes
As they arrive
- app signed.pdf
- Scan_0203.pdf
- dec page.pdf
- endorsement FINAL.pdf
After the workflow
- Harlan Freight/2026-02-11-application-signed.pdf
- Harlan Freight/GL-88213/2026-03-01-declarations.pdf
- Harlan Freight/GL-88213/2026-07-19-endorsement-added-vehicle.pdf
- Harlan Freight/GL-88213/CLM-4471/2026-08-14-loss-notice.pdf
One policyholder, one policy, one claim — the same four documents, filed at the level each of them actually belongs to.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When a policy document arrives by email or upload, save a copy, read the policyholder and the policy or claim number off it, and file it under the policyholder, then the policy, then the claim. Ask me about anything it cannot place.
Three levels, and no more
Policyholder, then policy, then claim. A fourth level is where filing systems go to die — somebody adds one, nobody else knows the rule, and within a month the same document type lives in two places.
Decide what sits at the top
Documents about the relationship rather than a policy: applications, signed authorisations, correspondence, the agency agreement. If it would survive the policyholder changing carriers, it belongs at the policyholder level.
Describe it once
You say the structure in plain English rather than building the folder tree by hand. The same description is what the workflow applies to each document it files.
Gate the ambiguous cases
A document naming two parties — a certificate where your policyholder is the vendor on somebody else’s job — is exactly where a filing system gets it wrong. The Ask a Person to Approve step stops on those and shows where the file is about to go before it goes there.
Why three levels and not four
Each level you add is a decision somebody has to make correctly every time they file something, and the decisions compound. Policyholder, policy, claim maps onto how an agency already talks about its work, so the filing decision is one most people make right without being told. A fourth level — by document type, by year, by producer — is a rule that has to be taught, and the first person who was not taught it starts a second convention.
The document that belongs in two places
A certificate naming your policyholder as a vendor on another insured’s job legitimately relates to both. Filing it twice means two copies that will disagree. The workable rule is that it files under the policy it is issued against, and the other party finds it by searching rather than by browsing — which works as long as search reads the contents of documents and not just their names.
What this does not solve
A filing structure makes documents findable. It does not tell you a policy is under-insured, that a renewal is unquoted, or that a producer has not touched an account in a year. Those live in an agency management system, and this sits alongside one rather than standing in for it.
FAQ
Common questions
How should an insurance agency organize its files?
In three levels: the policyholder, the policy under them, and the claim under the policy. Documents about the relationship rather than a specific policy — applications, signed authorisations, correspondence — sit at the policyholder level. Name documents date-first in ISO form so each folder reads chronologically.
Should files be organized by policyholder or by policy number?
By policyholder first, then policy number underneath. A policyholder usually holds more than one policy and keeps holding them as policies renew and change number, so the person is the stable thing and the policy number is not. Filing by policy number at the top level scatters one client across the drive.
Where does a document that relates to two policyholders go?
Under the policy it was issued against, once. Filing it in both places creates two copies that drift apart as one gets updated. The other party finds it through search, which works when search reads what is inside documents rather than only their filenames.
Does an agency have to move its files to do this?
No. The structure is applied in the cloud storage the agency already uses — Google Drive, OneDrive, SharePoint or Dropbox — and documents are renamed and moved in place. Links and permissions are unaffected because the files never leave the storage they were in.
Policyholder, policy, claim.
A structure applied when documents arrive, not remembered by whoever files them.
5 GB free · No credit card required