Define the Submittal Package Before Release
Start by identifying which documents the project team needs to review, when each is due, and who has authority to approve it. A useful submittal register can distinguish equipment data, outline and wiring drawings, component information, labeling schedules, inspection or test records, and closeout documents. Ask whether the owner, engineer, contractor, or commissioning team requires a particular file format, naming convention, review sequence, or document-control platform.
The specification should also distinguish required documents from items that are conditional on the equipment scope. Identify the assemblies and new retrofit components included, project tags, applicable drawings, and any required deviations or exceptions. Confirm whether calculations, coordination information, or interface details are part of the requested package. Agreeing on these boundaries with the project team helps prevent missing deliverables and avoids treating a general document list as a promise that every item applies to every configuration.
Review Drawings Against the Project Design
Drawing review is the opportunity to resolve fit, interface, and functional questions before equipment is released for manufacture. The project team should compare the submitted arrangement and dimensions with the approved equipment space, access requirements, cable entry and exit assumptions, and connections to adjacent equipment. Confirm that the drawing identifies the assembly sections and project design parameters needed for coordination; do not assume a preliminary outline is a final installation drawing.
Electrical drawings should make the specified circuit arrangement and control intent clear enough for review. Depending on scope, that may include one-line information, elementary or control diagrams, connection details, and terminal references. Check naming and device designations against the project's drawing set, and return consolidated comments through the designated reviewer. Record approval status and revision identifiers. Approval should resolve project comments without being treated as verification of site conditions that were not provided to the manufacturer.
Control Revisions and Approval Records
A documented revision process keeps purchasing, engineering, construction, and manufacturing aligned when requirements change. For each drawing or schedule, identify the revision, issue date, review status, and comment disposition. Ask the project team to state which revision governs procurement and manufacture, and how changes after approval will be evaluated. Maintain a traceable record of accepted exceptions so that a note in an email does not silently replace a requirement in the governing specification.
Before release, reconcile approved documents with the purchase scope, project specification, and quotation. Confirm quantities, equipment identifiers, interfaces, and any approved substitutions or deviations. If a project change affects a new retrofit component, verify that the revised scope and its documentation match the existing equipment information supplied for review. Engineering, component selection, schedule effects, and required records remain subject to project review; approval of one drawing does not automatically approve unrelated documents or later revisions.
Specify Test Reports and Acceptance Records
State which inspection or test documentation is required and what the project expects each record to identify. Useful traceability fields can include the equipment or assembly designation, document revision, inspection or test scope, date, and disposition. Clarify whether the requested record is a manufacturer’s report, a project inspection form, or another defined deliverable. The report must describe the work actually performed; do not assume a particular test, result, or report format is included until it is confirmed for the quoted configuration.
Coordinate documentation expectations with the project’s acceptance process before ordering. Ask who reviews the records, whether comments must be resolved before shipment, and whether copies are required in the closeout package. When applicable standards or a listing are specified, identify the precise requirement and confirm its relevance to the assembly and configuration under quotation. UL 891 applies to switchboards; it should not be treated as a blanket listing for all switchgear. Listing and applicable standards require configuration-specific verification.
Collect Component Manuals and Labeling Details
Request component manuals and product information for the components actually included in the new equipment or new retrofit scope. To make the package useful, agree on whether the project needs operating information, maintenance guidance, dimensional data, connection references, or manufacturer documentation. Confirm how documents will be indexed to the relevant device or assembly. American components may be specified for a project, but component origin and supporting documentation should be confirmed for the quoted scope; domestic-content compliance is not established merely by a general request.
A labeling schedule should align field-identifiable names with approved drawings and project conventions. Provide the required equipment tags, circuit or device descriptions, reference designations, and any specified text or format. Have the responsible reviewer check terminology, spelling, and consistency before labels are finalized. If a project has language, durability, or identification requirements, state them in the specification and confirm how they apply. The schedule is a controlled project document, not a substitute for verifying field conditions or installation requirements.
Assemble a Traceable Closeout Package
A useful final package lets the owner and maintenance team identify what was supplied and locate the corresponding records. Define closeout contents in advance: approved final drawings, applicable test or inspection reports, component manuals, labeling schedules, and other agreed project documents. Require a consistent equipment tag and revision reference across the index and files. Confirm whether deliverables are electronic, whether editable files are needed, and who will receive them so the format is established before closeout.
As-built documentation should reflect confirmed changes made to the supplied equipment and the information available from the completed project. Assign responsibility for reporting field changes and returning marked-up documents; the manufacturer cannot infer modifications made at the site. Reconcile the final set with approved revisions and identify unresolved items rather than silently presenting an incomplete record as final. Installation, servicing, testing, and energization require qualified personnel following approved procedures. Delivery timing and final documentation scope are confirmed during project review.
