# Contractor Storm Owner Scope Change Confirmation Map

Use this map when a storm lead needs a scope change repeated plainly before the next route gets credit.

## Fields
- Trade:
- Owner-approved scope change:
- Homeowner change memory:
- Owner scope note:
- Confirmation-ready route:
- Source:
- Primary source:
- Destination:

## Source-preserved route checklist
- Keep `primary_source=contractor-storm-owner-scope-change-confirmation-map`.
- Preserve owner scope-change confirmation before crediting website, local, or operational routes.
- Use Webzaz only for website forms, storm landing pages, service pages, city pages, galleries, scope-copy reassurance, proof blocks, and thank-you routes.
- Use LocalKit only for GBP/profile, QR, phone, booking, review, referral, and one-action local paths when the same source continues.
- Keep CRM, dispatch, scheduling software, AI answering, no-show automation, work-order systems, contracts, deposits, crew operations, and insurance claim handling separate.

Avoid exact pricing, guaranteed timelines, guaranteed claim outcomes, and internal planning labels.