Power distribution, with purpose.
A complete switchgear submittal package gives the project team enough information to verify that the proposed assembly fits the electrical design, physical space, controls, and contract requirements. Its contents depend on equipment type, project stage, and specification; a low-voltage switchboard package is not interchangeable with one for medium-voltage switchgear. Use the submittal review to resolve open interfaces before fabrication, not to assume that a drawing or rating has been approved merely because it appears in a package.
Start with the project inputs and review basis
A useful package begins with a defined basis of design. For a quotation and preliminary submittal, provide the applicable specification and drawing revisions, system nominal voltage and frequency, phase and wire configuration, service arrangement, available fault-current information, and the required equipment function. Identify whether the scope is a low-voltage switchboard, switchgear, or another assembly, and state the intended installation environment, lineup location, access constraints, and required delivery milestones. Missing or conflicting inputs can affect the proposed arrangement, component selection, ratings, and schedule.
The purchaser should also supply the one-line diagram, load or feeder schedule, control requirements, communications expectations, and project-specific forms or submittal rules. Clarify who furnishes upstream and downstream cables, protective devices, metering, control power, and field terminations. For projects in Dallas–Fort Worth or elsewhere, shipping and site access details may inform packaging and delivery coordination, but they do not establish a local manufacturing location or installation scope. Confirm all assumptions and exclusions in writing.
Use the one-line diagram to verify electrical intent
The one-line diagram should show the proposed electrical arrangement clearly enough to trace incoming sources, bus sections, ties, feeders, protective devices, metering, and grounding provisions. Compare it with the project design for source configuration, transfer or paralleling functions where specified, and the intended normal operating arrangement. Device tags and ratings should correspond to the project schedule and other package drawings; inconsistent labels or a missing tie point can conceal a scope gap.
Review system nominal voltage separately from the equipment’s maximum voltage rating. Check continuous current, interrupting or withstand requirements, and short-circuit ratings against the project’s available fault-current study and specification. A rating cannot be inferred from voltage alone, and final suitability depends on the specific configuration and components. UL 891 applies to low-voltage switchboards where applicable; it is not a general listing for medium-voltage equipment. Confirm standards, ratings, and any required certification for the exact assembly and order.

Check elevations, dimensions, and field interfaces
Front and side elevations, outline dimensions, and section arrangements let reviewers compare the proposed lineup with the electrical-room plan and installation clearances. Check overall width, height, depth, access space, cable entry and exit, conduit zones, and any top or bottom routing assumptions. Confirm the relationship to walls, doors, columns, overhead services, and adjacent equipment. If the room layout is still developing, mark dimensions and clearances that remain subject to coordination rather than treating them as final.
The package should make connection boundaries understandable: bus or cable termination points, grounding connections, control wiring interfaces, and any field-furnished components should be identified as appropriate to the design. Structural support, anchorage, seismic requirements, ventilation, and environmental conditions may require project-specific review and coordination with other disciplines. A drawing that fits the nominal room dimensions may still conflict with cable bending space or access needs, so reviewers should resolve those interfaces before releasing approved-for-production documents.
Reconcile device schedules, ratings, and controls
Device schedules help connect feeder names and circuit functions to the one-line and physical arrangement. Review each device tag, quantity, function, frame or device designation where applicable, trip or protective settings basis, metering, and accessory requirements against the project documents. Identify spare or future provisions explicitly, including whether they are spaces, installed devices, or provisions for later work. These terms are not equivalent and can affect both present scope and future expansion.
Control schematics should explain the intended control logic and show relevant power sources, interlocks, status points, alarms, and external connections within the manufacturer’s scope. Coordinate terminal designations and interface signals with the controls contractor, building system, or other equipment supplier. Do not assume that communications protocols, protective settings, or field wiring are included unless the specification and scope say so. Changes to control logic or device selection can affect drawings and component availability, so resolve them before final approval.
Make exceptions and review status visible
A useful submittal identifies deviations, clarifications, and unresolved items in a dedicated exceptions or notes section. Compare the proposed scope against each material specification requirement, including construction, environmental provisions, accessories, testing documentation, and required standards. If a requirement cannot yet be confirmed, label it as an open item and state what information or engineering review is needed. Silence should not be treated as acceptance of a deviation, and a reviewer’s stamp does not replace the purchaser’s technical review.
Agree on submittal stages and document status, such as preliminary review, approval with comments, or approved for production, using the project’s required terminology. Track revision numbers and incorporate accepted comments into the next issue. A change after approval—such as a revised fault-current study, room layout, feeder schedule, or control interface—may require a drawing update and a review of rating, cost, and schedule effects. A shorter lead time may be a manufacturing goal, but it is not guaranteed and depends in part on complete inputs and timely decisions.
Define final drawings and the scope boundary
The final package should distinguish approved submittal drawings from record documents and state what documents will be provided at each stage. Depending on the order and project requirements, the record set may include final one-lines, elevations, device schedules, control schematics, and applicable equipment data. Establish whether test reports, operation and maintenance information, or other closeout documents are required, and confirm their specific scope rather than assuming every project receives an identical package.
Custom new equipment can be developed around project requirements, with American components considered where specified and available; component origin and availability must be confirmed for the particular order. UL 891 assemblies may be applicable to low-voltage switchboards when the exact design and project requirements support that scope. Ratings, standards, listing or certification status, US-origin requirements, and drawing deliverables all require order-specific confirmation. A quotation should identify required equipment, quantities, key electrical and physical inputs, requested options, governing documents, and known exceptions so the manufacturer can define the proposed scope accurately.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Review factor | What to compare |
|---|---|
| Electrical basis | Nominal system voltage, equipment rating, and fault-current requirements |
| Physical fit | Lineup dimensions, clearances, access, and cable routing interfaces |
| Device definition | Feeder tags, device functions, accessories, and spare provisions |
| Controls and scope | Schematics, external interfaces, exceptions, and deliverables |
