1. Permit-delay source card
Copy/paste fields:
- Customer/job and project address:
- Permit, inspection, HOA, utility, or review item:
- Verified source: permit portal link, city email, inspector note, HOA message, utility ticket, CRM note, or owner confirmation:
- Current status: not submitted / submitted / needs correction / waiting for review / inspection scheduled / inspection failed / resubmission needed / approved:
- Known blocker: missing document, fee/payment, city backlog, contractor license proof, property access, photo/spec detail, weather, utility markout, HOA board timing:
- Customer-facing fact we can safely say:
- Internal uncertainty we should not promise:
- Allowed next step: request missing info / resubmit / hold schedule / schedule inspection / ask owner/manager / customer update only:
- CRM label: permit_delay / inspection_pending / resubmission_needed / owner_review_needed / schedule_hold:
- Owner/reviewer and next check date:
2. Customer-safe update texts
Status received: “Hi [Name], quick update: [permit/inspection item] is currently marked as [verified status]. We are watching the next step and will update you again by [next check date] or sooner if the status changes.”
Missing detail: “The reviewing office asked for [missing item]. Before we resubmit, can you confirm [specific detail]? We do not want to send an incomplete correction.”
Schedule hold: “We are holding off on promising a start date until [permit/inspection item] is cleared. Once the status is confirmed, we can review scheduling options.”
Do not say: “approved,” “guaranteed by Friday,” “inspection will pass,” “fee is included,” “crew is reserved,” “no delay,” “city will approve it,” or “we can start anyway” 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 permit, inspection, HOA approval, or utility/municipal delay.
Use only the verified facts below. Do not invent permit approval, inspection results, city timelines, fees, start dates, crew availability, legal advice, warranty coverage, or customer intent.
Facts I can verify: [paste permit-delay source card]
Create:
1) a short internal status summary;
2) one customer-safe update under 500 characters;
3) missing facts/questions that must be resolved before scheduling or promising next steps.
If the source record is unclear, write NEEDS OWNER REVIEW instead of a promise.STOP AUTOMATION
- Do not let AI mark permits, inspections, HOA approvals, or utility clearances as approved without source proof.
- Stop if the message involves legal/code interpretation, safety, fees, refunds, contract deadlines, warranty coverage, or starting work before approval.
- Do not invent a city/inspector/HOA timeline just to make the update sound complete.
- Escalate to an owner or manager when portal status, customer expectations, contract terms, and crew scheduling conflict.
4. Weekly review questions
- Which delayed jobs had no assigned permit/inspection owner?
- Which blockers repeat: missing photos, fees, forms, utility markouts, access, HOA timing, or failed inspections?
- Which customer update wording reduced “any news?” follow-up without overpromising?
- Should the Local Lead Rescue workflow add a permit-delay lane with owner, next-check date, customer update cadence, and STOP AUTOMATION rules?
Product bridge: Pair this with Local Lead Rescue quote follow-up, deposit confirmation, estimator-to-scheduler handoff, and permit inspection scheduling resources so teams avoid turning paperwork delays into unsupported customer promises.