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.
A change order in plant engineering gets paid when it is backed by evidence. The customer change is documented with date and source, the difference from the agreed contract scope is named, effort and schedule impact are quantified, and the customer agreed in writing before implementation. The earlier you submit it, the less is negotiated at the final invoice.
Contents
Final meeting with the customer. The plant is running and the acceptance is signed. The final invoice lists three items for changes: a changed transfer height, an additional emergency stop and a different controls variant. The customer says they remember the conversations, but not that any of it was supposed to cost money. The project manager searches for the emails. She finds two. The third agreement was made on the phone.
The changes were justified and the effort was real. In the end, what gets paid is what is backed by evidence.
When does a customer change become a change order?
When it goes beyond the agreed scope of supply. A change order is the supplier's claim for this additional work. The yardstick is the contract status: the customer specification, the quotation, the order confirmation and, where there is one, the functional specification. Anything that is not in them, or is in them differently, is a change. Whether it is paid for is a matter for the contract.
Changes are normal in project business. A head of engineering at a plant builder puts a figure on it for his company. In about one project in four, the customer changes the geometry after the fact. How such changes stay traceable is described in the article on customer changes in plant engineering.
What does a solid change order need?
Evidence of the change. The email, the minutes or the marked-up drawing in which the customer requested the change, with date and sender.
The contract status. The passage in the customer specification or quotation that applied before. Without this comparison it remains unclear whether it was a change or a clarification.
The additional effort. Design hours, material, manufacturing, assembly. A rough estimate that others can follow is often enough for the approval.
The impact on the schedule. Does the FAT or the delivery move? If a date is held because more capacity is used internally, that is part of the effort.
The approval. Written agreement from the customer to content, price and date before anything is implemented.
Why change orders fail at the final invoice
Submitted too late. The customer has planned with the quoted price, and the memory of the agreement has faded.
The agreement was verbal. Phone calls and conversations at the edge of the site, with no record.
The change was simply implemented. The new revision shows the new status, but not that it was a customer change.
The contract status is unclear. If the customer specification and the quotation contradict each other, the customer can argue that the change was already included. How to find such contradictions early is explained in the article on analysing customer specifications.
Checklist: change order before implementation
- The customer's request is in writing, phone calls are followed up with a short email
- The affected contract status is named with document and page
- The change is entered in the change register, with a number
- The additional effort is estimated, split into design, material, manufacturing and assembly
- The impact on the schedule is assessed, even if it is "none"
- The change order has been sent to the customer as a quotation
- The customer's written approval is in before implementation starts
- The changed drawing carries the number from the register in its revision note
How does KoAssist help with change orders?
Project Memory in KoAssist, the AI agent for machine and plant builders, reads the customer 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. That way the source of every change is on record at the final invoice. Project Memory is currently in pilot operation with existing customers.
For the comparison with the contract status, the knowledge assistant helps. It answers questions such as "What does the customer specification say about the transfer height?" with file, page and section. 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
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 - 15 November 2026Article6 min
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.
6 min
