Power distribution, with purpose.
Approved switchgear drawings document the design accepted for fabrication; as-built records document the equipment and connections actually delivered, including approved changes made during production. They are related records, not interchangeable labels. A project should define who maintains each record, what evidence supports revisions, and what the purchaser expects at handover before equipment is released for manufacture.
Approved design is not the same as as-built documentation
An approved drawing set is the design baseline at a particular review stage. Depending on the project, it may show the one-line diagram, arrangement, elevations, wiring, bill of material, and control details accepted by the purchaser or its engineer. Approval does not, by itself, prove that every page reflects the final manufactured assembly. A revision issued after approval may change a device, terminal assignment, label, or connection while retaining the earlier approval mark as evidence of design review.
As-built records should identify the final configuration, rather than simply repeat the approved submittal. The exact record may consist of revised drawings, schedules, and other agreed documents; it need not imply a field survey or independent verification of every installed conductor. The specification should state what “as-built” means for the order, which documents are included, and whether the record covers factory changes only or also changes made after shipment by others.
Assign ownership and define the record boundary
Record ownership is a project decision. The purchaser may require the manufacturer to maintain manufacturing changes through shipment, while the electrical contractor, engineer, or owner records later field modifications. Without a clear boundary, two parties can each assume the other has updated the controlled set. Identify who approves a change, who updates the source file, and who distributes the authoritative revision to operations and maintenance teams.
Set a document hierarchy for conflicts among the purchase specification, approved drawings, change notices, and final records. Also state whether the delivered record is the manufacturer’s equipment documentation or a complete facility record. For a Dallas–Fort Worth project or a shipment elsewhere in the United States, the same distinction matters: switchgear drawings cannot establish that site cabling, protection settings, or downstream equipment were installed as shown unless those items are expressly within the documented scope.

Capture changes with traceable revision control
A useful change process ties each revision to a specific decision. Record the affected drawing or schedule, revision identifier, date, change description, and approval status. Where applicable, link the change to a purchaser instruction or approved deviation. This makes it easier to distinguish a corrected drawing from a change that alters the specified function, interface, or equipment configuration. Unresolved comments should remain visible as open items, not be silently treated as accepted.
Choose a practical review process before fabrication. Frequent review cycles can catch interface errors early, but late comments may affect design coordination, component availability, or the target shipment schedule. A record set prepared only after manufacturing may also require extra engineering review if source documents are incomplete. Any commitment to provide or update as-built records should therefore be confirmed for the particular order, including revision limits, review timing, deliverable format, and treatment of changes requested after release.
Provide inputs that make a useful record possible
For a quote, supply the applicable specification and drawing list, system one-line, equipment schedule, required ratings, project revision, and the purchaser’s documentation requirements. Identify interfaces that depend on other packages, such as incoming and outgoing connections, control-power sources, metering, protection, communications, and external terminal wiring. Include the governing document formats, naming conventions, approval workflow, submittal dates, and required quantities or file-access method. These inputs help define effort without assuming every project requires the same record package.
Clarify whether the manufacturer is expected to document only its supplied assembly or coordinate changes originating with the engineer, contractor, or other vendors. State who provides final field redlines and who verifies them. If those responsibilities are not assigned, the handover may accurately describe the manufactured equipment yet omit later site changes. Custom builds and American components can be discussed as order requirements, but availability and any U.S.-origin conditions must be checked against the specified components and procurement rules.
Specify deliverables, formats, and handover checks
Name the records required at closeout rather than relying on a general phrase such as “complete documentation.” Depending on the agreed scope, this may include a final one-line, assembly arrangement, wiring diagrams, terminal plans, device or fuse schedules, nameplate information, and revision history. Specify whether files must be searchable PDFs, native editable files, or both, and whether paper copies are required. Native files can support future edits, but ownership, software compatibility, and limits on reuse should be settled in the purchase documents.
A handover review should check that document numbers and revisions are consistent, equipment identifiers match labels, referenced sheets are included, and open deviations are resolved or explicitly carried forward. It should also establish where the owner will store the controlled record and how superseded copies will be marked. UL 891 may apply to low-voltage switchboard assemblies when specified and appropriate; it is not a general listing for medium-voltage switchgear. Confirm applicable standards and assembly status for the actual order rather than inferring them from drawing delivery.
Treat field changes and unverified work honestly
After shipment, the owner should preserve the manufacturer’s final equipment records while separately tracking installation changes. A contractor’s field markups can be valuable evidence, but they are not automatically manufacturer-verified drawings. If a field change affects protection, control logic, bus connections, or equipment interfaces, route it through the responsible engineer and qualified parties. Do not represent an unverified redline as a confirmed equipment configuration or use drawing records as a substitute for required inspection, testing, or commissioning.
A purchaser can request a defined process for reviewing field information, but any such service, verification, or drawing revision is a planned capability until confirmed in the specific proposal and purchase order. Confirm scope, source information, engineering review, exclusions, and schedule before relying on it. Ratings, short-circuit values, component availability, applicable standards, and U.S.-origin requirements likewise need order-specific confirmation; the final records should reflect only the configuration and evidence actually established.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Decision to document |
|---|---|
| Record boundary | Factory configuration only, or factory plus defined field changes |
| Revision control | Approval authority, revision identifiers, and change traceability |
| File handover | Required formats, naming, access, and editable-file expectations |
| Verification | Evidence required and party responsible for confirming field updates |
