Project Detail - Cara Submittal Register (AI spec parse + submittal log + vendor compliance)¶
| Stage | Estimated |
|---|---|
| Status | Deferred |
| Design status | In progress |
| Estimate | 2w (L) |
| Confidence | Low |
| Linear | PIN-466 ↗ PIN-300 ↗ PIN-653 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C16 |
| Design | Design ↗ |
| Linear epic | Project Management & Controls |
| Module | Submittals & RFIs ↗ |
Status check: deferred, but shipped work exists
This surface is marked deferred, yet Linear shows PIN-300 and PIN-653 as Done. Confirm whether it actually shipped (move the status off deferred) or only the remaining scope is deferred. Flagged for reconciliation.
Priority: Medium
Scope¶
AI-driven submittal register for a project: Cara parses uploaded spec/drawing PDFs — book-spec section numbers when present, CSI cost-code fallback for drawing-only jobs — into a full initial submittal log, and separately seeds one submittal per qualifying equipment line straight from the awarded estimate. PM review and approval gate the register before it goes live; Smart Upload routes returned vendor packages to the right entry and drives a spec-compliance review. (Source: PIN-466, PIN-300, PIN-653.)
Acceptance criteria¶
- Cara parses uploaded spec/drawing PDFs into spec sections — book-spec section numbers when present, CSI cost-code fallback for drawing-only projects
- Cara generates a full initial submittal register from spec sections/drawings: type (Product Data / Shop Drawing / O&M), suggested vendor/trade, required on-site date
- Register auto-seeded at award from equipment-type estimate lines (Div 23 equipment cost codes), tagged "From estimate" and linked back to the source line — non-fatal and idempotent on re-award
- PM reviews, edits, and approves the AI-generated register before it becomes the live submittal log
- Smart Upload matches returned vendor submittal PDFs to the right register entry automatically, or prompts the PM to create/attach one
- Cara cross-references vendor packages against drawings/specs into a per-item Spec Compliance Report (Compliant / Partial / Non-compliant + notes)
- PM reviews and approves the compliance result before formal dispatch to GC / client / design team
- Reviewer comments on returned submittals are parsed into linked PM follow-up tasks
Conor's comments¶
All part of submittal module
Notes¶
3-phase: AI spec parse (3d) → submittal register (5d) → vendor upload + compliance (2w total)
Open question for Conor¶
Add CSI specs/submittals to QA agenda; confirm 3-phase scope