Freelance scope records
An extra work request should make the tradeoff visible
Extra work is easier to approve when the client can see the request, the reason it is outside the original scope, the cost, and the delivery impact in one place.
Where Work Scope Tracker fits
Work Scope Tracker gives each extra work request its own record and approval state. That keeps the conversation practical instead of turning it into a memory test later.
What to include before asking for approval
- The new work the client wants.
- The original scope item or exclusion it is being compared against.
- Estimated hours or fixed additional amount.
- Delivery impact, including no impact if that is true.
- Decision needed before work starts.
Good extra work request triggers
- A new page, feature, asset, report, file, or deliverable is added.
- A client asks for a revision after included rounds are used.
- A request requires another tool, vendor, meeting, or review cycle.
- The change is small alone but creates repeated follow-up work.
A practical workflow
- 1Record the request in the project.
- 2Explain why it is extra or unclear.
- 3Add hours, price, and deadline impact.
- 4Ask the client to approve before work starts.
- 5Export the approved extra work list for billing review.
Extra work request message
I can add this as extra work. Request: [summary] Original scope reference: [baseline] Why this is extra: [reason] Estimated hours: [hours] Additional amount: [amount] Delivery impact: [date or none] Please approve before I begin.
Related problem guides
Try it on a real project
Create a project, write the agreed scope, and record the next request before it becomes another memory test.