Keeping customer changes traceable in plant engineering.
In project business the customer often changes things in the middle of the project. Why such changes get lost between email, drawing and assembly, what should be recorded for each change and what a simple change register looks like.
A customer change is traceable when the record shows what changes, who requested it and when, which status applied before, what it means for schedule and cost and who in the project is affected. The simplest way is one change register per project in which every row points to its source, such as the customer's email or the minutes.
Contents
- How often do customers change things in the middle of a plant engineering project?
- Why do customer changes get lost in a project?
- What should be recorded for every customer change?
- What does a simple change register look like?
- When does a customer change become a change order?
- What can you do differently from the next project on?
- How does KoAssist help?
Three weeks after design release, the customer sends a short email. The transfer height to the existing conveyor is 150 mm higher than stated in the specification after all, and could that still be taken into account? The design engineer who received the email adapts the frame and releases the new revision. Purchasing orders the profiles from the old bill of materials, because the order went out the week before. In assembly, the frame does not fit the conveyor. At the final invoice the customer asks why the additional costs were never announced.
Each step was right in itself. What was missing was a place where the change was recorded as a change.
How often do customers change things in the middle of a plant engineering project?
More often than project planning allows for. A head of engineering at a plant builder puts a figure on it for his project business. In about one project in four, the customer changes the geometry after the fact. On top of that come changes that do not affect geometry, such as different interfaces to the controls, additional options or moved dates.
That is rarely down to poor specifications. In project business the customer learns as the project goes on. Their own line is replanned, another supplier changes an interface, or the operator has new requirements. Changes are part of project business. They only become a problem when they get lost along the way.
Why do customer changes get lost in a project?
They arrive by many routes. By email to the project manager, by phone to the design engineer, in passing in a meeting, as a comment on a drawing sent back. Each route ends with a different person.
The change is implemented but not recorded as a change. The new drawing revision shows the new state. That it was a customer change, when it came and who wanted it is usually not on it.
The consequences are not assessed. Whether a change moves the schedule or causes additional costs is often only asked when it is too late to announce it to the customer.
Those affected find out too late. Purchasing, electrical design, manufacturing and assembly work with the status they last received.
How agreements from emails reach the project instead of staying in one person's inbox is described in the article on project decisions from email.
What should be recorded for every customer change?
A change is traceable when someone who was not there understands in a year's time what happened. That needs the following:
- What changes? In one sentence, as concrete as possible: "Frame transfer height from 850 to 1,000 mm".
- Who requested the change, and when? With name and date on the customer side.
- Where is it written? A reference to the email, the minutes or the marked-up drawing. Without a source, a change is later just a claim.
- Which status applied before? Drawing number and revision, item in the bill of materials, section in the specification.
- What does it mean for schedule and cost? Even a rough estimate helps. "No impact" is also an answer.
- Who is affected? Purchasing, electrical, manufacturing, assembly, documentation.
- What is the status? Requested, assessed, ordered by the customer, implemented.
What does a simple change register look like?
For most projects one table per project is enough. What matters is that there is exactly one and that every row points to its source.
| No. | Change | Requested by, on | Source | Affected revision | Schedule | Cost | Affected | Status |
|---|---|---|---|---|---|---|---|---|
| 7 | Frame transfer height 850 to 1,000 mm | Customer, maintenance, 14 Oct | Email of 14 Oct | Drawing 4711-200 Rev. C, BOM items 12–15 | +3 days | Profiles, 6 h design work | Purchasing, assembly | ordered |
| 8 | Additional emergency stop at station 3 | Customer, project management, 21 Oct | Minutes of design review 21 Oct, p. 2 | Circuit diagram sheet 14 | none | Push button, wiring | Electrical | assessed |
Two rules make the register useful. First, a change is entered before it is implemented, not afterwards. Second, the status meeting looks at the register, not at people's memories.
When does a customer change become a change order?
The contract decides, and the answer differs from project to project. One habit helps in practice. Every change with an impact on schedule or cost is confirmed to the customer in writing before it is implemented. A short email with the content, the impact and a request for approval is often enough.
If you do that consistently, you can present a list with evidence at the final invoice. If you do not, you end up negotiating over memories.
What can you do differently from the next project on?
One register per project, from kick-off. Even if it is empty at first. If you only create it at the first big change, you have already lost the small ones before it.
One input channel. Agree with the customer that changes go to a fixed address or to the project manager. Phone calls are followed up with a short email.
Mark changes in the drawing. The revision field does not just say "frame adapted" but gives the number from the register.
Inform those affected actively. Especially after release for manufacturing. A new revision in the file storage is not enough when the order is already under way.
Review after the project. Which changes came, in which phase, with which consequences? For the next quotation this review is worth more than any lessons learned report. Why those reports are otherwise rarely read is covered in the article on lessons learned in machine building.
How does KoAssist help?
Project Memory in KoAssist, the AI agent for machine and plant builders, reads the specification, emails and minutes for a project. When an email with a customer change arrives, a proposal for the project status is created, with a reference to the email. It only becomes valid once someone on the team accepts it. The decision stays with the team, and the source is still attached to the change. Project Memory is currently in pilot operation with existing customers.
For completed projects the knowledge assistant helps. It answers questions such as "Which customer changes came after design release on similar plants?" from the existing documents, every statement with file and page.
If you would like to see how this looks 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
