are extra meetings out of scope?
Yes — meeting time past the checkpoints your contract scoped is billable work, even though it doesn't produce a deliverable. The exception is a retainer or a contract that priced in open-ended availability rather than a fixed set of reviews.
Why this answer
Meetings feel like overhead, so freelancers routinely give them away — and that's exactly how a project's margin quietly disappears. Your time is the asset you sell, and an hour on a call is an hour not spent producing the work or earning from another client. A fixed-fee project is priced around a specific amount of synchronous contact: a kickoff, a review or two, a handoff. When a client converts that into a standing weekly call, they've changed the shape of the engagement from 'deliver this thing' to 'be continuously available,' which is a fundamentally different and more expensive arrangement. The deliverables haven't grown, but the cost of producing them has, because every recurring call carries setup, context-switching, and follow-up time around it. Standing meetings are scope creep that hides in your calendar instead of your task list.
When the answer flips
The verdict flips to In Scope when you're on a retainer that explicitly buys ongoing availability, or when the contract priced for a named cadence of meetings and the client is staying within it. It also flips if the extra meeting is genuinely yours to fix — if you delivered something unclear and the call is to resolve your own ambiguity, that's part of delivering correctly, not new scope. A single ad-hoc call to unblock the work is usually absorbable goodwill; the problem is recurrence. And if the meetings are short, infrequent, and clearly moving the work forward rather than rehashing it, the relationship value often outweighs the marginal cost of billing them.
What to do next
Name the pattern without making it personal: 'We scoped two review calls into this project, and we've moved to a weekly standing call — happy to keep that cadence, here's how I handle ongoing meeting time.' Offer a clean structure rather than nickel-and-diming individual calls: a small monthly meeting allowance baked into a retainer, or a per-call rate for anything beyond the scoped reviews. If the meetings signal the client actually needs ongoing support, propose converting to a retainer — that's usually the right answer and a better deal for both sides. Cap the scoped calls in your next contract and state what additional meeting time costs.
Frequently asked questions
It's just a 30-minute call — is it really worth charging for?
A 30-minute call rarely costs 30 minutes. There's the prep, the context-switch out of deep work, and the follow-up notes or actions afterward, which often doubles the real cost. One such call is absorbable; a recurring one every week adds up to a meaningful share of your billable time over a project. The issue is the standing cadence, not any single call.
How do I charge for meeting time without seeming petty?
Don't itemize individual calls — that's what reads as petty. Instead, set a structure: a meeting allowance inside a retainer, or a flat per-session rate for calls beyond the scoped reviews. Presenting it as a clear policy rather than a reaction to one specific call keeps the conversation professional and predictable.
What if the client schedules calls and I just don't attend the extras?
Declining silently damages the relationship and reads as unreliable. Better to address the cadence directly, explain that meeting time beyond the scoped reviews is billable or belongs in a retainer, and offer the client a clear choice. Most clients would rather pay for your time than lose your engagement, but they need to be told it has a cost.
Should standing meetings push me toward a retainer?
Often, yes. Recurring calls usually signal the client wants ongoing access, not just a one-time deliverable. A retainer prices that access correctly and stabilizes your income, while giving the client the availability they're clearly after. When meetings keep multiplying on a fixed-fee project, proposing a retainer is frequently the cleanest fix.
Do discovery and kickoff calls count against the meeting scope?
They should be named explicitly in your scope so there's no confusion. Kickoff and discovery are typically expected and priced in. The calls that cause disputes are the unplanned recurring ones that appear mid-project. List the included meetings by name and number so everyone knows where the line sits.
How do I scope meetings in the contract to avoid this?
State the included meetings explicitly: number, length, and purpose — for example, one kickoff, two review calls, one handoff. Then add a line that additional synchronous time is billed at a stated rate or handled via retainer. That turns a creeping calendar problem into a defined, priced item upfront.
Related reading
- The full guide
The scope creep guide for freelancers
How to spot scope creep, why clients do it, what it costs you, and how to respond professionally.
- Scenario
Is a second round of stakeholder review in scope?
Ambiguous — a new stakeholder reviewing already-approved work usually introduces new feedback that exceeds the original scope, but the revi…
- Scenario
Is a client-requested training session out of scope?
Yes — a structured training session is almost always out of scope. A handoff call to explain deliverables is usually in scope; a training s…
- Clause guide
What a deliverables clause should include in freelance contracts
A strong deliverables clause names each artifact with a format, a quantity, and — critically — an exclusion list. If it's not named, it's n…
- Scenario
Is a rush deadline out of scope?
Yes — a mid-project deadline acceleration is out of scope unless your contract explicitly accommodated shifting timelines. The work itself…
- Scenario
is a competitor analysis out of scope?
Yes — a competitor analysis or market audit added partway through is a distinct research deliverable outside your original scope. The excep…
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.