Control Engineering Changes from CAD Release to the Shop

Prevent a drawing or bill-of-material change from reaching production without a clear revision, approval, and affected-job check. A Lean engineering handoff makes the request, impact review, release, and shop acknowledgement visible. This is a workflow guide, not a report of a named company implementation.

Use one controlled change path

Engineering change workflow with revision gates

Stage	Responsible role	Required record or check	Do not advance until
1. Request	Requester or shop lead	Part number, current revision, affected job, problem, evidence, requested need date	Request is uniquely identified and scope is clear
2. Impact review	Design, manufacturing, quality, purchasing as needed	CAD/model and drawing impact, BOM, tooling, inspection, supplier, WIP, and customer effects	Required technical and customer approvals are identified
3. Approve and release	Authorized design owner and document control	Approved product definition, revision record, effective date or lot/job applicability	Released source is accessible from the controlled system
4. Update production packet	Planner and document control	Traveler, routing, BOM, inspection plan, program/tooling references where applicable	All affected job packets point to the effective revision
5. Acknowledge at point of use	Cell lead and operator	Old copies removed or controlled; new revision verified at work area	Operator confirms the current packet before work resumes
6. Close and learn	Change owner	WIP disposition, supplier notification, completed checks, closure date	Impact list is reconciled and unresolved items have owners

Apply the organization’s configuration-management and customer-change requirements. A CAD file name, email attachment, or file timestamp is not proof of release. ASME Y14.35 defines practices for revising engineering product-definition datasets and associated documents; consult the applicable edition and the organization’s approved standards before setting a local procedure.

Use a change-request form that exposes impact

Copyable engineering change request fields

Field	What the requester records
Identity	Part number, assembly, drawing/model identifier, current revision, affected order/lot
Observed issue	Condition, operation, evidence, date, and containment needed
Proposed change	Requested geometry, material, process, or document update; attach controlled markup
Affected items	BOM, routings, work instructions, inspection, fixtures/programs, suppliers, WIP and finished goods
Risk and approvals	Customer, safety, regulatory, quality, cost, and delivery review owners
Effectivity	Approved job/lot/date/serial boundary and transition instructions
Release and closure	Approver, released revision, system location, packet update, point-of-use acknowledgement

Example: an incorrect revision reaches the laser queue

Illustrative scenario: a laser operator sees a traveler at revision B while the controlled drawing is revision C. The operator stops before cutting, identifies the affected job, and keeps the material segregated under the site’s process. The planner checks the job packet; document control confirms which revision is authorized and whether the job is covered by the approved change. Engineering and quality determine disposition. Only after the authorized release does the planner issue the corrected packet and the operator verify the revision at point of use.

Do not edit the drawing informally, rework a part, or continue based on a verbal instruction. If material has already been processed, use the applicable nonconformance and configuration-control procedure to identify affected units and obtain a documented disposition.

Measure handoff performance with defined events

• Request age: received timestamp to disposition or release, segmented by change type.
• Packet readiness: jobs with all required released documents ÷ jobs sampled before start.
• Revision mismatch: count of detected mismatches by operation and discovery point.
• Engineering queue: active requests by status, owner, and age; distinguish waiting for technical work from waiting for missing inputs.
• Rework exposure: affected WIP, parts, or orders requiring evaluation after a change.

Use consistent start/stop definitions and report the sample size. Faster release time is not a success if impact review or approvals are skipped. Review the oldest requests with the right decision owners and remove missing-information barriers upstream.

For production-side routing and traveler controls, use the high-mix machine-shop guide. For handoff ownership and shift communication, see the shop-floor handoff guide.

Map the change from request through shop acknowledgement

An engineering change is complete only when the authorized design and effectivity are controlled, affected work is dispositioned, and the shop knows which revision applies. Define each state in the actual local system: request received, impact reviewed, design updated, validation complete, approval recorded, release effective, affected jobs contained, and production acknowledgement returned. A software product may support some of these steps, but this guide does not assume a specific PDM, ERP, or document-control feature. Verify the capabilities and configuration in the site’s approved software documentation.

