# Personas and Top Pain Points

## Scope
This document defines the four core user roles for a large, site-execution-focused construction organization and the top three pain points for each role.

## 1) Project Manager (PM)
**Primary responsibility:** Delivery performance across multiple sites (time, quality, coordination risk).

**Top 3 pains**
1. No single source of truth for site blockers, so decisions are delayed.
2. Daily status updates are fragmented across calls, chats, and spreadsheets.
3. Late visibility into overdue RFIs/punch items causes schedule slippage.

**What value they need from the platform**
- Live list of unresolved blockers by priority and owner.
- SLA-driven escalation for pending decisions.
- Reliable weekly progress and risk snapshot without manual consolidation.

## 2) Site Engineer
**Primary responsibility:** Daily execution at zone/trade level on active site areas.

**Top 3 pains**
1. Repetitive reporting overhead reduces time spent on actual supervision.
2. Confusion from old drawing versions or unclear field instructions.
3. Difficult follow-up on assigned tasks when subcontractors are not responsive.

**What value they need from the platform**
- 60-second field logging (voice, photo, quick structured forms).
- Drawing pins linked to issues/tasks so context is never lost.
- Auto-reminders and clear "ball-in-court" status for follow-ups.

## 3) Subcontractor Foreman
**Primary responsibility:** Crew coordination, productivity, and closure of assigned work.

**Top 3 pains**
1. Receives instructions from multiple channels with conflicting priorities.
2. Progress claims are challenged due to missing evidence.
3. Punch and rework loops increase cost due to unclear acceptance criteria.

**What value they need from the platform**
- One prioritized task queue by area and due date.
- Easy proof submission (before/after photos, comments, timestamp).
- Transparent closure criteria and instant feedback on rejected items.

## 4) QA/QC Engineer
**Primary responsibility:** Inspection quality, non-conformance management, and closure compliance.

**Top 3 pains**
1. Hard to track recurring defect patterns across projects and trades.
2. Evidence quality for closure is inconsistent and often incomplete.
3. Re-opened punch/non-conformance items are not analyzed for root causes.

**What value they need from the platform**
- Standardized QA checklists with mandatory evidence fields.
- Re-open reason tracking and trend analytics.
- Audit-ready timeline of inspection, corrective action, and approval.

## Cross-Persona Shared Requirements
- Bilingual UI (Bangla + English) for field-level adoption.
- Offline capture with robust sync in low-network jobsite conditions.
- Role-based dashboards to avoid information overload.
- Tamper-evident activity history for dispute resolution.