When the Client Adds a Team Member Mid-Project and Your Scope Doubles

It starts with a friendly email. "We're looping in our marketing director, just to keep her in the loop." That sentence has cost me more unbilled hours than any other in my career.

One new stakeholder means new opinions, new revision requests, new onboarding conversations, and a whole new person who needs to be caught up on decisions that were already made. The scope does not double overnight. It doubles in two-hour increments over three weeks, and by the time you notice, the invoice is already wrong.

Why This Specific Situation Is So Hard to Catch

You are not doing dramatically different work. You are doing slightly more of the same work. Extra calls. Extra feedback rounds. Extra explanations. None of it feels like scope creep in the moment because each individual piece feels minor.

But minor things tracked are minor things billed. Minor things not tracked are donations.

The only way to see this happening in real time is to have a timer running when you are doing the work. Not a memory of the work. Not a rough estimate at the end of the week. A running record that shows you, by task and by client, where the hours actually went.

What to Do When the New Stakeholder Gets Introduced

Do not wait to see how it plays out. The moment you see that email, log the date. Open your time tracker and create a note. Something like: new contact added to project, monitoring hours from this point.

Then start tracking every interaction that would not have happened without this person. The call to get them up to speed. The revised document you sent because they had not seen the original direction. The extra revision round because their feedback conflicted with what the original client already approved.

This is not about being difficult. It is about having data when the conversation comes.

The Conversation You Will Need to Have

At some point, if the hours stack up, you will need to go back to your client and explain that the project scope shifted. That conversation is miserable without data and straightforward with it.

"Since we added your marketing director to the project three weeks ago, I have logged an additional eleven hours that were not part of the original scope. I want to talk about how to handle that before I send the next invoice."

That sentence works because it is specific. It has a date, an hour count, and a reason. You are not guessing. You are not complaining. You are reporting.

If you try to have that conversation without time data, you are going to estimate, the client is going to push back, and you are going to cave. Every time.

How to Protect the Project Going Forward

If a new stakeholder is joining, it is fair to send a short note about what that means for scope. Not aggressive, just clear. "Happy to include her in the process. I want to flag that additional review rounds and catch-up time may add to the project hours. I'll keep you updated as we go."

Then do exactly that. Send a mid-project time update before the invoice. Something simple: here is where we are on hours, here is what is left, here is what the current count looks like against the original estimate.

Clients who feel informed rarely dispute invoices. Clients who feel surprised almost always do.

The Habit That Prevents All of This

Start the timer before the call. Stop it when the call ends. Do not batch-enter time at the end of the day based on what you think you did. The new-stakeholder situation is precisely the type of slow drift that disappears in a rough estimate but shows up clearly in a logged record.

Your time tracker is not just for invoicing. It is for seeing the project clearly while there is still time to do something about it.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots