Engineering Change Order / Revision Control SOP

This procedure defines how a proposed engineering change is requested, evaluated, approved, and released at Blitzpanel, how the resulting revision is numbered and identified, and how the change is communicated to production, procurement, and the controlled document set.

It exists so that no drawing, schematic, BOM, or work instruction changes silently — every change has a traceable requester, a documented reason, a defined effectivity point, and an approved disposition for any material or job already in process.

A disciplined change-control practice prevents the shop from building to an out-of-date or unofficial revision, protects UL508A listing integrity, and gives Engineering, Quality, and Sales a defensible record of what changed, when, and why.

Applies to any proposed change to a released drawing, schematic, panel layout, bill of materials, wiring diagram, or work instruction, whether the change originates from a customer request, an internal design correction, a component substitution, or a non-conformance finding.

Covers change request intake, technical and commercial impact assessment, approval, revision numbering, effectivity determination, disposition of in-process jobs and stock, and notification/re-issue of controlled documents.

Does not cover the original design review and customer sign-off before first release (see Customer Submittal / Drawing Approval SOP) or the floor-level handling of an in-process redline before it is formally dispositioned as an ECO (see Job Traveler / Document Control SOP).

ECR — Engineering Change Request: the initial, unapproved proposal to change a released document, describing the problem or opportunity and the suggested change.

ECO — Engineering Change Order: the approved, released instruction that authorizes a specific change, assigns the new revision identifier, and states its effectivity and disposition instructions.

Revision (rev) — a uniquely identified, approved state of a controlled document; every approved change increments the revision. TODO: confirm the Blitzpanel revision-identifier scheme (letter vs. numeric, and whether pre-release drafts use a separate sequence from post-release revisions).

Effectivity — the point at which an approved change takes effect, expressed as a date, a specific job/serial number, or "next build"; it determines which units are built to the old revision and which to the new.

Disposition — the approved treatment of material, sub-assemblies, or jobs already in process or in stock when a change is released: use-as-is, rework, scrap, or return-to-vendor.

As-built — the final revision and configuration actually shipped on a specific job, which may differ from the current released revision if the job's effectivity predates a later change.

Role	Responsibility
Requester (any role)	Submits the ECR with a clear description of the problem, the proposed change, and the reason (customer request, error correction, cost/lead-time improvement, non-conformance).
Engineering	Evaluates technical feasibility and UL508A/listing impact, drafts the revised document, and assigns the new revision identifier once the ECO is approved.
Change Control Board / Approver	Reviews cost, schedule, and compliance impact and approves or rejects the ECO before release. TODO: define who sits on the change control board or who the single approver is, and any approval threshold (e.g., cost impact, safety-related change).
Document Control Administrator	Issues the new revision to the master file, pulls superseded copies from circulation, and updates the document log (see Job Traveler / Document Control SOP).
Production Control / Planner	Determines which in-process jobs are affected by the stated effectivity and coordinates disposition on the floor.
Procurement	Assesses impact on open purchase orders, on-hand stock, and approved vendor parts, and executes the approved disposition for affected material (see Procurement SOP).
Sales / Account Manager	Notifies the customer when a change affects price, lead time, form/fit/function, or a previously approved submittal, and re-quotes if required (see Quoting SOP).
Quality / QC	Confirms the ECO is closed out correctly on affected travelers and that no job ships against a superseded revision without an approved disposition.

ECR/ECO form or workflow used to log the request, impact assessment, approval, and effectivity. TODO: name the current form/template and whether it is paper, spreadsheet, or a PLM/ERP workflow.

Master document control file / system of record for current-revision drawings, schematics, BOMs, and work instructions (shared with Job Traveler / Document Control SOP). TODO: name the system of record.

ECO log or register tracking every request by number, status (open/approved/rejected/closed), affected documents, and effectivity. TODO: name the system used to maintain the ECO log.

Revision block/title-block standard on drawings so the current revision letter/number and date are always visible on the document itself. TODO: confirm or reference the standard title-block format.

6.1 Requesting a change

Any employee who identifies a needed change — a design error, a customer request, an obsolete or substituted component, or a non-conformance finding (see Non-Conformance / Rework SOP) — submits an ECR stating the affected document(s) and revision, the problem, the proposed change, and the reason.

