How do I handle scope creep with clients without damaging the relationship?

Short answer: agree on scope in writing up front, and treat every new request as a change that is acknowledged, estimated and approved. Done respectfully, this builds trust rather than damaging it.

Prevent it before it starts

• Write a clear scope: features, pages, integrations, revisions included and exclusions.
• State who provides content and by when.
• Define what "done" means and how changes are handled.
• Explain the change process at kickoff, not when the first request arrives.

When a new request arrives

1. Acknowledge it positively. "Good idea, that would help your users."
2. Check against scope. Is it covered, or new?
3. Estimate the impact on cost, time and other features.
4. Offer options:
   • Add it as a paid change with a revised timeline.
   • Swap it for something of equal size in the current scope.
   • Put it in a later phase.
5. Get written approval before doing the work.

Example reply

Thanks, adding a booking calendar is doable. It is outside the current scope, and I estimate it at about two days. I can add it for that amount and move delivery by a few days, or schedule it for phase two. Which would you prefer?

Habits that help

• Keep a running change log with dates and decisions.
• Show progress often so surprises appear early.
• Distinguish small tweaks within the agreed work from new features, and be generous with the former so you can be firm with the latter.
• Build a small contingency into your price.

Pitfalls

• Accepting changes verbally and billing later.
• Letting a goodwill exception become the norm.
• Becoming defensive instead of offering options.

Clients mostly want clarity and a good result; clear process gives them both.