Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
Scope Creep Checklist
A practical checklist for deciding whether a new client request changes scope, timeline, budget, or approval criteria.
Use it when
Start from a clear structure, then check the facts.
These templates are deliberately plain. The value comes from pairing the message with the source records that support it.
scope creep
Scope Creep Checklist
# Scope creep check
New request: [describe request]
Original scope source: [proposal / contract / approved change]
Check whether the request:
- Adds a new deliverable
- Changes timeline or launch date
- Adds revision rounds
- Requires new technical work
- Changes acceptance criteria
- Depends on a new person, tool, or asset
Decision:
- In scope: [why]
- Out of scope: [why]
- Needs clarification: [question to ask]
Suggested next step: [confirm / change request / later phase]Before sending
Review the evidence first.
Status
Is the project confirmed, unclear, overdue, or blocked by a missing record?
Tone
Does the message fit the client relationship and the current state of the work?
Related
Continue with the matching workflow.
FAQ
Who should use Scope Creep Checklist?
Independent professionals and small teams who need a calm, source-aware starting point before sending a client message.
Should I copy it exactly?
Use it as a structure, then adjust the facts, tone, and relationship context before sending.
What should I check first?
Check the relevant approval, scope, delivery, invoice, or payment record before using the template.
Early access
Bring this template into real client work.
Early access helps us test these workflows against actual project records.