A ready to use Excel register for every request for information and technical query on site, with response deadlines and programme impact flagged automatically. Built by quantity surveyors.
An RFI or TQ register is the log a contractor keeps of every request for information and technical query raised on a project. It records who raised it, the date, the response due date and whether the answer changed the programme or the cost, so no query gets lost and no late answer goes unclaimed.
A query with no logged response due date is a query nobody can be held to. The deadline is what turns a query into a claim if it runs late.Most RFI registers fail in the same two places: the response due date is never set at the point of raising, and nobody links the late answer back to the days it cost. This template fixes the first problem and gives you the fields to make the second one an easy argument.
| Field | Why it matters |
|---|---|
| Reference and raised by | Ties every query to a person and a date, so chasing it is not guesswork |
| Date raised and response due date | The two dates the query runs between, set at the moment of raising, not after the fact |
| Days outstanding (calculated) | The sheet works it out and flags anything overdue |
| Programme and cost impact | Whether the answer, or the lack of one, changed the sequence or the price |
| Linked drawing or spec reference | Points at the document the query relates to, so the answer is traceable |
Each row carries a status colour and a days outstanding count, so an overdue query is visible at a glance rather than buried in an email chain.
The Excel file with automatic days outstanding, overdue flagging and a worked example tab. No form to fill in.
Free download. No email needed. Yours to use and share with your team.An RFI register only works if every query gets logged the day it is raised. On most sites, queries live in email threads and site meeting minutes long before anyone transfers them to a register, and by then the response due date has already slipped.
Gather's AI QS turns the daily record into a contract aligned commercial position automatically, so the claim writes itself from evidence instead of memory.
See the AI QS in action A 30 minute call. No commitment. See if it fits how your team already works.FAQ
Both are requests for clarification raised on site, an RFI (request for information) and a TQ (technical query) mean the same thing on most UK projects. Some contracts use one term consistently; this register works for either.
At the point the query is raised, either against a contractual response period or a reasonable period agreed with the design team. The template calculates days outstanding from that date automatically.
Yes, if the register shows the date raised, the due date and the actual response date, and the delay it caused is evidenced elsewhere (programme, diary). The register is the record; the diary is the evidence.
Track them separately, but link them. Not every RFI becomes a compensation event, but every compensation event caused by a late answer should reference the RFI number.
Gather reads your site diaries as they come in and links every delay back to the query that caused it.
Book a demo