# MVP Workflows and SLA Rules (Frozen v1)

## Objective
Define end-to-end operating workflows for Daily Log, Blocker Board, RFI, and Punch processes with strict ownership and SLA enforcement.

## Global Workflow Standards
- Every record must include: `project`, `location`, `trade`, `owner`, `dueDate`.
- Every closure must include proof: photo/document/comment.
- Status model (common): `new -> inProgress -> pendingExternal -> resolved -> closed`.
- Escalation policy:
  - SLA breach +0h: alert owner.
  - SLA breach +24h: alert owner manager.
  - SLA breach +48h: alert PM + weekly risk board.

---

## 1) Daily Site Log Workflow
### Steps
1. Site Engineer creates daily log before end of shift.
2. Captures labor, equipment, weather, completed quantity, and blockers.
3. Attaches photos and voice notes (optional) for evidence.
4. PM reviews next morning and flags action items.
5. Action items automatically create tasks on Blocker Board.

### Mandatory data fields
- Date, shift, zone/location
- Trade-wise manpower count
- Equipment in use/down
- Planned vs completed quantity
- Top 3 blockers with owner

### SLA rules
- Log submission deadline: by 8:00 PM site local time.
- PM review SLA: by 10:00 AM next business day.
- Missing log alert: auto-reminder at 7:00 PM and 8:15 PM.

---

## 2) Task and Blocker Board Workflow
### Steps
1. Blocker created manually or auto-created from daily log/RFI/punch.
2. Owner accepts task and sets action plan.
3. If dependency exists, status set to `pendingExternal` with linked entity.
4. Owner uploads resolution proof.
5. Verifier (Site Engineer or PM) closes/reopens with reason.

### Priority model
- `P1`: safety/critical path impact
- `P2`: major productivity impact
- `P3`: routine execution issue

### SLA rules
- P1 acknowledgment: 2 hours; resolution target: 24 hours.
- P2 acknowledgment: 8 hours; resolution target: 72 hours.
- P3 acknowledgment: 24 hours; resolution target: 5 days.
- Reopened blocker must be addressed within 24 hours.

---

## 3) RFI / Clarification Workflow (Lean)
### Steps
1. Site Engineer raises RFI with drawing pin and question category.
2. PM verifies and routes to consultant/client/subcontractor.
3. External responder submits answer and attachment.
4. PM marks response as accepted/rejected.
5. Accepted RFI creates executable task if site action is needed.

### RFI categories
- Design ambiguity
- Quantity/spec conflict
- Site condition mismatch
- Method statement clarification

### SLA rules
- Internal PM triage: 8 business hours.
- External initial response:
  - Critical (path-impacting): 2 business days
  - Standard: 5 business days
- Escalation if no response by due date +1 business day.

---

## 4) Punch / QA Closure Workflow
### Steps
1. QA raises punch item with location pin, defect class, and photo.
2. Item assigned to responsible subcontractor foreman.
3. Foreman submits corrective evidence (before/after).
4. QA inspects and either closes or reopens with reject reason.
5. Repeat reopen reason is tagged for trend reporting.

### Defect classes
- Finish quality
- Dimensional compliance
- Safety housekeeping
- MEP installation issue

### SLA rules
- New punch acknowledgment: 12 hours.
- Closure target:
  - Critical: 48 hours
  - Major: 5 days
  - Minor: 10 days
- Reinspection SLA after resubmission: 24 hours.

---

## Governance and Exceptions
- SLA pause allowed only when status is `pendingExternal` with dependency note.
- Any manual due date extension needs PM approval and reason code.
- Weekly operations review must include: overdue count, reopen rate, and top delay causes.