All docs

RFIs

An RFI is a question for the architect or owner — a missing item, a conflict between documents, or a clarification you need. Struction drafts them from your documents; you sharpen the ones worth sending and export the list.

Updated 2 minApplies to: MapFeedback →

Where RFIs come from

Struction generates RFIs automatically when you create a project. You can also add one by hand from the + in the Risk Register's header, or ask chat to create one or find more.

What an RFI holds

Every RFI has a number, a name, a trade, a severity (Critical, Medium, Low), a status (Open, Risk Accepted, Resolved, Deferred), a source page, and a description. Edit any of these inline — the register behaves like a spreadsheet. Numbers are per project and carry their type: RFI-031, Risk-054, so your team can say "RFI 31" and mean one thing.

fields + source page chip
An RFI in the register: its number, the source sheet beneath it, the name, trade, status and rank — all editable in place.

Verify, then send

Review the generated RFIs, sharpen the wording, and confirm the ones worth sending. Click the source page to check the question against the sheet before you forward it. Then export the register to send to the owner or architect for resolution: Export issues in the Risk Register's header offers Export Excel or Export CSV, and it exports only what your current filter shows — filter Type to RFI first.

When the answer comes back

Upload the response as part of a new issuance (see Issuances and addenda), then mark the RFI resolved.

Workflow example — Struction flags that the fire-sprinkler heads aren't specified for the second-floor mezzanine. You open the RFI, confirm it's real by checking the source sheet, adjust the wording, and export it with the rest of your open RFIs to send to the architect — instead of discovering the gap after you've already bid.

Was this page useful?Stuck? help@struction.com