Public adjuster software and CRM: what to look for

A public adjuster’s work is a long chain of small obligations: a notice sent on time, a photo labeled correctly, an estimate line questioned, a call logged, a payment tracked. Software cannot do the work for you, but the right system keeps the chain from breaking when dozens of files are open at once. This guide describes the workflows a claims-focused CRM should cover, so you can judge any product, from a general project tool to purpose-built claims software, against what your practice actually needs.

How a claims CRM differs from a sales CRM

A typical sales CRM tracks contacts and deals moving through a pipeline. That is part of what a public adjusting firm needs, but only the first part. Once a prospect signs, the unit of work becomes the claim: a file with a loss date, a policy, a carrier, a claim number, a set of deadlines, a pile of evidence, one or more estimates, a stream of correspondence, and eventually a payment history. A claims CRM keeps all of that attached to one record, so anyone on the team can open the file and understand where it stands without asking the person who opened it.

That distinction should guide your evaluation. A tool with beautiful sales dashboards and no way to attach a policy, track a proof-of-loss deadline, or compare two estimates will leave you maintaining a second system for the real work. Conversely, a claims tool with weak contact handling will make intake awkward. Start by writing down the path one claim takes through your firm, from first call to closed file, and mark each point where information is created, handed off, or at risk of being lost. Those points are your requirements, and they matter more than any feature list a vendor presents.

Intake and lead capture

Intake is where a good file begins. The system should let you capture the essentials quickly, ideally while you are still on the phone: contact details, property address, date and type of loss, carrier and policy number, claim number if one exists, and the current status of the claim. Structured fields beat free-text notes, because they let you search and report later. Look for the ability to record where each inquiry came from, so you can see which channels produce clients you can actually help, and for a simple pipeline that shows every inquiry’s stage from first contact to signed contract or polite decline. Our guide to the public adjuster claim process shows the stages a file moves through, which makes a useful template for your own pipeline.

Consent and privacy belong in this conversation too. If inquiries arrive through a directory, a web form, or a referral, the system should record how and when the person asked to be contacted, so you can show that your outreach was invited. Be wary of any tool that encourages bulk texting or calling of lists of people who never asked to hear from you, since telemarketing rules and your state’s solicitation rules may restrict that, and confirm the current rules with your state’s department of insurance. A good intake process also records the honest outcome when a claim is not a fit, whether because it is too small, already resolved, or better suited to another professional.

Document and photo management

Documents are the raw material of a claim, and a public adjuster handles more of them than almost anyone. A good system stores each file against its claim, lets you sort by category such as policy, correspondence, estimates, invoices, and proof of loss, and keeps a version history so you can tell which draft was sent. Our guide to the documents a public adjuster needs lists the records a file typically requires, and your software should make it easy to see at a glance which ones you have and which are missing.

Photos and video deserve special attention. Damage evidence is most persuasive when it is organized by room or area, dated, and labeled, as our guide to documenting damage with photos explains. Look for tools that preserve original files, capture date and location information where available, and let you annotate copies without changing the originals. Check the practical details: upload from a phone in the field, handling of large files, search by label, and the ability to assemble a clean packet for a carrier or a client. Ask how uploaded files are checked for malicious content, since claim files pass between many parties, and how long the vendor retains them.

Estimate comparison and supplements

The heart of many claims is the gap between what the carrier offered and what the repair will cost. Estimating itself is usually done in dedicated estimating software, and our guide to reading an Xactimate estimate explains the line-item format carrier adjusters commonly use. What a claims CRM can add is the ability to hold the carrier’s estimate and yours side by side for the same claim, show variance line by line or by category, and keep revisions as they happen. Seeing whether a difference is concentrated in scope, in pricing, or in overhead and profit tells you where to focus your argument.

Look for support for supplements, meaning additional amounts requested when hidden damage is found or the first estimate missed items, and for a way to record the reason for each change. Our guide to comparing insurance and repair estimates describes the differences homeowners are advised to look for, and a good tool helps you present them clearly. Be skeptical of any product that claims to calculate automatically what a claim is worth. Estimates depend on professional judgment, local costs, policy terms, and the facts of the loss, and software that implies otherwise is overpromising.

Tasks, deadlines, and calendars

Missed deadlines hurt clients and expose firms, so deadline tracking is not a nice-to-have. Policies and statutes set time limits for notice, proof of loss, responses to carrier requests, and suit, and many states set response expectations for carriers as well. Your system should let you create dated tasks attached to a claim, assign them to a person, set reminders in advance, and surface everything overdue or due soon across all claims in one view. Recurring tasks, such as a periodic status check with the carrier, should be easy to set up.

