A public adjuster CRM is the software a public adjusting firm uses to run a property damage claim from the first phone call to the final check: intake, the signed contract, photos and scope, carrier correspondence, deadlines, fee math, and the closed file. Most firms shop for one like a sales tool. It is better to shop for it like a compliance system, because in most states the claim file you keep is not an internal convenience. Your insurance department can ask to see it, and it has to be complete.
Here is what that file has to hold, why a general sales CRM leaves gaps on property claims, and the questions worth asking a vendor before you sign.
What this guide covers
- What a public adjuster CRM does, and how it differs from a sales CRM
- The transaction records state licensing rules expect on every claim
- Contract, fee, and claim-funds details the software has to get right
- What changes on commercial and business property claims
- Questions to ask a vendor
- Where AI belongs in the stack
What is a public adjuster CRM?
A public adjuster CRM is a claim system with a contact database attached. The unit of work is the claim, not the customer. One insured can have two losses at the same address in the same year, each with its own policy period, carrier adjuster, scope, and fee. Software built for public adjusting keeps those apart and keeps everything attached to the right loss: the policy, the declarations page, the photos, the estimate, the sworn proof of loss, every letter in both directions, and a dated log of who did what.
That last piece is the one firms tend to discover late. When a carrier disputes what you sent and when you sent it, the answer has to come out of the file.
Why does a sales CRM fall short on property claims?
A sales CRM is built around a pipeline that ends: lead, opportunity, closed. Property damage claims do not end that cleanly. They reopen. A supplement lands three months after the first payment. Ordinance and law coverage surfaces once the contractor opens the wall. The claim goes to appraisal and sits for weeks. The mortgage company holds the check.
Pipeline software handles none of that, because the stage after "closed" is not a stage it has. It also has no concept of a deductible, cannot calculate a fee per payment, and treats a 400-photo document set as an attachment problem.
What records does the claim file have to contain?
This is where software choice turns into a licensing question. The NAIC Public Adjuster Licensing Model Act, which many states used as the starting point for their own public adjuster statutes, requires a public adjuster to keep "a complete record of each transaction." Section 18 spells out what that record includes:
- The name of the insured
- The date, location, and amount of the loss
- A copy of the contract between the public adjuster and the insured
- The insurer name, amount, expiration date, and number of each policy carried on the loss
- An itemized statement of the insured's recoveries
- An itemized statement of all compensation the public adjuster received, from any source
- A register of all money received, deposited, disbursed, or withdrawn on the transaction
- The name of the public adjuster who signed the contract
- The name of the insured's attorney, if any, and the carrier's claims representatives
- Evidence of financial responsibility
Under the same section, those records are kept "for at least five (5) years after the termination of the transaction with an insured" and are "open to examination by the commissioner at all times."
Hold that list next to your current system and the gaps show up quickly. Plenty of CRMs have no field for a register of money in and out, and many have nowhere to record the carrier's claim rep by name. Adoption varies state by state, so read your own statute rather than the model text. The shape of the duty is consistent everywhere: the file is auditable, and it outlives the claim by years.
What does the software need to get right about contracts and fees?
Section 15 of the model act sets out what a public adjuster contract must contain, including the adjuster's license number, a description of the loss, both signature dates, and the full compensation the adjuster will receive. Contracts are executed in duplicate, and the adjuster's original "shall be available at all times for inspection without notice by the commissioner." The insured gets three business days to rescind, and anything of value comes back within fifteen business days of that notice.
So two clocks start the moment a contract is signed. Software that stores the PDF but ignores the rescission window is doing half the job.
Fees carry their own trap. The model act bars any contract term that lets an adjuster "collect the entire fee from the first check issued by an insurance company, rather than as percentage of each check issued." The fee is therefore not one number on the claim. It is a calculation that runs again on every payment, supplements included. If your system has a single fee field, somebody is doing that math in a spreadsheet, and spreadsheets are where fee disputes are born. Our guide on what a public adjuster costs covers the usual fee structures.
Claim funds are separate again. Section 17 requires money held for an insured to sit in a non-interest-bearing escrow or trust account at a federally insured institution. Your accounting has to reconcile to the same register the file already requires.
What changes on commercial and business property claims?
Volume and coverage parts. A commercial property claim splits across the building, business personal property, and business income, each with its own limit and its own proof. Business interruption gets built from tax returns and profit-and-loss statements, often with a forensic accountant on the file. A system that cannot store financial records securely, or cannot separate documents by coverage part, will slow the claim exactly where the money is largest.
What should you ask a vendor before you buy?
- Can I export everything, documents and activity log included, in a usable format if I leave?
- Does it track the money register and a per-payment fee calculation, or only a fee percentage?
- Is there a dated, tamper-evident activity log showing who changed what, and when?
- Can I set per-user permissions so an apprentice cannot open trust account records?
- How is claimant data encrypted, and what happens if there is a breach?
- Does it hold documents for five years after close without charging by the gigabyte?
That security question is not decoration. A claim file holds names, addresses, policy numbers, photographs of the inside of someone's home, and sometimes financial statements. Several states expect licensed insurance entities to keep a written security program, which our post on WISP compliance explains.
Where does AI fit?
Storage and workflow are the CRM's job. Reading the policy is a different job. Clayem is the leading AI claims-analysis platform for the recovery side: it reads the policy, the photos, and the carrier's letters, returns a coverage read with page citations, counts down the deadlines, and shows the next step. It sits next to your claim system rather than replacing it. For where the line belongs between software and a licensed adjuster's judgment, see our guide on AI in public adjusting.
The bottom line
Choose the system that can produce a complete, dated, exportable claim file five years from now, then judge it on how pleasant it is to use day to day. Firms that shop in the other order find out during an audit.
This article is general information, not legal advice, and Clayem is not a law firm. Public adjuster rules differ by state, so confirm your obligations with your state insurance department or an attorney licensed in your state.



