FAQ / MANUFACTURER DIRECT
Switchgear tests are specified by matching the equipment, project documents and required evidence—not by choosing a generic test package. Buyers should identify which checks apply to the supplied assembly, which procedures are optional or project-specific, and whether anyone must witness them. Switchgear Builder Virginia can build custom equipment with all-American components and direct USA manufacturing; test scope, records and schedule should be confirmed in the project quote and approved documents.
Start With the Equipment
Specify tests against the equipment actually being supplied: its type, configuration, voltage class, ratings and intended application. A low-voltage switchboard, for example, does not share every test requirement with medium-voltage gear, and requirements for one assembly should not be copied onto another without review. Identify the governing project specifications and applicable product standards, then resolve conflicts with the responsible engineer or purchaser before release. For applicable low-voltage switchboards, UL 891 requirements may be relevant; they do not establish a blanket test scope for all switchgear. Confirm the equipment’s intended listing or approval requirements separately, because a test request alone does not establish a listing. A clear equipment description helps the manufacturer determine which routine checks apply and which additional procedures need separate definition, review and quotation.
Routine Checks and Options
Separate applicable routine checks from additional tests requested for a particular project. Routine requirements depend on the equipment type and governing standard; they should be identified by reference rather than replaced with an informal promise of a broad “full test.” Optional or project-specific work might include extra inspection points, measurements, functional demonstrations, or documentation beyond the baseline. State exactly what is requested, which components or functions are in scope, and the acceptance criteria or reference procedure. Do not assume a requested test is appropriate, included, or available for every configuration. The manufacturer and project team should review the request for technical fit, safety, schedule impact and cost before it becomes part of the approved scope. This distinction lets buyers prioritize meaningful evidence instead of paying for vague or duplicative activity.
Define the Procedure
A useful test specification says what will be checked, how the result will be judged, and which approved document controls the procedure. Identify the applicable standard or project clause, test sequence, equipment boundaries, instruments or tools where relevant, and any prerequisites. For functional checks, name the intended operating functions and expected results without treating a demonstration as proof of every system condition. Clarify whether settings, wiring diagrams, approved submittals or customer-furnished interfaces must be available before testing. If a project requests a special procedure, submit it for review before fabrication or the planned test date; late changes can affect engineering, coordination and schedule. Avoid ambiguous phrases such as “test per spec” when several documents or revisions could apply. The final procedure should be consistent with the supplied design and approved scope.
Witnessing and Records
Witness testing is a coordination requirement, not a different equipment rating. Project documents should identify who may attend, which tests require notice, how much notice is expected, whether attendance is in person or remote, and what happens if a witness cannot attend. Confirm responsibilities for travel, access, safety orientation and approval of any test record. Specify the records needed, such as completed check sheets, measured results where applicable, instrument identification or calibration evidence when required, nonconformance notes, and authorized sign-off. Do not assume that photographs, certificates or a particular report format are included unless the quote and approved documents say so. Agree on record delivery, review and retention responsibilities before testing. Clear ownership avoids disputes over whether a test occurred, whether its result was accepted, and who must resolve an exception.
Align Scope Before Release
Before approving the purchase documents, compare the requested test scope with the equipment schedule, drawings, specifications and quotation. List each requirement, its source, responsible party, acceptance criteria, witness status and required record. Resolve mismatches in writing, including any tests that are excluded, optional or dependent on customer-furnished information. For custom builds, early agreement matters because configuration changes can alter the applicable procedure or evidence needed. Switchgear Builder Virginia manufactures new equipment and ships nationwide; the applicable test scope, ratings, records and schedule remain subject to quote and verification. Ask the project team to confirm who reviews submittals, who accepts results, and how deviations are documented. This creates a practical handoff from design to manufacturing and testing without implying that an unverified test, approval or delivery date is included.
