Engineers reviewing a structural steel beam

RFI Management Process: A Practical Guide for UK Projects

An RFI (request for information) management process is a short, repeatable routine: spot a gap in the project information, check it is not already answered, raise one clear question with references, send it to the named person who can answer it, log it, chase it, record the answer and update the documents. Run well, it keeps site teams working from current information. Run badly, it creates delay, rework and disputes.

This guide walks through each step as it applies to UK projects, including what the main standard forms say about responses, what a good RFI contains, how to build a register and how to stop queries ageing.

Xponexusengineering
Keep Engineering Queries Moving
Xponexus provides remote civil and structural engineering support, including calculations, drawings and BIM coordination for UK consultancies.

Explore engineering support

TL;DR

  • Check the contract documents first. Up to 30% of RFIs are reportedly unnecessary because the answer already existed, according to BRCKS.
  • Raise one issue per RFI, with drawing numbers, revisions, a direct question and a labelled proposed solution.
  • Agree response times before the first RFI. Five to seven working days is a common standard, with 24 to 48 hours for urgent site queries.
  • Keep a register with a named owner, review it weekly and escalate overdue items at progress meetings.
  • Close an RFI only when the answer is a real answer and the drawings and work packs that depend on it have been updated.

Table of Contents

What an RFI is and when to raise one

An RFI is a business process used in construction to ask for clarification about documents, drawings, specifications or other project conditions, as Procore’s library puts it. In the UK the term sits alongside “technical query” (TQ), and the two are used interchangeably on most sites.

The CECA’s November 2024 NEC4 bulletin notes that RFIs and TQs are not referenced in NEC contracts, yet most projects use them to identify information that needs an answer before part of the works can progress. So the process is a matter of good practice and project protocol, not a creature of one contract form.

A team should raise an RFI when:

  • drawings or specifications conflict;
  • critical information is missing;
  • design intent is unclear;
  • site conditions differ from those assumed;
  • a client decision, such as a finish or material, is needed.

These triggers are listed in Scopekit’s UK RFI guide.

When not to raise one

The same guide is clear that an RFI is not the place to ask for information already in the contract, to chase a variation instruction or to record an opinion. If the question is really “please instruct a change”, it belongs in the contract’s instruction route, not the RFI log. Keeping those channels separate protects everyone’s commercial position later.

The RFI management process step by step

The sequence below follows the lifecycle described by Triangle PMO: identify the gap, draft after internal review, submit under the contract’s communication protocol, have the designer or engineer answer, distribute the answer to affected parties, then close and update the register.

1. Identify the gap and check the documents

Before drafting anything, search the drawings, specification, schedules, models and previous correspondence. An effective process starts with this internal verification, followed by submission through an electronic document management system so there is a formal audit trail. If the answer is already there, you have saved the design team a task and kept your own credibility intact for the RFIs that matter.

2. Draft one clear question

One issue per RFI. If three items sit on the same drawing, raise three RFIs, so each can be answered, closed and tracked on its own. Write plainly. SMACNA, a US trade body, offers a useful test: if a person pulled off the street can read the RFI and explain the problem, it is well written.

3. Send it to the person who can decide

Address it to the named role that owns the answer: the architect or contract administrator on a design-led job, the engineer for structural or civil matters, the employer’s agent on a design and build contract, the project manager on NEC. A query sent to the wrong person burns days before anyone looks at it.

4. Log it and set the response date

Every RFI gets a unique reference and a register entry the moment it is sent. The response date is tied to the programme, not to a habit.

5. Review, answer and distribute

The responder answers in writing, quoting the RFI reference, and issues the answer to everyone affected, not just the person who asked.

6. Close and update the documents

Closing means confirming the response is accepted and that downstream documents, such as drawings and work packs, reflect it. Quality in Construction stresses this last step: the site team must not be working from superseded information.

What a good RFI contains

A complete RFI answers the responder’s first five questions before they ask them. Scopekit lists the essentials as one issue, the precise location, document references and revisions, a description of the gap, a direct question and a proposed solution. CCM’s guidance adds the administrative layer.

