- Accepted baseline
- Order/quotation revision ___; specification ___; artwork/dieline ___; sample scope ___; accepted delivery arrangement ___; current approval conditions ___. Link the exact record that the supplier proposes to change. Comparing a new request with an obsolete draft can make already agreed work appear additional.
- Change description and reason
- Request reference/date ___; requested by ___; altered material, dimension, artwork, quantity or route ___; stated reason ___; evidence supplied ___. Keep the supplier’s explanation as a stated position until supported where needed. Distinguish a proposed improvement, buyer-requested revision and correction of an unfulfilled agreed deliverable.
- Affected work and dependencies
- Work already completed ___; unused materials ___; new setup or proof proposed ___; repeated testing/review proposed ___; delivery implications to confirm ___. Ask which tasks are genuinely incremental and which were included in the accepted scope. A changed file name alone does not demonstrate additional physical work.
- Cost explanation
- Quoted additional item ___; amount/currency as supplied ___; basis/quantity ___; source quote ___; prior included allowance ___; credits or avoided work proposed ___. Do not invent market rates or infer a confirmed credit. Ask for a scope-linked explanation that lets the buyer see what the added charge represents.
- Decision and revised commitment
- Accept, clarify, negotiate or retain baseline ___; authorized owner ___; accepted additional scope ___; revised offer/order ___; supplier acknowledgement ___; unresolved conditions ___. Record a technical decision separately from commercial authorization. A discussion of an alternative should not silently become approval to spend or commence revised production.