Gixo Keystone · Scope creep
Scope creep starts with an unclear decision
Scope creep is work expanding beyond the agreed project scope without a corresponding reviewed change to the agreement, schedule or commercial terms. A useful response makes the request and the decision visible before the team treats it as another task.
Project access, your subscription and the current release determine which controls are available.
Start with the recorded agreement
Find the version of the agreement that applies to the work. Read its included deliverables, exclusions, dependencies and acceptance terms. A request that sounds small can still alter the expected output. A larger task can also belong to scope if it is already part of the agreement.
Write down what changed
Capture the request in the client’s words and identify the affected deliverable. Separate a clarification, a correction to unfinished agreed work and a request for additional work. The classification needs context; the number of words in the request is not a useful test.
Make a decision before the new commitment
Ask the responsible manager to compare the request with the recorded scope. Keep the decision, the evidence and a short reason. If it needs a separate agreement, review the change’s deliverables, timing, price and acceptance terms with the client before treating them as agreed.
An agency example
A fictional launch project includes one article and one review round. The client asks for a workshop. The team reviews whether the workshop is already included; if it is additional work, it prepares a separate change for review. Calling the task “client feedback” would not by itself resolve the scope question.
Keep the record through delivery
Retain the original scope and later decisions. Review completion and client acceptance as separate steps. This gives the next project discussion a common record; it does not guarantee a dispute-free project or replace the legal review an agreement may need.
Use Keystone for the recorded workflow
Keystone’s supported scope controls connect requests with recorded scope and manager decisions. Read the scope-management page for the product workflow and the guide for the steps. Optional AI suggestions are review aids, not automatic scope judgments.
Product copy reviewed 2 November 2026.