# Why ECNs Stall Three Weeks at $40M Manufacturers Canonical: https://granular.to/blog/ecns-stall-three-weeks-mid-market-manufacturers Published: 2026-06-02 Updated: 2026-06-02 Author: Trey Category: Field notes Tags: manufacturing, operations, field-notes > A pattern we see at $40M precision manufacturers: ECNs take 18 days from release to floor implementation, not because the engineer is slow but because five functions have to touch the change and none of them share a system. > **TL;DR.** Engineering change notices at $40M manufacturers sit on the shop floor for two to three weeks after they are released. The engineer is not the bottleneck. The change has to be acknowledged by purchasing, production planning, quality, and the floor operator before the ERP master gets updated. Each function works its own queue, the ECN moves at the speed of the slowest reviewer, and during the wait you build parts to the old spec. The fix is treating ECN release as the start of a workflow, not the end of one. An engineering change notice released by your design team on a Monday morning will not be reflected on a job traveler until the following month. We have measured this at four different precision manufacturers in the last six months, all in the $30M to $60M revenue band, all on a current ERP (one Epicor, one Infor SyteLine, two JobBOSS). Median time from ECN release to first part built to the new revision: 18 days. Worst case we saw: 31 days. During that window, the line built parts to the superseded spec. Three of the four had to scrap or rework finished goods because of it. The engineer who wrote the ECN was not the problem. The problem was that an ECN at this size of manufacturer touches five functions, and no single workflow moves it through all five. ## The pattern we see Walk a $40M precision shop on a Tuesday morning and ask the production planner how many open ECNs there are. The answer is almost always "we have a list, hold on." The list lives in an Outlook inbox, a shared drive folder called "ECNs - 2026", or a Google Sheet that someone in engineering started maintaining when the old guy retired. There is no queue view, no aging report, no SLA on response time. The CNC operator running the first machining op on the affected part has the most recent printed traveler, which references revision G. The ECN moved the part to revision H ten days ago. The operator does not know. The ERP item master still says G because no one has updated it. The shop floor MES, if there is one, is reading from the ERP. So the system of record and the system of execution are both pointing at the old revision while the new revision sits in an email thread that engineering closed out three Mondays ago. The first time anyone catches the gap is usually at first article inspection on the next production run, or when a customer rejects a shipment because the part does not match the latest drawing they have. By then you have built between 50 and 400 units to the wrong revision, depending on lot size and how late the catch happens. Industry data backs up what we see on the floor. [Research summarized by Xavor in 2026](https://www.xavor.com/blog/best-practices-in-engineering-change-management/) puts paper or email-based ECN cycles at 14 to 21 days, with digital workflows cutting that under five days for routine changes. A separate February 2026 analysis from [SimplerQMS](https://simplerqms.com/engineering-change-order/) finds email-driven ECO cycles running three to eight weeks at most mid-market manufacturers. The 18-day median we observed lands squarely inside that range. ## Where the time actually goes We tracked one ECN end-to-end at a $52M aerospace precision shop. The change was a dimensional tolerance loosening on a non-critical feature, the kind of update that should close in 48 hours at a well-run plant. It took 22 days. Here is where the days went. Day 0: Design engineer releases ECN. Emails it to a distribution list of nine people. Days 1 through 4: Sits. Nobody is assigned. Three people are out that week. Day 5: Purchasing replies. They need to know whether existing inventory needs to be reworked or can be used to deplete. Engineer is now in a meeting. Answers Day 6. Day 7: Quality assurance flags that the inspection plan needs revision. The new plan needs review from the quality manager, who is at a customer site that week. Day 11: Quality manager returns, approves the revised inspection plan. Sends to documentation control. Day 13: Documentation control updates the work instruction PDF. Saves to shared drive. Emails the production supervisor. Day 14: Production supervisor schedules a job change meeting for the next morning. Pulls the operators off their machines to brief them. Day 15: Operators briefed. Existing printed travelers on the floor are still revision G. Production supervisor walks the floor pulling old travelers, replacing with new. Day 17: ERP analyst updates the item master to revision H. The MES finally sees the change. Day 22: First part built to revision H. No single person on this chain was lazy. Every hand-off was a reasonable amount of time given that the person on the receiving end had four other things going on. But the cumulative cost was three weeks of throughput at the old revision, plus $3,800 in rework on parts that were already in process. ## Why ECNs are different from other workflows A quote moves through your shop linearly. Estimating works it, sales approves it, customer receives it. Three steps, mostly inside one function. Even a complicated quote closes in a week. An ECN is not linear. It is a tree. The change touches purchasing (BOM update, supplier notification, inventory disposition), production planning (re-sequencing, in-process work, schedule impact), quality (inspection plan, supplier PPAP if applicable, audit trail), shop floor (work instructions, training, fixturing, tooling), and ERP master data (item master, routings, bill of operations). Five functions, all of which need to acknowledge the change before it is real. The reason ECN workflows break at $40M and not at $5M is hand-off count. At a five-person shop, the engineer who writes the ECN is the same person who updates the work instruction, the inspection plan, and walks it out to the operator. One brain, one walk. At $40M, those are five different people in three different buildings, and none of them works for the same manager. The five-person shop closes ECNs in a day not because the workflow is better but because the workflow does not exist as a workflow. It is just one person's morning. When you scale past 20 employees, the implicit workflow stops working and you need an explicit one. Almost nobody at $40M has built that explicit workflow. They are still running the five-person logic on a fifty-person plant. ![Manufacturing engineer reviewing CAD model and bill of materials at workstation with engineering change notice pending approval](/images/blog/ecns-stall-three-weeks-mid-market-manufacturers-engineering-review.jpg) *Engineering releases the ECN, but the workflow that actually implements it lives across five other functions.* ## What works The fix is not new PLM software. The shops we have helped close this gap had perfectly adequate document control. They were missing the workflow that ties ECN release to floor implementation as a single closed-loop process. Three changes account for most of the improvement we see. First, a structured intake form that requires the engineer to specify, at release, which functions need to acknowledge the change and what the deadline is. Not "FYI, ECN attached." Instead: "Purchasing must confirm BOM update by Tuesday. Quality must approve revised inspection plan by Wednesday. Production must confirm traveler swap by Thursday. ERP master update assigned to [name] for Friday." Each function gets a named owner and a date, not a copy of an email. The [oxmaint 2026 ECN guide](https://oxmaint.com/blog/post/what-is-an-ecn-or-eco-in-manufacturing) describes a similar intake gate, and notes that plants requiring mandatory impact data in the intake see a 22% drop in non-value-added engineering effort because half of the back-and-forth never happens. Second, an open-ECN dashboard that anyone in the building can pull up and see what is pending, who owns it, and how old it is. Aging report by function. Nobody is shamed, but everyone can see whether ECN-2026-074 is stuck on purchasing or stuck on the floor. The shops that built this dashboard saw a 40% to 60% drop in median cycle time within two months, mostly because the production supervisor walks over to purchasing on Day 3 instead of waiting until Day 7. Third, an automated ERP master update that fires when the floor confirms traveler swap is complete. This is the single most important hand-off because the ERP/MES is the source of truth for what the operator builds. If the master update lags the traveler swap, your system of record is wrong, and the next production run will read the old revision. Close that loop and you eliminate the "we built 200 parts to G after Quality already approved H" failure mode entirely. None of this requires AI. The AI conversation enters when you start measuring ECN cycle time as a recurring KPI and asking why certain part families generate disproportionate ECN volume. That is a design-for-manufacturability signal worth surfacing. But you do not need that signal in month one. You need the workflow in month one. ## FAQ **How long should ECN cycle time be at a $40M precision manufacturer?** Industry research puts world-class at under five days for routine documentation changes and under ten days for complex tooling or supplier-impact changes. If your median is over two weeks, the bottleneck is workflow, not engineering capacity. **Do I need a PLM tool to fix this?** No. The shops that fix ECN cycle time first usually do it inside their existing document control and ERP, using a shared workflow tracker (an Airtable base, a SmartSheet, sometimes just a well-disciplined Outlook task list) before they buy a dedicated PLM. PLM is what you buy in year two, after you have stabilized the workflow. **What is the cost of leaving this alone?** Two costs. Direct: rework and scrap on parts built to the old revision, which we have measured at 0.5% to 2% of revenue at most plants we walk. Indirect: design iteration speed, which compounds. A shop with a six-week ECN cycle iterates on its parts six times a year. A shop with a five-day cycle iterates 30 times. Over three years that is the difference between catching up to a competitor and falling behind. **Should engineering own the workflow?** No. The most successful implementations we have seen put operations in charge of cycle time and engineering in charge of change accuracy. Engineering still writes the ECN. Operations owns the SLA on every downstream function. The two roles need to be separated because engineering does not have authority over purchasing or the floor and should not be asked to chase them. ![Quality control technician at inspection station reviewing revised inspection plan on touchscreen kiosk with newly machined parts](/images/blog/ecns-stall-three-weeks-mid-market-manufacturers-quality-inspection.jpg) *The revised inspection plan and the traveler swap need to land at the same time, or you build to one spec and inspect to another.* ## Why this is worth fixing now Most $40M manufacturers have lived with an 18-day ECN cycle for years. It is the kind of operational drag you stop noticing until you scrap a six-figure aerospace lot, lose a customer because of revision drift, or get a major audit finding. The fix is not capital. It is workflow discipline plus a closed loop between floor confirmation and ERP master update. A team of three operators, an engineer, and a planner can build the first version in two weeks. Granular has built this closed-loop workflow at multiple precision shops in the construction equipment, aerospace, and industrial components verticals. If your ECN cycle has been running over two weeks and you are tired of the rework cost, [book 30 minutes with us](/) and we will walk you through what the first version looks like at your plant. Fixed price, four weeks, working tool. --- ## Keep Reading - **[Why Mid-Market Manufacturers Still Print Travelers](/blog/mid-market-manufacturers-still-print-travelers)**: The paper traveler problem that makes ECN traveler swap a hands-on, error-prone exercise at most $40M plants. - **[Work-in-Process Visibility for $40M Manufacturers](/blog/wip-visibility-mid-market-manufacturers)**: Why WIP visibility breaks at the same scale ECN workflow breaks, and what to build instead of buying another module.