Roof Tarp and Temporary Repair Authorization Checklist for Local Service Businesses

Use this before sending any AI-assisted customer update

STOP AUTOMATION: do not promise a tarp, temporary patch, price, insurance coverage, claim approval, crew arrival, safety clearance, warranty, reimbursement, or permanent repair schedule until an owner/manager has checked the job record, site photos, access notes, weather constraints, customer authorization, estimate status, and approved communication channel.

Do not invent that a tarp will prevent all water intrusion or that temporary work is a permanent fix.
Do not tell the customer insurance will pay, reimburse, approve, or waive anything unless the approved source record says so.
Do not send roof access, ladder, interior damage, tenant, or claim-document details until the customer-authorized channel and privacy/source record are confirmed.

Copy/paste temporary-repair source card

Customer / property / trigger: customer name, service address, caller role, storm/leak date if known, active water intrusion status, roof type if known, and customer-authorized communication channel.
Authorization boundary: who can approve tarp/temporary repair work, signed authorization status, estimate status, insurance/claim number if provided, and what must wait for manager/project review.
Evidence and access: exterior/interior photos, leak location, ceiling/wall damage notes, attic/roof access constraints, pets/tenants/gate codes, ladder/safety notes, and missing evidence.
Weather and crew limits: weather window, daylight/safety constraints, material availability, crew schedule, emergency/rush review, and whether the update is acknowledgement-only.
Customer-safe update owner: dispatcher, estimator, project manager, owner review, approved message template, and what cannot be promised before authorization and inspection.
CRM label: roof_tarp_request, temporary_repair_authorization_needed, storm_damage_photos_pending, insurance_claim_review, or owner_review_before_send.

Customer-safe snippets

Acknowledgement without overpromising

We have your roof leak / storm-damage request in the job record. Before we confirm tarp availability, pricing, arrival timing, insurance details, or permanent repair scope, our team will review the photos, access notes, weather window, authorization status, and approved communication path.

Photos or authorization still needed

To keep the temporary-repair record accurate, please send only the requested photos or authorization details through the approved channel. We will review them before giving a source-backed update about next steps.

Customer asks if insurance will cover it

We do not want to guess about coverage, reimbursement, deductible, or approval outcomes. We can document the issue and temporary-work notes, but claim or payment conclusions need to come from the approved claim/source record and manager review.

AI audit prompt

Review this draft customer update about a roof tarp, temporary repair, storm damage, leak mitigation, authorization, claim, estimate, arrival window, or repair schedule. Flag invented claims about availability, emergency dispatch, price, insurance coverage, reimbursement, safety, warranty, permanent repair, access, weather, or customer authorization. Rewrite it as a source-backed acknowledgement with clear unknowns, owner/project-manager review, customer-safe wording, and STOP AUTOMATION guardrails.

Why it connects to Local Lead Rescue

Local Lead Rescue System packages practical intake, follow-up, CRM-label, and human-review patterns for local-service teams. This free worksheet is a narrow example of the same source-card approach for high-pressure storm and leak response.

See Local Lead Rescue System Start with the free missed-lead checklist