Spotting delivery delays early in machine building: how to see that the delivery date is slipping.
A missed delivery date almost always announces itself weeks in advance, in order confirmations, pending approvals and questions that are left lying. Which warning signs there are and how to see them before the schedule turns red.
In machine building, delays usually show up weeks before they reach the schedule: in order confirmations with a later date than requested, approvals waiting with the customer, open issues without an owner, customer changes after design release and questions from manufacturing and assembly. If you check these signals every week, you see the delay before it appears in the plan.
Contents
The schedule for the assembly system is green. Three weeks before the FAT it turns out that the servo drives will arrive two weeks late. The supplier's order confirmation had shown the later date since the beginning of the month. Purchasing read it, but nobody transferred it.
Delays in machine building rarely come out of nowhere. They are usually written down somewhere early on, just not where the project manager is looking.
How often do machine building projects miss their deadline?
Often. In 2015 the study "Lean Development im deutschen Maschinenbau" by VDMA and Staufen surveyed 138 companies. Four out of ten projects miss their targets, and 83 percent of those miss the delivery date. 43 percent require unplanned additional effort.
The figures are not new, and neither is the pattern behind them. In project business with one-off and special-purpose manufacturing, dates depend on many places outside your own design department: the customer, suppliers, manufacturing, assembly.
How can you tell early that the date is slipping?
Order confirmations with a later date. The supplier confirms, but not for the requested date. Often it sits inconspicuously in the second line.
Approvals waiting with the customer. Layout approval, drawing approval, clarification of the specification. Every week without an answer pushes back everything that follows.
Customer changes after design release. They create rework, often without the date being reassessed. How to record such changes is described in the article on customer changes in plant engineering.
Open issues without an owner or a due date. They are left lying until they turn up again in assembly. More on this in the article on the open issues list.
Growing numbers of questions from manufacturing and assembly. A sign that documents are incomplete or that revisions do not match.
The same topics in several status meetings. An item that has been postponed three times is no longer an open issue but a risk.
Why can't you see this in the schedule?
Because the schedule is a summary. It is as current as the last update. The information about a later delivery date arises in an email or an order confirmation, the customer change in a set of minutes, the question on the phone. It takes days or weeks before this is in the plan, and sometimes it never arrives.
Planning tools such as MS Project show well what shifts when a task finishes later. But someone has to tell them that it will finish later. More on this in the article on project management software in plant engineering.
Checklist for the weekly schedule check
- Compare all order confirmations of the week with the requested date
- List pending approvals with the customer, with the date of the request
- Assess the customer changes of the week for their effect on the schedule
- Mark open issues without an owner or with an overdue date
- Count questions from manufacturing and assembly and look for patterns
- Treat items that have not changed for two status meetings as risks
With practice the check takes half an hour per project. It does not replace the schedule, it feeds it.
How does KoAssist help?
Project Memory in KoAssist, the AI agent for machine and plant builders, reads emails, minutes and documents for every project. Dates, deadlines, commitments and risks are part of the project status, every detail with a reference to its source. When an email with a later date arrives, a proposal to change the status is created. It only becomes valid once someone on the team accepts it. Project Memory is currently in pilot operation with existing customers.
KoAssist does not replace the schedule in MS Project or in the ERP system. It makes sure that the information that should change it does not stay in someone's inbox. If you would like to see this on one of your own projects, you can book a demo.
Frequently asked questions
More from the blog
Back to overview- 15 November 2026Article5 min
Can ChatGPT analyse a customer specification?
An 80-page customer specification, and the quotation has to go out by Friday. What ChatGPT does well in the analysis, where it reaches its limits and what to settle before a customer specification ends up in a chat window.
5 min - 15 November 2026Article4 min
Backing change orders in plant engineering: how additional work from customer changes gets paid
Customer changes create additional work, and it only gets paid when it is backed by evidence. What a change order in plant engineering needs, when to submit it and which documents make the difference at the final invoice.
4 min - 15 November 2026Article4 min
How much time does coordination cost in design engineering?
Collecting status, answering questions, preparing status meetings: in design departments, coordination takes up many hours a week. Two cases from special-purpose machine building and a simple method for measuring your own effort.
4 min
