Seven Breakpoints from Order to Delivery —— Slow Delivery Isn't Due to Slow Production, 80% of Delays Occur During Department Handovers
First, let's state a counterintuitive conclusion: the majority of delivery delays in most companies are not due to slow production on the shop floor, but rather because orders are waiting between departments.
There's a self-test data point: calculate the total duration from "customer order placement" to "customer sign-off," then subtract all the actual working time (review, design, procurement execution, processing, inspection, transportation). What's left is the waiting time.
In traditional manufacturing companies, this waiting time typically accounts for 70%~90% of the total delivery cycle. This means that the truly value-adding part of the delivery cycle is less than 30%, and in some industries, it's even less than 5%.
What does this imply? If you want to compress the delivery cycle, the most critical change is not to improve shop floor efficiency but to reduce the waiting time between departments. And where and why the waiting occurs is determined by your own breakpoint map.
The Essence of Breakpoints: No One Is Responsible for "Handover"
Production processes have workstations, rhythms, and evaluations; however, handovers between departments have none of these.
- Sales hand over the order to Planning, but Sales consider the handover complete while Planning is still waiting for complete information.
- Planning hands over the requirements to Procurement, but Procurement waits for all materials to be available before placing orders, while Planning believes orders should be placed as materials become available.
- Procurement hands over the materials to the Warehouse, but the Warehouse waits for IQC inspection before receiving, while Procurement believes materials should be stored upon arrival.
Each "consideration" results in a wait. This isn't due to lack of departmental cooperation, but rather because the process design lacks a responsible person for the "handover" role.
Seven Breakpoints
The following seven positions cover the primary sources of delivery delays in most manufacturing companies. Each is described with typical symptoms, quantification methods, and minimal changes.
| # | Breakpoint Position | Typical Symptoms | Quantification Metrics | Minimal Changes |
|---|---|---|---|---|
| 1 | Order Acceptance → Contract Review | Sales promise a delivery date on the spot, but the technical feasibility is rejected two weeks later | Median days from order acceptance to review completion | Move the "can we accept" judgment to the quotation stage, using a standard delivery schedule |
| 2 | Contract Review → Production Planning | Review is approved, but Planning says "not included in the monthly plan" | Waiting days from review completion to plan entry | Trigger plan reservation upon review approval, without waiting for the monthly unified schedule |
| 3 | Planning → Material Requirements | Planning issues the plan, but Procurement says they haven't received the complete material dates | Interval from plan issuance to procurement order placement | Issue the complete material dates with the plan, as a hard input for Procurement |
| 4 | Material → Production Start | 99% of materials are ready, but one missing item delays the entire order | Material completeness rate, distribution of missing items | Start production in batches based on the priority of missing items (begin with non-missing processes) |
| 5 | Production Start → Process Transfer | Work-in-progress (WIP) piles up at the entrance of the previous process | WIP turnover days between processes | Set an upper limit for WIP between processes, stop new inputs if the limit is exceeded |
| 6 | Completion → Warehouse Entry | Production is complete, but waiting for inspection, which is backlogged | Days from completion to inspection completion | Allocate inspection resources according to the production rhythm, not in batches |
| 7 | Warehouse Entry → Customer Sign-off | Goods are in the warehouse, but waiting for invoices, consolidation, or customer receiving windows | Days from warehouse entry to customer sign-off | Prepare shipping documents in parallel, not waiting for all goods to be ready |
Breakpoint 1: Delivery Promises Made Without Complete Information
This is the most expensive breakpoint because it turns all subsequent process errors into its own responsibility.
Sales promise a 30-day delivery to the customer, but during technical review, it is discovered that a new mold is needed (+25 days). However, the order has already been signed. As a result, everyone starts firefighting, and the costs of firefighting (overtime, expedited orders, urgent shipping fees) are not attributed to Sales.
Criterion: Calculate the deviation distribution between "promised delivery date" and "actual delivery date." If the median deviation exceeds 15%, it indicates that delivery promises are made without proper consideration. If it exceeds 30%, it suggests that the entire delivery system is running on luck.
Breakpoint 3: Material Completeness is a Black Box
Planning knows which orders need to be processed, but doesn't know when each order will have all materials. Therefore, they can only wait for a vague response from Procurement or rely on experience to schedule.
Criterion: Can you provide a forecast of the material completeness rate for an order on T+7, T+14, and T+21 when the plan is issued? If not, this is a breakpoint.
Breakpoint 5: Work-in-Progress (WIP) is a Disguise for Waiting
WIP appears to be "in production," but it's actually in a queue. The more WIP there is, the slower the turnover, and each process believes it is very busy.
Criterion: WIP turnover days between processes. If the turnover days between two processes exceed 3 days, there is likely an unmanaged queue.
Breakpoint 6: Inspection Queues by Batch
This is the easiest to overlook. The shop floor produces according to the rhythm, but inspection is done in batches—these two rhythms are inherently mismatched, leading to inevitable delays for completed goods.
Criterion: Days from completion to inspection completion. If it exceeds 1 day, it indicates that the inspection resource allocation does not match the production rhythm.
How to Identify Your Breakpoints
Don't guess based on feelings; use timestamps to calculate. Take the most recent 30 orders and list the following time points for each:
Order placement / Review completion / Plan issuance / Procurement order placement / First batch arrival / Material completeness / Production start / Completion / Inspection completion / Shipment / Sign-off
Then calculate the differences between adjacent time points, summarize by order, take the median, and sort them.
The top three positions with the longest cumulative waiting time are your breakpoints. Empirically, the top three breakpoints usually account for more than 60% of the total delay.
Three Common Misconceptions
Misconception One: Treating Breakpoints as Departmental Issues. "Procurement is too slow" or "Sales makes random promises"—such attributions only create conflict. Breakpoints are structural process issues: if the process does not specify "who is responsible for handover," replacing the entire department will not solve the problem.
Misconception Two: Implementing Systems Before Addressing Breakpoints. Systems will solidify the existing process (including waiting times) into workflows, turning waiting into "to-do" items in the system. After the project is completed, the cycle time will not have decreased.
Misconception Three: Only Compressing Production Time. Production is often the most efficient segment of the entire chain (because it is constantly monitored). Compressing it by 20% may contribute less than 3% to the total cycle time. Reduce waiting time first, then improve efficiency—reversing this order will result in poor return on investment.
In a Nutshell
The delivery cycle is not slowed down by production, but by handovers. The method to find breakpoints is not through meetings but by using timestamps to measure each waiting period, then start by addressing the position with the longest cumulative waiting time—fix one segment at a time, don't tackle all seven simultaneously.
This article belongs to the "Digitalization and AI Zone · Operational Digitalization" direction. For a quality perspective on delivery capability building, see "OTD and Delivery Reliability" (Knowledge code: 4.2.3). This article focuses on process breakpoint identification and can be read in conjunction with "Why Do We Still Rely on Excel After Replacing Three Scheduling Systems?" (Knowledge code: 16.2.1).
Knowledge code: 16.2.1 Version: v20261026 Author: QTank