The point where work gets scattered
Small requests become confusing when they enter production through a quick chat while the agreed price, review rounds and delivery date still describe the earlier project. Both people need the same picture of what changes.
Compare the request with the accepted baseline
Find the actual accepted scope and list the requested change in ordinary language. ‘Add a booking page’ is a new deliverable if the accepted five-page list does not include it. ‘Fix the broken contact button’ may be a correction to a promised working contact page. Avoid automatically labeling every piece of feedback as additional work.
Sample acknowledgment: ‘Thanks for the request to add online booking. The current scope includes the five pages listed in version 2. I’ll outline the booking addition and its effect on the timeline before we decide how to proceed.’ This acknowledges the idea without implying that you have agreed to deliver it at the existing price.
Make the tradeoffs visible
Describe the added output, required client inputs, dependencies and review effort. Include any effect on existing work. A new booking page may need offer details, calendar access through an approved process, testing and updated navigation. A price for the page alone can be misleading if its setup also changes the launch sequence.
Offer realistic choices. The client might add the work and move the date, replace a deliverable of comparable effort, or keep the original scope and schedule a second phase. Do not promise all three dimensions—more work, the same fee and the same date—unless you have deliberately confirmed that you can deliver them.
- Added deliverables and explicit exclusions.
- Price difference and revised total.
- Timing, client inputs and affected milestones.
- What remains part of the existing scope.
Ask for a specific review decision
Sample wording: ‘Change C-03 adds one booking page and setup of the agreed appointment offer. It adds $450 to the $3,000 project, for a revised total of $3,450. Delivery moves from 6 May to 10 May if the offer details arrive by Friday. The original five pages remain included. Please review this addition and confirm whether you want C-03 or prefer to retain the original scope.’
A useful response selects an option and identifies unresolved questions. If the client replies with another new requirement, update the change before treating it as settled. If an agreement needs revision, use your existing document and consent process with an identifiable new version. An informal reaction should not be stretched into acceptance of terms the person did not review.
Update the working record before production
Keep the earlier scope and the reviewed change. Summarize which version now guides the work and make sure the people producing and reviewing it have the same information. Update the milestone checklist, client responsibilities and relevant payment request after the decision, rather than relying on everyone to reconstruct it from a long message thread.
If the client declines the addition, confirm that the original scope continues and note any genuine scheduling effect caused by the review delay. If no answer arrives, leave the change open and avoid beginning disputed work. At handover, inspect delivery against the accepted scope plus accepted changes, with unfinished items named separately.
Keep the context with the conversation
Messages can help compare the scope context you select with the new request and prepare a change summary for your review. Keep ordinary agreement revision in the process you already use. Review any resulting payment or booking separately; a scope draft, an accepted change and a confirmed payment are different records.
Understand your Twin · See Business access and metered AI usage