Freelance scope records
A change request template for Excel needs more than a task column
A spreadsheet can work well for change requests if it captures the decision context: source, original scope, cost impact, approval state, and notes.
Where Work Scope Tracker fits
Work Scope Tracker can replace a spreadsheet when you need approval links and exports, but the same column logic is useful if you are starting with Excel or Google Sheets.
Recommended spreadsheet columns
- Request ID, date, requester, and source.
- Request summary and affected deliverable.
- Original scope reference and scope decision.
- Estimated hours, amount, and delivery impact.
- Approval status, approver, decision date, and notes.
Spreadsheet limits to watch
- Approval evidence can still be scattered outside the sheet.
- Clients may not see the cost impact before work starts.
- Rows become hard to read when one request contains several decisions.
- Exports are useful, but approval links usually need another tool.
A practical workflow
- 1Start with one row per client request.
- 2Use consistent values for included, extra, unclear, waiting, approved, and declined.
- 3Record hours, amount, and delivery impact before approval.
- 4Move requests into Scope when you need a client approval link.
- 5Export the final history when billing or closing the project.
When to use this page
| Situation | Use it when |
|---|---|
| Excel is enough | You only need an internal log and the client approves elsewhere. |
| Scope is better | You need request pages, client approval links, and a cleaner export. |
| Use both briefly | You are migrating older projects from a spreadsheet into Scope. |
Example spreadsheet row
CR-014 | 2026-05-29 | Dana | Email | Add pricing FAQ section | Pricing page | Original scope was copy edits only | Extra | 1.5 | $150 | No deadline change | Waiting | Needs approval before work starts
Excel column header row
ID | Date | Requester | Source | Request summary | Affected work | Original scope reference | Scope decision | Estimated hours | Amount | Delivery impact | Approval status | Approver | Decision date | Notes
Common mistakes
- Using free-form status labels that make filtering impossible.
- Putting several requests in one row.
- Tracking hours but not approval state.
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.