How to Write an RFI That Gets Answered Fast (A Detailer's Playbook)

An unanswered RFI is a stopped fabrication schedule. Most detailers and fabricator PMs know that. The problem is most RFIs are written in ways that practically guarantee a slow response. They're vague about what information is needed. They ask multiple unrelated questions in one document. They don't include a drawing reference or a grid location. They don't explain why the information is needed by a specific date. They describe the problem instead of asking for the answer. Engineers and GCs review dozens of RFIs per week across multiple projects. An RFI that makes them work to understand what's being asked gets put in the "respond when I have time" pile. One that's clear, specific, referenced, and includes a suggested resolution gets answered in a day. This playbook shows you exactly how to write the second kind.

Why Most RFIs Get Slow Responses — and It's Usually the RFI's Fault

Detailers and fabricator PMs often blame slow response times on unresponsive EORs or disorganized GC project teams. Sometimes that's true. But in most cases, the RFI itself is the bottleneck.

An EOR reviewing RFIs isn't sitting at an empty desk waiting for your question. They're managing multiple projects, responding to submittals, attending OAC meetings, and fielding calls. When an RFI lands in their inbox missing a grid reference, bundled with three unrelated questions, and containing no suggested resolution — they can't respond without doing investigative work first. That takes time they don't have right now. So it waits.

The best-written RFIs take that burden off the EOR. They're self-contained documents: they tell the reviewer what they need to know, where to look, what's being asked, and what a reasonable answer might look like. They make saying "yes" or "approved as noted" the path of least resistance.

The Anatomy of a Well-Written RFI

Clear Subject Line with Project, Drawing Reference, and Issue Type

The subject line is the triage mechanism. "RFI #047 — [Project Name] — Sheet S-301, Grid C.5/7 — Beam-to-Column Connection Clarification" gets routed to the right person immediately. "Question about connection" does not.

Every subject line should include: project name or number, the RFI sequence number, the specific drawing sheet and detail reference, and a brief issue type. This lets the EOR's admin route it correctly, and it lets the engineer orient themselves before they even open the document.

One Question Per RFI (or Clearly Numbered If Multiple Related Questions)

One question, one RFI — as a default rule. If you bundle a moment connection clarification with a column base plate anchor rod question and a roof deck edge angle conflict, you've created a document that requires three different engineers to respond, may have different response deadlines, and can't be closed until all three answers come back.

If questions are genuinely interdependent — for example, the anchor rod diameter affects the base plate thickness — they belong in one RFI, numbered clearly as Question 1, Question 2, and so on. But "related" doesn't mean "on the same project." Keep it tight.

Specific Location Reference — Sheet, Detail, Grid Line

"The beam connection at the second floor" is not a location. "W18x50 beam at Grid C.5/Elev. +18'-0", per Sheet S-201 Detail 4/S-201" is a location.

Give the EOR a coordinate system they can use without opening a separate index. Sheet number, detail bubble, grid intersection, elevation — all of it. If there's a Tekla model reference or a mark number, include that too. The less hunting they have to do, the faster they respond.

What Information You Need — Not What Problem You Have

This is the most common structural flaw in RFIs. "The beam flange conflicts with the HSS column" is a problem statement. "Please confirm whether the W14x48 beam at Grid D/4 should frame into the HSS8x8x1/2 column web or be offset to the column flange per Detail 6/S-402" is a question.

Frame every RFI as a request for specific information. The EOR already trusts that you wouldn't issue an RFI unless there was a real issue — you don't need to sell them on the problem. You need to make the answer easy to provide.

A Suggested Resolution If You Have One

This is the single highest-leverage thing you can do to accelerate RFI responses. Detailers who include a suggested resolution — "We propose extending the shear tab per the attached sketch to clear the HSS corner radius. Please confirm or revise." — consistently get faster turnaround than those who don't.

Why? Because engineers can say "Approved" to a reasonable solution in thirty seconds. They can't say "Approved" to an open-ended question without thinking through all the options themselves. Suggested resolutions do the engineering legwork for them and reduce the cognitive load of responding. When you've done 500 similar connections, you usually know what the answer should be. Put it in the RFI.

A Deadline Tied to Your Fabrication Schedule — and Why

"Please respond by [date]" with no explanation is easy to deprioritize. "Response required by March 15 to maintain our IFC submittal window of March 22 and the fabricator's release date of April 1" is a schedule impact statement.

Tie every RFI deadline to a real downstream event: IFC submittal, shop drawing release, material order cutoff, erection sequence. EORs respond to schedule pressure they understand. Give them the reason, not just the date.

What Not to Do: The 10 RFI Mistakes That Slow Everything Down

1. Vague subject lines with no drawing reference or issue type

2. Multiple unrelated questions in a single RFI document

3. Problem statements instead of questions — describe what you need, not what went wrong

4. No location reference — grid lines, elevations, and detail callouts are mandatory

5. No suggested resolution — making the EOR solve the problem from scratch

6. Unreferenced attachments — sketches and markups with no callouts explaining what you're showing

7. Arbitrary deadlines with no fabrication schedule context

8. Urgent RFIs for non-urgent issues — flagging everything as critical desensitizes the team

9. Duplicate RFIs for questions already in the submittal comments or addressed in prior correspondence

10. Issuing RFIs before checking the contract documents — confirm the information isn't already in the specs, the structural notes, or the geotech report before asking

How to Escalate an Unanswered RFI Without Torching the Relationship

RFIs go unanswered. It happens even when they're well-written. When response time is affecting your schedule, escalation is appropriate — but how you do it matters.

Start with a direct email to the EOR referencing the RFI number, the original sent date, and the schedule impact: "RFI #047 was issued March 8. We have not received a response. Our IFC submittal is March 22. Please confirm status." Keep the tone flat and factual.

If that doesn't move it in 24-48 hours, loop in the GC's project manager. Don't frame it as a complaint — frame it as a schedule coordination issue: "I wanted to make you aware of the open RFI below, as the response is now on the critical path for our submittal window." This gives the GC PM the information they need to apply their own pressure without you having to go over anyone's head.

Document every follow-up. An unanswered RFI with three documented follow-ups and clear schedule impact language is protection if the project ends up in a delay claim.

Using the RFI Log as a Project Management Tool — Not Just a Paper Trail

Most fabricator shops maintain an RFI log because their contract requires it. The smarter shops use it as an active scheduling tool.

Your RFI log should track: issue date, sent-to party, required response date, actual response date, and schedule impact if late. Review it weekly alongside your shop drawing release schedule. Any open RFI with a response date inside your next IFC window needs a follow-up call, not just an email.

A well-maintained RFI log also tells you patterns over time. If a particular EOR or GC consistently responds late, you can build that latency into your schedule on the next project. If a project is generating RFIs at three times the normal rate, that's a signal that something is wrong with the design documents — and that conversation needs to happen now, not after the delay.

When to Issue a Deviation vs. an RFI: Knowing the Difference

Not every field conflict or document discrepancy requires an RFI. A deviation is appropriate when you're proceeding with work that differs from the contract documents with prior written approval — typically because waiting for a formal RFI response would delay fabrication beyond what the schedule allows.

Issue a deviation when: the change is clearly minor, you have verbal or email confirmation from the EOR, and you need to document that confirmation before proceeding. Issue an RFI when: you don't have a confirmed answer, the change has structural implications, or the question could affect other assemblies or sequences.

Confusing the two is a liability issue. Deviations without documentation, or proceeding on informal answers to questions that should have been RFIs, are how fabricators end up holding the bag on field errors that originated in the design documents.

Template: NRSteel's Standard RFI Format

The following format can be adapted for any project management platform or standalone document:

RFI NUMBER: [Project #] - RFI - [Sequential Number]
DATE ISSUED: [Date]
ISSUED BY: [Detailer/Firm Name]
ISSUED TO: [EOR Name, Firm]
COPY: [GC PM, if applicable]
PROJECT: [Project Name and Number]
DRAWING REF: [Sheet Number, Detail Reference]
LOCATION: [Grid Line / Elevation / Mark Number]
SUBJECT: [One-line description: issue type + location]

QUESTION:
[Single, clearly framed question requesting specific information]

BACKGROUND:
[Two to three sentences of context — only what the reviewer needs to understand the question. No narrative. No editorializing.]

SUGGESTED RESOLUTION:
[Your recommended approach, with sketch or markup attached if relevant. Label clearly as a suggestion, not a directive.]

ATTACHMENTS:
[List any markups, sketches, or relevant excerpt from the drawings]

RESPONSE REQUIRED BY: [Date]
SCHEDULE IMPACT: [Specific downstream event affected if response is late]

This format works whether you're managing RFIs through Procore, Submittal Exchange, PlanGrid, or a shared spreadsheet log. The structure matters more than the platform.

NRSteel works exclusively with steel fabricators on commercial and institutional structural projects — and RFI management is part of every engagement, not an afterthought. If you're evaluating detailing partners for your next project, get in touch with NRSteel for a scope review. Same timezone, direct engineer access, no relay chains.