Free Construction Template

    Construction RFI Template

    Use this template to document a construction question clearly, reference the exact drawings or specifications involved, route it to the right party, and preserve the response for the project record.

    How to use this construction RFI template

    1. 1Give the RFI a unique number so it can be tracked, referenced, and closed.
    2. 2Reference the exact drawing, detail, specification section, room, grid line, or project location.
    3. 3Describe the conflict or the missing information factually.
    4. 4Ask one clear question that can be answered directly.
    5. 5Attach supporting evidence — markups, photos, or the conflicting sheets.
    6. 6State when the answer is needed, based on the work in front of it.
    7. 7Identify potential schedule or cost impact when it is known.
    8. 8Route the response to everyone affected by the decision, not just the sender.

    If you want the wider context behind the form — who submits, who answers, and how RFIs connect to submittals and change management — learn the full construction RFI process.

    Example of a completed construction RFI

    A generic, fictional example of a drawing-conflict RFI written the way it should be written.

    RFI Number
    RFI-042
    Subject
    Conflicting north corridor wall dimension
    Discipline
    Architectural / Structural
    Drawing References
    A-201 and S-103
    Location / Area
    Level 2, north corridor, grid lines C–E
    Requested Response Date
    March 12

    Description of issue

    The architectural and structural drawings show different dimensions for the same north corridor wall location. Framing layout cannot proceed until the governing dimension is confirmed.

    Question

    Confirm which dimension governs at the north corridor wall so framing layout can proceed.

    Proposed resolution

    Proceed using the architectural dimension shown on A-201 unless otherwise directed.

    Schedule context and attachments

    Framing layout for this area is scheduled shortly after the requested response date. Attachments: marked-up A-201 and marked-up S-103.

    Actual project contracts and procedures govern RFI requirements and response authority.

    What makes a construction RFI effective?

    A strong RFI has

    • One clear issue
    • One clear question
    • Exact document references
    • Exact project location
    • Relevant attachments
    • A requested response date
    • Schedule context when applicable
    • Neutral, factual wording
    • A documented response

    A weak RFI has

    • A vague question
    • No drawing or specification references
    • Several unrelated issues in one RFI
    • No attachments
    • No required response date
    • Emotional or blame-oriented wording
    • A response buried in an email thread

    Why use a formal RFI instead of just sending an email?

    Email can be a perfectly reasonable way to raise an issue, and project procedures vary. What email usually does not create on its own is a durable project record. A formal RFI gives the team:

    • A unique record number
    • A named responsible party
    • A due date
    • Project-document references
    • Attachments held with the record
    • Full response history
    • A defined distribution list
    • A searchable project record
    • A connection to schedule and change workflows

    An RFI is not a change order. An RFI documents a question and its response. If the answer changes contract scope, cost, time, or another contractual requirement, the project team should follow the applicable change-management procedure — tracked through construction cost management and routed with workflow automation. Project-specific contract documents and procedures govern actual requirements.

    When the spreadsheet stops scaling

    A template works. Until the project has 60 open RFIs.

    A document template is the right tool for writing an individual RFI well. What it does not do is tell you the state of the project. As the volume grows, teams also need to see, in one place — which is what a construction RFI log template is for:

    • Open RFIs
    • Responsible party
    • Due dates
    • Response dates
    • Overdue items
    • Drawing references
    • Attachments
    • Related schedule activities
    • Related changes
    • Project-wide distribution

    Manage RFIs alongside the rest of the project.

    Jet.Build keeps RFI records centralized with status, ownership, due dates, and attachments held against the same project record as drawings, specifications, submittals, schedules, and cost workflows. Responses are routed to the responsible party, visible to the project participants who need them, and reportable across projects — so an open question is something the team can see rather than something someone has to remember.

    See how Jet.Build manages RFIs across active projects.

    Take about 30 minutes with our team to see how Jet.Build connects RFIs, submittals, documents, approvals, schedules, cost workflows, and reporting.

    Schedule a Demo