Project Detail - Project Controls: Submittals (approval + AI draft)

Stage	Building
Status	Partial
Design status	In progress
Estimate	1w (M)
Confidence	Medium
Linear	PIN-51 ↗ PIN-300 ↗
Linear status	Done
Cycle	C16
Design	Design ↗
Linear epic	Project Management & Controls
Module	Submittals & RFIs ↗

Priority: High · Route: /projects/:id/detail?tab=project-controls&subtab=submittals

Scope

Submittals tracking on Project Detail: spec-section-numbered submittals routed sequentially Vendor → PM → GC → Engineer through a 9-state lifecycle, with ball-in-court escalation and an "Approved as Noted" gate requiring PM acknowledgment before procurement proceeds. Cara generates the initial register from project drawings/specs for PM review and approval, and turns returned reviewer comments into PM follow-up tasks. (Source: PIN-51, PIN-300.)

Acceptance criteria

• Submittals numbered [spec section]-[sequence].[revision] (e.g. 23-73-00-001.01), typed Product Data / Shop Drawing / Sample / Test Report / O&M Manual / Warranty / Closeout
• 9-state lifecycle: Draft → Submitted → Under Review → Approved / Approved as Noted / Revise and Resubmit / Rejected / Void
• "Approved as Noted" is a yellow gate requiring explicit PM acknowledgment before procurement can proceed
• Sequential routing enforced by the state machine: Vendor → PM → GC → Engineer, never parallel
• Ball-in-court escalation: Day 1 yellow, Day 7 red, Day 14+ health-dot + email
• Revision history preserved across Revise-and-Resubmit cycles; bulk CSV import for migrating off spreadsheets
• Cara generates the initial submittal register from project drawings/specs (CSI code, spec section, type); PM reviews and approves before it goes live
• Reviewer comments on returned submittals are parsed into linked PM follow-up tasks

Conor's comments

Needs more detail, testing and alighment with the Pinley CO template. Review design prototype.

Notes

AI draft works. Not sending emails to GC

Open question for Conor

-