RFI Policies
Configure how RFIs are reviewed, what's required before submit, and the guards on closing — at the organization and project level.
RFI policies control how RFIs flow from question to closure. They're set under Admin → RFIs → Policies, at two scopes: Organization defaults that apply everywhere, and Project overrides for a specific job.
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.
Organization defaults, project overrides
Organization policies are the starting values; a project can override any of them. Set your house rules at the org level and only deviate where a job needs it.
Review Workflow
| Setting | What It Does |
|---|---|
| Review mode | Two-step (coordinator-gated) — a coordinator screens each RFI, routes it to a responder, then reviews the answer before closing. Single-step (direct) — RFIs go straight to the assigned responder with no coordinator screening. |
| Response SLA (days) | The default due date, counted from submission, when the initiator doesn't set one. |
Required Before Submit
Toggle the fields an initiator must complete before an RFI can be submitted:
| Field | Effect |
|---|---|
| Discipline | Must pick a discipline before submitting |
| Due date | Must set a due date (otherwise the SLA default applies) |
| Responder | Must nominate a responder before submitting |
Closure & Escalation
| Setting | What It Does |
|---|---|
| Require official response before close | Blocks closing an RFI until an authoritative answer of record exists. Recommended on. |
| Allow initiator to close (single-step) | Lets the initiator accept & close their own RFI in single-step mode. |
Keep the close guarded
Leaving Require official response before close on is what keeps RFIs honest — nothing closes without an answer people can cite later.
Related
- Statuses & Ball-in-Court — how review mode shapes the workflow
- Raising an RFI — which fields the required-before-submit rules affect