# Scope creep starts in meetings: the phrases to catch and what to say

> For freelance developers and consultants on fixed-scope or fixed-price work who meet clients on Google Meet or Microsoft Teams: the phrases that signal new scope, what to say on the call without refusing, how to write the request down, a change request email to send the same day, and the habits that stop it starting. Ends with how TrackHeros helps you find what was agreed.

Canonical: https://trackheros.com/blog/scope-creep-starts-in-meetings/  
Author: Sami Kanafani  
Updated: 2026-10-22

**In short:** Scope creep usually arrives as a casual sentence in a meeting: 'while you're in there', 'it should be quick', 'we assumed it would'. Acknowledge it on the call without agreeing, write down the client's exact words, and send a change request the same day with its effect on cost and dates. TrackHeros records Google Meet and Microsoft Teams calls so you can find what was actually agreed.

Scope creep starts in meetings far more often than in email. A client mentions something in passing, you say "should be fine", nobody writes it down, and three weeks later it is something you promised. This guide is for freelance developers and consultants on fixed-scope or fixed-price work who meet clients on Google Meet or Microsoft Teams. It covers the phrases that signal new scope, what to say on the call, how to write it down, and a change request email to send the same day.

## Why does scope creep start in meetings rather than in email?

Because a spoken request is casual, friendly and agreed with a nod, and nobody writes it down. An email asking for a new feature is visible and gets a considered reply. The same request made out loud at the end of a good demo gets "sure, I'll take a look".

Meetings also put you at your most agreeable. The client is pleased, the call is running over, and saying "that's out of scope" feels like spoiling the mood. So you say something vague, the client hears yes, and the gap between what each of you remembers starts there. Three weeks later neither of you can quote the sentence, and memory decides.

## Which phrases signal new scope?

A small set of sentences carries most new work into a project. Learn to hear them, because the client does not think of them as requests.

| What the client says                       | What it usually means                           | What to ask                                                  |
| ------------------------------------------ | ----------------------------------------------- | ------------------------------------------------------------ |
| "While you're in there, could you…"        | New work next to the current work               | "Is that instead of something planned, or as well as?"       |
| "It should be quick to…"                   | The client's estimate replacing yours           | "Let me look at it properly and send you a number."          |
| "We assumed it would…"                     | A requirement nobody stated                     | "Can you show me where that came up? I'll check the spec."   |
| "Can it also…"                             | A new feature                                   | "What would it be used for, and by when?"                    |
| "Just a small tweak to…"                   | A change to work already accepted               | "Was the version we accepted wrong, or is this an addition?" |
| "Our director saw it and wants…"           | A new stakeholder with new requirements         | "Should they join the next review so I hear it directly?"    |
| "For phase one we really need…"            | Phase two being pulled forward                  | "What should move out to make room?"                         |
| "Could you join our call with the vendor?" | A new kind of work: meetings, support, advice   | "Happy to. Shall I bill that time separately?"               |
| "Let's not worry about the budget for now" | The budget question being postponed, not solved | "I'll send the estimate anyway, so it's in front of you."    |

Your own phrases count too. "Sure, no problem", "I'll take a look" and "that should be easy" are the three most expensive sentences a freelancer says on a call. Each one is heard as a yes. Whether meetings themselves are billable is its own question; [should freelancers charge for meetings](/blog/should-freelancers-charge-for-meetings/) covers it.

## What do you say on the call?

Acknowledge the idea, label it as new, and move the decision into writing. You are not refusing anything; you are making sure it is decided with the cost in view.

Scripts that work, word for word:

- **The default:** "That makes sense. It's outside what we scoped, so let me write up what it would take and send it today."
- **When it might replace something:** "Do you want it instead of something already planned, or as well as?"
- **When pressed for a number:** "I don't want to guess on the call and be wrong. You'll have a number by tomorrow."
- **When it is essential for a date:** "If it has to be in the launch, let's look at what moves to make room. I'll send two options."
- **When you choose to absorb it:** "I'll do this one inside the current work. I'll note it in the recap so we both know it was extra."
- **When it is a change to accepted work:** "The version we accepted on the 14th did it this way. Changing it is fine; it's a change rather than a fix, so I'll estimate it."

Then read it back before the call ends, with the other actions: "Two new requests today: emailing the export to your accountant, and the CSV import. I'll send both with estimates by tomorrow." That sentence is where the client learns that both were noticed, and that neither was agreed.

## How do you write a scope change down?

Keep requests separate from action items, in the client's exact words, with who asked and when. An action is something agreed; a request is something asked. Mixing them in one list is how a request turns into an obligation.

