← Back to Field Notes

March 21, 2026 · The Bloomfield Team

How Late Shipments Actually Start

A shipment goes out three days late. The production manager gets asked what happened. The answer is usually some version of: the job took longer than expected, or the machine went down, or we had a quality issue on first article. The explanation focuses on the last few days before the ship date, the final link in a chain that started breaking much earlier.

Late shipments in job shop manufacturing almost never originate where they become visible. The visibility point is the shipping dock. The origin point is typically two to four weeks upstream, in quoting, order entry, purchasing, or planning. Tracing that path back from the dock to the actual root cause reveals patterns that production speed alone cannot fix.

The Quoting Phase: Where Lead Times Get Set Wrong

A late delivery often begins the moment the lead time is quoted to the customer.

An estimator receives an RFQ for 200 precision-ground shafts. The customer asks for delivery in four weeks. The estimator checks the ERP for open capacity, sees that three weeks from now there is an opening in the grinding department, and confirms four weeks. The quote goes out. The customer places the order.

What the estimator did not check: material lead time for 4340 alloy steel in the diameter required is currently running six weeks from two of the shop's three suppliers. The third supplier can deliver in three weeks but at a 15% price premium that was not included in the quote. The estimator quoted based on processing time and assumed material availability. That assumption created a delivery commitment the shop cannot keep without either absorbing a cost increase or missing the date.

This pattern accounts for a meaningful share of late deliveries. A 2023 study by the Precision Machined Products Association found that 23% of on-time delivery failures in surveyed job shops traced back to lead time commitments that did not account for current material availability. The estimator had no easy way to check material lead times during the quoting process because that data lived in purchasing's email threads, not in a system the estimator could access.

The quoting process already carries pressure to respond quickly. Adding a material lead time verification step slows the quote down. Skipping it creates a delivery promise built on an assumption that may be wrong. Both outcomes are bad. The fix is making material availability data accessible to the estimator at the moment they build the quote, which requires connecting systems that currently operate in isolation.

The Order Entry Phase: Where Details Get Lost

The customer approves the quote and sends a purchase order. Someone in the front office enters the order into the ERP. They create the job record, enter the quantities, assign the operations, and set the due date.

During order entry, critical details from the RFQ and the customer's PO sometimes get lost or simplified. A note on the RFQ specified that parts must be individually wrapped. The order entry person did not see the note because it was on page three of a six-page email thread. The parts get produced correctly but packed in bulk. The customer rejects the shipment. It comes back, gets repacked, and ships again four days late.

In another common scenario, the customer's PO contains a revision to the drawing that differs from the revision quoted. The order entry person enters the PO number and the part number but does not compare drawing revisions because the quoting file is in a different system. The job launches with the wrong revision. The error is caught at first-article inspection, which consumes a day. The correct revision is programmed, set up, and run, which consumes another two days. The shipment is now three days late because of a detail missed at order entry.

These are not dramatic failures. They are small administrative gaps between the quoting process and the production process, places where information crosses a system boundary and loses fidelity. Each gap adds hours or days to the job's timeline. Stacked together across a month, they account for a meaningful percentage of late deliveries.

The Purchasing Phase: Where the Clock Starts Without Anyone Noticing

Material procurement is the most common upstream cause of late shipments, and it operates on a different timeline than production. A job with three weeks of processing time and a five-week delivery commitment looks comfortable in the ERP. It looks comfortable until the purchasing agent realizes that the material will not arrive until week three, leaving no margin for the processing work.

The root cause is timing. In most shops, material is ordered after the job is created in the ERP, which happens after the customer's PO is received, which happens after the quote is approved. Each handoff adds one to three days. By the time the purchase order reaches the material supplier, a week or more of the delivery window has passed with no production progress.

Some shops pre-order common materials to avoid this problem. They carry inventory on frequently used bar stock, sheet metal, and hardware. This helps for repeat work but does not solve the problem for one-off jobs or jobs requiring specialty materials, which are precisely the jobs with the longest material lead times and the highest risk of late delivery.

