Public Adjuster vs Carrier Adjuster Workflows

A public adjuster works for the insured. A carrier adjuster, whether staff, independent, or desk, works for the insurer. Both inspect, both estimate, and both write to the same claim, but they answer to different people and run on different clocks. The friction sits at the handoffs: reinspections, competing estimates, and documentation requests. A system that records who owns each step and what the other side asked for keeps the file coherent when the two accounts diverge.

Where the two workflows grind against each other

The two estimates get compared line by line by hand

The carrier’s estimate arrives as a PDF. Somebody prints it, prints yours, and works through both with a highlighter looking for missing scope, different quantities, and omitted trades. That comparison is redone from scratch every time either side revises.

Requests from the desk adjuster arrive through three channels

A portal message, an email to one adjuster, and a voicemail to the office. A request for the contents inventory or a sworn proof of loss lands wherever the desk adjuster prefers that day, and nothing turns it into a task with a deadline.

The joint inspection is not recorded as a joint event

Both parties walk the property the same morning. Two photo sets are taken and an understanding is reached in the driveway. Nothing in either file records who attended, what was agreed, or which conditions both observed.

Nobody records which carrier-side adjuster is currently assigned

Desk adjusters rotate, files transfer between independent adjusting firms, and a supervisor steps in for two weeks. The file still shows whoever handled the first fortnight, so the follow-up call goes to someone who no longer has it.

The insured hears two different versions of the same claim

Your status update and the carrier’s letters do not line up, because the carrier’s correspondence was never logged into the file. The insured receives a reservation of rights letter you have not seen and calls to ask what it means.

Ownership map across a claim, side by side

Each row is a step both sides participate in. The middle columns name who actually owns it, the fourth names where the two processes collide in practice, and the last names what has to exist in the file for that collision to be manageable.

Turning a carrier side request into a tracked obligationHow a documentation request arriving by portal, email, or voicemail becomes one queued object with a source, a deadline, an owner, and a date satisfied.1Request arrivesPortal, email, or avoicemail2Logged as one objectSource, date, and who itcame from3Deadline and ownersetIt appears on a list, notan inbox4Response producedThe documents the requestnamed5Date satisfiedrecordedSent, to whom, and onwhat date
Claim stepPublic adjuster side ownsCarrier side ownsWhere they collideWhat has to be recorded
Notice of lossConfirming the loss was reported and a claim number issuedAssigning the claim number and an adjusterDuplicate reports when the insured also called their agentClaim number, date reported, and who reported it
RepresentationThe executed agreement and the letter of representationAcknowledging representation and redirecting contactThe carrier still contacting the insured directly after the LORThe LOR transmission date and the carrier’s acknowledgment
Field inspectionAn independent scope with its own measurements and photo setThe field or independent adjuster’s inspectionTwo inspections on different dates showing different conditionsInspection date, who attended, and site conditions at the time
EstimatingThe insured’s estimate and the basis for each lineThe carrier’s estimate and its basisDifferences in scope, quantity, or which trades are includedA dated comparison naming which line items differ and on what basis
Documentation requestsProducing what the policy requires of the insuredRequesting proof of loss, contents inventory, receipts, or an examination under oathRequests on three channels with different deadlinesEach request with its date, source, deadline, and date satisfied
ReinspectionAttending and documenting independentlyOrdering the reinspection and setting its scopeA reinspection scheduled without the public adjuster presentWho requested it, who attended, and what changed since the first visit
PaymentConfirming what was paid against what was claimedIssuing payment and applying deductible and depreciationRecoverable depreciation released on conditions nobody trackedEach payment with its date, whether issued on an ACV or RCV basis, and what it covered
None of this changes what a carrier decides. It changes whether the file can show, on any given date, what was asked, what was sent, and who was standing in the room.

What the system has to hold

The carrier side is modeled as records, not as notes

Desk adjuster, field adjuster, independent adjusting firm, and supervisor are contacts on the claim with a role and a date range. When the file transfers, the previous holder stays visible with the dates they had it.

One request queue regardless of which channel it arrived on

A portal message, an email, and a voicemail all become the same object: a request with a source, a date, a deadline, and an owner. Only the capture method varies. What does not vary is that it appears on a list.

Correspondence in both directions lands in the file

Letters received from the carrier, including reservation of rights and coverage correspondence, are filed against the claim with their received date rather than read and left in an inbox.

Estimate versions are dated objects, yours and theirs

Each version is stored as received with its date and source. A comparison view lines up the current version of each so an adjuster can work the differences, and the previous comparison stays available.

Joint events are logged as events with attendees

A joint inspection, reinspection, or on-site meeting is recorded with a date, the people present on both sides, and the photo sets attached. What was agreed in conversation stays a note written by a named person that day.

Where this connects on both sides

Is this a fit for your business?

A good fit when

  • Files routinely involve a desk adjuster, a field adjuster, and sometimes an independent adjusting firm
  • Documentation requests arrive on more than one channel
  • Carrier-side personnel change during the life of a claim
  • You have had to reconstruct who said what and when

Probably not a fit when

  • You want a tool that evaluates whose estimate is correct
  • You handle both public adjusting and carrier-side work in one system without separation
  • You are looking for guidance on claims practice or licensing obligations

What to have ready

  • A recent file with its full correspondence history, however scattered
  • The channels your main carriers use to send requests
  • Your current method of comparing estimates, even if it is paper and a highlighter

Questions we get asked

Can it read the carrier's estimate and compare it to ours?

Partly, depending on what arrives. Estimating platforms export structured files that can be parsed into line items, in which case the two line up automatically for a person to work through. A flat PDF gives less to work with. Either way an adjuster decides what the differences mean.

What about invoking the appraisal clause?

That is a policy provision and a decision for the insured, usually with counsel. We treat it as a dated file state with its own document set: demand date, the appraiser named by each side, umpire selection, and any award document. The system tracks the process and has no view on entering it.

We run an independent adjusting firm on the carrier side. Does this apply?

The mechanics are the same and the orientation is opposite. Assignment intake, inspection documentation, and turn-time obligations model the same way. What we would not do is serve both public adjusting and carrier-side work from one system without a hard separation, because the duties run in different directions.

Does this replace our claims management software?

Usually it sits alongside it. Most claim systems model the insured, the policy, and the documents well, and model the carrier’s people and their requests poorly. We build the missing layer and connect it rather than migrating a system their adjusters know.

Related


Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.

Scroll to Top