Three weeks into a project, a director who wasn't in any of the earlier calls gets looped in — and immediately has notes on the direction that was formally approved two rounds ago. From the freelancer's side, this can feel disorienting: the work was signed off, and now it isn't, through no failure of process on your part. From the new stakeholder's side, they're often just encountering the work for the first time and reacting honestly to it.
It's worth knowing upfront that this isn't a sign anything went wrong. It's closer to the statistically expected shape of how organizations actually make decisions above a certain size.
The research that reframes this entire situation
Analyst firm Gartner's widely-cited research on B2B purchasing found that a typical buying group for a complex decision includes somewhere between 6 and 10 people — not one decision-maker with a rubber stamp, but a genuine committee, each member entering with their own priorities and often their own independent research they haven't yet shared with the group. Forrester's separate research puts the average B2B purchase at 13 stakeholders, with the large majority of decisions crossing more than one department.
This research is drawn from enterprise software and B2B procurement specifically, not freelance creative or consulting work — but the underlying organizational dynamic it describes applies by close analogy: any client above a certain size is very unlikely to have a single person making every project decision alone, even when a freelancer only ever talks to one point of contact. The person you've been emailing the whole time is very often what this research calls the champion — an internal advocate who genuinely wants the project to succeed and has real influence, but who structurally, in a meaningful share of organizations, lacks unilateral authority to make a decision fully final without at least the tacit sign-off of others: an economic buyer controlling budget, a technical evaluator checking fit, an executive sponsor weighing broader risk, sometimes a gatekeeper controlling what even reaches the group in the first place.
None of this means your contact was dishonest about their authority, or that anything about your process was wrong. It means the visible, single point of contact freelancers naturally treat as “the client” is often just the most visible node of a larger, mostly invisible decision structure — one that was always going to surface eventually, whether at kickoff or three weeks in.
Why this reframe actually matters, practically
If a new stakeholder rejecting approved work is treated as a rare, unfortunate exception, the natural response is frustration and a search for what went wrong. If it's understood instead as a predictable structural pattern — especially likely on any engagement involving a client organization of meaningful size — the more useful response is to plan for it as a near-certainty from the start, the same way a B2B sales team maps out a buying committee before a deal ever closes, rather than being surprised by it partway through.
There's a specific, useful implication in the “champion” framing worth carrying into how you handle the moment itself: your original contact, the one who approved the work that's now being questioned, is very likely still your ally in this situation, not the source of the problem. Sales research on this dynamic describes champions as needing “ammunition to sell internally” — meaning their job, when a new stakeholder pushes back, isn't to abandon the decision they made, it's to defend it credibly to someone else, which requires material you can help provide rather than a fight you're having with them directly.
How to handle it in the moment
Don't immediately treat it as a new, unscoped revision request. The instinct might be to just start redoing the work — resist that until the situation is clarified, since what's actually needed here is a scoping conversation, not an assumption that the previous approval simply doesn't count.
Give your original contact material to defend the decision, not just a redo. Rather than only asking “so what do you want me to change,” offer your champion something to work with: a short rationale for the original direction, the context behind key decisions, anything that helps them make the case internally before assuming the work itself needs to change. Sometimes a new stakeholder's objection dissolves once they understand reasoning they weren't present for — no rework required at all.
Point to the approval record plainly, without defensiveness, once genuine disagreement is confirmed. “This direction was approved by [name] on [date] — happy to walk [new stakeholder] through the reasoning, or if their feedback means we're revisiting the direction, let's talk about how that affects timeline and scope.” This isn't refusing to engage with the new feedback — it's making clear that revisiting a decision is a different thing than a standard revision.
Get clarity on who has final approval authority going forward. This is the actual structural fix, and it's worth treating as close to inevitable rather than a one-off cleanup: “Given [new stakeholder]'s involved now, can we confirm who has final sign-off from here so we don't run into this again?” A single clear answer prevents the same situation from recurring at the next milestone.
A worked example
A brand consultant gets sign-off on a new visual identity from their primary contact, a marketing director, after two structured revision rounds. Three weeks later, mid-rollout, the CMO — who hadn't been in a single call — sees the new identity for the first time and pushes back hard on the color direction.
The consultant's first instinct is defensive: the work was approved, formally, twice. But rather than leading with “this was already signed off,” they reach out to the marketing director first: “Happy to walk the CMO through the reasoning behind the color direction if that's useful — want me to put together a short rationale doc, or would a quick call work better?” The marketing director, now equipped with a clear, professional explanation rather than having to reconstruct the reasoning from memory in a hallway conversation, uses it in a five-minute conversation with the CMO. The color direction survives unchanged — not because the consultant argued for it directly, but because their actual ally in the situation, the marketing director, had something concrete to defend it with.
Had the CMO remained unconvinced even with that context, the conversation would have shifted to scope and pricing for a genuine direction change — but the first move wasn't rework. It was giving the champion what they needed to make the case themselves, which resolved the situation without any billable work at all.
Whether to charge for the rework
This depends on how the situation is framed, but a reasonable default: if a previously approved decision is being reopened due to a stakeholder the client's organization added, that's closer to a scope change initiated by the client than a normal revision — worth treating similarly to any other out-of-scope request, with a priced option rather than an assumed free redo.
Planning for this before it happens, given how common it actually is
Given research suggesting the average complex B2B decision involves somewhere between 6 and 13 people, asking about decision-making structure at kickoff isn't an overly cautious extra step — it's addressing something closer to a near-certainty for any client past a certain size. A simple version: “Just so I can plan the process well — is this a decision you're making solely, or will others be weighing in at some point?” Most contacts, asked directly and early, will name at least one other person who might get involved later, which is far easier to plan around at the start than to discover mid-project.
Why the approval record matters most in exactly this situation
This is one of the clearest cases where an informal “looks good!” reply is far weaker than a structured record. A vague email thread makes it easy for a new stakeholder to reasonably say “I don't see where this was actually approved” — because, functionally, it might not be clear even to someone reading closely. A specific, dated, named approval entry removes that ambiguity entirely, and it protects the client's own team as much as it protects you: your original contact isn't left in an awkward position trying to convince a colleague that a decision was really made — they have exactly the “ammunition” described above, in a form a skeptical new stakeholder can't easily dismiss.
SwiftSignoff's decision log exists for exactly this — every approval records who took the action and when, visible to anyone with portal access, so a later dispute about whether something was really signed off has a specific answer rather than a debate, and your champion has something concrete to point to internally rather than having to vouch for the decision from memory alone.
Related guideHow to stop scope creep: the stakeholder-multiplication problem on $10K+ projects
FAQ
Should I ask upfront, at kickoff, who has final approval authority?
Yes — given how common multi-stakeholder decision-making actually is even on modest-sized engagements, this is worth treating as a near-certain question to ask rather than an edge case, and the answer sometimes changes the process in ways that are much easier to plan for than to discover midway through.
What if the new stakeholder is clearly correct and the original approval was a mistake?
Worth acknowledging honestly rather than defending the previous decision on principle — but the scope/pricing conversation for the rework still applies, since the redo work is real regardless of who was right.
Is it reasonable to charge the client for a new stakeholder's onboarding time — walking them through prior decisions?
For a brief context conversation, generally not worth charging for. If it turns into a substantial re-presentation of work or a full strategy re-review, that's closer to legitimate scope and worth pricing accordingly.
Does this happen more often in certain types of client organizations?
Generally yes — larger organizations structurally involve more stakeholders in a purchasing or project decision, so a solo freelancer's primary contact is statistically less likely to be the sole decision-maker as the client's organization size grows.
Is my main point of contact usually the actual decision-maker, or someone else on their team?
Often, your day-to-day contact functions as what B2B research calls a “champion” — someone who advocates for the project internally but frequently lacks unilateral authority to make it final on their own. That's precisely why a later-appearing stakeholder with real authority can reopen something the champion believed was settled — it's a structural pattern, not a sign anything was mishandled.
A decision that isn't clearly recorded is a decision that can be argued away later — and your champion needs that record as much as you do.
PricingSee how the decision log protects approved work on the pricing page