Freelance scope records
A filled change request example shows what to record before work starts
A blank template is useful, but a filled example shows the level of detail that keeps later billing and delivery conversations practical.
Where Work Scope Tracker fits
Work Scope Tracker is built for this exact record: what changed, what the original scope said, why approval is needed, what the cost or timeline impact is, and what the client decided.
What the example should prove
- The request is tied to a real deliverable, page, or milestone.
- The original scope reference is visible next to the new request.
- The decision explains whether the work is included, extra, or unclear.
- Cost, hours, and delivery impact are written before approval.
- The final approval state can be reviewed later.
Details that prevent confusion
- Use the client wording or a faithful summary.
- Avoid vague labels such as small update or quick fix.
- Separate one request from another if they affect different work.
- Add the decision date when the client approves or declines.
A practical workflow
- 1Write the new client request as a separate record.
- 2Attach the original project scope or approved deliverable.
- 3Classify the request and explain the reason.
- 4Add price, hours, and delivery impact.
- 5Send an approval link and preserve the decision.
When to use this page
| Situation | Use it when |
|---|---|
| Included | The request is already named in the agreed deliverables or revision rules. |
| Extra | The request adds a new deliverable, page, feature, meeting, review round, or deadline impact. |
| Unclear | The original scope does not say enough to price or start confidently. |
Filled change request example
Request title: Add testimonials section Source: Client email, 2026-05-29 Request summary: Add a new homepage section with three customer quotes and logos Original scope reference: Homepage copy edits and one layout pass only Scope decision: Extra Reason: New section, new layout work, and additional QA were not included Estimated hours: 2.5 Additional amount: $250 Delivery impact: +1 business day Approval status: Approved by client email before work started
Copyable change request example format
Request title: [short name] Source/date: [where it came from] Client request: [exact or faithful summary] Original scope reference: [baseline] Decision: [included/extra/unclear] Reason: [why] Hours/amount: [estimate] Timeline impact: [impact] Approval status: [waiting/approved/declined] Decision source: [approval link/email/call note]
Common mistakes
- Treating the example as a task list instead of a scope decision record.
- Leaving out the reason the request changes the original agreement.
- Approving a bundle of unrelated changes in one line.
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.