Scope Lock & Change Request Kit for Freelancers: a practical guide

Document the agreed scope and route new requests through a visible approval decision before work changes. This guide explains the inputs, workflow and limits behind the decision so you can use the tool deliberately rather than treating its output as an automatic verdict.

The decision to make clearer

The core question is whether a new client request is already included, needs clarification, or requires an approved change to cost or timeline. Write that decision down before entering data. It gives the review a finish line and stops adjacent problems from turning one focused workflow into an unmanageable system.

What to gather before you start

Use current information you can explain. Keep estimates visible and date-sensitive assumptions easy to review.

• the agreed deliverables and acceptance points.
• what is explicitly out of scope.
• assumptions, dependencies and client responsibilities.
• the new request in the client's words.
• estimated impact on effort, price and schedule.

A focused workflow

1. Record the baseline

Summarize the scope both sides accepted. This step keeps the working view tied to the real decision rather than a decorative dashboard.

2. Log the request

Capture what changed and why it matters. This step keeps the working view tied to the real decision rather than a decorative dashboard.

3. Approve before acting

Confirm the decision and impact in writing first. This step keeps the working view tied to the real decision rather than a decorative dashboard.

How to read the result

The kit is working when a new request cannot silently enter delivery. Each change should be connected to the original scope, an impact assessment and a visible approval outcome.

Common mistakes to avoid

• Relying on memory instead of an agreed baseline.
• Starting extra work before approval.
• Discussing price without showing schedule impact.
• Using a change log as a substitute for an appropriate contract.

Frequently asked questions