Project coordination

Construction RFI: How to Write, Track and Close a Clear Request

Write a construction RFI with a precise question, current drawing references, useful attachments and traceable follow-up. Includes a worked example and closure checklist.

Ashish Khadke
Created and Written by:

Designation: Founder8 min read

Technically reviewed by: Riya Kulkarni | BE Civil Engineer

A construction RFI, or request for information, asks for clarification when the available project information does not resolve a specific question. A useful RFI connects a precise location and document reference to an answer that the team can apply and trace. This guide explains how to prepare a focused request, track its response and reflect its actual status in daily reporting.

Key Takeaways

  • Check current drawings, specifications and previous responses before creating another request.
  • Ask a specific, answerable question and identify the affected work boundary.
  • Separate facts, assumptions and any proposed interpretation.
  • A requested response date is not a guaranteed turnaround or permission to proceed.
  • Track the answer, communication and any separate authorization needed before closing the issue.

What a construction RFI is meant to resolve

An RFI is useful when a missing detail, conflicting reference or unclear interface needs clarification through the project's designated process. It should help the recipient understand the information gap without reconstructing the entire issue from a chain of informal messages. Name the question rather than sending a general complaint about coordination.

The applicable contract and communication procedure determine who can issue and answer a request and what authority a response carries. This article provides a documentation method, not a contractual interpretation. Do not assume that an RFI automatically authorizes a change, approves a substitution or establishes cost or time entitlement.

Check the existing information first

Confirm that the documents in use are current and applicable to the location. Review the relevant detail, specification, schedule, approved submittal and previous RFI responses. A request based on an obsolete revision can create avoidable confusion even if the question was reasonable when first noticed.

Record the review you performed. “Detail 4 on S-302 revision D and penetration schedule M-102 revision B reviewed; opening arrangement remains unclear at grid C4” explains the gap more clearly than “drawings do not match.” These fictional references demonstrate the format; they are not actual project documents.

Essential construction RFI fields

  • Unique reference, subject, issue date and revision.
  • Project, location and affected work package.
  • Drawing, detail, specification and other source revisions.
  • A concise description of the information gap.
  • The specific question and any clearly labeled proposed interpretation.
  • Relevant attachments and their identifiers.
  • Requested response date with a factual planning basis.
  • Authorized recipient, response record and follow-up status.

FHWA's WFLHD 70 form is a primary example of a structured RFI record with identifiers, description, submission and response fields. Its signatures and certification belong to that form's own context. Use your project's required form and authority arrangements rather than copying agency-specific declarations into unrelated work.

Write one decision-focused question

State the observed conflict

Identify what the current documents show and the location where the difference matters. Avoid describing a suspected error as an established design failure. The recipient needs enough context to locate the issue and evaluate it.

Ask for a defined clarification

A question such as “Which referenced detail governs this opening at grid C4?” has a clear answer boundary. “Please review everything” does not. If several questions are related, number them and keep their dependencies visible.

Label a proposed interpretation

A proposed interpretation can help explain the request, but it must remain a proposal until the appropriate process resolves it. Do not phrase the record so that silence appears to accept an unapproved assumption.

Worked example: conflicting opening references

This fictional example concerns documentation, not the design of an opening. A team finds that two current references appear to describe different arrangements at grid C4. The writer records both document revisions and attaches a location sketch showing exactly where the question applies.

A weak request is “Opening detail wrong. Confirm ASAP.” A more useful request is “RFI-028: Please clarify which detail governs the identified opening at grid C4. S-302 revision D, detail 4, and M-102 revision B, schedule entry P-07, appear inconsistent for this location. Attachments A and B mark the relevant references. Please confirm the governing arrangement and identify any revised documentation required.”

A separate planning note can explain that the information is needed before the affected activity is scheduled. The request does not include invented dimensions, announce an unauthorized solution or treat the requested response date as an agreed commitment. A clear boundary makes the eventual response easier to communicate.

Choose attachments that reduce uncertainty

Use an overview to establish location and a focused markup to identify the exact issue. Label drawing references, photograph orientation and attachment revisions. Keep the underlying document distinguishable from the writer's annotations. Large unindexed bundles make the recipient search for the question again.

Photographs can show an observed field condition, but they may not establish hidden dimensions or the governing design. If a measurement supports the question, record its unit, location and source. The site photograph guide explains context and labeling for a traceable daily record.

Explain the requested response date

Relate the date to a named planning event or decision, rather than using urgency as a substitute for context. Distinguish a requested date from an acknowledged response commitment. If the work sequence changes, update the planning information through the designated process so the recipient understands the current need.

Record when the request was issued, received, returned for clarification and answered. A revision that changes the question should not hide the original history. Do not assume a standard turnaround period applies to every recipient or project unless it is established in the relevant requirements.

Track response and implementation separately

Suggested statusMeaning to document
DraftQuestion being checked before issue
IssuedRequest transmitted through the required channel
Clarification neededAdditional information requested before an answer
Response receivedAnswer recorded, with source and revision
Implementation follow-upCommunication or other required action remains open
ClosedProject-defined closure evidence recorded

These are working labels, not a required universal workflow. A response may answer the question while leaving an associated document revision, authorization or field communication outstanding. Use separate references so closing the RFI does not conceal those continuing obligations.

Check that the answer resolves the actual question

