Quick Answer
Compare the request with the active SOW, separate new scope from included revisions and owed corrections, and write the scope, fee and date changes. Obtain approval by the contract’s required method before starting changed work. Keep unaffected obligations moving; require cash before restart only for an agreed advance condition or applicable suspension right.
Key Takeaways
- Classify new scope separately from clarifications, included revisions and owed corrections.
- Agree scope, price, dependency dates, invoice events and payment due dates in the changed terms.
- Obtain approval tied to the exact version by the required method; signatures are conditional, not universally mandatory.
- Hold unapproved new work while preserving unaffected delivery and payment obligations.
- An advance can be an agreed restart condition; check unknown payment status before retrying.
Start with the request and the active scope#
When a client request changes deliverables, timeline, budget or another agreed term, compare it with the active scope before promising the change. Separate new work from clarifications, included revisions and corrections you already owe. Informal requests can become disputed extras when approval, price and dates remain unclear.
Draft the actual change and obtain approval by the method required by the contract and applicable law before starting new or amended work. Keep unaffected obligations moving. A request to correct your own failure to meet the agreed acceptance standard is not automatically a paid scope change.
Before you start#
Before you draft anything, pull four inputs into one project record: your written contract, the active SOW version, the latest approved deliverables baseline, and the client request in writing. Keep them together with a version log. You want to see what changed and when.
| Project input | What it shows | Record note |
|---|---|---|
| Written contract | Amendment rule and controlling terms | Keep it in the project record |
| Active SOW version | Current scope baseline | Use it to map the request line by line |
| Latest approved deliverables baseline | What output was already approved | Compare changes against this baseline |
| Client request in writing | Exact wording of the new ask | If the request came in on a call, send a recap and ask the client to confirm the wording in email or Slack |
The active SOW is your anchor because it gives you the current scope baseline. That gives you a usable reference for deciding whether the new ask stays inside scope or changes the deal. If the request came in on a call, send a recap right away and ask the client to confirm the wording in email or Slack. Drafting from memory is a common way to create mismatches.
Run the first four steps#
Step 1: Capture the request text exactly. Copy the client's request verbatim into the project record. If you need to summarize it, keep the original text beside your summary, not instead of it. The test is whether someone else could open the file and tell what was requested, by whom, and on what date. If that trail is fuzzy, you do not have a usable input yet.
Step 2: Classify each item against the active SOW. Mark each requested item as in-scope, new or changed, or unclear. Included revisions and correcting a failure to meet existing requirements stay within the original obligations. New outputs, changed technical requirements, a new deadline or commercial terms need a proposed change. Clarify uncertainty in the affected tasks, while continuing work whose requirements remain clear.
Step 3: Draft the scope and commercial deltas. Rewrite only the changed parts, and write them in result-based language that can be checked later. For each changed deliverable, define the revised output, the due date, and the fee impact or invoice trigger tied to that output. Include enough technical and pricing detail that the client can approve the change as a real decision, not a placeholder. You want terms that are measurable enough to deliver, review, and bill without a second interpretation fight.
Step 4: Obtain approval before starting changed work. Send the revised scope, budget, timeline and exact approval version to someone with authority. Follow the amendment method in the contract and applicable law. Where signatures are required, obtain them; where explicit written approval is permitted, retain an approval that identifies the document and terms. A recap of a discussion is not necessarily acceptance.
Keep unaffected work and obligations moving while the new or amended tasks await agreement. If the request changes an existing SOW line, use the change-control process. A records gap does not itself authorize withholding an already owed deliverable or payment; follow any contractual and lawful suspension rights.
Pass or fail before execution#
| Check | Required record | Status |
|---|---|---|
| Approval | Signed terms are filed, or the written approval matches the contract's amendment rule | Pass |
| Budget update | Revised fee or invoice trigger is explicit | Pass |
| Timeline update | Changed milestone or delivery date is explicit | Pass |
| Version trail | Request text, approved version, required authorization and version log are identifiable. | Pass |
| Affected work restarted early | One of those records is still missing | Fail |
Before new or amended work starts, confirm the material scope, fee, timing and required authorization. Fix administrative gaps promptly, but do not turn a missing folder copy into a new suspension condition for obligations already due. The approval record should identify the final version and authorized decision.
Define what triggers a change order#
Start with one decision: is this a clarification, or did the client actually move the deal? If the request changes Deliverables, Timeline, Budget, or another contract term, treat it as a change and pause affected work until it is approved.
Step 1: Verify the active baseline first. Confirm the active written contract and current SOW version, then log the client request in your project record. Map each request line against the current scope and milestone plan, and classify it as in-scope, net new, or unclear. Your checkpoint is simple: you should be able to point to the exact SOW line the request matches. If you cannot, do not guess.
Step 2: Run a clarification vs scope-change check. A clarification explains existing agreed work. A scope change alters what was agreed, even when the ask sounds small. Uncontrolled scope expansion rarely arrives all at once; it usually shows up as small, reasonable-sounding requests that stack up over time.
| Check | Clarification | Scope change |
|---|---|---|
| Scope fit | Explains existing agreed work | Adds, omits, substitutes, or cannot be tied cleanly to current scope |
| Schedule impact | No timeline movement | Timeline or delivery timing changes |
| Cost impact | No price or billing change | Price, billing, or paid-work scope changes |
| Contract impact | No contract term changes | One or more contract terms change |
| Path | Log and continue under current terms | Route to change order approval before executing changed terms |
Freeze any unclear line until the client confirms the output, exclusions, dependency owner, and acceptance test in writing.
Step 3: Reply in a decision-ready format. State the request, classification, and impact before you draft final paperwork. If terms changed, route it through a change control process before changed work proceeds.
- Acknowledge the request.
- State what changed: added, removed, substituted, or clarified.
- State schedule and cost impact, or explicitly confirm no impact.
- State that changed terms require approval before the changed work proceeds.
Step 4: Apply the decision rule and log it. If any material term moved, formalize the change in writing and get mutual agreement on the terms. If nothing material moved, log it as a clarification in the project record and continue under existing terms. Record the timestamp, approver name, and affected task IDs so your delivery history and billing record still match later.
Gather what you need before you draft#
Gather the active baseline and the requested scope, schedule and commercial impact. You can draft with clearly marked open points to help the client decide; unresolved material terms must be agreed before new or amended work starts.
Step 1. Assemble one controlling folder#
Build one source-of-truth folder before you write terms: the active written contract version, active SOW version, latest approved deliverables baseline, and the exact request thread. If your SOW sits under a master agreement, confirm the correct child SOW is tied to the correct parent agreement.
Quick test: another person should be able to open the folder and identify which contract controls, which SOW controls, what baseline was approved, and where the request originated.
Step 2. Map each requested change before drafting language#
Map each requested item to project impact before writing scope text. Keep the mapping simple, but explicit.
| Requested change (client wording) | Affected deliverable | Affected milestone | Dependency touched | Acceptance criteria status |
|---|---|---|---|---|
| Requested item pending confirmation | Deliverable pending confirmation | Milestone or date pending confirmation | Dependency pending confirmation | Defined or unclear |
Keep client wording beside the scope mapping. If a row is unclear, ask a precise written question. Draft confirmed rows in parallel, without treating an unresolved row as approved.
Step 3. Pre-fill commercial terms#
Propose the revised fee, billing currency, payment method, invoice trigger and due date in the draft. Price approval is the outcome of negotiation; it is not a prerequisite to preparing a useful proposal.
Specify both when an invoice may be issued and when payment is due. Valid negotiated triggers can include signing for an advance, a calendar date for periodic billing, delivery, acceptance or recorded hours. An acceptance trigger needs a review deadline and a way to handle disputed items.
Step 4. Assign owners and enforce the execution gate#
Assign one owner to each control point: scope validation, commercial approval, and approval-packet send. Then enforce one gate: no changed work starts until written approval is filed in the project record.
Confirm the exact approved version and approval record are available to the people executing it. Retain signatures where the required method calls for them.
Related reading: How to Write a Follow-Up Email That Closes the Deal.
Step 1 classify the request and freeze ambiguity#
Classify each request line before pricing or drafting so ambiguous items do not slip into approved work. Against the active SOW and latest approved deliverables baseline, use working labels in-scope, out-of-scope, or unclear, and treat every unclear line as on hold. Use a line-by-line table so mixed requests are not bundled into one yes-or-no decision.
| Request line | Scope label | Next action |
|---|---|---|
| Client wording (verbatim) | in-scope / out-of-scope / unclear | leave as-is / move to pricing / send clarification |
Write one controlled change statement#
After labeling, write one short change statement that captures what is added, replaced, removed, deferred, and which milestone or acceptance criteria are affected. If you cannot state those fields clearly, pause and clarify before moving forward.
Send a clarification script and hold unclear items#
For any fuzzy line, send one written clarification note and keep that item parked until answered. Your note should confirm:
- The requested output in concrete terms.
- What is excluded and remains unchanged.
- Dependencies, inputs, or client review needed.
- Whether the item is approved for quoting now or still under discussion.
Use a hard checkpoint: if a neutral reviewer cannot map each request line to a scope label and next action, this step is not complete.
Keep the source request, classification table, clarification thread, decision log and pricing/timeline handoff in the project record. Save the agreed correction or new-work decision so an in-scope obligation is not accidentally priced as an extra.
Step 2 decide price and timeline with clear tradeoffs#
Use one decision rule: if scope or speed changes, update price, delivery terms, or both in writing before work resumes. A change order is not automatically a price increase. It can raise fees, lower fees, or only move dates, as long as the addendum matches the actual change.
When you present options, keep the revised scope identical in both. Change only budget and timeline so the client is choosing a real tradeoff instead of comparing different scopes. Price by effort type, not by email length.
| Decision point | Option A: preserve the deadline | Option B: lower the additional fee |
|---|---|---|
| Revised scope | Same explicitly listed revised scope | Same explicitly listed revised scope |
| Budget | Includes a stated rush/resource premium | May remove the rush premium if the longer schedule actually lowers cost |
| Timeline | Original deadline only if resources and client inputs support it | Later agreed date |
| Limit | A higher fee cannot make an impossible deadline feasible | More time does not make all added effort free |
| If the original budget is fixed | Negotiate a specific scope swap or reduction as a third option | State what is removed; do not promise identical extra work at no cost |
| Dependency rule | Specify input and review dates | Specify revised input and review dates |
| Request type | Price treatment | Timeline treatment |
|---|---|---|
| Net-new deliverable | Add cost for distinct added work | Add time as needed; define a new acceptance check |
| Accelerated turnaround | Price the compression effort (resource load, parallel work, shorter review windows) | Keep the earlier date only if compression assumptions are met |
| Added revision cycle | Add recurring execution cost for the extra round | Add review or iteration time for that round |
| Dependency-driven rework | Price reperformed or obsolete work and impacts to unchanged work | Re-date affected milestones tied to that rework |
List client inputs, review windows and signoff owners. State the agreed consequence of late dependencies, including notice and how revised dates will be confirmed. Do not invent an automatic schedule extension after a delay if the contract has not provided one.
Choose billing triggers that fit the work and cash needs: an agreed advance at signing, periodic time billing, milestone delivery or acceptance. Make the amount, invoice event and payment due date distinct. Signing or calendar-based billing is legitimate when agreed; a completed milestone is not the only possible trigger.
Before you send#
Before the draft goes out, run three checks against the invoice and milestone logic:
- Confirm each revised milestone has a matching invoice trigger in the addendum.
- Confirm trigger order matches the real sequence of work and approvals.
- Confirm amount, payment date, and delivery event match your invoice draft.
Recheck applicable freelancer protections after a change. NYC requires a written contract for covered work totaling at least $800 with the hiring party over 120 days. Illinois covers qualifying independent-contractor work totaling at least $500 over 120 days, with Illinois work or a contracting entity located there and statutory exceptions. Both authorities describe payment by the contract date, or within 30 days after completion if no date is specified. A pending change does not cancel payment already due.
Step 3 write the contract addendum line by line#
Draft only the delta once price, dates, and invoice triggers are set. Write each changed line so it is testable, billable, and date-anchored; if a line fails any check, revise it before sending.
| Addendum part | Include | Control check |
|---|---|---|
| Document identification | Addendum title, addendum ID, effective date, legal party names, base agreement title, and base agreement date | A third party should be able to match the addendum to one specific signed baseline |
| Scope change lines | Changed deliverable, acceptance test, dependency owner, and revised milestone anchor date | Each changed line should be testable, billable, and date-anchored |
| Payment lines | Amount, trigger event, invoice timing, and payment instructions when relevant to the project | Keep amount, invoice event and due date explicit; include an advance, periodic billing or milestone trigger if agreed. |
| Closing terms | State that all base terms remain in force except where changed and include signature blocks for all parties | Party names and document labels should exactly match the original contract |
A contract addendum sits alongside the original agreement, updates specific terms, and leaves the rest in force. Use it when a change affects rights, obligations, timelines, or payment terms. If an undocumented change could affect a dispute outcome, put it in writing now.
Identify the deal exactly before you touch scope.#
Start with the addendum title, addendum ID, and effective date. Then list legal party names exactly as they appear in the signed contract, plus the base agreement title and base agreement date. If work is split between a master contract and an SOW, copy those labels word for word and keep references aligned with your change control in an Agile SOW.
Use one check: can a third party match this addendum to one specific signed baseline without asking what you meant? If not, fix document-control fields before drafting scope language.
Write scope changes as line items, not paragraphs.#
Give each changed deliverable its own line and use the same four fields every time:
- Changed deliverable
- Acceptance test
- Dependency owner
- Revised milestone anchor date
Make unresolved fields visibly open in the draft, with an owner and decision date. An estimate can be useful if labeled and its pricing effect explained; do not present it as an agreed fixed fee or date. Minor typo corrections and included revisions need accurate records, but are not automatically new paid work.
Map each commercial term to a real trigger event.#
For each payment line, include the same core details:
- Amount
- Trigger event
- Invoice timing
- Payment instructions, including currency and rail details only when relevant to this project
An agreed advance can be invoiced at signing; a milestone invoice can be issued on the stated delivery or acceptance event. Use an explicit due date or define the calculation. For example, an invoice issued October 10, 2026 and due 14 calendar days later is due October 24. If you use 14 days after month-end instead, that invoice is due November 14. Those terms differ; choose one and write it consistently.
Close for enforceability, then run a pre-send validation pass.#
State which base terms remain in force and which specified provisions this change supersedes. Provide signature blocks where required by the amendment method. Signatures are not a universal prerequisite to every binding commercial agreement: applicable law and the parties’ authorization method matter. In relevant U.S. interstate or foreign-commerce transactions, 15 USC section 7001 prevents denying a record legal effect solely because it is electronic; it does not make every message a valid signature or override other obligations.
- Not testable: no measurable acceptance check or no named deliverable
- Not billable: no amount, no invoice trigger, or no payment timing
- Not date-anchored: no effective date, milestone date, or dependency date
- Not document-matched: party names or document labels do not exactly match the original contract
Templates can speed drafting, but they should not make legal decisions for you. If a change is large, sensitive, or likely to be disputed, treat the template as a draft and get legal review before signature.
Step 4 lock the legal clauses clients forget to revisit#
Before signature, run a legal consistency pass, not just a scope-and-price pass. Scope edits can quietly affect termination rights, liability allocation, indemnity responsibility, and dispute enforceability.
| Clause | Recheck focus | What to confirm |
|---|---|---|
| Termination rights | Cancellation or termination triggers, notice flow, and when either side can stop performance | Clause still matches new approvals or phases |
| Limitation of liability | Whether liability-limiting wording still fits the revised work | What liability is limited and where responsibility still sits |
| Indemnification | Whether the scope change shifted who controls inputs, outputs, or approvals | Indemnity wording reflects that shift |
| Dispute terms | Governing law, forum selection, and continued performance during disputes | Addendum does not conflict with the base contract |
Use this sequence while the addendum is still editable:
Termination rights: recheck trigger events.#
If scope changes alter approvals, phases, or delivery flow, confirm termination triggers and notice mechanics still match how the work will actually run.
Limitation of liability: recheck exposure fit.#
When risk shifts, verify liability-limiting language still fits the revised work and still clearly states what is limited versus what remains each party's responsibility.
Indemnification: recheck responsibility shifts.#
If control of inputs, outputs, or approvals moved, update indemnity language so it tracks that new allocation instead of old assumptions.
Dispute terms (governing law and forum): recheck enforcement alignment.#
Confirm the addendum does not conflict with the base contract on governing law (which law applies) or forum selection (where disputes are decided), and does not break any continued-performance workflow already in the contract.
Compare the addendum with the master agreement and SOW. Agree an order-of-precedence rule where needed, identify the provisions superseded and keep unchanged terms in force. Use the contract’s required amendment method. An electronic signature can be appropriate where legally and contractually permitted; a vague email about an unidentified draft is weak evidence of the terms agreed.
Step 5 handle cross-border payment and tax friction upfront#
Agree executable payment terms alongside the new scope. Receiving an advance is a restart condition only if the parties have agreed that condition. A net-terms project may require delivery before payment; adding an internal cash-confirmation gate does not change that obligation.
| Control point | What to lock | Evidence to keep |
|---|---|---|
| Currency-to-settlement path | Invoice currency, settlement currency, what happens if payment is sent in a different currency, and who covers conversion or transfer costs | Signed addendum; final invoice version |
| Payment rail | Required details for the chosen bank transfer or platform payment method, plus who initiates payment on the client side | Payment instructions sent to the client |
| Failed-transfer rule | Who investigates the original attempt, when a confirmed failure is retried, who bears agreed correction costs, and how received funds satisfy the invoice. | Original transaction reference and verified status; bank/provider receipt record; correction trail. |
For cross-border projects, define one complete path from invoice to settled funds. If a client contact, project lead, and accounts payable person would each read the packet differently, tighten it before signature.
Step 1. Lock the currency-to-settlement path#
Confirm a supported receiving account for the agreed payment method. If details are not ready, resolve the payment setup promptly or agree an alternative. Continue obligations under existing terms unless a negotiated advance condition or a lawful suspension right permits a hold.
Then make the addendum and invoice packet internally consistent: invoice currency, settlement currency, what happens if payment is sent in a different currency, and who covers conversion or transfer costs. Keep all of that in one place. If those terms are split across chat, email, and invoice notes, you are still exposed.
A useful check here is simple: can the payer tell, from the approved terms alone, what currency to send and what account should receive it? If not, the path is not locked. Also share only the information the chosen method needs. Over-sharing payment data can create confusion or unnecessary risk.
Step 2. Choose and verify the payment rail#
Confirm the actual payment method with accounts payable, including the provider route, recipient details, supported currencies and reference. Compare expected timing and costs for that route. A Spain bank-account article is not a universal cross-border setup instruction.
To keep processing from stalling, use a method-based checklist:
- Bank transfer: include legal name, bank name and address, account number or IBAN, SWIFT/BIC code, account currency, and the payment reference to include.
- Platform payment: include the account email, account ID, or payment link tied to the account, the exact payment target details, required reference format, and who initiates payment on the client side.
Your verification point is whether finance can confirm the exact rail and the exact destination without follow-up questions. A common failure mode is delay caused by incorrect details or unclear instructions. Do not treat "AP will sort it out later" as a completed payment setup.
Step 3. Write the failed-transfer rule and keep a tight record trail#
Assign an owner to investigate a returned, pending or misdirected transfer. Check the original transaction reference and bank/provider status before any retry. Unknown or pending status is not a confirmed failure; a second payment can duplicate the first. Once failure is confirmed, agree correction details and fees and retry through the approved method. Receipt must satisfy the agreed invoice terms, while later withdrawal availability or a provider payout is a separate state. A work hold must follow an agreed advance condition or applicable suspension right.
Confirm applicable invoice and tax treatment for the actual parties and transaction, including VAT/GST and lawful withholding where relevant. Accounts payable’s requested fields do not establish the legal tax result. Record required certificates and how withholding is credited against the invoice; unresolved tax questions need qualified review rather than guessed amounts.
Keep an evidence pack for this step so you can prove what was sent, paid, and corrected:
- approved addendum
- final invoice version
- payment instructions sent to the client
- transfer proof or remittance confirmation
- correction trail for any returned or amended payment details
Resolve material currency, method, fee and tax terms before agreeing new work. Apply payment-related holds only where the negotiated terms or applicable suspension rights permit them. Pay and deliver existing obligations when due; a new internal checklist cannot rewrite a net-terms contract.
Keep cross-border terms proportionate to the project. Domestic payment details can stay unchanged if the change does not affect them.
Step 6 send the change order and control execution risk#
Do not restart changed work until revised terms are sent, written approval is received, and that approval is filed with the addendum and project record. This is the execution gate: if the approved version is unclear, delivery and billing risk rises fast.
Treat the send step as a control point, not a courtesy email. Use one check: can someone outside the thread read the packet once and identify what changed, what it costs, what date moved, and what action is required to approve it?
Step 1. Send a decision-ready approval packet#
Send one decision-ready packet: a summary message plus the contract addendum attachment. In that message, state:
- what changed from the current SOW or deliverables
- the impact on price
- the impact on timeline or milestones
- the exact approval action required, for example, sign the PDF or reply from the written approval workflow your client actually uses
If you present options, keep them directly comparable and mark your recommended choice. Send the packet to the person who can actually move it forward. If more than one reviewer is involved, say that clearly so the packet does not stall in forwarding.
Step 2. Hold affected tasks and separate them from in-scope work#
While approval is pending, hold changed tasks and label them clearly in your tracker. Keep unaffected tasks separate by task, milestone, or deliverable so you can keep moving without quietly expanding scope.
Obtain clear authorization tied to the final scope and price. An informal message can be adequate only if it actually agrees the identifiable terms through the method the contract and applicable law permit. Clarify doubtful wording; do not reject valid approval merely because it arrived electronically.
Use task-level separation, not blended cards. If part of a work item is old scope and part is changed scope, split task IDs or labels so your record trail shows what stayed in scope, what was held, and what restarted after approval.
Step 3. Run the same restart workflow every time#
Use one repeatable sequence every time: pause, recalculate, send revised terms, confirm written approval, then restart only against approved language. If timing shifts before approval, revalidate fees and dates before resuming.
If fixed-fee scope is too fluid, propose time-based pricing for the changed portion, with a rate, recording method, estimate or cap, and billing dates. The client must agree the switch before you use it; you cannot retroactively replace the fixed price on your own.
Archive the request, summary, approved addendum, required approval/signature record, any hold notice and revised invoice. Confirm the team, tracker and working files point to that approved version. Keep the change-control process linked to the SOW so later requests follow the same method.
Step 7 execute only against approved terms#
Only restart changed work when approval is documented and the active file set is final. If approval status, effective terms, or working version is unclear, keep affected work paused.
Step 1. Confirm the restart gate#
Use the approved addendum and updated SOW as your execution baseline. Before you resume, confirm written approval, effective terms, and the current version label in your project record so no one restarts from an older draft.
Step 2. Re-baseline every live task#
Map each live task and milestone to an approved deliverable and acceptance check in the updated scope. If a task does not map to approved language, park it until the terms are clarified in writing.
Step 3. Bill from approved lines and keep one complete record#
Invoice from approved lines only: each billed item should map to a contract line, milestone trigger, or deliverable approval. Keep one complete paper trail with status updates, delivery evidence, approval messages, invoice revisions, and payment confirmations, and save corrections as new versions so the history stays intact.
If new work or delivery activity is not tied to approved terms, pause it and run a new change-order cycle.
Fix common mistakes before they cost you money#
Most change-order problems come from a few repeat mistakes, not edge cases. When any of these appears, pause changed work and restart only after your active SOW/addendum, payment terms, and written approval record are aligned.
1) Verbal extras#
Classify a verbal request against the baseline before calling it an extra. Risk signal: new work starts after a vague call instruction. Recovery: confirm whether it is an included revision, owed correction or proposed change; send the scope, date and fee effects for approval when terms change. Proof: retain the request, recap, proposed version and required approval. Keep existing obligations separate.
2) Vague scope#
If a proposed changed item is vague, define it before execution. Risk signal: support, optimize or a few revisions lacks a measurable output or acceptance standard. Recovery: write the deliverable, criteria, due date and owner. Check each later request against the approved baseline before calling it a paid extra. Proof: retain the approved redraft and client decision for each changed task.
3) Missing payment terms#
Check whether the approved change carries forward sufficient payment terms from the base agreement. Risk signal: a material fee or due-date term was never agreed. Recovery: clarify and agree that term before new work; preserve already approved obligations and amounts due. Proof: retain the approved addendum, invoice calculation and payment dates. A missing internal invoice draft alone does not authorize withholding owed delivery.
4) Unapproved updates#
A draft without required authorization is not the working baseline. Risk signal: the team cannot identify which revision was accepted. Recovery: consolidate the proposed terms, obtain approval by the required method and mark superseded drafts. Proof: retain the approved version, effective date and approval/signature record; a separate signed PDF is required only when that method calls for it.
| Common mistake | What you might assume | Defensible correction |
|---|---|---|
| Verbal extra | "We both know what we agreed." | Send a written recap, issue an addendum, and wait for approval. |
| Vague scope | "We can sort details out during delivery." | Rewrite into specific deliverables with acceptance criteria. |
| Missing payment terms | "The old billing setup still applies." | Restate fee lines, invoice triggers, and any upfront payment term. |
| Unapproved updates | "This draft is close enough." | Work from the current approved version, with signatures where required. |
Before resuming changed work, run this reset check once:
- active SOW or approved addendum version matches the work you are about to do
- each changed deliverable has acceptance criteria and an owner
- each fee line has an invoice trigger and any required upfront payment term
- approval record is written, filed, and tied to the effective document
If any item fails, keep changed work on hold until approved terms are active.
Copy and paste this change order checklist#
Use this checklist to confirm the material restart conditions for new or amended work: agreed scope, fee, dates and required authorization. Keep the supporting records dated and tied to the accepted version. Resolve missing approval before starting the change; fix administrative copies promptly without inventing a suspension right for obligations already due.
Step 1. Reject weak proof before you check anything off#
Use the table to identify missing terms or approval and to organize evidence. Distinguish an unapproved change from an approved change whose internal folder copy needs updating.
| Checklist line | What counts as proof | Common weak proof to reject |
|---|---|---|
| Baseline docs | Active contract or SOW, latest approved revision label, original request message, change ID | Old draft, unlabeled PDF, "latest version" with no version label |
| Scope delta | Written comparison of changed deliverables, timeline impact, and budget impact | Call notes without a deliverable list, "small update" in chat |
| Approvals | Signed addendum or written approval record with an effective date | "Looks good" message from someone not designated to approve scope or price |
| Execution controls | Documented restart condition, invoice trigger, payment terms, archived final file set | Verbal go-ahead, unsigned markup, missing invoice event |
| Delivery plan | Updated milestone date, dependency notes, owner for the first restarted task | Generic task list with no date or owner |
Step 2. Run the gate checklist#
Work through the list in order. Check whether delivery, billing, and approval records all point to the same live document.
- Verify baseline docs. Attach the active contract or SOW, latest approved version label, client request message, and internal change ID.
- Confirm the scope delta. Attach one written comparison that shows changed deliverables, revised timeline, and budget impact.
- Confirm approvals. Attach the approved addendum or other written approval record with the effective date.
- Confirm execution controls. Attach invoice trigger, payment terms for changed work, restart condition, and archived final file set that replaced drafts.
- Confirm the delivery plan. Attach next milestone date, dependency notes, and the named owner for the first restarted task.
Quick check: open the file you plan to work from and confirm its name, version label, and approval record match what is attached in the project record.
Step 3. Restart only after a clean pass#
Prepare and send the revised SOW or addendum before collecting approval. Once approved, archive that exact version and map changed tasks to its scope lines; then start under its agreed conditions. Generating a fresh version after approval requires checking the changes and obtaining new authorization where necessary. The SOW generator can help prepare a draft, but does not approve it.
This handoff is where errors often return. If your task tracker, invoice draft, or delivery file names still point to an older draft, you do not have a clean pass yet.
Worked example: one new output and one owed correction#
Assume SOW-01, agreed October 1, 2026, covers a five-page website design for USD 2,000, delivery October 20 and one review round. The client asks for a sixth FAQ page and correction of a mobile layout that already fails the SOW’s agreed requirements. Correct the mobile issue under the existing fee. Quote the new page separately; this avoids treating your own correction as a paid extra.
Illustrative CO-01: Parties [same legal names as SOW-01]; effective October 8, 2026. Add one FAQ-page design using client-supplied approved text, responsive desktop/mobile layouts and one consolidated review round. Exclude copywriting, implementation and further pages. Client supplies text October 9 and comments within two business days after the first draft. Revised delivery is October 23, provided those inputs arrive on time; delayed inputs trigger notice and an agreed revised date. Added fixed fee: USD 300; revised total fee: USD 2,300. No change to amounts or dates already due under SOW-01.
Agreed billing example: USD 150 advance invoiced on approval, payable before the new FAQ-page work starts; USD 150 invoiced on delivery October 23, due November 6. The advance condition applies to the new page, while existing work and the owed mobile correction continue. Existing payment method remains unchanged. CO-01 supersedes only the specified scope, price and delivery provisions; other terms remain in force. Approve the exact CO-01 version by the amendment method in the base agreement.
Illustrative approval message: “Please approve CO-01 version 2: one FAQ-page design, USD 300 additional fee and October 23 delivery on the stated dependency dates. The mobile correction remains included. Use [required signature or approval action] to accept this version. I will continue the original work while the additional page awaits approval.” These dates and amounts are examples to adapt, not a universal clause.
Close the loop and make this your default operating habit#
The FAQ covers edge cases, but day-to-day protection comes from one repeatable sequence: trigger -> action -> proof. If a request changes scope, timeline, price, or acceptance terms, pause affected work and run these four steps before restart and closeout.
| Step | Core action | Done when |
|---|---|---|
| Classify the request | Compare the request against the active SOW, label each item as in scope, net new, or unclear, and pause unclear or changed task IDs | The client request is saved, the scope comparison is written, and paused items are visible in your tracker |
| Draft from your standard files | Build the update from your template and checklist and carry forward the original contract date, project name, addendum number, effective date, revised fee, milestone dates, invoice trigger, and payment method | The draft addendum and checklist are versioned, filed, and match the exact file you send for approval |
| Confirm approval before restart | Send one approval packet with the summary, final PDF, and the exact option the client is approving | Written approval, approval record and any required signatures, and approval date are filed in the project record |
| Close the loop | Match approved terms to delivery proof, invoice line items, and payment records | Request, draft, approval, final approved file, invoice copy, and payment proof are stored together in the project record |
Step 1: Classify the request.#
Compare the request against the active SOW and label each item as in scope, net new, or unclear. Pause unclear or changed task IDs until terms are updated. This is where drift usually starts: a message can sound minor while still changing output, review rounds, or approval criteria. Done when: the client request is saved, the scope comparison is written, and paused items are visible in your tracker.
Step 2: Draft from your standard files.#
Build the update from your template and checklist, not memory. Carry forward the original contract date, project name, addendum number, effective date, revised fee, milestone dates, invoice trigger, and payment method. The file you send for approval should already be the file you can store, invoice from, and execute against. Done when: the draft addendum and checklist are versioned, filed, and match the exact file you send for approval.
Step 3: Confirm approval before restart.#
Send the approval packet with the summary, exact final version and selected option. Verify that the authorized client agrees those terms through the required method. Done when: the approved version, required approval/signature record and effective date are retained.
Step 4: Close the loop.#
Before marking the change complete, match approved terms to delivery proof, invoice line items, and payment records. Think in artifacts, not memory: what was approved, what was delivered, what triggered billing, and what was paid. Done when: request, draft, approval, final approved file, invoice copy, and payment proof are stored together in the project record. Set retention timing for your tax or recordkeeping obligations.
Check that changed deliverables map to approved scope, invoices map to agreed triggers and receipts are reconciled to the right invoices. Fix records promptly and distinguish missing evidence from an actual missing approval or payment. Preserve completed-work billing and unaffected obligations while proposed extras await agreement.
Keep reusable intake, scope-delta, approval and billing files so the next request starts from the current baseline. Reuse the structure, while checking the actual change and required approval each time.
Frequently Asked Questions
When is a change order mandatory?
Use a documented change when the parties alter agreed scope, price, dates or another contract term. Whether a particular form or signature is mandatory depends on the contract and applicable law. Clarifications, included revisions and correcting your own nonconforming work are not automatically paid changes.
Can you start early with verbal approval?
Follow the required authorization method. Starting new work on a vague verbal instruction risks a dispute over its scope and price. Obtain approval tied to clear terms before starting the change, with signatures where required; continue unaffected duties and owed corrections.
What is the practical difference between a change order and a contract addendum?
Both can update specified terms while leaving the rest of the agreement in force. Tie the document to the active agreement and identify what it supersedes. Use the required approval method and signatures where required, rather than relying on the document’s label.
What counts as a valid client signature?
Confirm signer authority, intent to approve and the exact document. Use the contract’s amendment method and applicable law. An electronic signature is not invalid merely because it is electronic in transactions covered by U.S. E-SIGN, but a vague approved message is not automatically an adequate signature or assent.
Should you handle small requests informally?
Log true clarifications and included revisions under existing terms. For changed scope or pay, obtain explicit approval in the required form. The size of the request does not decide whether it is new work; the existing scope and acceptance obligations do.
Should you bundle changes or split them into separate updates?
Either can work if the client can identify each scope, fee and date change. Keep the selected option and approved version clear and obtain the required authorization before the related changed work starts.
What matters most on cross-border payment and tax terms?
Agree invoice and settlement currencies, the payment method, fee allocation, invoice event and due date. Determine actual VAT/GST or withholding treatment rather than relying only on payer preferences. Check original payment status before retrying and apply advance-payment holds only if agreed.
Can you rely on one template for every country and dispute setup?
No. Adapt the approval method, governing law, dispute terms, invoicing and tax treatment to the deal. Preserve unchanged obligations and check local mandatory rights; a generic template or electronic-signature rule does not settle every legal question.
Watch
How to Write a Freelance Change Order
Try a related tool
Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.
Sources
Educational content only. Not legal, tax, or financial advice.
Related Posts

10 Freelance Contract Red Flags to Check Before Signing
Use this as a fast decision screen, not a legal theory exercise: sign the Freelance Contract, send a Contract Redline, or walk away.

Structure Change Control in an Agile SOW Before Scope Creep Starts
Use this practical approach for **change control in agile sow**: keep requests in writing, record impact, and make approval ownership explicit before work starts. Think of it as an operational control to reduce confusion, not a legal standard.

The Freelance Payment Penalty: A Modeled Audit of Platform Fees, FX Spreads, and Payout Delays
The money rarely disappears through a single, easy-to-spot fee. The real loss is stacked. A marketplace takes its commission, a processor adds a charge for international cards, a bank or payment company converts the currency at a spread, a platform holds the funds before release, and a wire sheds a little to intermediaries on the way in. Each layer looks defensible on its own, but the worker feels the combined result as a smaller deposit and a later payday.

