Use change orders, milestones, acceptance criteria, and revision limits to protect margin.
Key takeaways
- Define what is included and explicitly excluded.
- Require written approval before added work begins.
- State the rate or method used to price changes.
A written change process
A marketing engagement starts with four landing pages. The client later requests email copy, analytics setup, and a webinar deck. A change order identifies the added deliverables, $1,900 fee, and seven-day extension before the freelancer starts the extra work.
Run a contract-specific review
Scope control begins with a baseline that can be observed. List deliverables, included rounds, client dependencies, dates, and exclusions. A change process is useful only when it explains who can request a change, what information is required, and when work may resume.
1. Create a baseline
Attach the approved brief, content inventory, technical requirements, and delivery assumptions.
2. Define included feedback
Count revision rounds and distinguish corrections from new direction or new deliverables.
3. Price the change
Estimate added fees, schedule impact, dependencies, and any work that must be discarded.
4. Approve before work
Require written authorization from a named decision-maker before starting changed scope.
Stress-test the difficult case
Small requests can create material scope growth when they arrive separately. A single new field, integration, export format, or stakeholder review may look minor, but the combined requests can change testing, accessibility, security, and delivery dependencies. The agreement should allow the freelancer to aggregate related requests and assess their cumulative effect. It should also explain what happens when the client delays an input and later asks the original launch date to remain unchanged. Schedule compression is a new constraint and may require a revised fee or reduced scope.
Verification pass before signing
Dry-run the change process with a realistic request before signing. Write the request, identify the baseline it changes, estimate labor and third-party costs, state the schedule effect, and route it to the named approver. Confirm that neither casual chat messages nor feedback from an unauthorized stakeholder can silently authorize work. The test should produce a complete change record with request date, assumptions, price, revised milestone, acceptance method, and approval. If the process is too cumbersome for a small change, create a lightweight threshold rather than abandoning documentation.
Evidence to retain
Keep the baseline brief, request date, impact estimate, signed change order, revised timeline, and acceptance record together.
Worked example
Changing the color of an approved page may fit a revision round; adding a membership system changes deliverables, testing, security work, and the launch schedule and should use a change order.
What to verify
1. Scope
Define what is included and explicitly excluded.
2. Trigger
Require written approval before added work begins.
3. Evidence
State the rate or method used to price changes.
4. Fallback
Update dependencies and delivery dates with every change.
Build the decision record
| Review item | Record before signing |
|---|---|
| Create a baseline | Attach the approved brief, content inventory, technical requirements, and delivery assumptions. |
| Define included feedback | Count revision rounds and distinguish corrections from new direction or new deliverables. |
| Price the change | Estimate added fees, schedule impact, dependencies, and any work that must be discarded. |
| Approve before work | Require written authorization from a named decision-maker before starting changed scope. |
Warning signs
- “Minor changes included” has no measurable boundary.
- Teams discuss changes in chat but never approve cost.
- The original deadline remains after scope expands.
Questions to resolve before signing
- What would prove that “create a baseline” is satisfied if the parties later disagree?
- What would prove that “define included feedback” is satisfied if the parties later disagree?
- What would prove that “price the change” is satisfied if the parties later disagree?
- What would prove that “approve before work” is satisfied if the parties later disagree?
Sources and further reading
- IRS: Independent contractor status
- U.S. Copyright Office: Works made for hire
- FTC: Endorsements and testimonials
External sources explain general rules and terminology. Your signed agreement, current policy, jurisdiction, provider documents, and individual facts control the actual outcome.
Open the related ContractFixPro tool