Skip to main content
Out of Scope

is giving advice after the engagement ends out of scope?

Yes — once the deliverable ships and the engagement closes, continued advice, strategy calls, and 'quick questions' are a separate service, not part of the original deal. The exception is a brief, contractually stated handoff or support period meant to land the work.

Why this answer

Advice is the easiest thing in the world to give away without noticing, which is exactly why it slips out of scope so quietly. A project has a deliverable and an endpoint; once you've handed over the work and the engagement has closed, your contractual obligation is complete. But clients often don't experience the relationship as closed — they experience it as a standing line to someone who understands their situation. So the 'quick question' arrives, then the follow-up, then the call to think through a decision your past work touches. Each one feels too small to charge for, and collectively they become an unpaid retainer. The reason this counts as out of scope isn't stinginess; it's that your expertise applied to their ongoing problems is the literal thing consultants sell. Giving it continuously after delivery means you're providing your highest-value service — judgment — for free, indefinitely, with no boundary that tells either of you when it ends. The work shipped. The relationship is warm. But continued counsel is a new service, and naming it as one is what keeps it sustainable.

When the answer flips

The verdict softens when your contract included a defined handoff or support window — a stated number of weeks of questions, a wrap-up call, a documented support period to help the client adopt the deliverable. Inside that window, answering is owed. It also stays reasonable to absorb a single, genuinely quick clarification about the work you delivered — 'which file is the final one?' is closing-out the project, not consulting. The flip toward Out of Scope is sharp when the questions stop being about your delivered work and start being about the client's broader decisions: strategy, new initiatives, choices your deliverable merely touches. That's when 'quick question' has quietly become 'ongoing advisor,' and the cleanest signal is volume — one note is a courtesy, a recurring rhythm of them is a service.

What to do next

Respond warmly but reframe the relationship, because the goal is to convert a freebie into either a clear courtesy or a paid arrangement — not to seem cold. For a one-off question tied to your delivered work, just answer it; protecting the relationship is worth one reply. When the pattern repeats, name it kindly: 'I love that you keep me in the loop — this is exactly the kind of ongoing thinking I do on a retainer or call basis, want me to set that up?' That sentence does two things: it flatters the client and it draws the line. Offer concrete structures so the ask has a home — an hourly advisory rate, a monthly retainer, or a per-call fee. If the client balks, that itself is clarifying: it tells you they valued the advice precisely because it was free. Going forward, write a short support-window clause into your contracts so the end of free help is a date, not an awkward improvisation.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

It's just a quick email here and there. Am I really supposed to charge for that?+

A single quick email, no — answering one short question keeps a relationship healthy and costs you almost nothing. The thing to watch is the rhythm. When quick emails become a standing pattern, each one cheap but the stream constant, you've drifted into providing ongoing advisory work without a fee or a boundary. The fix isn't to start billing for individual notes; it's to notice the pattern and offer a structure — a retainer or call rate — that gives the steady stream of questions a proper, paid home.

How do I start charging for advice I've been giving away for months?+

Reset the relationship rather than retroactively bill it. Don't try to invoice for past help — that reads as a bait-and-switch and damages trust. Instead, mark a clean forward line: thank them for keeping you involved, say the ongoing thinking has grown into something worth structuring, and propose a retainer or advisory rate from here on. Framing it as recognizing the value of what's been happening — rather than as cutting off a freebie — lets the client say yes without feeling they did something wrong by asking.

What if the advice is genuinely about the work I delivered, not new stuff?+

Then the line is how far past delivery you are and how often it's happening. Helping a client understand or adopt what you handed over is a fair part of landing the work, especially right after delivery. But 'about the delivered work' can stretch a long way — months later, repeated calls to interpret or extend a past deliverable are effectively support you're providing unpaid. Use a stated support window to settle it: inside the window, questions about the work are owed; outside it, even work-related counsel is a service worth pricing.

Won't asking to be paid for advice make me look greedy or unhelpful?+

Only if you frame it as cutting them off rather than formalizing something valuable. Clients respect freelancers who know what their expertise is worth, and most are slightly embarrassed to realize they've been getting ongoing counsel for free. Lead with warmth and offer a structure, not a refusal: you're not declining to help, you're making the help reliable and repeatable. The version that looks bad is silently resenting the unpaid stream; the version that builds respect is calmly naming it as the service it is.

The client implies the advice was always part of the deal. How do I respond?+

Go back to the contract's scope. If the agreement named a deliverable and an endpoint without a stated ongoing-advisory component, then continued counsel wasn't part of the deal no matter how it now feels to the client. Say it without litigating: the project covered the work through delivery, and you're glad to keep advising on a retainer or call basis going forward. If the contract genuinely was vague about post-delivery support, treat that as a one-time grace and tighten the clause next time so 'always part of the deal' can't be assumed.

What's a clean way to scope post-delivery support so this doesn't recur?+

Write a support window into the contract with three specifics: how long it lasts, what it covers, and what happens after. For example, two weeks of questions about adopting the deliverable, included; anything beyond that billed at your advisory rate. That single clause converts a vague open door into a defined service with a closing date, so the end of free help arrives as a contract term rather than an awkward conversation you have to invent. Clients adopt the work faster when they know the support window is finite, too.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide