Freelance scope records
A change request log keeps client changes from disappearing into chat
Client changes usually arrive through email, chat, calls, or comments. A log turns scattered requests into one project record that can be reviewed before work begins.
Where Work Scope Tracker fits
Work Scope Tracker is built around this basic habit: each request gets a record, a scope decision, and an approval state. The tool is intentionally narrower than a full project manager.
Fields worth tracking
- Request date and requester.
- Original request text or a short summary.
- Affected deliverable, page, milestone, or file.
- Scope decision: included, extra, or unclear.
- Estimated hours, amount, and delivery impact.
- Approval status and decision date.
When a simple note app starts to break
- You cannot tell which requests were approved before work started.
- The same request is discussed across several channels.
- Billing depends on proving what changed, not just remembering it.
- You need to export a clean record instead of forwarding a messy thread.
A practical workflow
- 1Create one project record per client project.
- 2Add each change as a request instead of mixing it into notes.
- 3Attach the request to the affected deliverable or milestone.
- 4Mark whether approval is needed before starting.
- 5Export the log when closing the project or preparing billing.
Change request log columns
Date | Request | Source | Affected work | Scope decision | Estimated hours | Amount | Approval status | Notes 2026-05-20 | Add landing page section | Email | Homepage | Extra | 2.5 | $250 | Waiting | Needs approval before work starts
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.