Field What to put in it
Reference Unique number, never reused
Date raised The day it was sent
From and to Originator and the named addressee
Project Contract or project details
Location Grid lines, level, room or chainage
Documents Drawing numbers, schedule references and revisions
Question Short, specific and answerable
Proposed solution Optional, clearly labelled as a proposal
Required response date Linked to the programme or an order deadline
Impact if unresolved What stops, and when
Attachments Marked-up extracts, photographs, sketches

Offer a solution

Including a proposed solution can speed the answer and shows you have thought about the problem, as Triangle PMO notes. SMACNA goes further and recommends proposing at least two options, defining what counts as an adequate response, and deferring cost and time effects until the answer is known.

A worked example

Weak: “Beam size unclear on first floor, please advise.”

Stronger: “RFI-014. Drawing S-201 rev C shows a 203 x 133 UB over the opening at grid B/3-4; the calculation package rev B lists a 254 x 146 UB. Which governs? Steel order closes on Friday. We propose the larger section, pending your confirmation. Marked-up extract attached.”

Engineer marking a structural drawing extract

The second version has a reference, two document revisions, a location, a direct question, a deadline and a proposal. A designer can answer it in minutes.

Who answers, and how fast

What the contract says about responses depends on the form, and the differences matter when an answer is late.

Form Position on RFIs and response
NEC4 RFIs/TQs are not an NEC process. The CECA bulletin says there is no contractual obligation to reply within the period for reply for an RFI, but a response date can be requested and the Project Manager should respond in a timely way.
JCT SBC 2024 The Architect/Contract Administrator must provide further drawings or details reasonably necessary to carry out the works. Failure to respond can be a Relevant Event under clause 2.26.6.
JCT Design and Build 2024 The Employer’s Agent must issue information in line with the Information Release Schedule. Late information may support an extension of time (clause 2.26) and loss and expense (clause 4.20).

The NEC4 point comes from the CECA bulletin; the JCT clause references are summarised in BRCKS’s UK guide. Always check the clauses in your own contract and any amendments.

The CECA bulletin also gives a practical route for urgent queries on NEC projects: an RFI that is becoming urgent can be notified as an early warning and discussed at an early warning meeting. And any answer that changes the Scope should be issued under a separate Project Manager Instruction, not left inside the RFI reply. On JCT projects, Tradefox notes that if an RFI reveals an error or omission, the Architect/Contract Administrator may issue an Architect’s Instruction to formalise the change.

Agree response times first

Best practice is to agree response times before the first RFI is raised. BRCKS suggests 5 to 7 working days as a standard with 24 to 48 hours for urgent site queries. Triangle PMO gives a different example, 24 hours for critical items and 10 days for standard queries. The numbers matter less than having them written into the project protocol and tied to the programme.

What a sound response looks like

According to CCM, a response should quote the RFI reference, answer the question directly and in writing, refer to revised drawings, schedules or specifications with their revisions, be issued to everyone affected, and be recorded in the RFI log and, where documents change, the drawing register. Informal verbal answers should be confirmed in writing. If the answer is not available yet, the responder should acknowledge the query and give a realistic date.

Building an RFI register that works

The register is the backbone of the process. Scopekit says a functioning one tracks the reference, date raised, required response date, actual response date, the answer, and whether the answer generated a variation. Mastt adds the status, the cost or time effects, and the instrument and role authorising any change.

A layout that covers all of that:

Ref Raised Addressed to Needed by Response due Responded Status Variation? Documents updated
RFI-014 03/11 Structural engineer 14/11 10/11 Open

Two dates deserve attention. Mastt highlights that “needed-by” (the date work is actually held up) and “response-due” (the administrative target) are different. Track both, because the first is what a delay argument turns on. Scopekit notes that a late response may support a delay claim only if the activity is actually delayed and completion is affected.

Review weekly and escalate

Review weekly and escalate

Stephen McKenna MCIOB, writing for Construction AI, reports an average response of about 10 working days against a contractual expectation of 5 to 7, with the slowest fifth almost always on the critical path. His advice: review the register weekly and put outstanding RFIs on the progress meeting agenda so overdue items are on the record. Treat a non-answer such as “refer to latest revision” without naming the revision as an open item, not a close-out.

