T-3 reinspection readiness scan
How Pip flags pre-inspection prep issues three days out from any scheduled inspection.
Reinspection-Prevention runs every weekday morning, three days before any scheduled inspection.
What it checks
The scan reads install photos for that project and matches them against the Expedite Playbook:
- Disconnect placard present and labeled
- Rapid shutdown labels at panel + roof access
- Bonding photos
- Conductor color coding visible
- Inverter nameplate readable
- (And any AHJ-specific items)
Missing items become a T-3 readiness task on the project, routed to the PM.
Workflow
Pip drafts a readiness task
Lands in Buddies inbox if Copilot, or auto-creates if Autopilot.
PM reviews the gap list
A short bullet list of what's missing vs the playbook.
QS verifies on site
The Quality Surveyor adds missing photos or labels before the inspector arrives.
Mark resolved
Tick each item; the task closes when all are checked.
Why a Buddy and not a checklist
The playbook is fed by historical fail reasons per AHJ. As more inspections accumulate, the playbook updates automatically — you don't have to maintain a per-AHJ checklist by hand.
Related
AHJ Intelligence
How SunrAI builds a profile per AHJ — pass rates, contacts, interconnection timelines — and how Pip uses it to flag risky inspections before install day.
Approving and undoing Buddy work
Review Buddy proposals, distinguish reversible from irreversible actions, and undo eligible writes from Activity.