Fixed-price project control
Scope Creep Checklist for Fixed-Price Projects
Use a scope-creep checklist whenever a client request could add a deliverable, exceed a revision allowance, change approved work, or compress the schedule. Compare the request with the written scope, clarify uncertain details, calculate the real price and timing impact, and wait for written approval before beginning anything additional.
Scope creep is not a personality diagnosis. It is an operational gap between what was agreed and what someone now expects. A neutral checklist makes that gap visible early enough to decide what happens next.
Checkpoint 1
Capture the exact new request
Copy the client’s actual wording, requested deadline, attachments, and channel into one record. Do not silently translate “a quick tweak” into a defined deliverable. The difference between a question, a revision, and a new output matters.
If the request arrived in a meeting or voice note, restate it in writing and ask the client to correct your summary. A usable record describes the result they want, not only the activity they mentioned.
- What new output is being requested?
- Which existing deliverable would change?
- What deadline or launch date is attached?
- Who has authority to approve the change?
Checkpoint 2
Compare it with the agreed boundary
Find the relevant statement of work, proposal, email approval, deliverable list, revision allowance, exclusion, and acceptance rule. Compare the request with the written boundary rather than relying on memory or on how reasonable the message sounds.
A request that is already included should be called included. A consistent process builds trust precisely because it does not turn every client question into an extra charge.
- Named deliverables and formats
- Number and type of revisions included
- Client inputs and approval responsibilities
- Explicit exclusions and schedule assumptions
Checkpoint 3
Choose included, clarify, or paid change
Choose included when the request clearly fits the promised output or remaining revision allowance. Choose clarify when a missing fact could change effort, price, risk, ownership, or timing. Choose paid change when the request adds work or changes a commercial assumption.
Do not price a vague change. If “make it more premium” could mean a color adjustment, a new interaction system, or five new screens, first ask what visible result will count as approved.
Checkpoint 4
Calculate the complete impact
The impact is more than hours. Include production work, project management, review cycles, dependencies, rework risk, testing, handoff, and the opportunity cost of moving other scheduled work. The professional doing the work owns this judgment.
State schedule impact even when the client accepts the price. A paid change that keeps an impossible date simply converts a scope dispute into a delivery dispute.
Checkpoint 5
Stop before work and record the decision
Send a decision-ready reply that states feasibility, scope status, price, schedule impact, and the approval required. Do not start because the client sounded enthusiastic, attended a meeting, or failed to object.
Keep the original request, scope reference, final terms, written approval, and current status together. A PDF or email record supports shared understanding, but it is not automatically a legal contract.
- Written approval names the added deliverable.
- Price and schedule are both explicit.
- Work has not begun before approval.
- The final status is visible to both sides.