You can acknowledge a good idea without immediately agreeing to unpaid work. Start by understanding the outcome, then check whether it fits the approved baseline.
For a vague request, try: “When you say [request], do you mean [option A] or [option B]? What should a visitor be able to do when it is finished? Once that is clear, I can confirm the scope and timing.” This asks for useful information rather than defending a price before there is a defined feature.
For an included revision, say so directly: “This fits [approved deliverable or feedback round], so I’ll handle it within the current project fee. I’ve added it to the tracker for [date], assuming [dependency].” Clarity works in both directions.
For new scope, use a neutral baseline reference: “[Feature] adds [specific deliverable] beyond [baseline reference]. I can prepare a change quote covering the fee and schedule impact, or we can put it in a later phase.” Avoid blaming the client for asking.
If the client calls it a small change, explain the tasks behind the estimate: “The visible edit is small, but it also needs [implementation, integration and testing]. A smaller option is [reduced scope] if that better fits the priority.” Offer the reduced option only if it is actually workable.
After sending a quote, do not silently begin the extra work while waiting for a decision. Continue with the current scope, subject to your existing agreement. Explain any real approval deadline without manufactured urgency.
When approval arrives, record the scope version, amount, currency and schedule impact. Confirm the next step under your agreed payment and approval process. When the feature is ready, ask for review against the stated completion criteria.
Revision Desk includes twelve editable scripts covering clarification, defects, included revisions, change quotes, reminders, deferral and handoff.