Agreement
What was originally promised or approved?
Guide
Scope Creep Checklist for Designers
A designer-focused way to decide whether an extra client request changes the agreed creative scope.
Framework
Review the decision before writing the message.
Change
What new fact changes timing, cost, scope, or tone?
Action
What message, invoice, confirmation, or wait state is now supported?
Copyable
Scope Creep Checklist
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]Related
Use this with Revelare.
FAQ
What is the first thing to check?
Start with the source record that controls the decision: agreement, approval, delivery record, invoice, or payment promise.
Can I use the template without Revelare?
Yes. The template is useful on its own, but Revelare is designed to connect it to the supporting client records.
Early access
Help shape a clearer way to run client work.
We are inviting independent professionals and small teams to test with real or anonymized client projects.