Freelance scope records
A change request template keeps extra client work specific
A useful change request template does more than capture a task. It records what changed, why it may be outside scope, what it costs, and whether the client approved it before work starts.
Where Work Scope Tracker fits
Work Scope Tracker turns a change request template into a project record: request text, scope decision, estimated hours, amount, delivery impact, approval link, and exportable history stay together.
Fields to include in a change request template
- Client request in the original wording or a short faithful summary.
- Original scope reference, affected deliverable, and requester.
- Scope decision: included, extra, or unclear.
- Estimated hours, additional amount, and deadline impact.
- Approval status, approval date, and decision source.
When the template matters most
- A client asks for work that was not listed in the original agreement.
- The request affects schedule, budget, deliverables, or revision rounds.
- A small change creates follow-on work in another part of the project.
- You need a cleaner record than screenshots from chat or email.
A practical workflow
- 1Write the baseline scope before the request is evaluated.
- 2Add the new change request as its own record.
- 3Compare it against the original scope and choose a scope decision.
- 4Add hours, amount, and delivery impact if approval is needed.
- 5Send the approval link before starting billable extra work.
Change request template
Request title: [short name] Request source: [email/chat/call/comment] Request summary: [what the client asked for] Original scope reference: [what was agreed] Scope decision: [included/extra/unclear] Estimated hours: [hours] Additional amount: [amount] Delivery impact: [date or none] Approval status: [waiting/approved/declined] Notes: [context]
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.