# Pilot KPI Baseline and 12-Week Targets

## Pilot Definition
- Duration: 12 weeks
- Scope: 1 active large site, 3 major trades, all shift logs
- Goal: Prove execution discipline and faster decision-to-action cycle

## Baseline Capture Window
- Week 1-2 is baseline period.
- Sources: existing WhatsApp logs, spreadsheets, email RFI trackers, QA sheets.
- If historical data missing, establish baseline by direct observation during first 10 working days.

## KPI Dictionary
1. **Decision-to-Action Cycle Time (North-Star)**
   - Definition: time from issue creation to verified resolution.
   - Unit: hours.
2. **Daily Log Submission Rate**
   - Definition: submitted logs / expected logs per day.
   - Unit: percentage.
3. **Overdue Blocker Count**
   - Definition: total blockers past due date at end of day.
   - Unit: count.
4. **Average RFI Turnaround**
   - Definition: average business days from RFI submission to accepted response.
   - Unit: days.
5. **Punch Reopen Rate**
   - Definition: reopened punch items / closed punch items.
   - Unit: percentage.
6. **PM Reporting Time**
   - Definition: PM time spent weekly on manual status reporting.
   - Unit: hours/week.

## Baseline Sheet Template

| KPI | Baseline (Week 1-2) | Week 6 Target | Week 12 Target | Owner | Source |
|---|---:|---:|---:|---|---|
| Decision-to-Action Cycle Time | 72h (example) | <= 48h | <= 30h | PMO | Task/issue logs |
| Daily Log Submission Rate | 45% (example) | >= 75% | >= 90% | Site Eng Lead | Daily log module |
| Overdue Blocker Count | 36 (example) | <= 20 | <= 10 | PM | Blocker board |
| Average RFI Turnaround | 9 days (example) | <= 6 days | <= 4 days | Design Coordinator | RFI tracker |
| Punch Reopen Rate | 28% (example) | <= 20% | <= 12% | QA Lead | Punch module |
| PM Reporting Time | 8h/week (example) | <= 5h/week | <= 2h/week | PM | PM timesheet |

> Note: "example" values must be replaced with measured site baseline in Week 1-2.

## Weekly KPI Review Cadence
- Monday: KPI snapshot auto-generated at 8:00 AM.
- Tuesday: 30-minute operations review with PM, Site Engineers, QA.
- Friday: trend and risk review with management.

## Threshold Alerts
- Daily log submission < 70% for 2 consecutive days -> field coach intervention.
- P1 overdue blockers > 5 -> PM escalation same day.
- RFI > 5 business days average -> consultant/client escalation.
- Punch reopen rate > 20% for 2 weeks -> QA process audit.

## Expected Outcomes by Week
- Week 1-2: data stabilization and baseline confidence.
- Week 3-6: behavior change (compliance improvement).
- Week 7-10: decision cycle compression through SLA discipline.
- Week 11-12: adoption lock and scale/no-scale decision.
