COMPARISONS / MANUFACTURER DIRECT
Routine tests and type tests answer different questions. A routine test checks an individual assembly or unit against specified acceptance criteria; a type test supports the design by evaluating a representative configuration under defined conditions. The terms, scope, and required records depend on the applicable standard, equipment class, and project documents. Buyers should confirm what evidence is required before approving a design or shipment. Switchgear Builder Virginia manufactures new, custom switchgear in the USA with all-American components; applicable low-voltage switchboards may use UL 891 assemblies. Ratings, test scope, records, and schedules require project-specific verification and quote.
Two different purposes
A routine test is associated with an individual manufactured assembly, while a type test evaluates a representative design or configuration to establish that it meets specified design criteria. These terms are not interchangeable, and neither label alone tells a buyer exactly what was tested. The governing standard may define the terminology, test methods, sample basis, and required documentation differently for different equipment. Ask the supplier to identify the standard and edition, the exact assembly or design covered, and the acceptance criteria. Also clarify whether the requested evidence is a report, certificate, test record, or another document. This prevents a broad statement such as “tested” from being mistaken for evidence that every project requirement has been met. For new custom switchgear, compare the proposed scope with the one-line diagram, specifications, and approved submittals before treating a test label as proof of suitability.
What routine testing can show
Routine testing can provide evidence about a particular completed assembly, but its scope depends on the applicable standard and the agreed project requirements. It may address specified checks or measurements; buyers should not assume that every routine test covers every component, operating condition, or performance characteristic. Request a clear list of checks, the acceptance limits, the identification method linking records to the delivered assembly, and any exceptions. Confirm who performs the work and whether witnessing or inspection is required by the contract. Where documentation matters for commissioning or later maintenance, define its format and delivery point in the purchase documents. A routine test record is most useful when the equipment identification, test date, criteria, and results are traceable. It does not, by itself, establish that a design has passed every form of type testing or that the assembly matches an unreviewed application.
What type testing establishes
Type testing is design evidence based on testing a representative design or configuration under conditions defined by the relevant standard or specification. It can help demonstrate that a design meets specified criteria, but the result applies only within its stated scope. Differences in construction, ratings, materials, enclosure, or configuration may affect whether a report is applicable; have the manufacturer identify the tested design and explain any permitted variations. Buyers should review the report or other accepted evidence for the standard, test conditions, specimen description, results, and limitations. Do not infer a project rating from a test title or from a test performed on a different configuration. Type-test evidence also does not replace any routine tests required for the individual assembly. Before ordering, settle which design characteristics are fixed and which project options must remain consistent with the evidence, then record those assumptions in approved submittals.
Compare scope and records
A practical comparison starts with the purchase specification, not a generic test checklist. Identify the equipment class, governing standard and edition, required ratings, and each test or document the project calls for. Then separate evidence about the specific delivered assembly from evidence about its underlying design. Ask whether routine records will identify the exact assembly and whether type-test documentation covers the proposed construction and options. Clarify acceptance criteria, review timing, witness arrangements, deviations, and responsibility for resolving a failed or incomplete result. Requirements may differ among a low-voltage switchboard, medium-voltage equipment, and other assemblies, so avoid carrying assumptions from one equipment category into another. For applicable low-voltage switchboards, verify the specified UL 891 requirements and documentation; do not treat that standard as applicable to medium- or high-voltage switchgear. Keep approved answers with the project record.
Plan verification before release
Resolve test expectations while drawings and specifications are being reviewed, before manufacturing details are finalized. Provide the intended application, system information, required ratings, options, and governing project documents so the proposed configuration can be evaluated. If a specification calls for a particular test, report, inspection, approval, or witness point, state it explicitly and confirm feasibility, scope, and responsibility in writing. Ask how a proposed design variation affects the relevance of existing type-test evidence, and what records will accompany the specific assembly. Schedules and ratings remain subject to quote and verification; required review or testing can affect project planning, so agree on milestones rather than assuming a delivery date. Switchgear Builder Virginia builds new custom equipment in the USA with all-American components and ships nationwide. The final acceptance basis should be the applicable standard, approved submittals, and documented project requirements—not a test label standing alone.
