MultiHub Forum

Full Version: What should I do about scope creep from a friendly freelance client?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hey everyone, I’ve been freelancing for about three years now and mostly things have been smooth, but I just wrapped up a project where the client was perfectly pleasant yet constantly asked for tiny, last-minute additions that weren’t in the scope. I didn’t mind at first, but it really ate into my time for other projects. How do you all handle that kind of gentle scope creep without seeming difficult? I’m worried pushing back might hurt the relationship even if the requests are small.
I hear you. scope creep can feel like a compliment until it starts nibbling at your calendar. I try to acknowledge the goodwill, then frame the tiny asks as a separate task with a quick review and a fair add on. A simple policy helps any change beyond the original scope logs as an extra hour or a small fee, scheduled as a next sprint. Do you have a go to line that feels warm but clear?
From a numbers mindset, those little requests add up fast. Track every additional task and the time it takes, then show the client a short log and a rate for extras. If you can offer a pre set add on rate or a 0.5 hour buffer for late changes, the conversation stays practical. It isn't about punishing them, it's about protecting your plan and theirs. Worth trying next time?
I get the worry about hurting the vibe. Maybe the client just wants to keep the project visible, not to test you. Still, a policy helps more than a lecture. If you say, 'these small changes are optional, here's the impact on the timeline' it becomes a standard choice rather than a friction point. Curious how you prefer to respond in the moment?
Reframe: what if those tiny requests are a signal you are shaping a longer relationship? You could propose a quarterly backlog review where priorities are rebalanced and extra work is planned, not sneaked in. It shifts the frame from policing scope to collaboration.
Practically I keep a shared change log. When a new task pops up, I drop it there and we decide if it goes into the current sprint or into an extras list. It makes scope creep visible and gives the client agency, not guilt trips.
One time I ignored the boundary and found a pile of tiny edits that bloated the schedule. After that I learned to quote a small add on fee for every odd request and to point to the plan we signed. It was awkward, but better than the scramble.
Writing habit note: tiny edits accumulate like editor notes; you end up with a different manuscript if you don't track them. A clear change policy is not a punishment, it is a craft choice about pacing and reader expectations.