Compare the response with each numbered question and the identified work boundary. If the answer refers to another document, verify that the team can identify the correct revision. If a term or condition remains ambiguous, seek clarification through the agreed process rather than choosing the most convenient interpretation.

Do not extend an answer to other floors, grids or products without a stated basis. An answer for one location may not apply elsewhere. Where a response requires separate cost, schedule, substitution or change procedures, retain those links and keep the corresponding status visible.

Record actual field effects in the daily report

Use Civilable's daily report generator to record the affected activity, location and confirmed status. A factual entry might read “Grid C4 opening preparation not advanced during this shift pending clarification referenced by RFI-028. Adjacent work progressed as recorded below.” Include times and resource effects only where they were observed and supported.

A daily report should not conclude that every open RFI causes a compensable delay. Keep the event record distinct from a contractual assessment. The construction delay documentation guide explains factual timelines, while the handover guide helps transfer open actions. Civilable does not automatically submit RFIs, notify reviewers or manage response deadlines.

A practical closure checklist

  1. Match the response to the correct RFI number and revision.
  2. Confirm that every specific question has an identifiable answer or follow-up.
  3. Reference any revised document and verify that the relevant team has the correct version.
  4. Record separate approvals or changes where the project process requires them.
  5. Communicate the confirmed information to the affected field team.
  6. Retain the issue, attachments, response and closure evidence together.

A closed log entry should be reconstructable by someone who did not attend the discussion. “Answered verbally” without a traceable confirmation may leave the work team unable to establish what was agreed or where the answer applied.

Frequently asked questions

Is an RFI the same as a change order?

Do not assume that it is. An RFI requests information; the effect of a response and any separate change authorization depend on the applicable project process.

Can work proceed while the request is open?

This guide cannot authorize that decision. Follow the project's designated instructions and keep the affected scope and current restrictions explicit.

Should unrelated questions share one RFI?

Separate unrelated issues where combining them would obscure recipients, response status or work boundaries. Follow the project's numbering and submission requirements.

Sources and review status

Primary reference consulted 14 November 2026: FHWA Form WFLHD 70, Request for Information, April 2025 revision. It illustrates a structured agency-specific request and response record; it does not establish a universal contract procedure. The worked example and suggested workflow are original editorial guidance and do not claim agency endorsement. Created and written by Ashish Khadke, Founder. Technical review completed by Riya Kulkarni, BE Civil Engineer. See editorial standards and corrections.

TECHNICAL REVIEWER

Riya Kulkarni | BE Civil Engineer

Riya Kulkarni qualifications and experience
QualificationBE Civil – Shivaji University, Kolhapur (2018)
Experience8+ Years
Technical SpecialisationsStructural Engineering, Construction Materials, Site Execution and Concrete Technology.

Project experience

1. Shree Ganesh Residency

Location: Rajarampuri, Kolhapur

Project Type: G+4 Residential Apartment Building

Technical responsibilities
  • RCC structural construction coordination.
  • Reinforcement and shuttering inspection.
  • Concrete pouring and curing supervision.
  • Monitoring construction materials and workmanship.
  • Site quality-control documentation.

2. Vrindavan Heights

Location: Tarabai Park, Kolhapur

Project Type: G+5 Residential Building

Technical responsibilities
  • Structural drawing interpretation.
  • Reinforcement detailing checks.
  • Concrete workability and placement monitoring.
  • Construction sequencing and site coordination.
  • Building material quality assessment.

3. Sai Krupa Row Houses

Location: Kalamba Road, Kolhapur

Project Type: Residential Row Housing Development

Technical responsibilities
  • Foundation and plinth construction coordination.
  • Brick masonry and plastering inspection.
  • Concrete mixing, placement and curing.
  • Waterproofing and finishing work coordination.
  • Construction progress documentation.

4. Greenview Enclave

Location: Ujalaiwadi, Kolhapur

Project Type: G+3 Residential Apartment Complex

Technical responsibilities
  • Site execution monitoring.
  • RCC work and reinforcement inspection.
  • Construction material management.
  • Concrete quality testing coordination.
  • Workmanship and quality documentation.

5. Lotus Business Plaza

Location: Shahupuri, Kolhapur

Project Type: G+3 Commercial Building

Technical responsibilities
  • Structural construction coordination.
  • Slab and column reinforcement inspection.
  • Concrete placement and quality monitoring.
  • Construction activity sequencing.
  • Contractor and site-team coordination.

6. Omkar Residency

Location: Kadamwadi, Kolhapur

Project Type: G+5 Residential Apartment Building

Technical responsibilities
  • Foundation and superstructure execution coordination.
  • Reinforcement and formwork inspection.
  • Concrete testing and curing monitoring.
  • Material specifications and quality checks.
  • Site inspection reporting.

7. Silver Oak Villas

Location: Kasaba Bawada, Kolhapur

Project Type: Independent Residential Villa Development

Technical responsibilities
  • Residential foundation construction.
  • RCC structural component inspection.
  • Masonry and plastering quality checks.
  • Flooring and finishing coordination.
  • Site execution and material monitoring.

8. Pratham Commercial Complex

Location: Ruikar Colony, Kolhapur

Project Type: Commercial and Retail Building

Technical responsibilities
  • RCC construction coordination.
  • Concrete quality-control procedures.
  • Structural component inspection.
  • Construction material assessment.
  • Execution progress and quality reporting.
All guides