Guide
Client Asked for "One More Thing." Is It Scope Creep?
A source-backed checklist for deciding whether a small request changes the original agreement.
Direct Answer
A client request becomes scope creep when it adds work, revisions, deliverables, integrations, timing pressure, or responsibility beyond the original agreement without an updated tradeoff. The safest response is not immediate refusal. It is to compare the request against the agreed scope and clarify impact before starting.
When This Problem Happens
This usually happens when a client-work decision depends on scattered files: an agreement in one place, a message in another, and an invoice or delivery record somewhere else. The risk is taking action from memory instead of reviewed context.
What to Check First
- What source controls the decision?
- Who has authority to approve, change, or pay?
- What exact deliverable, invoice, or request is involved?
- Is any concern, dispute, or missing asset still open?
- What action is now supported: confirm, invoice, follow up, or wait?
Evidence You Need
What Usually Blocks This Action
- Vague approval that does not name the deliverable.
- A new request that changes timeline, price, or acceptance criteria.
- Missing delivery proof, invoice terms, or payment promise details.
Example Scenario
A client says the work looks good, then asks for one more item before paying. Treat the praise as a signal, not final proof. Review the original scope, delivery record, and invoice terms before deciding whether to confirm, change scope, invoice, or follow up.
Recommended Next Step
Use the checklist to identify the controlling record, then send the smallest message that clarifies the next action without over-explaining the whole project history.
Markdown Template
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]How Revelare Helps
Revelare turns scattered project files and messages into reviewable records, project status, and next steps. It is built to support judgment, not replace it.
FAQ
What should I check first?
Start with the source record that controls the decision, then confirm whether anything important is missing or disputed.
Can I use the Markdown template directly?
Yes, but adjust the facts, tone, and next action after reviewing your own client records.
How does Revelare help?
Revelare is designed to keep client files, approvals, scope changes, invoices, and next actions visible in one reviewed workspace.