Skip to content
All articles

Project Management

RFI Log: What to Track on Every Construction Project

An RFI log is only useful if it shows what is holding up work. Here are the columns every construction RFI log needs, how to measure turnaround, and how to use the log in weekly meetings.

· 4 min read

An RFI log is the register of every request for information on a project: what was asked, who has it, when an answer is due and what the answer was. Every project keeps one in some form. The difference between a log that helps and one that does not is whether it answers three questions quickly: which RFIs are holding up work, who needs to act, and how long answers are taking.

This article lists the information a useful RFI log captures, and how to use it to keep answers moving.

The Core Columns

Every RFI log should record the RFI number; the subject; the date it was raised; who raised it, including the subcontractor where one is involved; who it is addressed to; the drawing sheet and specification section it concerns; the date a response is required; the current status; the date it was answered; and a short summary of the answer.

Number RFIs sequentially across the project and never reuse a number. If an RFI is withdrawn or replaced, keep its row and mark it so the numbering still makes sense at closeout. Our free RFI log template has these columns ready to use.

Ball in Court

The most useful single column in an RFI log is the one that says who currently holds the RFI. A status such as 'open' says nothing about who needs to act. 'With structural engineer since March 3' does.

An RFI often passes through several hands: the subcontractor who raised it, the general contractor who reviewed it, the architect who routed it, the engineer who answered it, and back. Recording the current holder, and the date it reached them, shows where answers are stalling and makes follow-up specific.

Due Dates and Overdue Items

Record the date a response is required for each RFI, based on the contract or Division 01 response period, or on the date the work needs the answer, whichever is sooner. Then sort or filter the log by that date.

An overdue RFI should stand out without anyone having to compare dates by eye. Teams that review overdue items at every coordination meeting, and send a polite reminder before the due date rather than after it, see answers come back noticeably sooner.

Cost and Schedule Impact

Add a column to flag whether an RFI may affect cost or time, and a second to link it to any resulting change order or change directive. When a question turns into a change, the link between the RFI and the change is what supports the claim, and it is far easier to record that link as it happens than to rebuild it at closeout.

If the project schedule is updated regularly, also note which activity each open RFI affects. A short list of open RFIs that hold up critical activities is one of the most useful things a project manager can bring to an owner meeting.

Measuring Turnaround

Record both the date each RFI was sent and the date it was answered, and the log can tell you how long answers take. Track the median number of days from sent to answered, overall and by consultant. The median is more useful than the average, because a few RFIs that stay open for months can distort an average badly.

Turnaround figures turn a vague sense that answers are slow into something specific that can be discussed with the design team. They also show whether changes to the process, such as clearer questions or earlier reminders, are working. The closed-loop RFI management guide covers how to act on these numbers.

Distribution and Closure

An RFI is not finished when the answer arrives. Record who the answer was distributed to, so the field crews and subcontractors who need it actually receive it, and close the RFI only when its answer has been acted on. A common cause of rework is an answer that sat in an inbox while the work went ahead to the old detail.

Spreadsheet or Software

A spreadsheet log works on small projects with a handful of open RFIs at a time. As volume grows, keeping the log, the email threads and the documents in sync becomes a job in itself, and the log falls behind the real state of the project.

Construction RFI software keeps the log current automatically: numbering, ball in court, due dates and turnaround are recorded as the RFI moves. In PlanSpan, reminders are prepared before the due date for a project manager to approve, and each RFI can come with a cited response draft for the design team to review.

Your next RFI, already drafted

See it on your own project.

PlanSpan prepares cited RFI responses and first-pass submittal reviews from your own drawings and specifications. Start free with one project.