Power distribution, with purpose.
A switchgear submittal exception is a proposed departure from the project documents, not a detail to accept simply because it appears in a vendor’s package. A disciplined review connects each exception to the affected requirement, its technical and commercial consequences, the evidence needed to assess it, and the person authorized to decide. That record helps prevent unresolved assumptions from becoming costly changes during fabrication, delivery, or commissioning.
Trace each exception to a controlling requirement
Start with the exact specification section, drawing note, schedule entry, or approved design criterion that the exception changes. Record the vendor’s wording accurately, then describe the difference in plain terms. “Alternate breaker” is too vague on its own: identify the specified and proposed breaker type, frame or trip characteristics where applicable, control interface, and affected lineup position. Check whether the proposal also changes dimensions, access, maintenance clearances, or the documented one-line arrangement.
Confirm which project document governs when requirements conflict, and ask the engineer of record or designated reviewer to resolve ambiguity rather than assuming the vendor’s interpretation controls. Distinguish a genuine deviation from a clarification, an approved equal, or an incomplete response. One exception can touch several disciplines: a bus arrangement may affect protection coordination, cable terminations, equipment-room layout, and utility requirements. Cross-reference those interfaces so a decision does not close only one part of the issue.
Assess technical consequences and required evidence
Review the exception against the project’s actual operating conditions and ratings, not just a catalog description. Relevant checks may include nominal system voltage versus equipment maximum rating, continuous current, available fault current and required short-circuit rating, protective-device coordination, temperature-rise limits, enclosure and environmental conditions, and the specified construction standard. The applicable values depend on the project. A proposed rating or component must not be treated as acceptable until the responsible design reviewer confirms it against the approved basis of design.
Request evidence that answers the specific question. Depending on the exception, that may mean a revised outline drawing, a complete bill of material, breaker or trip-unit data, bus details, control schematics, terminal information, test documentation, or a written comparison against the requirement. Verify that documents apply to the proposed configuration and revision, rather than a similar product family. If a standard, UL 891 applicability, component availability, or U.S.-origin requirement matters, obtain confirmation for the specific assembly and order; do not infer compliance or origin from a general statement.

Document risk, scope boundaries, and approval ownership
An exception log should make the decision auditable. For each item, capture its unique identifier, source requirement, vendor proposal, affected equipment or interface, missing evidence, technical and schedule implications, disposition, approver, and date. Label unresolved matters as open; “noted” is not approval. Record whether acceptance requires a drawing revision, specification clarification, contract change, or coordination with another supplier. Preserve the vendor’s original exception text alongside the final decision so later reviewers can see precisely what was accepted.
Set boundaries on what the decision covers. Approval of a switchboard arrangement does not automatically approve field wiring, upstream protection, downstream equipment, installation means, commissioning responsibilities, or utility acceptance. State who owns each interface and what must be supplied by others. If an exception shifts responsibility or excludes an item, make that explicit in the purchase documents. Only the designated project authority should approve a departure from design intent; manufacturer confirmation of buildability is not a substitute for engineering approval.
Worked hypothetical: weigh a proposed breaker substitution
Suppose a project specification calls for a particular low-voltage breaker configuration and the submittal proposes a different breaker family. The vendor says it fits the compartment, but the package does not show the trip-unit functions or control connections. The reviewer should leave the exception open, identify the exact specified and proposed devices, and request configuration-specific data, revised drawings, and confirmation of the relevant short-circuit and coordination characteristics. Physical fit alone does not establish electrical or functional equivalence.
Assume the evidence then shows the proposed trip unit lacks a required function used in the protection study. The project engineer could reject the exception, request a compliant configuration, or—only if the design permits—evaluate a revised protection scheme and its effects on coordination, controls, and other equipment. The decision, supporting study revision, approving authority, and any cost or schedule effect should be recorded before release. This is a hypothetical review path, not a statement about a particular manufacturer’s equipment or a completed project.
Close the review with a controlled handoff
Before authorizing fabrication, reconcile the exception log with the latest approved submittal. Confirm that accepted changes appear on the applicable drawings and schedules, rejected items have been removed or corrected, and open items have an assigned owner and due date. Transmit the final disposition to the manufacturer, engineer, purchasing team, and affected trades through the project’s document-control process. If a decision changes the contract scope, route it through the authorized change process rather than relying on meeting notes or informal email.
For a quote on new custom equipment, provide the current one-line diagram, specification and applicable sections, equipment schedules, system voltage and available fault-current information, required ratings and standards, enclosure and environmental conditions, control and metering needs, cable-entry and termination constraints, and the project schedule and delivery destination. Mark known deviations separately from requested features. A manufacturer can assess buildability and proposed configuration, but project-specific ratings, component availability, standards, and U.S.-origin requirements must be confirmed for the order. Shorter lead time may be a goal, not a guarantee. This clear handoff is useful for Dallas–Fort Worth projects and for shipments elsewhere, without implying a local manufacturing facility.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Review question |
|---|---|
| Requirement traceability | Is the exact specification or drawing reference identified? |
| Technical evidence | Does documentation match the proposed configuration and revision? |
| Interface ownership | Are affected disciplines and supplied-by-others boundaries clear? |
| Decision control | Is an authorized approver and final disposition recorded? |
