← Files magicplanARCHIVED FILE

skills/magicplan-adjuster-handoff/references/handoff-guide.md

3.23 KB · Oct 5, 2026 · 18:17 UTC

↓ Download file

# Adjuster Handoff — Template & Best Practices

This reference complements the built-in `restoration://playbooks/adjuster-handoff` playbook. When the
playbook is available, its review sequence governs; use this file for the document template and the
communication best practices.

## Best practices for adjuster communication

- **Neutral, not adversarial.** Adjusters read dozens of files. A measured, factual package that clearly
  separates observed conditions from recommendations earns credibility and gets approved faster than one
  that argues for scope.
- **Show the documentation, don't assert it.** Every affected area and every scope driver should trace
  to a photo, a reading, a measurement, or a form. Point to the evidence.
- **Name gaps yourself.** If a reading or photo is missing, saying so plainly is far stronger than hoping
  it goes unnoticed. It also frames the open questions you want the adjuster to resolve.
- **No opinions on price adequacy.** State what the estimate covers. Do not editorialize on whether it is
  high, low, or fair — that invites a fight you don't need.
- **One reference set.** Lead with claim number, policyholder, property address, loss date/type, and your
  company contact so the adjuster can file it instantly.
- **Separate facts, assumptions, recommendations.** Keep the three visually distinct so the adjuster can
  see exactly what is confirmed.

## Document structure

```
# Adjuster Handoff — [Property address]
[Company name] · [contact name] · [phone] · [email]
Claim #: [value or "pending"] · Policyholder: [name] · Loss date: [date] · Loss type: [type]
Prepared: [date]

## 1. Loss summary
[3–5 neutral sentences: what happened (cause of loss, whether the source is confirmed stopped), water
category/class if established (note if assumed), and the migration path. Facts only.]

## 2. Property & affected areas
Property type, floor count, approximate square footage. Then affected rooms by name and floor, each with
the documented damage type and the affected floor/wall measurements where recorded.

## 3. Documentation on file
- Forms: [which workspace forms are complete].
- Photos: [count, and coverage by affected room — note affected rooms with no photos].
- Moisture readings: [instruments and monitoring period — note instruments placed but unread].
- Files: [reports, third-party assessments, other documents].
Present this as an inventory the adjuster can rely on, with gaps named.

## 4. Estimate posture
What the estimate covers and its status. No opinion on adequacy. If no estimate exists, say so and note
it can be generated in magicplan.

## 5. Open questions
Group as neutral questions, not demands:
- **Field items** — conditions needing re-inspection or more documentation.
- **Adjuster items** — approvals, authorizations, or decisions pending.
- **Customer items** — access, contents decisions, scheduling.
- **Third-party items** — environmental testing, specialty vendors, permits.

## 6. Attachments
List the photos/files referenced, with links where available.
```

## Tone rules

- Factual and measured throughout.
- Observed conditions and recommended actions are visibly separated.
- Documentation gaps are neutral open items.
- The package documents the project; it does not decide coverage.

SHA-256: a4b5e05f419849618ebe9d08c882c468b0508730c77e93be068df7291cf6a527