"That's outside the scope of this project."

What exactly counts as scope creep?

Scope creep is when the work starts expanding beyond what was originally agreed. This may look like extra rounds of revisions, new deliverables, changes to the brief midway through, or requests that keep getting added on top of each other. It can happen gradually, which is what makes it tricky. One small ask feels easy to say yes to, then another, then another, and before long you've taken on significantly more work than you quoted for.

Is it rude to push back on a client's request?

No, you're just pointing out that something is outside the scope of work you agreed on. It keeps the project on track and makes sure both sides are clear on what's been agreed. Clients who respect your work will respect the boundary. And if they don't, finish the current project and think carefully before taking on another one with them.

Do I have to quote for extra work, or can I just say no?

You can absolutely say no. Quoting for the extra work gives the client a choice rather than a dead end, but it's not a requirement, especially if you don't have capacity or simply don't want to take it on.

That said, this may be trickier to do when the client doesn't think the extra work is out of scope. In that case, you need to have a frank conversation with the client first.

What if the extra request seems small?

Small requests add up. A 5-minute ask once a day becomes a significant chunk of unpaid time over a project. If you're regularly absorbing small extras, it's worth pausing and deciding: is this goodwill I'm happy to extend, or is it becoming a pattern that's eating into my time?

What if the client says it was "implied" in the original scope?

This is where a clear, detailed agreement or scope of work document at the start of a project earns its keep. If what's in scope is documented, you have something to point back to.

If the agreement was vague and there's genuine ambiguity, use your judgement. If it's something that could reasonably have been assumed to be included, you might choose to absorb it this time and use it as a prompt to write more detailed agreements going forward.

If it's clearly a new ask dressed up as something implied, it's okay to say so politely but clearly.

What if I already started the extra work before realising it wasn't in scope?

It happens. Raise it as soon as you notice, rather than waiting until the project is done. Pause on the extra work, flag that it sits outside your original scope, and agree on the cost before you continue. The sooner you say something, the less awkward it is.

Should I have a contract for this?

Yes. Even a simple written agreement that outlines what's included — and what isn't — gives you something to refer back to when scope starts shifting. Having the agreed deliverables in writing protects both you and the client.

The more specific you are about what's included upfront — deliverables, formats, revisions, quantity — the less room there is for ambiguity later.