Esc

↑↓ move↵ openIndex · Pagefind

How to write an RFI that gets answered.

Most slow RFI answers start with a vague question. Run this checklist before you send one: it takes two minutes and saves a round trip.

  • Free
  • No signup
  • Print · CSV · Markdown
Download CSVDownload Markdown

RFI writing checklist

os.construction · free template
Project
RFI #
Subject
Date needed by
Written by
Assigned to

Before you write it

ItemDoneComment / follow-up
Searched the drawings, specifications, addenda, ASIs and bulletins for the answer
Checked earlier RFIs and approved submittals for the same question
Confirmed it is a question, not a submittal, a means-and-methods decision or a change request
Talked to the trade that raised it and understood exactly what they need to proceed

The question

ItemDoneComment / follow-up
One question per RFI
Subject names the element and the location (e.g. “Corridor fire damper detail, L2 grid C”)
References the sheet, detail and specification section involved
States the conflict or gap in a sentence: what the documents say and why it doesn’t work
Proposes a solution the designer can accept or reject
Asks for a specific answer: a dimension, a product, a yes or no, a detail
Marked-up sheet or photo attached

Routing

ItemDoneComment / follow-up
Assigned to the person who can answer it, with the right people on distribution
Due date set from when the field needs the answer, inside the contract response time
Cost and schedule impact marked: yes, no or to be determined
Logged with a number so it can be tracked and referenced in meetings

When the answer comes back

ItemDoneComment / follow-up
The answer actually answers the question; if not, follow up the same day
Official response distributed to the field and affected trades
Drawings or field sets marked with the RFI number
Change event opened if the answer adds cost or time
RFI closed, with the closed date recorded

Sample rows are illustrative and marked for deletion. Your contract, drawings and specifications govern. Template from os.construction/resources/templates/rfi-checklist

How to use it

Using the RFI writing checklist

  1. Use the first section to decide whether you need an RFI at all. A question already answered in an addendum or a previous RFI is a day lost.
  2. Write the subject last: element plus location. It is what everyone sees in the log and in meeting minutes.
  3. Put your proposed solution in. A designer can approve a proposal faster than they can design from scratch.
  4. Set the due date from the schedule, not by habit. If the work is three weeks out, say so; if it is tomorrow, call as well as send.
  5. Review open RFIs by ball in court every week, in the meeting, so nothing waits silently.
Who has the ball on an RFIDraft, then Open, no response yet, then Response received, then Official response distributed, then Closed. Not answered: back: from Response received back to Open, no response yet.Not answered: backDraftBall in court: the writerOpen, no response yetBall in court: the assigneesResponse receivedBall in court: the RFI managerOfficial response distributedField and affected tradesClosedNobody: closed date recorded
  1. DraftBall in court: the writer
  2. Open, no response yetBall in court: the assignees
  3. Response receivedBall in court: the RFI managerNot answered: back: back to “Open, no response yet”
  4. Official response distributedField and affected trades
  5. ClosedNobody: closed date recorded
Who has the ball on an RFI
Text version
  1. Draft: Ball in court: the writer
  2. Open, no response yet: Ball in court: the assignees
  3. Response received: Ball in court: the RFI manager
  4. Official response distributed: Field and affected trades
  5. Closed: Nobody: closed date recorded

Not answered: back: from “Response received” back to “Open, no response yet”.

In os.construction

Do this in os.construction instead of a spreadsheet

RFIs in os.construction save as a draft until they’re ready, then open to the assignees. Ball in court is worked out from the RFI’s state, overdue RFIs are flagged in the log, and the answer that settles the question can be marked official. An RFI links to drawings, submittals, change events and photos, and Export PDF downloads the full RFI with its responses.

Watch the walkthrough · 1:57

Create a draft RFI and open it

  1. 0:00Start a new request for information
  2. 0:27Give the RFI a clear subject
  3. 0:59Write the question
  4. 1:15Save the draft
  5. 1:28Review the saved question
  6. 1:43Open the RFI
Read the transcript

Here we are in the actual os.construction app, using a local sample project. On the New RFI page, we can prepare a question and save it as a draft before opening it.

Use a subject that tells the reviewer what needs clarification. In this example, we are asking about the corridor fire damper detail. The demo adds a unique reference so each recording creates a separate sample record.

State the decision the team needs. Our question asks the reviewer to confirm the required fire damper detail before installation and identify which detail the field team should follow.

Select Create as Draft. The app saves the RFI and opens its detail page. We will check that the Open RFI action is available before moving forward.

The saved record now has its own detail page. Review the subject and question here. A draft gives the team a chance to check the request before opening it.

Select Open RFI. Wait for the Open RFI action to disappear after the update. Close RFI remains available. We have written a request, saved it as a draft, reviewed it, and moved it into the open workflow.

Try it on the sample project

Every trial workspace includes a sample project to run this workflow on. 14-day free trial. Pricing for paid plans isn't set yet.

FAQ

Questions about the RFI writing checklist

What is an RFI in construction?

A request for information: a formal written question to the design team (or owner) about the contract documents, used when the drawings or specifications are unclear, conflicting or incomplete.

How long should an RFI response take?

Whatever your contract says; many contracts set a response period, and the due date on the RFI should reflect when the field actually needs the answer. If none is set, agree one at the start of the job.

Should an RFI include a proposed solution?

Usually yes. A proposal the designer can accept is faster to answer than an open question, and it shows the field’s preferred approach. The designer still decides.

Is an RFI a change order?

No. An RFI asks a question. If the answer changes the scope, cost or time, open a change event and price it; the RFI is the backup.

Can I see a filled-in RFI in os.construction?

Yes. Every trial includes a sample project with RFIs you can open, and the walkthrough above shows drafting and opening one.

Keep going

Open file