Appointments belong in the same place: inspections, carrier re-inspections, and client meetings. Calendar integration helps as long as it works the way your team does, so test it rather than trusting a feature list. Templates for common claim types can save time, since a roof claim and a fire claim carry different steps, and a checklist that appears automatically reduces the chance of forgetting one. Be realistic about automation. Reminders and checklists help people, but they do not know the particular deadline in your client’s policy or your state’s rules, so someone must still enter the right date, and the software should make that date visible and hard to miss.

A client portal and clear communication

Policyholders in a long claim want to know what is happening, and many complaints about public adjusters come down to poor communication. A client portal gives them a place to see the status of the claim, upload documents, read and answer messages, and see what you are waiting on. It also gives you a record, because communication that lives in a portal is findable later, unlike a text thread on a personal phone. Check that the portal is easy enough for a stressed, non-technical person, that it works on a phone, and that it does not make them build something complicated just to see a document.

Look closely at permissions. You may need to share a claim with a spouse, a co-owner, a mortgage company, a contractor, or a second professional, and each should see only what they need. Scoped, revocable access is better than sharing a login. Keep carrier communication organized too: log every call and email, store letters, and be able to find what was said and when. If your state or your contract requires particular notices or updates to clients, build them into your task list. Clear, regular communication, documented in the file, is among the best defenses against disputes.

Settlement and fee tracking

A claim ends in money, and money tracking needs to be exact. Look for a ledger that separates the categories that tend to get blurred: payments received from the carrier, amounts for building repairs, contents, and additional living expenses, supplements, recoverable depreciation released later, prior payments, the policyholder’s deductible, expenses, and your fee. Keeping them distinct protects the client and you, because a single running total hides errors. Your fee depends on your contract and your state’s rules, which may cap it, so the software should calculate from the contract terms you enter and show the arithmetic instead of hiding it. Check how it handles partial payments, reissued checks, and fees on recoverable depreciation, and confirm the rules for each with your state’s department of insurance, because they vary.

Confirm how your state treats claim payments as well. Some states restrict whether a public adjuster may handle proceeds at all, and others require fiduciary accounts and specific records. Software can track what happened, but it does not create compliance. If you do handle client funds anywhere, keep them in the account your state requires, reconcile it regularly, and ask whether your system can export the records a regulator might want to see. Outcome reporting is useful too. Looking back across closed files at how long they took, how carrier offers compared with final payments, and which claim types you serve best gives you a factual picture of your practice, without any need to claim that you outperform anyone.

Audit trail, security, and choosing a vendor

An audit trail is a record of who did what and when: who opened a claim, who changed a deadline, who edited an estimate, who viewed or downloaded a document, and who was granted access. It protects you in a complaint or a dispute, since you can show exactly what happened, and it protects clients, since it discourages careless or improper access. Look for records that cannot be quietly edited after the fact, for role-based permissions that limit what each team member can see and do, and for the ability to review the log when you need to.

Security matters because claim files hold personal, financial, and property information. Ask vendors how data is encrypted in transit and at rest, how access is controlled, how backups work, how incidents are handled, and where data is stored. Ask what happens to your data if you leave: can you export every file and record in a usable form, and does the vendor delete it when you ask? Many states have adopted insurance data security rules based on a model law from the NAIC, so ask your department of insurance whether and how they apply to licensees like you. Do not rely on marketing claims. Ask for written answers, and check references from firms of your size.

A note on our own product: Adjusterio is mainly an independent directory for property owners and public adjusters, but it also offers a firm workspace for adjusters, described on the software page, covering claims management, document organization, estimate comparison, tasks, a client portal, and an audit trail. We mention it because it is relevant to this topic and because we have an obvious stake in it, so treat our description as one input rather than a recommendation. You can open the demo with sample data, judge it on what is live today rather than on roadmap items, and hold it to the same checklist you would use for any other product. A short pilot with one or two real files, not a feature demo, is the best way to find out whether any tool fits your firm.

Whatever you choose, plan the move. Migrating files from a spreadsheet or an older system takes time, so start with new claims, keep a copy of the old records for the period your state requires, train everyone who will use it, and revisit the decision after a few months. If you are still building the firm itself, our guide to starting a public adjuster business puts software in context with licensing, insurance, and contracts.