For every change, identify the part or assembly, old and new revision, reason, affected drawings and bill of materials, linked processes and inspection documents, approval authority, effective date or lot/serial boundary, inventory and WIP exposure, and person responsible for communicating the release. The engineering change owner should keep a single controlled record that points to the authoritative documents rather than emailing detached copies as if they were current.

Engineering-change handoff and responsibility matrix; adapt to local authority

State	Responsible role	Required evidence	Next handoff
Request and problem statement	Requester / engineering coordinator	Part, revision, affected job, observed condition, requested result.	Design owner screens scope and priority.
Impact review	Engineering with manufacturing, quality, materials, service as needed	Drawing/BOM, tooling, work instruction, stock, WIP, supplier, inspection impact.	Named approvers receive the defined change package.
Design and validation	Design owner and qualified reviewer	Updated controlled document and verification/validation evidence.	Quality and customer approval when required.
Effectivity and release	Authorized change approver / document control	New revision, effective lot/date/serial, released records.	Production control and impacted work centers notified.
Contain and disposition	Production control, quality, materials, engineering	List of affected WOs and inventory; hold and disposition records.	Each affected order has a clear route and owner.
Shop acknowledgement	Supervisor or designated work-center owner	Current packet verified; obsolete copies removed under local control.	Requester and change owner receive completion status.
Effectiveness review	Process owner / quality	First production checks, deviations, open actions, recurrence.	Close or reopen the change record.

Define a RACI or equivalent role map for each state. The person performing the design work is not automatically the person authorized to approve it. A shop acknowledgment confirms receipt and understanding; it does not approve the design or waive required inspection. If an approver is unavailable, use the documented delegate rather than an informal verbal substitution.

Work an illustrative Rev B to Rev C change

The following scenario is fictional. A bracket drawing changes from Rev B to Rev C after a hole location is corrected. The change owner identifies 20 open work orders and checks their status with planning and the affected cells. Five are not released, eight are cut but not formed, four are between bending and welding, and three are complete but not shipped. These quantities are illustrative and sum to 20. The team does not assume that every unit can simply be reworked; engineering and quality decide which product is affected and what disposition is allowed.

Illustrative work-order impact register for a drawing revision change

Work-order status at review	Count	Immediate control and decision owner	Release evidence
Not released	5	Planner holds release until the effective revision and packet are confirmed.	Current Rev C packet issued and acknowledged.
Cut, not formed	8	Identify material and cut parts; engineering/quality decide applicability and disposition.	Approved lot-specific disposition and revision link.
Between bending and welding	4	Keep identified; verify geometry and affected operations before movement.	Authorized inspection or disposition recorded on the order.
Complete, not shipped	3	Shipping hold while quality and engineering assess customer/order effect.	Authorized release or documented alternate disposition.
Total open work orders	20	Reconcile list to planning system and physical work locations.	All 20 have named status, owner, and next action.

The change owner checks supplier stock, purchased parts, fixtures, programs, inspection criteria, and any customer approval that the actual change requires. Affected parts remain traceable by job and revision. Work does not move forward merely because the new drawing is published; the effective boundary and old-work disposition must be clear. When the shop has acknowledged the new packet, planning can release eligible orders under the approved rules.

Use a change-request form that exposes impact

A change-request form should capture enough information to route decisions without duplicating the design record. Include request ID and date, requester, part/assembly and revision, problem or customer need, proposed change, reason, affected products and work orders, stock and supplier exposure, process/tool/program impact, required inspection or validation, risk review, approvals, effectivity, communication list, and closure evidence. Mark unknown items as open questions with an owner and due date.

Separate “request approved to investigate” from “design approved,” “document released,” and “production may use.” These are different authorizations. The release notice states which revision is current, when or where the change applies, how to handle old stock and WIP, what records changed, and whom to contact with a mismatch. Avoid ambiguous phrases such as “use latest” when a job-specific effective revision is required.

When a change is rejected or deferred, tell the requester and affected shop roles why the current method remains in force, what risk or evidence is unresolved, and when the decision will be reviewed. An open request should not leave a part in a shadow state where some employees use the old drawing and others use an unofficial revised sketch.

Measure the handoff with explicit events

