# Implementation Rollout Playbook

## Purpose
Drive successful adoption of the Site Command Platform across a large construction organization using structured training, champion ownership, and escalation controls.

## Rollout Principles
- Keep workflows simple at launch (minimum mandatory fields).
- Train by role, not by feature list.
- Tie adoption to measurable site performance outcomes.

## 12-Week Rollout Timeline

### Week 1-2: Preparation and Baseline
- Finalize pilot site scope and role mapping.
- Configure workflows and SLAs from frozen v1.
- Run baseline KPI capture.
- Identify champion network (see model below).

### Week 3-4: Controlled Go-Live
- Start with Daily Log + Blocker Board only.
- Conduct daily support huddle for first 10 working days.
- Track top 10 user friction points and fix quickly.

### Week 5-8: Workflow Expansion
- Enable RFI and Punch modules.
- Run weekly refresher training by trade/role.
- Activate manager dashboard and escalation reports.

### Week 9-12: Stabilization and Scale Decision
- Audit data quality and SLA adherence.
- Perform leadership review with KPI trend lines.
- Decide: expand to new sites, hold, or re-tune process.

## Training Plan (Role-Based)
- PM training (2 sessions):
  - SLA governance, risk dashboard, escalation handling.
- Site Engineer training (3 sessions):
  - daily logging speed workflow, task closure proof standards.
- Subcontractor Foreman training (2 sessions):
  - task queue usage, evidence upload, acceptance criteria.
- QA training (2 sessions):
  - punch classification, reopen reason coding.

## Champion Model
### Structure
- 1 Executive Sponsor (Director/Head of Projects)
- 1 PM Champion per pilot site
- 1 Site Engineer Champion per shift
- 1 QA Champion per site
- 1 Subcontractor Champion per major trade

### Responsibilities
- First-line support for peers
- Daily adoption check (submission/completion compliance)
- Escalate recurring workflow blockers to central team
- Provide weekly feedback for process adjustments

## Escalation Policy
1. **L1 (Operational):** Site Engineer to Trade Foreman, same shift response.
2. **L2 (Management):** PM intervenes if SLA breach > 24h.
3. **L3 (Leadership):** Project Director review if critical issue > 48h unresolved.
4. **L4 (Governance):** Portfolio-level action for repeated breaches over 2 weeks.

## Adoption Governance Cadence
- Daily: 15-minute standup (compliance and urgent blockers).
- Weekly: 45-minute KPI and SLA review.
- Bi-weekly: process tuning workshop.
- Monthly: executive steering committee decision review.

## Communication Pack (Minimum)
- One-page role cheat sheet (per role).
- 5-minute quick-start video for field users.
- FAQ for common objections.
- "What changed this week" release note in Bangla + English.

## Success Exit Criteria (Pilot Complete)
- Daily log submission >= 90% for 3 consecutive weeks.
- P1 overdue blockers reduced by >= 50% vs baseline.
- RFI turnaround improved by >= 30% vs baseline.
- Punch reopen rate <= 12%.
- At least 80% active users logging in 4+ days per week.

## Common Failure Signals and Immediate Actions
- Signal: users return to WhatsApp for assignments.
  - Action: enforce task creation-first rule and disable informal closure.
- Signal: low evidence quality.
  - Action: mandate photo before/after at form level.
- Signal: high reopen rate.
  - Action: targeted coaching for specific trade and QA criteria alignment.