# Construction RFI Log: [Project name]

> A register of construction requests for information (RFIs): questions
> from the site team or a contractor to the designers or contract
> administrator about drawings, specifications or site conditions, with
> the drawing and model references, the answer, the due dates and any
> cost or time impact. Based on common construction practice. This is
> the site RFI, not a procurement request for information (for that, see
> `business/rfi`). Replace every `[bracketed]` value and every row marked
> *Example*.

<!--
Guidance: How to use this template
- One question per RFI. Reference the exact drawing, revision, grid and
  specification clause, and propose an answer where you can.
- Set a required-by date from the programme, not from habit. An RFI that
  blocks work next week is not "routine".
- An answer is not an instruction to change the contract. If the answer
  changes scope, cost or time, raise a change record
  (`construction/change-order-variation`) and link it.
- Fictional example: Fernhollow Library and Learning Centre (code FHL),
  contractor Quillmere Construction, architect Marrowpike Architects,
  structural engineer Okeburn Structures. All names are invented.
-->

## Document control

| Field | Value |
|---|---|
| Log ID | [RFI-LOG-FHL] |
| Owner | [Contractor's design manager, @name] |
| Contractual response period | [Days stated in the contract, or agreed working days] |
| Last updated | YYYY-MM-DD |

## 1. RFI register

<!-- Guidance: Keep closed RFIs in the log. Status values: Open, Answered, Closed (answer accepted and drawings updated), Withdrawn. -->

| RFI ID | Raised | Raised by | To | Subject and question | Drawing, revision, grid | Spec clause | Required by | Answered | Answer summary | Cost impact | Time impact | Change ref. | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RFI-041 *(Example)* | YYYY-MM-DD | Steel erector | Structural engineer | Connection detail for beam B12 at grid D/4 not shown; confirm bolt group | FHL-OKS-ST-02-DR-S-00220 rev C01, D/4 | [Clause] | YYYY-MM-DD | YYYY-MM-DD | Use standard detail SD-07 | None | None | | Closed |
| RFI-042 *(Example)* | YYYY-MM-DD | Roofing contractor | Architect | Client request for two extra rooflights: confirm sizes and trimming | FHL-MPA-01-R1-DR-A-00410 rev C01, C-D/4-5 | [Clause] | YYYY-MM-DD | YYYY-MM-DD | Revised drawing rev C02 issued | Yes | Yes | VO-007 | Closed |
| RFI-043 *(Example)* | YYYY-MM-DD | Groundworks | Architect | Existing drain found at grid A/1 clashing with pile cap PC-03; propose diversion | Survey drawing rev P02, A/1 | [Clause] | YYYY-MM-DD | | | Possible | Possible | | Open |
| [RFI-nnn] | YYYY-MM-DD | [Who] | [Who] | [One question] | [Ref] | [Clause] | YYYY-MM-DD | YYYY-MM-DD | [Answer] | [None/Yes/Possible] | [None/Yes/Possible] | [VO-nnn] | [Status] |

## 2. Summary

<!-- Guidance: Report weekly at the contractors' meeting. Overdue RFIs on the critical path go to the top of the agenda. -->

| Measure | Value |
|---|---|
| Total raised | *Example:* 43 |
| Open | *Example:* 1 |
| Overdue (past required-by date, no answer) | *Example:* 0 |
| With cost or time impact | *Example:* 1 confirmed (RFI-042, linked to VO-007); 1 possible (RFI-043), change record to follow if confirmed |

Related: BIM issues tracked as BCF items in the BIM execution plan
(`construction/bim-execution-plan`), product approvals in
`construction/submittal-register`.

## Standard and licence note

Based on common construction project practice for requests for
information. The text is original. Check your contract for the formal
procedure, response periods and notice requirements. Template licence:
MIT.