A request log can be a section of each meeting's notes or one table per client:

| #   | Date       | Asked by | Exact words                                               | Said on the call         | Status                  |
| --- | ---------- | -------- | --------------------------------------------------------- | ------------------------ | ----------------------- |
| 3   | 22 October | Priya    | "Could it also email the file to our accountant?"         | Estimate by 23 October   | Estimate sent           |
| 4   | 22 October | Tom      | "We assumed the import would take the old CSV format too" | Will check the spec      | Not in spec; estimating |
| 5   | 29 October | Priya    | "Just move the logo to the left"                          | Absorbed, noted as extra | Done, no charge         |

Number the requests. "Change request 4" is easier to refer to in a later call than "the CSV thing", and a running number tells the client, without any comment from you, how many there have been.

## What should a change request email say?

What was asked, why it is new, what it would take, and the options. Send it the same day, while the call is fresh, and keep it short enough to read on a phone.

```text
Subject: Change request 3: email export to accountant ([Client] [project])

Hi Priya,

In today's call you asked whether the export could also email the file
to your accountant. That isn't in the current scope: the agreed export
is a download (proposal, section 3; accepted at the review on 22 October).

What it involves: an email setting per account, sending through your
mail service, and a log of what was sent.

Effect: about three days of work. On its own it moves the 7 November
milestone to 12 November.

Options
1. Add it now, and the milestone moves to 12 November.
2. Add it now and drop the rounding report from phase one; the date holds.
3. Do it after launch as a separate piece of work.

Which would you like? I'll carry on with the current plan until I hear
from you.
```

Give a number, not "a bit of extra time". Give options, so the reply is a choice rather than a negotiation. And say what happens if they do not answer: work continues on the agreed plan. Your contract may say how changes are agreed and signed; follow it.

## How do you stop scope creep before it starts?

Most of the protection is set up in earlier meetings:

- **An out-of-scope list** in the proposal and in the [kickoff recap](/blog/client-kickoff-meeting-agenda/), so "not in this phase" was written down by both sides at the start.
- **Testable requirements**, with an ambiguities list, so "we assumed" has something to be checked against; see [requirements gathering meetings](/blog/requirements-gathering-meeting/).
- **Explicit acceptance** at each [sprint review](/blog/sprint-review-with-a-client/), so "just a small tweak" can be told apart from a fix.
- **A [decision log](/blog/decision-log-for-client-projects/)**, so a decision made in month one is still findable in month four.
- **A standing requests item** in the [weekly status call](/blog/weekly-client-status-meeting/), so new requests have a place to go other than a passing remark.

## How does TrackHeros help with scope creep?

TrackHeros is an AI meeting notetaker that records client calls on Google Meet and Microsoft Teams and files them under the client. It does not label anything as scope creep; it keeps the record so you can. Each meeting's notes have a decisions section and action items with the owner as heard and the due date as it was said, resolved to a date.

When a request comes back as "you said you'd do it", open the client and ask "when did they first ask about emailing the export, and what did I say?" The answer comes only from that client's meetings, cited to who said it and when, and the citation plays the recording from that moment. Answers export as Markdown, PDF or email-ready HTML, so the cited version can go into the change request itself. Nothing is emailed to your client for you. More at [ask your meetings](/features/ask-your-meetings/), [meeting minutes](/features/meeting-minutes/) and [client isolation](/features/client-isolation/).

## Frequently asked

**How do I tell a client something is out of scope without damaging the relationship?**

Acknowledge the idea first, label it plainly, and move the decision to writing: 'Good idea. It's outside what we scoped, so I'll send you what it would take today.' Offer options rather than a refusal. Clients rarely mind a change request; they mind a surprise invoice.

**Should I ever do small extras for free?**

Yes, deliberately and in writing. Say on the call that you will absorb it, then note it in the recap as extra work done at no charge. A favour that nobody recorded becomes part of the scope; a favour that was recorded stays a favour.

**What if the client says the work was always in scope?**

Go to the written record: the proposal, the kickoff recap, the minutes of the meeting where it came up. If the record is clear, point to it calmly. If it is genuinely ambiguous, say so and agree a split rather than arguing about memory.

**Is a change request the same as a contract variation?**

That depends on your contract, which may say exactly how changes are agreed and signed. Follow what it says. A change request email is a practical record of what was asked and what you proposed; whether it changes the contract is a question for the contract itself, not for this guide.

---

TrackHeros is in early access: https://trackheros.com/#early-access