1. Failed-inspection correction source card

Copy/paste fields:

2. Customer-safe update snippets

Correction notice received: “Hi [Name], quick update: the inspection report lists [verified correction item]. We are reviewing the correction path and will update you by [date/time] after [owner/manager/permit coordinator] confirms the next step.”

Reinspection not ready yet: “We do not want to schedule a reinspection until [correction item] is verified complete. Once that is confirmed, we can review the next available inspection window.”

Possible added scope: “The correction may require [scope item] before reinspection. We are checking whether that affects price, timing, or approvals before we promise the next step.”

Do not say: “it will pass next time,” “the inspector is wrong,” “no extra cost,” “we can fix it today,” “approved by the city,” “warranty covers it,” or “crew is booked” unless the source record and owner review support that wording.

3. AI draft prompt with guardrails

You are helping a local-service business draft a customer update about a failed inspection, correction notice, or reinspection.
Use only the verified facts below. Do not invent code interpretations, inspection pass/fail results, permit approval, fees, warranty coverage, safety status, crew availability, legal advice, customer blame, or city timelines.
Facts I can verify: [paste failed-inspection correction source card]
Create:
1) a short internal owner/manager summary;
2) one customer-safe update under 650 characters;
3) missing facts/questions that must be resolved before promising correction timing, reinspection, price, or approval.
If the source record is unclear, write NEEDS OWNER REVIEW instead of a promise.

STOP AUTOMATION

4. Weekly review questions

Product bridge: Pair this with Local Lead Rescue permit-delay, permit-inspection scheduling, work-order authorization, parts backorder, and warranty update resources so inspection failures become tracked correction workflows instead of unsupported customer promises.