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.

RFI policies page showing review workflow, required fields, and closure settings
RFI policies — review workflow, required fields, and close-out guards

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

SettingWhat It Does
Review modeTwo-step (coordinator-gated) — a coordinator screens each RFI, routes it to a responder, then reviews the answer before closing. — 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:

FieldEffect
DisciplineMust pick a discipline before submitting
Due dateMust set a due date (otherwise the SLA default applies)
ResponderMust nominate a responder before submitting

Closure & Escalation

SettingWhat It Does
Require official response before closeBlocks 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.
Require coordinator assignment (two-step)Blocks auto-routing without an explicit coordinator screen.
Auto-escalate overdue RFIsNotifies escalation roles when an RFI passes its due date.

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.