Free construction template
Construction RFI register template
Track each question, responsible recipient, response date, programme impact, answer and resulting action.
No account or email required.
Who owns it
Usually the contract administrator, design manager or project manager responsible for the project RFI process.
When to create it
Create the register entry when the formal RFI is issued and update it when a response, revised response or resulting direction is received.
Field-by-field guide
What to record and why.
| Field | Why it matters | Completed example |
|---|---|---|
| RFI ID and subject | A unique reference and concise issue description. | RFI-018 - Level 3 services clash |
| Date raised | When the question entered the formal process. | 14 July 2026 |
| Raised by / sent to | The originator and responsible recipient. | Builder - mechanical consultant |
| Location and reference | The area, drawing or specification affected. | Level 3 corridor - M-214 |
| Question | One direct, answerable question. | Confirm revised duct level below Beam B3. |
| Response required | The realistic date needed and programme impact. | 16 July - ceiling rough-in waiting |
| Status and response date | Open, answered, superseded or closed. | Answered - 15 July 2026 |
| Resulting action | The task, instruction or change created by the answer. | Update set-out before installation |
Common mistakes
- Combining several questions
- No drawing or location reference
- Using an RFI as a hidden variation notice
- Closing the RFI without recording the resulting action
From template to workflow
The downloadable file helps create a consistent manual record. Only use Convoe for the fields and actions currently supported by the product.
See how the current workflow fitsOne site is enough to start
Start with one project. See what your team stops losing.
The crew can keep working in conversation while confirmed tasks, owners, dates and status become visible.