Track scope changes before they become unpaid work.
Keep the original scope, each new request, the agreed price or schedule impact, and the client approval together on one dated project record.
Scope creep rarely arrives as a formal change order.
It often begins with a short message: one more page, another revision, or a quick addition before launch. The request sounds small in isolation, but several small requests can change the cost and schedule of the whole project.
A dated change record gives the original agreement and the new request a clear relationship. It lets the freelancer and client see what changed without relying on memory or searching across conversations.
Turn an extra request into a clear project decision.
The goal is not more administration. It is a short record that makes the commercial impact explicit before the work disappears into the project.
- 01
Return to the accepted scope
Identify the deliverable or boundary the new request changes.
- 02
Record the request
Write down what was requested and keep the event dated.
- 03
State the impact
Record the agreed change to price, timing, or deliverables.
- 04
Keep the approval
Add the client decision before connecting the change to delivery and invoicing.
Invoice the work from an agreed record.
When the final invoice differs from the original proposal, the approved changes explain why.