Bottom Line Up Front
Guidewire was built for carriers, not for the people fighting them. If you’re running your PA practice on a system designed around insurer workflows — or worse, on spreadsheets and a shared drive — you’re leaking claims, follow-ups, and revenue you can’t see until the aging report tells you it’s already gone. The firms scaling past a one-person book have already made the switch to platforms built around the PA workflow: intake, scope, submit, supplement, negotiate, close.
The Claims Lifecycle for PAs
Every claims management decision you make should map back to how a claim actually moves through your shop — not how a carrier’s claims system thinks about it.
FNOL intake and initial assessment is where you qualify the claim before you commit resources. You’re looking at policy language, deductible thresholds, coverage type (Coverage A/B/C/D), and whether the loss clears the bar for a representation agreement. A weak intake process means you’re signing clients whose claims never should have made it past your desk.
Documentation and evidence gathering starts the moment you’re on site — not after the carrier’s IA has already been through. Your file needs to establish the loss independent of the carrier’s version of events.
Scope of loss and estimate preparation is where your Xactimate or Symbility line-item estimate either holds up to desk review or gets picked apart line by line. This is your leverage document.
Carrier submission and the supplement cycle is where most firms bleed time. A clean initial submission reduces round-trips, but supplements are a normal and expected part of the process — treat them as a discipline, not a failure.
Negotiation, appraisal, and resolution is where your file quality and your follow-up cadence either earn you a fair settlement or force you into the appraisal clause.
Settlement, fee collection, and file closing should be the fastest part of your lifecycle, but it’s often where firms lose track of depreciation holdback releases and let receivables age past when they should’ve been collected.
Building a Pipeline That Doesn’t Leak
If you can’t see your pipeline in stages, you’re managing by memory — and memory doesn’t scale past a handful of active files.
Visual pipeline stages should mirror your actual workflow, not a generic CRM template: New Lead → Signed Rep Agreement → Documentation → Scope Submitted → Carrier Response → Supplement → Negotiation → Appraisal (if needed) → Settled → Closed/Paid. Anything more granular than that and your team stops updating it.
Tracking by status, claim value, and carrier response time turns your pipeline into a forecasting tool instead of a to-do list. When you pull your aging report, you should immediately see which claims are past your internal SLA for carrier response — not discover it three weeks later on a phone call.
Follow-up cadences need to be aggressive enough to keep files moving but disciplined enough that you’re not burning goodwill with the desk adjuster. A good baseline: initial submission follow-up at 10 business days, then every 7-10 days until you get a substantive response, escalating to a written demand if you hit 30 days of silence.
Identifying bottlenecks means knowing whether your claims are stalling at intake (documentation gaps), at submission (weak scopes getting kicked back), or at carrier response (a specific desk adjuster or carrier sitting on files). Your pipeline data should tell you which one it is without you having to dig through individual files.
Escalation to appraisal or attorney referral should be a defined trigger in your workflow, not a gut call made in frustration after a bad phone call with a carrier.
| Bottleneck Stage | Common Cause | Fix |
|---|---|---|
| Intake | Weak qualification criteria | Tighten rep agreement thresholds; qualify coverage before signing |
| Documentation | Field team inconsistency | Standardize photo/video checklist per peril type |
| Scope submission | Estimates kicked back on desk review | Build Xactimate templates by loss type; peer-review before submission |
| Carrier response | Desk adjuster inaction or lowball | Escalate on defined SLA; document every contact |
| Negotiation | No leverage documentation | Strengthen file with third-party technical evidence |
| Settlement | Fee collection lag | Automate invoicing tied to depreciation release |
Documentation That Wins Negotiations
Carriers argue with opinions. They have a much harder time arguing with a well-documented record.
Photo and video standards mean wide shots for context, close-ups for damage detail, and a consistent shot list across every claim so your field team isn’t improvising. Timestamp everything and shoot before any emergency mitigation disturbs the scene.
Moisture mapping, thermal imaging, and technical evidence move a water claim from “he said, she said” to an objective record a carrier’s engineer can’t easily wave off. On larger losses, this technical documentation is often what separates a clean settlement from a drawn-out fight.
Writing scopes of loss in Xactimate that withstand desk review means matching your line items to your photo documentation, applying O&P correctly when multiple trades are involved, and addressing matching issues on the front end instead of waiting for the carrier to raise them.
Organizing claim files for instant retrieval matters most when you’re on a call with a carrier and they’re disputing a line item — you need the photo, the moisture reading, and the estimate note pulled up in seconds, not five minutes of digging through folders.
Audit-ready records aren’t optional. Every communication, every submission, every carrier response needs to be logged and retrievable — this is your E&O protection as much as it is your negotiation tool.
Carrier Communication Strategy
Your file wins the claim. Your communication strategy determines how fast and how cleanly you get there.
Demand letters that move the needle cite specific policy language, reference your line-item estimate directly, and set a clear, reasonable deadline for response. Vague demands get vague responses.
The follow-up cadence should be persistent without becoming noise — carriers deprioritize adjusters who call daily with nothing new to add, and they also deprioritize adjusters who go quiet for a month. Consistency, not frequency, builds pressure.
Your CYA file is built from documenting every interaction — call logs, emails, submission confirmations, adjuster names and IDs. If a claim ends up in a bad-faith conversation or a DOI complaint, this file is your record.
Recognizing bad faith indicators — unreasonable delay, failure to communicate a basis for denial, lowballing without a written explanation — means preserving the record in real time, not reconstructing it after the fact. Unfair claims settlement practices standards vary by state, so know what your state’s statute actually requires before you characterize carrier conduct that way.
Invoking the appraisal clause is appropriate when you and the carrier disagree on the amount of loss and negotiation has genuinely stalled — not as a first move, and not as a substitute for a well-built file. Appraisal doesn’t resolve coverage disputes, only valuation disputes, so make sure that’s actually what you’re fighting about before you invoke it.
Technology and Automation
The spreadsheet trap is real, and it’s the single biggest ceiling on firm growth. A spreadsheet doesn’t remind you a carrier deadline is approaching. It doesn’t trigger a follow-up. It doesn’t give your client visibility into their own claim.
Claims management platforms built for PAs — as opposed to generic CRMs or carrier-side systems like Guidewire — track your pipeline, your documents, and your deadlines in one place, purpose-built around the PA workflow instead of retrofitted from something else.
Automated status updates, reminders, and carrier follow-up triggers are what let you run more active files per adjuster without dropping any of them. This is the infrastructure that turns a solo practice into a scalable firm.
Mobile access matters because your documentation happens in the field, not at a desk — your platform needs to let your team upload photos, moisture readings, and notes on-site, in real time.
Policyholder portals eliminate the majority of “what’s happening with my claim?” calls by giving clients real-time visibility into status, without your team having to field the same phone call repeatedly.
Integration with Xactimate, Symbility, and your document management system means your scope, your file, and your pipeline stay connected instead of living in three disconnected systems.
| Approach | Pipeline Visibility | Automated Follow-Up | Policyholder Visibility | Scalability |
|---|---|---|---|---|
| Spreadsheets + shared drive | Low | None | None | Breaks down past a handful of adjusters |
| Generic CRM | Moderate | Generic, not claims-specific | Limited | Requires heavy customization |
| Carrier-side systems (e.g., Guidewire) | Built for insurer workflows | Not built for PA-side tracking | Not applicable | Not designed for PA use case |
| Purpose-built PA platform (e.g., ClaimFlow) | High, stage-based | Deadline and status triggers | Real-time client portal | Built to add claims without adding headcount |
ClaimFlow was built specifically to close this gap — pipeline tracking, automated carrier follow-ups, a policyholder portal, and Xactimate integration in one system, rather than the patchwork most firms are running today.
Metrics That Matter
If you’re not tracking these numbers, you’re running your firm on instinct.
Average settlement per claim tracked over time shows you whether your negotiation leverage — your documentation quality, your escalation discipline — is actually improving, or whether you’re settling the same way you did years ago.
Claims cycle time — FNOL to closed file — is a direct measure of operational efficiency. Top-performing firms keep average cycle time tight by controlling the variables they can control: documentation speed, submission quality, and follow-up discipline.
Pipeline value and projected revenue should be visible at a glance from your aging report — total active claim value, weighted by stage, gives you a real forecast instead of a guess.
Supplement approval rate is the metric most PAs never track, and it shouldn’t be. A low approval rate usually points to weak initial documentation or scopes that don’t hold up — fix the front end and your supplement cycle gets shorter and more successful.
As a general operating benchmark, most healthy PA practices target somewhere in the range of 15-20 active claims per adjuster — enough volume to sustain revenue without so much that file quality and follow-up discipline start slipping.
FAQ
Is Guidewire something a public adjuster should even be trying to use?
No. Guidewire is carrier-side claims infrastructure built around insurer workflows, underwriting integration, and policy administration — it’s not designed for the PA side of a claim at all. When PAs ask about “alternatives,” they usually mean platforms built specifically for the intake-to-settlement workflow a public adjuster actually runs.
What should I look for in a claims management platform if I’m scaling past a solo practice?
Prioritize stage-based pipeline visibility, automated carrier follow-up triggers, a policyholder portal, and integration with Xactimate or Symbility. If a platform can’t show you claim aging and supplement status without you manually digging through files, it won’t scale with you.
How do I know if my claims are stalling at documentation or at the carrier?
Pull your pipeline by stage and look at how long claims sit at each one relative to your internal benchmarks. If files are piling up before submission, it’s a documentation or scope-writing problem; if they’re piling up after submission with no carrier response, that’s a follow-up and escalation issue.
When should I move from negotiation to invoking the appraisal clause?
When the dispute is genuinely about the amount of loss, not coverage, and continued negotiation has stopped producing movement despite a well-documented file and a clear demand. Don’t invoke appraisal as a shortcut around building your case — a stronger file often resolves the dispute before appraisal becomes necessary.
What’s a reasonable benchmark for supplement approval rate?
There’s no universal number, since it varies by claim complexity and carrier, but a consistently low approval rate is a signal to audit your initial scope quality rather than accept it as normal. Firms that document thoroughly and write tight, well-supported line-item estimates up front tend to see meaningfully higher approval rates on supplements.
Conclusion
The firms outgrowing their competitors aren’t necessarily the ones with better negotiators — they’re the ones who’ve built operational infrastructure that keeps every claim moving, every deadline tracked, and every client informed without adding headcount for each new file. That’s the difference between a practice that scales and one that plateaus at whatever a single adjuster can hold in their head.
If you’re still running your pipeline out of spreadsheets, shared drives, and memory, you already know where the leaks are — you just haven’t quantified them yet. ClaimFlow was built for exactly this: pipeline and claim tracking, automated carrier follow-ups, document and photo management, a real-time policyholder portal, and integrations with the tools you’re already using like Xactimate. It’s the infrastructure thousands of public adjusters — from solo practitioners to multi-state firms — are running their practices on today. Start a free 14-day trial or book a demo and see what your pipeline looks like when nothing falls through the cracks.
This article is for general operational guidance and does not constitute legal advice. Claims handling requirements, licensing rules, fee structures, and unfair-claims-settlement-practices statutes vary by state — consult your state Department of Insurance or licensed counsel for guidance specific to your practice and jurisdiction.