A corporate gift production change order should identify the approved baseline, the proposed replacement and the exact units that may change. Start there before discussing a rush fee or a revised delivery date. The downloadable workbook below helps procurement, brand, finance and regional teams record those decisions without treating a spreadsheet approval as proof that a factory has stopped or a shipment has changed. It is designed for changes after sample or proof sign-off, not for replacing the original approval process.
Lock the baseline before accepting a new specification
Preserve the last approved proof, its source files, the applicable item and the purchase-order version. Record who approved which question: brand appearance, translated copy, physical fit, cost or delivery. A message saying “please use the new box” is incomplete if nobody can identify the old box, affected quantities or agreement it changes.
Use the artwork preflight and proof-approval workflow to establish that initial baseline. This change log begins afterward. It records a proposed deviation and the consequences of accepting it. Do not overwrite a signed proof with a new file bearing the same name or attach yesterday's approval to a different carton, decoration process or language insert.
One change identifier should survive discussion, rejection, revision and closure. Keep a separate proposed-proof version and preserve superseded proposals. If an email, factory system and purchasing system use different references, add their mappings to the evidence record. A new identifier is not a remedy for an operation whose outcome is unknown; it can leave two instructions active.
Distinguish an internal method from a supplier's actual process. For example, the University of Michigan's published change-order guidance describes its own approval route and excludes credits or negative quantities from that route. That is an institutional example, not a universal rule for merchandise orders. This workbook allows a negative estimated cost delta, but your purchasing owner must confirm how an actual reduction, credit or cancellation is processed under the applicable agreement.
Download the workbook and understand its limits
Download the English seven-sheet workbook, version 1.0, or download the English register as a values-only CSV. Both contain the same two fictional, unapproved example changes. Replace them with your own records before a live decision. Evidence URLs, named approvers and approval dates are deliberately blank, so a worked estimate cannot be mistaken for a real signed change.
The workbook contains Instructions, Change Register, Impact Calculator, Approval Log, Lot Market Scope, Exception Queue and Version History. Enter the stable identifier in each relevant source table. Cost, approval and lot records match that key; they do not depend on the register remaining in its original row order. The exception view reads those records and shows the next action. It does not own a second set of business calculations.
Amber cells are editable and pale-blue cells calculate. Each change uses one currency. Do not add a dollar estimate to a Taiwan-dollar estimate or assume a currency code performs conversion. Enter explicit zero for a known zero charge; a blank means the figure is unknown. Tax and freight are quoted manual deltas, not calculated legal rates or assumed exemptions.
Total estimated delta equals the unit-cost difference multiplied by affected units, plus separately entered one-time charges, scrap, freight delta and tax delta. The total rounds to two decimal places. Confirm your currency and contractual rounding before use. Schedule delta is new promised date minus old promised date in calendar days. It is not a working-day calculation, holiday calendar, forecast probability or confirmed delivery guarantee.
The file supports twenty changes, twenty impact records, eighty approval rows and forty scope rows. Before expanding it, extend dependent ranges, tables and validations together and test the next unused row. The CSV is a portable snapshot, not a live calculator: editing its price will not update its total. Retain the workbook version and extraction date whenever sharing that snapshot.
Define the fields and give each decision an owner
Procurement owns the change request and supplier acknowledgement. Brand checks the proposed physical or visual result. Finance decides whether the quoted variance is authorized. The regional owner identifies affected markets and language versions; legal reviews changed legal wording where required. Logistics confirms what can still be held, reworked or released. One person may hold more than one role, but the record should show which responsibility they exercised.
This field dictionary is an original operating model dated October 20, 2026. It describes the minimum evidence to obtain, not a claim that every supplier or software platform has implemented the fields.
| Field group | What to record | Evidence to obtain | Decision owner |
|---|---|---|---|
| Change identity | Stable change ID, item and baseline/proposed proof | Signed baseline and exact proposed source version | Procurement with brand |
| Cost basis | Quantity, currency, unit costs and separate charges | Versioned quote and explicit assumptions | Supplier and finance |
| Date basis | Old/new promise and critical-path dependency | Supplier's dated confirmation, not an estimate alone | Production and logistics |
| Approval requirements | Required roles, named decisions, dates and proof version | Accessible decision evidence for that scope | Authorized role owners |
| Market and lot scope | Affected units, state, disposition and installed version | Lot mapping and regional confirmation | Regional and warehouse owners |
| Closure | Executed result, remaining costs and customer notice | Actual acknowledgement, order match and exception result | Procurement with finance and logistics |
Define the required roles before collecting approvals. The workbook compares their declared count with distinct role rows and checks the proposed version, named approver, date and evidence. Repeating a role does not create additional authority. A filled name is still a record to verify, not authentication of that person's delegation. Keep permissions and actual evidence access within your organization's controls.
Use one location for each input. The calculator owns additional charge assumptions and dates; the register owns item quantity and unit prices; the approval log owns decisions. If the supplier revises a quote, record its new source version and route the affected cost decision again. A favorable total must not conceal an old approval or an outdated shipping promise.
Compare unchanged, changed, rejected and paused work
A stockout or copy correction creates a decision, not an automatic obligation to accept the proposed alternative. Compare the same affected quantity, evidence and delivery requirement across the available paths. Where an option cannot meet the requirement, state why; do not assign invented scores to make one route look objectively best.
The workflow table below compares four decisions using the same cost, date and execution questions. Amounts and authority remain specific to the actual quote and contract.
| Decision | Required evidence | Cost and date trade-off | Stop or acceptance condition |
|---|---|---|---|
| Approve unchanged specification | Original proof and supplier availability confirmation | Avoid new specification work; original availability may still fail | Confirm the original route can actually perform |
| Approve a scoped change | New proof, quoted delta, role decisions and affected lots | Accept revised cost or timing only for defined units | All applicable decisions plus supplier execution evidence |
| Reject and revert | Rejected proposal and retained signed baseline | May avoid change cost; committed materials can remain payable | Verify the supplier stopped the rejected revision |
| Pause or re-source the item | Hold acknowledgement and comparable replacement quote | Protect unresolved work; new sampling and capacity can add delay | Re-source only after resolving original commitments |
For re-sourcing, use a consistent supplier quote comparison rather than comparing one supplier's bare unit price with another's delivered total. A cheaper component can still require a new insert, different packing labor or another sample. Keep those consequences visible instead of hiding them in a single revised unit price.
Separate decision from execution. “Approved record; verify execution” means that the documented prerequisites have been entered. It does not send a factory instruction, amend a purchase order or confirm a hold. The responsible owner must obtain those results through the actual supported workflow and preserve the original references.
Hypothetical decision: replace a welcome-kit carton
Assume a supplier reports a stockout after a welcome-kit carton has been approved. Procurement creates a change for one thousand affected kits, links the original carton proof and requests a proposed carton version. The supplier supplies dimensions, material, fit and a revised quote. Brand reviews an actual sample where fit cannot be established digitally. Finance assesses the variance, and logistics checks the packing and dispatch dependencies. These are fictional quantities and dates, not a customer result or a market benchmark.
For the example estimate, old unit cost is two US dollars and proposed unit cost is 2.30 dollars. The variable delta is three hundred dollars. Add fifty dollars of one-time charges, zero scrap, forty dollars of freight delta and zero tax delta: total estimated increase is 390 dollars. The explicit zeros are assumptions to confirm, not evidence that scrap or tax can never apply. The workbook's calculated value does not make the quote binding.
The old promised date is November 10 and the proposed date November 15, 2026, a five-calendar-day difference. Identify which dependency creates the change: sample approval, carton supply, assembly slot or transport booking. Ask whether it changes the arrival promise or only a factory milestone. Do not add every supplier's delay together if the tasks run in parallel, and do not call a factory completion date customer delivery.
Compare accepting the scoped carton change with retaining the original specification or pausing and finding another source. The original carton may no longer be available, so rejection alone does not restore capacity. A substitute carton may damage the brand experience or fail to secure the cup. A faster source may create another sampling cycle. The owner chooses using current evidence rather than a generic preference for speed or lowest price.
If the new sample fails fit review, stop the proposal and record the failure against that proof. Preserve the original baseline, ask the supplier what work has already been committed and obtain a rollback or hold acknowledgement. Reverting is useful only if the original route can still be performed. If not, keep the case paused with the unresolved availability and cost decision, rather than recording a successful rollback that nobody confirmed.
Acceptance for the hypothetical changed route requires a signed or appropriately approved change identifier, exact linked proof, revised supplier delivery promise, authorized variance and matching purchase-order version. Reconcile affected quantities and obtain actual execution evidence. If a supplier response times out after an instruction, check the original operation before sending another version. Keep remaining commitments, fees or unconfirmed holds visible until their owners resolve them.
Hypothetical decision: change legal insert copy after packing
Now assume a multilingual insert needs a late legal wording revision. The responsible reviewers determine that Taiwan and Korea are affected, while six hundred Japan-market kits may retain their existing approved insert. The affected four hundred units comprise two hundred packed Taiwan kits and two hundred unstarted Korea kits. That market boundary must be a documented qualified decision, not an inference from which cartons happen to be easiest to open.
The regional owner maps each affected lot, quantity, installed source version and production state. Legal identifies the replacement wording and version. The supplier quotes printing, unpacking, insertion, resealing and scrap separately as applicable. Logistics compares holding all affected work with a controlled partial release of genuinely unaffected lots. Nobody should mark the entire order ready because one market's new copy has been approved.
For the fictional estimate, unit cost rises from six to 6.50 Taiwan dollars for four hundred affected units: a two-hundred-dollar variable delta. Add 150 in one-time charges, sixty in scrap, one hundred in freight delta and zero in tax delta, all in the same stated currency. Total estimate is 510 Taiwan dollars. The old November 12 promise moves to November 14, 2026: two calendar days. These numbers illustrate the formula, not local tax rules or typical rework pricing.
Test two failures before treating the file as a working control. Duplicate the change identifier and confirm that an ambiguous lookup does not quietly select the first record. Then leave one required approval date or named decision blank while completing the others. The next-action field must still call for the missing approval, rather than becoming ready because somebody has typed an overall approved label.
If a packed lot cannot be reworked without damaging the item, pause that scope and obtain a disposition decision. Do not replace a legal copy decision with a warehouse opinion that the old wording looks harmless. If the Korea lot can be corrected before packing, its readiness still depends on its own version, evidence and execution result. Partial release is an explicit lot-level decision, not a way to hide the Taiwan exception in a whole-order total.
Accept the case only when market and lot scope, approved source version, cost impact, disposition and customer notice match the actual result. Record the condition of reworked units and any scrap or remaining payment obligation. A notice prepared by marketing is not a notice actually sent by an authorized owner. If the affected quantity changes, recalculate the estimate and reopen the decisions that depend on it before releasing more work.
Test the workbook before entering live orders
The template was recalculated and behavior-tested in its authoring and saved-file import engine. That is not a claim of running your desktop spreadsheet application or your supplier's system. Open it in your intended environment, check the example totals and try one changed input before adding actual records. The blank evidence and approvals should remain visibly unresolved.
Use this pre-change checklist as an execution record. Each check should point to dated evidence, not just a green cell.
-
Identify the signed baseline, item, proposed proof and stable change identifier without overwriting the original.
-
Confirm affected market, lot, production state and units, including what remains unchanged.
-
Obtain versioned before/after unit costs, one-time charges, scrap, freight and tax assumptions in one currency.
-
Confirm old/new promise dates and the actual critical-path dependency with the supplier.
-
Declare required roles and collect their named decisions, dates and evidence for the exact proposed version.
-
Test zero and blank quantities, negative deltas, blank dates, duplicate identifiers and a missing approval.
-
Confirm the supplier's hold, revision or rollback through the original reference; resolve unknown operations before repeating instructions.
-
Match the executed result, purchase order, remaining costs, disposition and authorized customer notice before closure.
For the sample carton, zero affected units still leaves ninety dollars of entered one-time and freight charges. That is why zero is not treated like a blank. A negative unit-cost delta remains a negative estimate rather than being forced to zero. Blank dates do not become a fictitious zero-day delay. These checks protect distinctions; they do not decide whether a charge is contractually due.
Keep record-key tests as part of maintenance. Sorting the change register should not attach one change's freight to another. Adding the next row should retain formulas and validations. When increasing capacity, recheck first, middle and last rows plus all cross-sheet ranges. Do not assume a copied visual table carries the original calculations with it.
Recover from late changes and uncertain instructions
Keep an exception on its original change record when a quote, approval or supplier result is unresolved. Assign a next action and responsible owner. A requested hold, a confirmed stop and completed rework are different events. Do not delete an exception merely because it is inconvenient for a campaign report or create a new change to conceal the old one.
What if the requested change arrives after dispatch?
Identify the original shipment and exact affected lots first. Ask logistics what can still be intercepted and obtain actual confirmation before promising recovery. Legal and regional owners determine the appropriate disposition and customer communication for the changed content. Keep delivered, in-transit and not-yet-shipped units separate. Record actual interception, return, rework or replacement evidence and costs. An attempted intercept is not success, and a new replacement order must not race an unresolved original shipment.
For a rejected proposal, preserve both the rejection and any work already committed. The supplier may have purchased materials or reserved a line before the stop was received. Finance should reconcile those obligations against the agreement and original evidence. The workbook's negative estimate is not a credit note and a cancellation request is not a settled balance.
If a source file is wrong, issue a new proposed version and invalidate only the approvals affected by that change. Retain earlier evidence as history. Ask each responsible reviewer the question that changed, then check the final accepted artifact rather than only the email announcing a correction. Restoring a filename is not restoring its old contents.
Close the decision while preserving what still matters
A useful production change log preserves the signed baseline, explains the exact difference and connects each affected unit to a current decision. Its estimates should make trade-offs visible, and its status should reveal missing evidence instead of replacing it. Close the change when the executed specification, order, cost, lot disposition and required notice can be reconciled. Leave genuine residual obligations open with their owners.
For a program that fits, Giftpack's merchandise and production guidance can help frame sampling, production and fulfillment discussions. Confirm the actual supplier route, approval responsibilities, change handling and delivery commitments in your agreement. You can discuss an approved production plan with Giftpack; this workbook does not establish an automatic change-order integration or replace brand, finance, legal or logistics decisions.