# Engineering Change Order (ECO) Template > Source: https://netray.co/tools/engineering-change-order-eco-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An ECO and ECN document template with affected items, effectivity, stock disposition and implementation tasks, exportable as PDF or Word. ## Category engineering-plm ## Industry Discrete Manufacturing ## Audience - Engineering manager - Document control - Production planner ## Tool **Kind:** template **Output:** document **Fields:** #### Company name **Key:** company **Type:** text **Default:** Northfield Precision Components #### ECO number **Key:** eco_no **Type:** text **Default:** ECO-2026-0087 #### Source ECR **Key:** ecr_ref **Type:** text **Default:** ECR-2026-0142 #### Issue date **Key:** date **Type:** date **Default:** 2026-10-26 #### ECO owner **Key:** owner **Type:** text **Default:** R. Khan, Engineering #### Description of change **Key:** description **Type:** textarea **Default:** Change material callout on HM-300-100 from 6061-T6 to 6082-T6. Update drawing note 4 and material certificate requirement. #### Effectivity type **Key:** effectivity **Type:** select **Options:** - Date - Serial number - Lot / batch - Work order - Use up existing stock - Immediate cut-in **Default:** Use up existing stock #### Effectivity value **Key:** effective_value **Type:** text **Default:** When existing 6061-T6 stock is consumed, est. 2026-12-07 #### Disposition of existing stock and WIP **Key:** stock_disposition **Type:** select **Options:** - Use as is - Rework - Scrap - Return to vendor - Sell as spares **Default:** Use as is #### Field and customer impact **Key:** field_impact **Type:** textarea **Default:** None. Form, fit and function unchanged. Customer notified for information only. **Blocks:** #### Engineering Change Order **Body:** Company: {{company}} ECO number: {{eco_no}} Source ECR: {{ecr_ref}} Issue date: {{date}} ECO owner: {{owner}} #### Description of Change **Body:** {{description}} #### Effectivity **Body:** Effectivity type: {{effectivity}} Effectivity value: {{effective_value}} Disposition of existing stock and WIP: {{stock_disposition}} #### Affected Items **Table:** **Columns:** - Item - Old rev - New rev - Document type - Change summary **Rows:** **0:** HM-300-100 **1:** C **2:** D **3:** Drawing **4:** Material callout **0:** HM-300-000 **1:** B **2:** B **3:** BOM **4:** Component rev update #### Implementation Tasks **Table:** **Columns:** - Task - Owner - Due - Done **Rows:** **0:** Release new drawing revision **1:** Document control **0:** Update BOM and routing in ERP **1:** Engineering **0:** Update purchase orders and supplier notice **1:** Purchasing **0:** Update inspection plan **1:** Quality **0:** Adjust MRP and stock plan **1:** Planning **0:** Train shop floor / revise work instructions **1:** Manufacturing #### Field and Customer Impact **Body:** {{field_impact}} #### Approvals **Signatures:** - ECO owner - Engineering manager - Quality manager - Production / planning - Document control (release) **Notes:** Starting point for your own change procedure, not a controlled corporate form. Effectivity wording must match what your ERP supports (date, serial, lot or work order). Check customer contracts for mandatory notification or approval before release. ## Content **Intro:** An engineering change order is the approved instruction that turns a change request into released drawings, BOMs and routings. This template captures the description, effectivity, stock disposition, affected items and the task list that makes sure every department acts. **Sections:** #### How to use the ECO template **Body:** Reference the source ECR, then describe the change in terms that a planner, buyer and operator can all understand. Choose the effectivity type and value carefully: this is what tells the ERP and the shop floor when the new revision starts. Decide what happens to existing stock and work in process, then list every affected document and the revision change in the affected items table. The task table converts approval into action, with an owner and a due date for each function. Export to PDF for sign-off or Word if you need to adapt layout before circulating. **Bullets:** - One ECO can carry many affected items, but keep one coherent purpose - State effectivity explicitly, never assume 'immediately' - Every affected item needs an old and new revision - Assign a named owner and date to each task #### Effectivity and stock disposition explained **Body:** Effectivity defines when a change takes effect: by date, by serial number, by lot, by work order, or when existing stock runs out. Serial or lot effectivity is common in aerospace and regulated products where traceability matters, while date or use-up effectivity is common in commodity discrete manufacturing. Disposition answers a separate question: what happens to parts already made or purchased to the old revision. The cheapest answer is often use as is, but rework, scrap or return to vendor may be required when the change fixes a quality or safety issue. Record both so planners can adjust MRP and buyers can adjust open orders. #### Worked example **Body:** In the default content a material change is released with use-up effectivity. Engineering issues drawing revision D, the BOM is updated, purchasing places orders for the new grade timed to the estimated end of existing stock, and quality updates the incoming inspection requirement to look for the new material certificate. Because the disposition is use as is, no rework cost arises. Compare this with a safety-related change, where effectivity would be immediate and disposition would be rework or scrap. Use the companion cost impact calculator to quantify that difference before approval. #### ERP and PLM notes **Body:** Most ERP and PLM systems model this as a change master or engineering change number with a list of affected objects, a status workflow and effectivity dates. Examples include SAP engineering change management with change numbers and revision levels, Oracle Engineering change orders with revised items, and the change object in dedicated PLM tools. Whichever system you run, the paper or PDF form should match the data entered there. A common audit finding is an ECO document that says one revision while the ERP shows another, so reconcile the two at close-out. **Cta:** Netray can help tie ECO tasks to live ERP data such as open purchase orders and on-hand stock, so disposition decisions use real quantities. The template itself is free to use as is. **Faq:** #### What is the difference between ECN and ECO? **Answer:** Usage varies. Commonly the ECO is the order that authorises and details the change, while the ECN is the notice that informs affected parties. Some companies use the terms interchangeably. Define your own meaning in the change procedure. #### What should an ECO include at minimum? **Answer:** A unique number, description of change, reason or source request, affected items with old and new revisions, effectivity, disposition of existing stock, implementation tasks with owners, and approvals. Attach the updated drawings or reference their revision. #### How is ECO effectivity different from revision? **Answer:** Revision identifies the version of a document or item. Effectivity says when or for which units that version applies. Two revisions can be in use at the same time while stock is consumed, which is why effectivity must be explicit. #### Who closes an ECO? **Answer:** Usually document control or the ECO owner, once all tasks are complete and the ERP or PLM data matches the released documents. Closure should be recorded with a date so the audit trail is complete. ## Search terms ECO template, ECN ECO template, engineering change order template, engineering change notice template word, ECO form manufacturing, engineering change order example, ECO effectivity, ECO process steps --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json