Project Detail - Project Controls: RFIs (AI draft + PDF)¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In progress |
| Estimate | 1w (M) |
| Confidence | Medium |
| Linear | PIN-1081 ↗ PIN-52 ↗ PIN-301 ↗ PIN-459 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C16 |
| Design | Design ↗ |
| Linear epic | Project Management & Controls |
| Module | Submittals & RFIs ↗ |
Priority: High · Route: /projects/:id/detail?tab=project-controls&subtab=rfis
Scope¶
RFI tracking on Project Detail: auto-numbered RFIs on a Draft → Open → Answered → Closed workflow, with ball-in-court and cost/schedule-impact flags and overdue highlighting. Cara drafts candidate RFIs from project drawings for PM review, and finalized RFIs send straight to the GC/engineer by email; single-RFI and full RFI-log PDF export are also available. (Source: PIN-52, PIN-301, PIN-459.)
Acceptance criteria¶
- Auto-numbered RFIs (
RFI-001…) with question, asked-by/directed-to, key dates (sent/required/answered), response, cost-impact and schedule-impact flags - Status workflow Draft → Open → Answered → Closed; an insufficient answer can reopen the RFI into a new response cycle
- Ball-in-court tracking (GC / architect / engineer / Pinley); overdue RFIs (past required date, no response) highlighted red
- RFI count badge on the project overview; table sortable/filterable by status, date, ball-in-court, cost/schedule impact
- Cara drafts candidate RFIs from drawings and project context (question, target party, impact, urgency); PM reviews and accepts/edits/rejects each in batch
- Accepted drafts create RFIs in
draftstatus; rejected suggestions feed back into the prompt as negative examples - "Send" on a finalized RFI emails it directly to the directed-to party — no PDF/Outlook round trip; status auto-advances to
sent, ball-in-court updates, send is audit-logged - "Export as PDF" for a single RFI (full thread + attachments) and "Export Log as PDF" for the project's full RFI log, both company-branded
Conor's comments¶
Needs more detail, testing and alighment with the Pinley CO template. Review design prototype.
Notes¶
No delete button
Open question for Conor¶
Verify with Artem (due date TBC)