Somewhere around week three, a new name shows up in the email thread. A VP who wasn’t at the kickoff. A referral partner the client trusts. A new hire who inherited the account from someone who left. They ask a few questions, then they ask you to change something the original stakeholder already signed off on.
Years ago, I was working on a website project, and three weeks before launch, a new voice started chiming in. He was a new VP, and he basically started the vetting process all over again. Lots of questions that took me away from doing the actual work. He was showing off to his new bosses by making me look bad.
Most freelancers treat this as a normal part of client work. It isn’t. A new stakeholder joining a project after it started is a scope change, the same as a client asking for an extra concept direction or a second round of copy. It should be quoted and billed the same way. The work doesn’t get easier because the person asking for it just met you. It gets harder, and if you don’t say so out loud, you’re the one who eats the difference.
What Does It Mean When a New Stakeholder Joins a Project Mid-Way?
It means someone outside your original scope of reviewers now has enough influence over the project to ask for changes, without having been part of any of the decisions that got the work to where it is. The most common versions: a manager who was cc’d from the start and finally starts reading the thread, a colleague the client brings in “just to get another opinion,” a new hire who inherits the account partway through, or a client’s own client who suddenly wants to weigh in on the deliverable.
Each version looks different, but they all do the same thing to your project. Every decision you and the original stakeholder already made, about direction, tone, structure, priorities, gets reopened for someone who wasn’t there to make it the first time. Your deliverable doesn’t move backward. Their understanding of it does, and closing that gap is real, billable work.
Why Does a New Stakeholder Mid-Project Cost You Money?
It costs you money because every new stakeholder re-opens decisions you thought were closed, and re-opening a decision takes real time even when the final answer doesn’t change. You explain the reasoning again. You produce a comparison of the option they’re now asking about, even though it was already ruled out in week one. Sometimes you redo work that was already approved, because the new person simply prefers something else.
This isn’t a rare inconvenience. Agencies and creative freelancers already run over budget and behind schedule more often than not: in a 2025 PMI-commissioned survey of 130 U.S. marketing and advertising agency professionals, 55% said their campaigns went over budget in the past year and 54% said deadlines slipped. A late-arriving stakeholder rarely gets named as the reason on a post-mortem, but it’s one of the most common ones: the work is functionally done, and then someone new gets a vote on it.
What Is a Named-Approvers Clause?
A named-approvers clause is a line in your contract or statement of work that lists the specific people who can approve deliverables and request revisions on the project. Anyone not on that list, a new manager, a referred colleague, a client’s own client, doesn’t get automatic access to your revision rounds. Their feedback either routes through a named approver who decides whether it’s worth acting on, or it triggers a separate, quoted round of work.
The clause doesn’t stop clients from adding people to a project. It just stops a new name from silently becoming a new source of free revisions. It turns “who’s allowed to weigh in on this” from an assumption everyone’s guessing at into a term you both signed and can point back to.
How Do You Add a Named-Approvers Clause to a Contract or SOW?
Name the actual people, not just their titles, and set the rule that any feedback from outside that list is treated as a new round, not part of the ones you already quoted. A short version works fine in most freelance contracts:
“Deliverables in this project will be reviewed and approved by [Name(s)]. Feedback from other individuals will be incorporated at [Freelancer]’s discretion and, if substantive, billed as an additional revision round at the standard rate.”
That one clause protects two things at once: the rate you set for the project, and the revision budget you built into your quote. Without it, both quietly erode every time someone new joins the thread, the same kind of unbilled drift that shows up when you audit a quarter of invoices against the work you actually did. Put the clause in the SOW, not just the kickoff email. Emails get lost in a thread with six new names on it. Contracts don’t.
What Do You Do When a New Stakeholder Shows Up and You Don’t Have a Clause Yet?
You say something the same day, before you do any work based on their feedback. Send a short, plain note: “Happy to have [Name] involved. Since they weren’t part of our original scoping, I’ll treat their first round of feedback as an additional revision round at [rate]. Let me know if that works before I start.” That’s it. No apology, no long explanation. You’re naming a cost that was already true, just previously invisible.
If I had thought of this years ago, it would have made the launch of that website go so much smoother.
Before you act on anything they’ve asked for, ask the client to bring the new stakeholder up to speed internally: decisions already made, direction already approved, feedback already incorporated. Without that step, a new stakeholder often repeats questions the project already answered weeks ago, and it reads as your work being wrong when it’s really just new to them. A ten-minute internal briefing from the client costs you nothing and prevents a full round of rework on your side.
How Many Free Revision Rounds Should a New Stakeholder Get?
Zero. The revision rounds in your quote were priced for the reviewers who existed when you quoted them, not for whoever gets added to the project later. If the client wants their new hire, their boss, or their referral partner to have real input, that’s reasonable, but it’s additional scope, not a rounding error you absorb to keep things friendly.
This is where a named-approvers clause pays for itself fastest, especially for designers working through revision rounds that were already the tightest part of the budget. A new reviewer asking for “just one small change” rarely stays small once you’re two exchanges deep. Quote it up front, even if it’s a short, low-stakes email instead of a formal change order. The goal isn’t to make it hard for the client to add people. It’s to make sure that when they do, the cost shows up somewhere other than your unpaid time.
Track the new stakeholder’s round the same way you’d track any other task, as its own line, with its own hours. If it’s on the board, it’s on the invoice, and a stakeholder who joined in week three is easiest to bill fairly when their feedback was logged as its own piece of work from the moment it landed, not folded quietly into hours you’d already spent.
Had I done this on the web project, it would have saved everyone a lot of headaches.
Start a 30-day free trial. No credit card required.
Frequently Asked Questions
What is a named-approvers clause?
A named-approvers clause is a line in your contract or SOW that lists the specific people who can approve deliverables and request revisions on a project. Anyone not named on that list doesn’t get automatic access to your revision rounds. Their feedback either routes through a named approver or triggers a separate, paid round. The clause turns an assumption about who’s allowed to weigh in into a term you can point back to.
How do you bill a client when a new stakeholder joins mid-project?
Treat the new stakeholder’s first round of feedback as an additional revision round, not an extension of the current scope. Send a short note the same day they join: who they are, what they’re reviewing, and that their input will be billed at your standard rate. Quote it before you start the work, not after. If your contract already has a named-approvers clause, you’re enforcing a term the client agreed to. If it doesn’t, it’s still a reasonable ask.
Can you make a client’s new stakeholder catch up before they review your work?
Yes, and it protects both of you. Ask the client to brief the new stakeholder internally on decisions already made and feedback already incorporated, before that person reviews your latest draft. Without that step, a new stakeholder often repeats questions the project already answered, which can read as your work being wrong when it’s actually just new to them. A short internal briefing from the client costs nothing and prevents a full round of rework.
What if the client won’t agree to a named-approvers clause?
Some clients resist naming approvers, especially when their own internal structure is unsettled. If they won’t put it in writing, fall back to a lighter version: state in your proposal or kickoff email that your quoted revision rounds assume one consistent reviewer, and that adding a stakeholder after kickoff will be billed as an additional round. That’s a defensible position to hold even without a formal clause, and it gives you something to reference the first time it happens.