Compliance & ContractsFree templatePDF, Excel, Word exportEngineer-to-Order Machinery

Customer Change Order Proposal Template

A change order proposal should leave the customer in no doubt about what changes, what it costs and what it does to the delivery date. This template gives project managers a clear, one-page structure that can be exported to PDF or Word and sent for signature.

Fill in

Live preview
Download:

Customer Change Order Proposal Template for ETO Projects

Change Order Proposal CO-004

From: Northline Automation Inc. To: Harlan Packaging Co. Project: Case Packer Line 3 Customer PO or contract: PO-448120 Date issued: 2026-10-20 Reason for change: Customer-directed scope change

Description of change

Replace the specified 3-axis pick head with a 4-axis head to handle the new 12 oz carton, including revised mounting frame, PLC rack relocation and updated safety validation.

Price breakdown (USD)

ItemAmount
Engineering5,400
Fabrication and assembly labor9,620
Material and purchased parts14,200
Subcontract and freight2,100
Overhead and profit5,900
Total change order price37,220

Schedule impact

This change extends the contract delivery date by 9 calendar days from the date of written acceptance. Work on the changed scope will begin only after written acceptance of this proposal.

Exclusions and assumptions

Price excludes customer-side electrical work and any changes to the carton design after issue of this proposal. Lead times for the 4-axis head are as quoted by the supplier on the issue date.

Validity and payment

This proposal is valid for 30 days from the date issued. Payment terms follow the original contract unless stated otherwise here. Acceptance of this change order forms an amendment to PO-448120.

Acceptance

Customer authorised signatory / Date
Date / Date
{{company}} project manager / Date
Date / Date

This is a starting point for change proposals, not legal advice. The change clause in your contract governs notice periods, pricing method and who may authorise a change. Have your contracts or legal team review the final wording, especially for fixed-price work.

Draft change proposals from live ERP data

Optional: see a private agent that assembles the proposal from BOM, routing and cost data for your review.

Optional. The tool and every export work without this. No spam.

How to use the template

Fill in the project details and reference the customer PO or contract so the document ties to the original agreement. Choose the reason for the change, because it affects who bears the cost. Describe the change in plain engineering terms, then enter the price breakdown by cost category. State the schedule impact in calendar days and list the exclusions and assumptions the price depends on. The preview updates as you type, and you can export to PDF or Word with a signature block.

  • Quote the price breakdown to the dollar, not rounded
  • Include exclusions that stop later scope creep
  • Attach drawings or a redline when the change is physical

What a good proposal contains

Good proposals have six elements: identification of the contract and change number, a clear scope description, a price broken down by category, a schedule effect, assumptions and exclusions, and a validity period with a signature block. The breakdown matters more than the total because the customer's reviewer will challenge individual lines. Showing time impact separately avoids the common dispute where a small price change hides a large delay.

Process notes

Send the proposal as soon as the effect is understood and record it in your change log. Do not start the changed work before the written acceptance is in hand if your contract requires it. Keep the numbering sequential and link the document to the work order or project task in the ERP so actual cost can be compared to the quote when the job closes. If the customer partially accepts, issue a revised proposal rather than editing the original.

Common mistakes

Frequent errors include describing the change vaguely, leaving out the schedule impact, forgetting to state the validity period, and not tying the proposal to the original contract number. Teams also let several small changes accumulate without telling the customer the combined effect on delivery.

  • One change per proposal where possible
  • Always state whether price includes freight and tax
  • File the signed copy against the project in the ERP

Frequently Asked Questions

Who should sign a change order?

The person with authority to amend the contract on the customer side, often a purchasing manager or project sponsor, and an authorised person on your side. Check your contract's notices and authority clause, because an engineer's email is often not enough.

Can I start work before the change order is signed?

It depends on the contract. Many require written authorization first, and starting early can weaken your right to payment. If you must proceed to protect the schedule, get a written notice to proceed with a not-to-exceed value.

Should the proposal show markup separately?

Showing overhead and profit as one line is common and transparent. Some contracts fix the markup percentage or require itemised labor rates, in which case follow the contract format. Hiding markup in labor rates tends to invite audit requests.

How long should the proposal stay valid?

Choose a period that matches your supplier quote validity and labor availability. Thirty days is common. For changes with volatile material, such as steel or electronics with long lead times, a shorter period is more prudent.

Netray can draft these proposals directly from your ERP data, pulling BOM changes, labor rates and open commitments for human review. Ask how it would work with your system.

Keep exploring

Free tools

Guides

AI on your ERP