A simple escalation ladder works on most jobs:

  1. Day of due date: reminder to the named responder.
  2. Two working days late: call, and copy their line manager.
  3. Five working days late, or any item on the critical path: raise at the progress meeting and, under NEC, consider an early warning.

Why late RFIs cost real money

Unresolved or poorly managed RFIs lead to schedule delays, idle labour, rework costs and commercial disputes, as Triangle PMO sets out. A crew waiting on an answer is paid either way, and the next trade in the sequence slips with it. The same pattern shows up in other trades: this contractor-focused piece on why project delays cost money shows how a small hold-up compounds once labour and follow-on work are affected.

That is why the register, the response dates and the weekly review are not paperwork for its own sake. They are the cheapest delay prevention on a project.

Common problems and how to prevent them

Problem Prevention
Vague RFIs Use a template with mandatory fields and one issue per RFI
Answers already in the documents Search drawings, specs and models before sending
Overdue responses Agreed response times, weekly register review, tiered escalation
Nobody owns the log Name a register owner on day one
Answers not reaching the site Distribute to all affected parties and update drawings and work packs
RFIs used to chase variations Use the contract’s instruction route for changes

One more tip from SMACNA: issue an early “No Cost or Impact” RFI to get the process moving in a non-adversarial way, much as a first change order that is a credit sets a cooperative tone.

Preventing RFIs at the source

Many RFIs come from coordination gaps between drawings, calculations and models. Clear general arrangement drawings remove a good share of them, and disciplined engineering document control means everyone is quoting the same revision when they do ask a question. Our write-up of a structural drawing and calculation coordination project shows how aligning the two before issue keeps queries down.

Our perspective

Most RFIs we see are not really questions about engineering. They are questions about information that was never aligned: a calculation on one revision, a drawing on another, a model that says something different again.

When we embed an engineer into a UK consultancy’s workflow, we treat the RFI log as part of the deliverable. Calculations, drawings and BIM coordination are prepared to UK standards and Eurocodes and checked against each other before they go out for review, so the question that would have been raised on site is answered on paper first.

We also think the response side deserves as much care as the query side. A consultancy that is stretched during a busy period answers late, and late answers cost the contractor. Extra capacity that works inside your own systems, under your own name and with your client relationships untouched, lets the design team answer in days instead of weeks.

Mohammed

Extra engineering capacity for faster answers

If your team is slow on RFI responses because designers are overloaded, we can help. Xponexus Engineering provides remote civil and structural engineers who work inside your workflow on calculations, drawings and CAD and BIM coordination, producing review-ready outputs aligned to UK standards and Eurocodes. Projects can kick off within 48 hours, with NDA protection, and you keep direct control of your client relationships. See our remote engineering support or our CAD and BIM services for details.

Xponexusengineering

FAQ

What is the difference between an RFI and a technical query?

In practice they mean the same thing on most UK projects: a written question asking for information needed to progress the works. “TQ” is more common on civil and infrastructure jobs, and “RFI” on building projects. Neither is a defined process in NEC contracts, so the project’s own communication protocol should say how they are handled.

How long should an RFI response take?

There is no single legal figure. A common benchmark is 5 to 7 working days for standard queries and 24 to 48 hours for urgent site matters, according to BRCKS. Agree the periods in the project protocol before the first RFI, and tie each due date to the programme.

Who is responsible for answering an RFI?

The person who owns the design decision under the contract: the architect or contract administrator on JCT SBC, the employer’s agent on JCT Design and Build, the project manager on NEC. Structural and civil queries are usually passed on to the relevant engineer, so state the addressee on the RFI itself.

When can an RFI be closed?

Only when the response is a genuine answer, is accepted by the person who raised it, and the affected drawings, schedules or work packs have been updated. If the reply is a placeholder such as “further information to follow”, keep the RFI open and chase.

Sources


Comments

Leave a Reply

HTML Snippets Powered By : XYZScripts.com