Raising an RFI
The Raise an RFI capture panel field by field — subject, question, discipline, priority, references, routing, and evidence.
You raise an RFI from the register with New RFI — shown to anyone whose role can raise RFIs (by default every role except client representative and viewer). The capture panel steps through four sections — only the first is required (plus the responder under single-step review, and anything your policies mark required), so you can raise a well-formed question in seconds and add the rest as you go.
RFIs are in beta
The RFI module is in beta — in production and usable, but not yet part of a versioned release of its own.
Section 1 — Question (required)
| Field | Required | What to Put |
|---|---|---|
| Subject | Yes | A short, scannable summary of the question |
| Question | Yes | The full detail — the conflict, ambiguity, or missing information |
| Discipline | Yes | Architectural, Structural, MEP, Civil, Geotech, Electrical, Plumbing, or Other |
| Priority | — | Low, Medium (default), High, or Urgent |
| Cost impact expected / Schedule impact expected | — | Yes, No, or To be determined (default) — the responder confirms the assessed impact in the answer |
Write a self-contained question
The best RFIs can be answered without a phone call. State the drawings in conflict, the exact location, and what you need decided.
Section 2 — References
Point the responder straight at the source so they can answer quickly.
| Field | What to Put |
|---|---|
| Spec reference | The specification section, e.g. Section 03 30 00 |
| Drawing reference | The drawing and detail, e.g. A-201, detail 4 |
| Suggested answer | Optional — propose a resolution to speed things up |
Section 3 — Routing
| Field | What to Put |
|---|---|
| Responder | Optional under two-step review — leave blank and the coordinator assigns it. Required under single-step, or when your RFI policy makes it required. The list only offers people whose role can answer RFIs. |
| Distribution (watchers) | People who should be kept in the loop |
| Due date | Optional — defaults to the policy SLA from submission if left blank |
Section 4 — Evidence
Attach photos or documents that show the issue — a marked-up drawing, a site photo of the clash, or a product data sheet.
What Happens on Submit
Pressing Submit RFI creates and submits the RFI in a single action:
- The RFI is assigned its number (e.g. RFI-014)
- Under two-step review it becomes Submitted — the ball is with the coordinator
- Under single-step review it becomes Open — the ball is with the responder you chose
No responder yet? That's fine
Under two-step review you don't need to know who'll answer — leave the responder blank and the coordinator routes it after screening. If your project has turned off Require coordinator assignment, naming a responder sends the RFI straight to them.
Related
- Statuses & Ball-in-Court — where your RFI goes next
- Policies — which fields are required and the default SLA
Questions
Can I save an RFI and finish it later?
No. Submit RFI creates and submits it in one go, and closing the panel before then discards what you typed. An RFI is only left as a Draft if the submit fails. Open it from the register and press Submit RFI to try again.
Why does the panel say Responder is required?
Your project's RFI policy requires one, or the project uses single-step review, where an RFI goes straight to its responder. Pick one under Routing. The list only offers people whose role can answer RFIs.
Can I change or withdraw an RFI after I've submitted it?
You can't edit it once it's submitted. Add anything you forgot as a clarification on its page. To withdraw it, press Void. If you don't see Void, your role can't move RFIs through the workflow, so ask the person who routed it or the project owner.