Precision metal and engineering plastic parts from prototype through repeat production.
Tooling development, molded parts and production support for repeat plastic manufacturing.
Functional prototypes, complex geometry and low-volume parts without conventional tooling.
Explore 3D PrintingStart with geometry, material, quantity and critical requirements before selecting the route.
Request Engineering ReviewSend your CAD, drawing, material and quantity for an initial manufacturing review.
Request Engineering ReviewEngineering Change Notice · Release Record
A release-ready injection molding ECN form should identify exactly what changed, which approved revision is affected, what evidence confirms the change, who authorized release, and when the revised production baseline becomes effective. The form should make the decision traceable without turning the ECN itself into a complete engineering-change procedure.
Release rule: do not close the ECN until the affected object, validation result, controlled-record update, approval status, and effective production lot can all be traced from the same record.
Download Injection Molding ECN PDF Template Includes identification, change scope, risk review, validation plan, evidence, approval, and effective-lot fields.The ECN form does not manage the entire engineering-change process. Its job is to create one controlled release record showing what approved baseline changed, which production objects are affected, what evidence supports the revision, who approved it, and when the new condition becomes effective.
Every ECN should identify the exact production baseline being changed before validation evidence or approval is reviewed. If the ECN number, affected part, tool location, or revision status is ambiguous, the release record cannot reliably distinguish the old condition from the new one.
| Required Field | What It Must Identify | Release Purpose |
|---|---|---|
| ECN Number | Unique controlled change record and issue sequence. | Required |
| Project / Customer | The program or customer release context to which the change belongs. | Prevents cross-project release errors. |
| Part Number | Exact molded component affected by the engineering change. | Links the ECN to the correct drawing and inspection record. |
| Tool / Cavity / Insert ID | Specific mold, cavity, insert, slider, lifter, or tooling location affected. | Prevents a local tooling change from being mistaken for a full-tool revision. |
| Current Revision | Previously approved drawing, specification, or controlled baseline. | Defines the condition being replaced. |
| New Revision | Revised drawing, specification, or document level approved for release. | Defines the new controlled production baseline. |
The ECN should describe the changed object and its affected scope precisely enough to prevent a revision from being released too broadly or too narrowly. Risk classification then determines how much validation and approval evidence must be referenced before the revised baseline becomes effective.
| Scope Field | What the ECN Should Record | Typical Example |
|---|---|---|
| Changed Object | Identify the exact feature, component, material, process record, inspection method, or controlled document being revised. | Insert, cavity feature, resin grade, setup sheet, CMM program. |
| Physical Scope | State whether the change applies to one cavity, one insert, the full mold, one part number, or multiple released items. | Cavity 3 only; all four cavities; one family tool. |
| Document Scope | List which controlled records must be updated so the released documents match the revised condition. | Drawing, setup sheet, inspection plan, work instruction. |
| Potential Impact | Record the characteristics that could be affected and therefore require validation or release review. | Fit, function, CTQ dimensions, appearance, traceability. |
The ECN validation plan should state what must be checked, how much evidence is required, which characteristics matter, and what result will count as acceptable. It should define the release test without turning the ECN into a full mold-trial, FAI, or process-validation procedure.
Release planning rule: avoid entries such as “check samples” or “verify dimensions.” The ECN should state what will be checked, against which criterion, on how many samples, and by whom.
A validation plan does not close the ECN by itself. The completed form should show what was actually checked, the result obtained, where the supporting evidence is stored, and whether the revised condition passed, failed, or remains on hold.
| Result Field | What to Record | Release Purpose |
|---|---|---|
| Actual Result | Record the measured, inspected, functional, visual, or trial result rather than repeating the planned validation activity. | Confirms what actually happened. |
| Evidence Reference | Identify the report, inspection record, trial sheet, image, measurement file, or other controlled evidence used for release. | Makes the decision traceable. |
| Dimensional Evidence | Where drawing or CTQ dimensions are affected, reference the controlled injection molding FAI report or equivalent approved dimensional record. | Links the ECN to verified dimensions. |
| Pass / Fail Status | State whether the acceptance criteria were met, partially met, or not met. | Prevents subjective release decisions. |
| Disposition | Record the next controlled action: release, hold, rework, repeat validation, or further approval. | Defines what happens next. |
The final ECN should identify the required approvers and define exactly when the revised condition becomes the active production baseline. Approval signatures without an effective date or lot can leave production, inspection, and document-control teams working to different revisions.
| Approval Field | What the ECN Should Record | Release Purpose |
|---|---|---|
| Engineering Approval | Name, signature or controlled approval record, and approval date for the responsible engineering function. | Required |
| Quality Approval | Quality sign-off confirming that required evidence and acceptance criteria have been reviewed. | Confirms release evidence is complete. |
| Customer Approval | Record approval status, reference, and date where the customer-controlled baseline or contractual requirement requires it. | Prevents unsupported supplier-only release. |
| Release Authority | Identify the person or function authorized to close the ECN and release the revised condition. | Establishes final responsibility. |
| Effective Date / Lot | State the date, lot number, batch, serial range, or other traceable point from which the revised baseline applies. | Separates old and new production. |
An ECN can look complete while still leaving the revised production baseline ambiguous. Release should be held when the form cannot clearly identify the active revision, affected tooling location, supporting validation evidence, or production effectivity point.
The ECN describes the change but does not clearly identify both the current approved revision and the new revision intended for release.
Release effect: production and inspection may continue using different drawing or specification levels.
A tooling change is recorded only as a general mold modification even though the physical revision applies to a specific cavity, insert, slider, or local tool area.
Release effect: unaffected and revised tooling conditions can become mixed under the same ECN.
The ECN states that the trial or inspection passed, but no controlled report, measurement record, result reference, or evidence identifier is attached.
Release effect: the approval cannot be independently verified against the planned acceptance criteria.
Engineering and quality approvals are complete, but the ECN does not define the lot, batch, date, or traceable point from which the revised condition becomes active.
Release effect: old and new production baselines may be mixed in inventory, inspection, or shipment records.
A signed ECN is not automatically a releasable ECN. The record should identify the active revision, affected scope, supporting evidence, approval status, and production effectivity before the revised baseline is released.
Before the ECN is closed, verify that the identification, change scope, validation result, supporting evidence, approvals, and production effectivity all point to the same revised baseline. A missing field should remain visible as a release hold rather than being replaced by an informal approval.
These answers focus on completing and releasing the ECN record itself rather than explaining the full engineering-change-management process.
It should identify the ECN number, affected part and tool, current and new revision, change scope, risk, validation plan, actual result, evidence reference, approvals, and effective production date or lot.
The ECN should reference the controlled report or record that proves the planned acceptance criteria were checked, such as dimensional, trial, functional, visual, or other approved validation evidence.
The form should record the responsible engineering and quality approvals, final release authority, and customer approval where the applicable customer or contractual baseline requires it.
Record a traceable effectivity point such as the production lot, batch, serial range, or release date from which the new revision becomes active and the previous baseline no longer applies.
Yes. An Excel log can track ECN number, revision, owner, status, and effectivity, while the controlled ECN form retains the detailed scope, evidence, approval, and release record.
SPI can review the affected part, tooling condition, validation evidence, and release requirements as part of our production injection molding support .
