Make every procurement question traceable
Request for information management gives the project team a controlled way to resolve uncertainties before they affect new switchgear selection, pricing, or release. An RFI should identify the document or requirement in question, explain the conflict or missing detail, and state what decision is needed and by when. Tie each item to a drawing, specification section, equipment tag, or interface where possible. This helps procurement, engineering, the manufacturer, and other project participants discuss the same issue rather than relying on informal email threads.
The goal is not simply to collect answers. A useful record shows who raised the question, who is responsible for responding, the response date, and whether the answer changes scope or requires a revised submittal. Keep the original question and response together; avoid replacing earlier text with an unexplained update. That history supports review of new switchgear requirements and gives the team a clearer basis for later approvals and purchasing decisions.
Start with the right project inputs
An RFI is easier to answer when it includes the information that governs the equipment. Relevant inputs may include the one-line diagram, load and feeder schedules, equipment location, system voltage, available fault-current information, grounding approach, operating sequence, and project specifications. Identify which documents are current and note conflicts between them. Do not treat an incomplete drawing or preliminary value as a confirmed design requirement; ask the responsible electrical professional to verify the governing information.
Also identify the procurement boundary: what equipment is included, what is supplied by others, and which connections or functions depend on adjacent systems. Relevant interfaces can include upstream protection, downstream feeders, transformers, generators, transfer equipment, metering, controls, and building or utility requirements. Their applicability varies by project. A concise RFI with marked-up references and a focused question helps the team distinguish a true design decision from a document coordination issue.
Resolve ratings and design choices deliberately
Questions about voltage, continuous current, short-circuit withstand or interrupting ratings, enclosure, bus arrangement, and protective devices need project-specific review. Do not infer an acceptable rating from a single drawing note or assume a particular configuration is universally available. The design team should confirm system conditions, load requirements, environmental conditions, applicable codes and standards, and coordination with connected equipment before directing a selection. Where information is pending, record the open item and identify who will establish the requirement.
An answer can also affect assembly layout, access, cable entry, metering, controls, or future provisions. Ask the responder to state whether the answer is a clarification, a design change, or a request for additional information. If a change is intended, specify the affected equipment and documents and request confirmation of its procurement impact. UL 891 may apply to suitable switchboard assemblies, but it does not automatically apply to every switchgear product; applicability and other standards must be verified for the actual design.
Record decisions, not just responses
A response becomes useful procurement documentation when the team records its disposition. Mark whether the RFI is answered, rejected, superseded, or awaiting more information, and identify the person authorized to approve the relevant design direction. Capture any conditions, assumptions, and related approvals in the response itself. A manufacturer’s clarification about its proposed new equipment should not be treated as approval of the project’s electrical design unless the responsible parties explicitly establish that authority.
When a response changes requirements, link it to the affected specification, drawing, schedule, or submittal revision. Identify whether the change affects scope, cost, lead time, or release timing, and request confirmation rather than assuming the impact. This creates a practical audit trail for procurement and reduces the risk that an obsolete answer is used to authorize fabrication. Keep a current RFI log with status, owner, due date, response, disposition, and associated document revisions.
Coordinate submittals, interfaces, and verification
Before accepting an answer for procurement, compare it with the complete equipment submittal and the project’s interface requirements. Check that revised one-lines, elevations, connection details, schedules, and control information remain consistent where applicable. Confirm who will update each document and how the revision will be distributed. If an answer affects protection settings, control logic, interlocking, or coordination with another assembly, route it to the qualified electrical professionals responsible for those decisions.
Testing and inspection expectations should also be stated clearly in the project documents. Identify what inspections, factory tests, or field verification are required, who witnesses or accepts them, and which requirements govern, where applicable. Do not assume that an RFI response changes a test scope or establishes a listing. Any required testing and acceptance criteria depend on the equipment design and project specifications. Keep unresolved test or interface questions open until the responsible parties document an agreed path.
Close the loop before equipment release
For each open item, set a response owner and a needed-by date tied to the procurement schedule. Prioritize questions that could change equipment selection, interfaces, approved submittals, or release authorization. Before ordering or authorizing a revision, circulate the final response to the affected parties and confirm that the intended documents reflect it. If requirements remain uncertain, document the hold point and the information needed to clear it; do not convert an assumption into a purchase requirement.
A practical closeout is a dated log showing the question, answer, decision authority, disposition, and resulting revision, with superseded files clearly identified. Review that log against the latest approved project documents before procurement release. For custom assemblies, provide the manufacturer with the confirmed requirements and identify any remaining exclusions or open decisions. This disciplined handoff helps teams procure new switchgear against an agreed scope while preserving a clear record for later coordination and verification.
Project specification checklist
Use this checklist to organize the details for a project-specific review. Final ratings, applicable standards and equipment selections depend on the approved design.
| Item | What to confirm |
|---|---|
| System and load basis | Confirm project voltage, load requirements, available fault-current information, grounding, and the documents that establish each value. |
| Equipment scope | Identify included assemblies, exclusions, equipment tags, and boundaries with equipment or work supplied by others. |
| Ratings and environment | Have qualified project professionals verify required ratings and enclosure conditions for the actual installation and system. |
| Interfaces | Document upstream and downstream connections, protection, controls, metering, and other applicable coordination points. |
| Revision control | Track each RFI response, disposition, approval authority, affected documents, and resulting revision before release. |
| Verification expectations | Confirm applicable inspection, testing, witnessing, and acceptance requirements in the project documents. |