Project Detail - Change Orders (scope change; rev/cost split)¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In review |
| Estimate | 2w (M) |
| Confidence | Medium |
| Linear | PIN-1082 ↗ PIN-53 ↗ PIN-298 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C16 |
| Design | Design ↗ |
| Linear epic | Project Management & Controls |
| Module | Change Orders ↗ |
Priority: High · Route: /projects/:id/detail?tab=change-orders
Scope¶
Change Order management on Project Detail: COR / CO / ICO / Backcharge records with line items and auto-numbering, routed through a GC approval workflow that rolls approved COs into a revised contract value (original contract + approved COs). Includes a permission-gated Subcost Tracker for vendor-quote rollup and per-CO profit visibility. (Source: PIN-53, PIN-298.)
Acceptance criteria¶
- Four CO types — COR, CO, ICO, Backcharge — each auto-numbered per project (
COR-001,CO-001, etc.) - Line items (qty / unit / cost) auto-calculate to the CO total
- ICO submission requires a reason code (missed in estimate / field error / design change / coordination / other) plus free-text detail
- Status workflow Draft → Submitted → Under Review → Approved / Rejected / Revised, with GC revision history
- Approved COs roll into a CO impact summary: original contract + approved COs = revised contract value
- Ball-in-court tracking (Pinley PM / GC / owner) with email notification on status change
- Subcost Tracker (Senior PM / Executive / Owner / Admin only): per-vendor quote rows, multi-vendor rollup, lowest cost vs. CO total
- Budgeted- and actual-profit fields gated to Senior PM / Executive / Owner / Admin
Conor's comments¶
Needs more detail, testing and alighment with the Pinley CO template.Review design prototype.
Notes¶
No AI draft. Canon contradiction: shipped ICO/PCO-spawn vs INT one-record (migration owed; status-vocabulary §3.5 / M-1…M-10)
Open question for Conor¶
Verify with Artem (due date TBC)