{"id":78505,"date":"2026-09-10T00:55:12","date_gmt":"2026-09-10T00:55:12","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=78505"},"modified":"2026-09-10T00:55:14","modified_gmt":"2026-09-10T00:55:14","slug":"rfis-in-electrical-construction-writing-them-faster-and-getting-answers-that-stick","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/rfis-in-electrical-construction-writing-them-faster-and-getting-answers-that-stick\/","title":{"rendered":"RFIs in Electrical Construction: Writing Them Faster and Getting Answers That Stick\u00a0"},"content":{"rendered":"\n

An RFI that comes back with a vague answer is almost worse than no answer at all. It delays the decision, muddies the documentation trail, and leaves the estimator or foreman making an assumption they’re not supposed to make. Writing an RFI that produces a useful, binding response \u2014 rather than a non-committal reply that generates a follow-up \u2014 is a skill that separates contractors who control their projects from those who get managed by them. The right electrical estimating software<\/a> can give estimators a faster, clearer read of the drawing set \u2014 where many preconstruction RFIs originate \u2014 but the fundamentals of writing an effective request matter regardless of the tool. <\/p>\n\n\n\n

RFIs and RFPs: What They Are and How They Differ<\/h2>\n\n\n\n

The terms often get conflated, especially by teams new to formal commercial project structures. An RFP \u2014 Request for Proposal \u2014 is a procurement document. An owner or GC issues an RFP to solicit competitive bids or proposals from contractors and vendors. It defines the scope, requirements, and evaluation criteria for a project or service. It’s a document that initiates a commercial relationship.<\/p>\n\n\n\n

An RFI \u2014 Request for Information \u2014 is a project document. Contractors, subcontractors, and estimators submit RFIs to designers, engineers, or project owners when the construction documents contain ambiguity, apparent conflicts, or missing information that can’t be resolved without official clarification. It’s a document that protects everyone from assumptions becoming disputes.<\/p>\n\n\n\n

In electrical construction, RFIs most frequently surface during two phases: preconstruction, when estimators are reviewing drawings for bid and discover gaps that affect scope or pricing; and construction, when field teams encounter conditions that don’t match what the drawings show.<\/p>\n\n\n\n

What Are RFIs in Construction: The Electrical Context<\/h2>\n\n\n\n

For electrical subcontractors specifically, RFIs tend to cluster around a predictable set of issues. Understanding the categories helps both in writing better requests and in anticipating which drawing areas to scrutinize before a bid goes out:<\/p>\n\n\n\n

    \n
  • Symbol ambiguity.<\/strong> A device symbol appears on the drawing that isn’t in the legend, or a symbol in the legend doesn’t match what appears on the plans. Without clarification, the estimator either guesses or excludes the device \u2014 both of which create risk.<\/li>\n\n\n\n
  • Panel schedule gaps.<\/strong> The panel schedule shows a circuit but no corresponding device on the floor plan, or shows a load that doesn’t match any identifiable equipment. Either the drawing is incomplete or the estimator is missing context that the design team has.<\/li>\n\n\n\n
  • Conduit routing conflicts.<\/strong> The electrical routing path shown on the plans conflicts with structural or mechanical elements \u2014 a beam, a duct, a pipe chase \u2014 that occupy the same space. This is a coordination conflict that needs a design decision before installation begins.<\/li>\n\n\n\n
  • Specification conflicts with drawings.<\/strong> The specification requires a specific conduit type, fixture, or installation method that contradicts what’s shown on the plans. Which governs? Without a formal answer, the contractor is exposed.<\/li>\n\n\n\n
  • Scope boundary questions.<\/strong> Who provides and installs the fire alarm pull stations \u2014 Division 26 or Division 28? Who furnishes the low-voltage rough-in? These boundary questions are better resolved before bid submission than after award.<\/li>\n<\/ul>\n\n\n\n

    Writing RFIs That Get Useful Answers<\/h2>\n\n\n\n

    The quality of the response an RFI receives is largely determined by the quality of the question. Vague questions produce vague answers. Specific questions with clear context and a defined request for action produce answers the contractor can actually build from.<\/p>\n\n\n\n

    A well-constructed RFI includes:<\/p>\n\n\n\n

      \n
    1. A precise description of the condition.<\/strong> Not “there’s a conflict on sheet E-3” but “Sheet E-3 shows a 4-inch EMT conduit routed through grid line B-7 at elevation 9′-6″, which conflicts with the structural beam shown on structural drawing S-12 at the same location. The beam occupies elevation 9′-2″ to 10′-2″.”<\/li>\n\n\n\n
    2. The specific question being asked.<\/strong> “Please confirm the revised routing path for this conduit run, or advise whether the structural drawing requires revision.” One question per RFI \u2014 not three questions bundled into one submission.<\/li>\n\n\n\n
    3. The drawing and specification references.<\/strong> Every claim in the RFI should reference the specific sheet, detail, or specification section it’s drawn from. This protects the contractor and gives the design team what they need to answer without going back for more information.<\/li>\n\n\n\n
    4. The impact on scope, schedule, or cost if the question isn’t answered.<\/strong> Not as a threat \u2014 as factual context. “Clarification is required prior to material procurement, which is scheduled to begin [date].” This framing makes the urgency concrete without being adversarial.<\/li>\n\n\n\n
    5. A proposed solution where appropriate.<\/strong> Offering a suggested resolution \u2014 “Contractor proposes rerouting the conduit to elevation 8′-0” \u2014 gives the design team something to confirm or modify rather than starting from scratch. Responses to proposed solutions tend to arrive faster than responses to open-ended questions.<\/li>\n<\/ol>\n\n\n\n

      Preconstruction RFIs: The Category Most Electrical Subs Underuse<\/h2>\n\n\n\n

      Most contractors think of RFIs as a construction-phase tool \u2014 something you submit when the field encounters a problem. The more valuable application is preconstruction, during the estimating phase, when drawing issues can be clarified before they become priced assumptions.<\/p>\n\n\n\n

      An estimator who submits a targeted RFI during the bid phase \u2014 identifying a scope conflict, a missing detail, or a drawing inconsistency \u2014 does two things simultaneously: they get the information they need to price accurately, and they document that they identified the issue before award, which strengthens their position if the same issue generates a change order later.<\/p>\n\n\n\n

      This is where a faster, more structured takeoff helps. When counting doesn’t consume the entire bid window, estimators have time to review the drawing set critically \u2014 and a structured takeoff makes the gaps easier to spot: a symbol that isn’t in the legend, a panel-schedule circuit with no matching device, a routing path that looks like it conflicts with structure. Catching those during the bid, while there’s still time to submit an RFI, is what moves RFI generation from a reactive response to field problems toward a proactive step in the estimating process \u2014 which is where it produces the most value. <\/p>\n\n\n\n

      What a Licensed Electrical Contractor’s Written Estimate Should Include<\/h2>\n\n\n\n

      The RFI process and the written estimate serve related but distinct purposes. Understanding what should be included in a written estimate from a licensed electrical contractor helps clarify what the estimate documents versus what RFIs need to resolve before the estimate is finalized.<\/p>\n\n\n\n

      A complete written estimate from a licensed electrical contractor covers: a detailed scope of work with explicit inclusions and exclusions; a cost breakdown separating labor, materials, overhead, and profit; the specific drawings and specification sections the estimate is based on, including which addenda were incorporated; a list of assumptions made where the documents were ambiguous \u2014 this is where unresolved RFI questions should appear explicitly; payment terms and schedule; project timeline; and licensing, bonding, and insurance documentation.<\/p>\n\n\n\n

      The connection between RFIs and the estimate is direct: every open question that gets resolved through an RFI before submission produces a more defensible estimate. Every question that doesn’t get resolved becomes an assumption in the estimate \u2014 and assumptions that aren’t documented become disputes after award.<\/p>\n","protected":false},"excerpt":{"rendered":"

      An RFI that comes back with a vague answer is almost worse than no answer at all. It delays the decision, muddies the documentation trail, and leaves… <\/p>\n","protected":false},"author":56,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-78505","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/78505","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/56"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=78505"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/78505\/revisions"}],"predecessor-version":[{"id":78506,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/78505\/revisions\/78506"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=78505"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=78505"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=78505"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}