A purchasing manager at a 45-person aerospace shop described the cycle this way: "We get the PO on Monday. I enter the material requisition Tuesday morning. The buyer reviews it and places the order Wednesday. The supplier confirms delivery in four weeks. The job is due to the customer in five weeks. We need three weeks of floor time. That leaves us one week of negative margin on the schedule, and nobody knows it until the material actually arrives and someone in planning does the math."

The math was doable on the day the quote was sent. Nobody did it because the quoting system, the purchasing system, and the scheduling system are three separate tools with no connection between them.

The Scheduling Phase: Where Conflicts Hide

A new job enters the schedule. The planner looks at the due date, works backward from the required operations, and slots the job into available capacity. On paper, it fits. On the floor, it may not.

The schedule shows Machine 4 available on Tuesday for a 6-hour first operation. What the schedule does not show is that Machine 4 is currently running a job that is 4 hours behind estimate and will not be finished until Wednesday morning. Or that the operator who ran this type of part before is on vacation next week and the replacement operator will need an extra 2 hours of setup time. Or that Machine 4 is due for a scheduled maintenance event on Thursday that will take it offline for a full shift.

Each of these conflicts is knowable. The ERP has the current job's actual progress versus estimated progress. The attendance system has the operator's vacation schedule. The maintenance system has the PM schedule. But none of these systems feed into the scheduling process in real time. The planner builds the schedule from the ERP's static capacity view, and the floor reveals the conflicts one at a time as the week unfolds.

A schedule built on incomplete information generates late deliveries because the conflicts it misses consume the buffer time that was supposed to protect the ship date. When the buffer is gone, the job runs late. When several jobs run late simultaneously, the production manager starts triaging, which means some jobs get pushed further to make room for the most urgent ones. The cascade effect turns one scheduling gap into three late shipments.

Tracing the Chain

A late shipment that looks like a production problem on Friday afternoon is often the final symptom of a sequence that started two or three weeks earlier. The lead time was quoted without checking material availability. The order entry missed a drawing revision. The material was ordered three days later than necessary. The schedule did not account for a machine running behind on the prior job.

Each of these upstream events removed a day or two of margin from the delivery window. By the time the job reached the floor, the remaining time was too tight to absorb any production variability at all. The machinist ran the parts in exactly the estimated time. The job still shipped late because it arrived at the machine three days later than it needed to.

Measuring on-time delivery honestly is the first step. Tracing each late shipment back through the chain to identify where the delay originated is the second. When shops start categorizing late deliveries by root cause, the distribution is usually surprising. Production speed accounts for less than 40% of the total. The majority originates in the administrative and planning processes that precede production.

The data to perform this analysis exists across the shop's systems: quoting records, purchase orders, material receipt dates, job start dates, operation timestamps, and ship dates. Connecting that data and running the analysis reveals the upstream patterns that no amount of floor-level expediting can fix.

Fixing the Origin Points

Once the root cause distribution is visible, the fixes become specific. If 25% of late deliveries trace back to material procurement timing, the fix is integrating material lead time data into the quoting process so that lead times are set based on actual supply chain conditions. If 18% trace back to scheduling conflicts with jobs already in process, the fix is a scheduling tool that shows actual job progress against plan and flags conflicts before they consume buffer time. If 12% trace back to missing or incorrect information at order entry, the fix is a structured handoff process between quoting and production that verifies critical details before the job launches.

Each fix addresses a specific link in the chain. The combined effect is a delivery process that stops generating the problems it currently spends most of its energy reacting to. The production team stops fighting fires. The shipping dock stops being the place where upstream problems become visible for the first time.

The tools to connect these upstream processes and surface the risks before they become late shipments are buildable now. The hardest part is accepting that the answer to "why was this shipment late" is rarely "because production was slow." It is usually "because we did not have the right information at the right time, three weeks ago."