Define timestamp events before measuring engineering handoff performance. For example, request-to-screened time begins when a complete request is received; engineering-cycle time begins when required inputs are accepted and ends at authorized release; shop acknowledgement time begins when the release notice is sent and ends when each impacted work center confirms the current packet. Keep waiting for requester information separate from active design time, and report the sample size and change type.

Useful measures include requests missing required impact fields, changes released without a complete effectivity plan, affected work orders without disposition, shop acknowledgements overdue, and first-job deviations after release. A fast release is not a good result if it creates a revision mismatch or hides unresolved inventory. Review measures with engineering, quality, planning, and production; do not compare unlike change complexity as if cycle times were equivalent.

Control old copies and verify first use

At release, remove superseded copies from points of use using the site’s document-control process and retain them only as required for history. Confirm that job travelers, programs, inspection references, supplier instructions, and digital links resolve to the intended revision. If the system cannot guarantee that every local copy is current, identify the manual check and role responsible for it.

After the first affected job, verify that the released revision was used, the required characteristic was checked, and any remaining Rev B product followed its approved disposition. Record deviations and update the change owner. Close only when all affected orders, stock, shop locations, and required customer or supplier communications have a documented status.

Do not claim a software system automatically prevents revision errors unless the site’s configuration and behavior are verified. Do not claim a change reduced scrap or improved lead time without source records and a comparable baseline. The engineering workflow succeeds when each stakeholder can identify the current requirement, affected work, decision authority, and next action.

Trace one change through its handoffs

Revision-change swimlane checklist for a bracket from request to first production use

Handoff	Sender provides	Receiver confirms	Evidence and exception route
Requester to engineering	Part/revision, problem, affected job, requested need.	Request is complete enough to screen.	Request ID; missing information returns to requester.
Engineering to reviewers	Proposed document, impact list, validation plan, risk.	Technical and quality review scope is clear.	Review comments and approvals; unresolved risk remains open.
Approver to document control	Approved change and effectivity boundary.	Released revision and related records are identified.	Release record and effective date/lot/serial rule.
Document control to planning	Release notice, affected orders, inventory/WIP action.	Each work order has an eligible revision and disposition.	Work-order impact register reconciles to system and shop.
Planning to work center	Current packet, job status, required checks.	Supervisor/operator acknowledges the correct revision.	A mismatch stops the affected job and returns to engineering/quality.
First production job to owner	First-use inspection and process records.	Change performs as approved; open issues are visible.	Effectiveness review, correction, or documented closure.

At each handoff, define a completion signal rather than assuming an email was read. If the receiving role does not acknowledge within the agreed local interval, escalate to the named delegate. Keep one authoritative record so that the change owner can see which orders and work centers remain open.

If the first Rev C job reveals an interference or a missing inspection note, stop the affected release, identify other orders that used the same change, and open a controlled correction. Engineering evaluates the design issue; quality determines product containment and inspection; planning updates the work-order list. Do not silently edit the released drawing or reuse the prior approval. Preserve the record chain so reviewers can see which instruction applied to each job and when.

Close deferred requests without creating shadow revisions

If a change request is deferred or rejected, retain the decision, approver, reason, unresolved evidence, and review date in the controlled record. Tell planning and affected work centers which released revision remains in force. Do not circulate a marked-up drawing or screenshot as an informal production instruction. If an urgent deviation is allowed by the site’s process, identify its scope, authority, traceability, expiration, and disposition requirement. When the request is later reopened, recheck the affected-order list because WIP and supplier stock may have changed.

Keep the impact list tied to controlled records

Reconcile affected jobs from the approved planning source, then verify their physical locations with each work center. Check supplier purchase orders and received stock through the authorized materials process. Record who completed each check and when; do not mark an order clear based only on an old spreadsheet export. If the list changes during review, update the controlled impact register and repeat the affected handoffs before release.

Sources

• ASME Y14.35: Revision of Engineering Product Definition Datasets and Associated Documents — standard scope covers revision practices and identification/recording of revisions; use the edition applicable to your organization.
• Lean Enterprise Institute: Visual management in product development — discusses using visual management to make engineering work and issues visible.