Inspection reports + daily reports + punch lists are the third-highest-volume AEC daily document after RFIs and submittals. /inspection-tracker is the fourth AEC daily-action surface — same architecture as /rfi-tracker, /submittal-tracker, and /change-order-tracker.
**The flow:**
1. Inspector files an inspection report or daily report (PDF, Word, scan). 2. Kodori's auto-classifier flags the doc as "inspection report" or "daily report" via the existing pre-trained pattern matcher. 3. The extract-inspection Inngest function pulls structured fields via Haiku — inspector, inspection date, project ref, spec section (when scoped), trade, location, verbatim result, open-finding count, and a 1-2 sentence summary of what's still blocking. 4. Row lands on /inspection-tracker for the project team.
**What you see on the page:**
- **Five status counters** — Open / Open findings (total count) / Pass-no-findings / Closed out / Extraction failed. - **Top trades by open finding count** — single-line breakdown ("MEP 27 · structural 4 · envelope 2") so a project executive sees where the issues live without drilling per-doc. - **Per-row detail** — inspection number, subject, inspector, trade, location, verbatim result, inspection date, and the Haiku-extracted findings summary. Rows with open findings tint amber + show the "N open" badge. - **Sort order** — open-with-findings first (the actionable queue), then pass-no-findings, then closed-out for historical reference.
**Status lifecycle:**
- *open* — initial state after extraction. Stays open until the operator (or an automation) flips to closed-out. - *closed-out* — operator has marked the inspection's findings resolved. Closed-out inspections surface for historical reference but don't count against the open-findings total. - *extraction-failed* — Haiku couldn't pull a usable subject + inspection number. Surfaces for human review.
**Per-project drill-in.** Open /projects/[ref] for any project; the page already shows RFIs / submittals / COs by project. The inspection tracker accepts ?projectRef=<ref> for the same filtering pattern (drilling into "all inspections on Spring Hill Tower" works identically).
**Coming next:** auto-flip status to closed-out when a follow-up inspection on the same spec section reports zero open findings; per-finding tracker (each finding gets its own row with severity + closure date) for projects with deep punch-list workflows; auto-link an inspection's response packet (architect / consultant sign-off) via the same linkResponseDocument MCP tool the RFI/submittal trackers use.