Skip to main content
Hybrid App Logo
freelance change order example

Freelance change order example for added scope

See a fictional freelance change order example that documents the original scope, new request, price impact, timeline impact, and approval language.

Fictional example. Last reviewed 2026-05-31.

Draft change orderView all examples

Example change order: extra CMS template and training

A fictional scope-change draft for a freelancer documenting extra work before starting it.

Original scope

One landing page sprint

New request

Add one CMS blog template and training walkthrough

Business impact

Extra build time, QA time, and handoff work

Approval need

Written approval before work starts

Change order summary

This change order covers the added CMS blog template and training walkthrough requested after approval of the original landing page sprint. The new work adds design, build, QA, and handoff time that was not included in the approved quote.

Scope and price impact

Added CMS template design/build

$1,200

CMS QA and responsive cleanup

$350

Training walkthrough and handoff notes

$250

Total change order

$1,800

Timeline impact

If approved by June 3, this adds three business days to the delivery window. If approval arrives later, the timeline will shift based on the next available production window.

Approval language

Please reply with 'Approved' if you want me to add the CMS blog template and training walkthrough to the project at the $1,800 change-order price. I will not start the added work until the change order is approved in writing.

Why this works

  • The draft separates original scope from the new request.

  • The added price is tied to work categories instead of a vague surcharge.

  • The timeline impact is visible before the freelancer absorbs the delay.

  • The approval line prevents work from beginning on an ambiguous yes.

Guardrails

  • This is business drafting support, not legal advice or a contract validity review.

  • Review your original agreement, approval authority, payment terms, and local requirements before sending a change order.

  • Reply-based approval language is illustrative only and may be insufficient for enforceable authorization, charging rights, or contract amendment in some jurisdictions.