AI forward commitments (RFI→CO detection / invoice-vs-progress / vendor RFP suggestion)¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In review |
| Estimate | 4w (L+) |
| Confidence | Low |
| Linear | PIN-264 ↗ PIN-162 ↗ |
| Linear status | Done · +1 backlog |
| Design | Design ↗ |
| Linear epic | Cara AI & Automation |
| Module | Cara ↗ |
Priority: Medium
Scope¶
AI detects drawing revisions on active projects, overlays base vs. revised drawings, and maps changed scope to affected vendors — with a PM confirm-and-send gate before any RFP goes out, plus vendor-response tracking on the Change Order. Separately, AI suggests vendors and quote data to estimators during takeoff, in a suggest-then-approve model. (Source: PIN-264, PIN-162.)
Acceptance criteria¶
- AI overlays base vs. revised drawings and flags changed scope items with confidence scores
- PM confirms project + drawing titles before any RFP is drafted — no auto-fire (human-confirm gate)
- AI drafts RFP scope + vendor list; PM edits and sends
- Confirmed changes auto-create a Change Order record; vendor quotes feed CO pricing
- Vendor-response tracking (not sent / sent / pending / responded / declined) on the CO row
- Estimator gets AI-suggested vendors during takeoff based on trade + scope history
- Vendor quote PDFs parsed into line items with CSI mapping to pre-fill the estimate
- Audit log on every AI-driven step
Conor's comments¶
This is a feature built into Cara, not necessaryily a separate workspace. This also ties into tasks.
Notes¶
Four "specified-unbuilt" AI capabilities (R-8); depends on Action gate + Takeoff; ex old "AI layer" row; noted from Conor email
Open question for Conor¶
Foundations first - confirm which R-8 AI commitments are in launch scope