RFI Register Template

Log, track and chase every request for information so answers come back before they delay the programme.

An RFI that sits unanswered is a delay waiting to happen. This register keeps every RFI, its status and its days-open visible, so overdue ones get chased and programme impact is recorded.

What's inside

RFI number, subject and date raised
Discipline, related drawing/spec reference
Date required, date answered and days open
Status and programme impact
Responsible reviewer so chasing is easy

Columns

RFI No.	Date Raised	Subject	Discipline	Related Ref	Date Required	Date Answered	Days Open	Status	Programme Impact
RFI-042	2026-06-20	Slab edge detail clash with facade	Structural	Dwg S-110, A-301	2026-06-27		5	Open	Holds L1 electrical rough-in
RFI-041	2026-06-15	Door hardware spec clarification	Architectural	Spec 08 71 00	2026-06-22	2026-06-19	4	Closed	Nil

How to use it

One question per RFI — bundling stalls the whole thing until the slowest part is answered.
Attach the exact spec section and drawing reference so the reviewer can act straight away.
Sort by Days Open every week and chase anything past its date required.

Frequently asked

What should an RFI register track?

Each RFI's number, subject, discipline, related references, the date it was raised, required and answered, days open, status and programme impact. Days-open and programme-impact columns are what turn the register from a log into an early-warning tool.

What is a reasonable RFI turnaround time?

Many contracts specify 7–14 days, but it depends on your agreement. The register's date-required and days-open fields let you hold reviewers to the agreed turnaround and evidence delay if they miss it.

From template to system

This template captures the data by hand. Alloovium reads it straight from your project documents, keeps it current, and checks it against your compliance gate automatically.

See how it works