An RFI log is the numbered list of every request for information a project team has sent, with who asked, who must answer, the due date, the answer and the status. This page gives you a log to copy, then shows what slow answers cost, and how to keep the log from your email without losing control of what gets answered or escalated.
It is for contractors and subcontractors who send and receive RFIs by email and track them in a sheet. It is also honest about the other path: if your project already runs on a platform with an RFI tool, use it.
An RFI log template you can copy
Use one row per RFI. The fields below match what construction platforms record, and the numbering rule is the one Procore documents: numbers are assigned in sequential order, and duplicate numbers are never permitted (Procore support, RFI numbering). A manual log needs the same discipline.
| Column | What goes in it | Example |
|---|---|---|
| RFI no. | One running number per project, optional prefix, never reused | RFI-032 |
| Subject | Number, spec or drawing reference and the issue in one line | Spec 08 71 00, door hardware at stair 2 |
| Question | The exact question, with the sheet or detail number | Drawing A-501 shows no closer, spec requires one |
| Raised by | Name and company of the person who asked | Field superintendent |
| Directed to | Architect, engineer or GC contact who must answer | Architect of record |
| Date sent | The day it left your hands | 2026-04-06 |
| Response due | Date sent plus the contract response period | 2026-04-13 |
| Status | Draft, Open, Answered, Closed, Overdue (keep a fixed list) | Open |
| Ball in court | Who must act next | Architect |
| Date answered | The day the response arrived | 2026-04-15 |
| Days to answer | Date answered minus date sent, calculated | 9 |
| Response | The answer, or a link to the marked-up drawing | Closer at all stair doors |
| Cost impact | Yes, no or unknown, and a reference to the change event | Unknown |
| Schedule impact | Yes, no or unknown, with the activity affected | Door install, week 14 |
| Linked documents | Drawings, spec pages and photos | A-501, photo 12 |
Two columns do most of the work: Days to answer, because it shows which reviewer is slow, and Cost impact, because an RFI answer that changes the scope should become a change request before the work happens.
Writing RFIs that are easy to answer and easy to log
Good RFIs get answered faster because they are easy to answer. The subject line carries the context, and the question can be read without opening anything else. A pattern that works in a log and in an email subject is: RFI number, spec section or sheet, location, issue. For example, "RFI-032, 08 71 00, stair 2, closer shown on spec not on A-501". It makes the log searchable and lets a language model, or a person skimming an inbox, match a reply to the right row.
| Weak RFI | Stronger RFI |
|---|---|
| "Door question" | "RFI-032, 08 71 00, stair 2: spec calls for closer, A-501 does not show one. Please confirm." |
| No drawing reference | Sheet and detail number, plus a marked-up screenshot |
| Asks "what do you want?" | States the proposed solution and asks the reviewer to confirm or correct |
| No date needed | States the date by which an answer avoids a schedule impact |
| Sent to a general inbox | Addressed to the named reviewer with the next contact copied |
Put the proposed solution in the question. Reviewers confirm a proposal faster than they design an answer, and the proposal is on record if work has to start before the answer arrives. Whether you may proceed at your own risk depends on your contract, so ask your attorney or contract administrator before you rely on that.
The Days to answer column then shows patterns. If one reviewer averages three times the response period of everyone else, that is a conversation to have with the design team, with dates as evidence, and not an argument about whose fault the delay is.
What RFIs cost to process
RFIs cost money in two separate ways, and the research measures them separately. A study published in Construction Research and Innovation, led by Dr Ajibade Aibinu with the Aconex data team, examined 168 projects in Australia and New Zealand, all managed on one platform (Global Construction Review, 13 December 2018).
Processing cost. Global Construction Review reported an average processing cost of US$656,000 per project (AUS$910,000), lower in New Zealand at about US$243,000. This is the cost of handling RFIs, not of delay.
Turnaround. Separately, it reported that RFI turnaround fell to fewer than five days with three or more users per organisation, and was more than 14 days at about two users per organisation.
This is Australian and New Zealand data from one platform, so read it as evidence of the pattern, not as a US price.
| What goes wrong | Why it costs money |
|---|---|
| The RFI is emailed and not logged | Nobody sees it is open, so nobody chases it |
| The answer arrives in a reply, not in the log | The field crew works from the old drawing |
| No due date or the wrong one | The answer is late and nobody can say by how much |
| The same question is sent twice | Two numbers, two answers, and one of them conflicts |
| A scope-changing answer is not flagged | Extra work starts before a change request exists |
| No record of days to answer | You cannot prove a delay or tell which reviewer is slow |
Most of these are about the email that never got into the log. That is the part we automate.
How to keep the log from email, with a person approving
This is a design for a subcontractor or contractor log kept in a sheet or database. It is not a delivered client result, and every outgoing message is approved by a person.
- Capture. RFIs and replies go through one shared mailbox. A workflow tool such as n8n or Make reads each new message; n8n documents an IMAP email trigger that receives emails and can download attachments (n8n Email Trigger (IMAP)).
- Classify. A language model such as Claude decides whether the email is a new RFI, an answer, a request for clarification or something unrelated, and reads the RFI number from the subject or body.
- Number and log. A new RFI gets the next number from your sequence, never a reused one, with due date calculated from your contract response period. A person sees the draft row first.
- Attach the answer. A reply is matched to its RFI by number, and the tool proposes the answer text, the date and any marked-up drawing link. A person confirms before the status changes to Answered.
- Flag cost and schedule words. If the answer contains language such as "additional", "revise" or "change", the row is flagged for the project manager to review as a possible change event. The tool never decides it is one.
- Track response time. Days to answer is calculated for every RFI, and a weekly summary lists the slowest reviewers and the oldest open items.
- Escalate with approval. At two days before due, the tool drafts a reminder to the reviewer. At the due date it drafts an escalation to the next contact named in your project directory. A person reads and sends each one.
When to use Procore or another platform instead
Procore's own page for its RFI tool says it keeps RFIs in one searchable place, lets architects and engineers reply from email without a login, logs every comment and reply, sends automated reminders, and includes an RFI Agent that searches project documents to help draft responses (Procore RFIs). Other construction platforms offer RFI tools too; we did not open their pages for this article, so we do not describe them.
The honest rule is simple:
| Your situation | What we would do |
|---|---|
| The whole team works inside a construction platform with an RFI tool | Use the platform. Do not build a parallel log |
| You are a sub on a project run in the GC's platform | Work in the GC's tool, and keep a light internal view only if you need cross-project reporting |
| You send fewer than about 20 RFIs a quarter | A sheet with fixed columns is enough |
| RFIs and answers live in email across several projects and GC systems | This is the case for an email-fed log with approvals |
| You need the answers to flow into your estimating, scheduling or accounting system | Custom integration is justified, because platforms rarely know your internal system |
See also the sibling jobs with the same shape: submittal log, certificate of insurance tracking, lien waiver tracking and the subcontractor compliance tracker, plus the overview on AI automation for construction companies. If your pain is payroll reporting on public work, read certified payroll and the WH-347.
Guardrails for an automated RFI log
An RFI answer is information for people to act on, so the human step matters more than the extraction:
- Answers are never auto-closed. A person confirms the answer is complete before the status changes.
- Possible change events are surfaced, not decided. The project manager decides whether to issue a change request.
- Escalations are drafts. A reminder to a reviewer is a relationship, so a person reads it first.
- Every action links to its email. You can show who asked what and when, which matters if a dispute starts.
Ask your own construction attorney how long to keep project records, and what your contract says about notice for changes. This page does not give legal advice.
What shapes the cost and how to start
The build is small, but the price is shaped by details. We would ask:
- Where does the RFI log live today, and who edits it?
- How many projects and GC systems send you RFIs, and in what form?
- Do answers need to reach estimating, scheduling or accounting?
- Who approves answers and escalations, and how fast must they respond?
Describe the job and the budget range you have in mind in the contact form, and Devvista quotes in writing after a short call. Our AI agents and workflow automation pages describe how we build, and our case studies show delivered work in other industries. We have not shipped a construction project and do not claim one.