# Contractor Storm Proof Owner Handoff Card

Use this card when storm traffic needs proof before a quote, inspection, emergency repair, documentation, or callback request. The goal is to assign the proof owner, preserve the source, and turn approved storm proof into a booked-job handoff instead of a forgotten file.

## Proof owner fields
- Storm proof asset: before/after photo, city job proof, review, testimonial, license, insurance documentation, project gallery, or service-page proof.
- Proof owner: office manager, estimator, technician, owner, marketer, or website operator.
- Placement: homepage, storm landing page, service card, quote form, thank-you page, service-area page, or city page.
- Source attribution: preserve organic, GBP, LSA, referral, storm page, homepage CTA, proof card, phone, form, and repeat-customer source fields.
- Callback expectation: who follows up, when, with what proof, and what the homeowner should expect next.

## Handoff checks
1. Put the proof asset beside the exact storm CTA that needs confidence.
2. Assign one owner to keep the proof updated, approved, and source-safe.
3. Preserve source, primary_source, search query, CTA route, proof type, city, urgency, clicked card, and thank-you expectation.
4. Repeat the same proof promise on the callback or inspection-prep route.
5. Route Webzaz-fit website fixes only when the bottleneck is proof layout, service-card hierarchy, CTA copy, form placement, storm landing pages, or thank-you structure.
6. Keep LocalKit, review/referral, CRM, dispatch, scheduling, AI answering, estimate follow-up, and no-show workflows separate.

## Webzaz-fit website fixes
Webzaz fits when the contractor needs better storm proof hierarchy, service-card layout, CTA copy, form placement, proof blocks, source-preserved thank-you pages, or storm landing page structure. Avoid exact pricing and do not force product CTAs into operations-only workflows.