Assign the ECR a sequential tracking number at intake and log it as open before any evaluation begins.

Route the ECR to Engineering for technical review; incomplete requests are returned to the requester for the missing information before evaluation proceeds.

6.2 Impact assessment & approval

Engineering assesses technical feasibility, safety implications, and whether the change affects the panel's UL508A listing basis (e.g., short-circuit current rating, component listing, spacing/clearance) or other referenced standard. TODO: verify exact UL508A / NFPA 79 clause references before citing a listing impact.

Procurement assesses cost, lead time, and impact to open purchase orders or approved-vendor status; Production Control assesses schedule and capacity impact to jobs currently in the shop.

Sales assesses whether the change affects a quoted or contracted price, delivery date, or a customer-approved submittal, and whether customer notification or re-approval is required before release.

The Change Control Board / Approver reviews the consolidated assessment and approves, rejects, or returns the ECR for rework; only an approved ECR becomes an ECO. TODO: define approval authority and any dollar/safety threshold requiring a higher level of sign-off.

6.3 Revision numbering & identification

On approval, Engineering assigns the next sequential revision identifier to each affected document and records the ECO number, date, and a brief description of the change in the document's revision history block.

Every controlled document must show its current revision identifier and date directly on the document (title block or header) so the revision in hand can always be checked against the master file without opening the ECO log.

Revision identifiers are never reused or skipped; if an ECO is rejected after a revision has been tentatively assigned, that identifier is retired rather than issued to a later change. TODO: confirm whether Blitzpanel uses letters, numbers, or a major.minor scheme, and how pre-release (unreleased) drafts are distinguished from post-release revisions.

6.4 Effectivity & in-process job impact

The ECO states the effectivity: the date, job/serial number, or "next build" point at which the new revision applies, and explicitly lists any jobs already released to the floor that fall within or before that effectivity.

For each affected in-process job, Production Control and Quality jointly determine and record the disposition: use-as-is, rework to the new revision, scrap, or return-to-vendor for affected material.

A job already in progress is not pulled to the new revision without an explicit disposition on the ECO; absent a stated disposition, the job continues to the revision it was released against and the deviation is documented on its traveler.

If the change affects fit, function, or a safety-related characteristic, halt shipment of any affected in-process unit until disposition is confirmed by Quality.

6.5 Notifying production & procurement

Document Control distributes the released ECO and the new-revision document set to every affected work cell and pulls/marks superseded copies before work resumes on the affected operation (see Job Traveler / Document Control SOP).

Procurement is notified of any component substitution, added/removed part, or vendor change so open purchase orders and on-hand stock are reconciled against the approved disposition (see Procurement SOP).

Notification is targeted, not blanket: only work cells, jobs, and functions actually affected by the stated effectivity receive the ECO, to avoid confusion on unaffected work. TODO: confirm the notification channel/system (email, ERP alert, posted log) and expected acknowledgment.

6.6 Updating and releasing documents

Engineering finalizes the revised drawing, schematic, BOM, or instruction with the new revision identifier and files it as the master copy in the document control system.

Document Control confirms the prior revision is removed from active circulation everywhere it was distributed and archives it (not destroyed) for as-built traceability.

Close the ECO in the log once all affected documents are re-issued, all in-process dispositions are executed, and all required notifications are acknowledged.

ECR/ECO log entry: request number, requester, description, impact assessment, approval decision and approver, revision identifier assigned, and effectivity.

Disposition record for any in-process job or stock affected by the change, including who authorized the disposition.

Revision history on each controlled document, cross-referenced to the ECO number that produced it.

Archived copies of superseded revisions, retained to support as-built traceability and UL508A documentation requirements. TODO: verify exact UL508A clause on documentation retention before citing; set the retention period.

Job Traveler / Document Control SOP, Customer Submittal / Drawing Approval SOP, Non-Conformance / Rework SOP, Procurement SOP, Quoting SOP, UL508A Compliance Documentation SOP.

UL508A — Standard for Industrial Control Panels (listing basis affected by component or design changes). TODO: verify exact clause references before citing.

NFPA 79 — Electrical Standard for Industrial Machinery (as-built documentation expectations, where applicable). TODO: verify exact clause references before citing.

Back to document index