A reader asks: my Big 4 engagement partner keeps moving the goalposts

The question (paraphrased from r/Big4):

I’m a first-year on an audit engagement and the partner has changed what he wants three times in the last week. Monday it was a clean workpaper. Wednesday he wanted a client-ready summary. Friday he asked for a deck for the closing meeting. Every version is the input to the next one, and I keep getting feedback that I’m “not quite there.” Am I missing something, or is this just what the job is?

Both. This is what the job is, and you are missing something. The good news is the thing you are missing is a technique, not a personality trait. You can install it in a week.

What’s actually happening

The partner isn’t moving goalposts to mess with you. The partner is refining what he needs as he gets closer to the moment he has to use it. On Monday, he was thinking “I need documentation for the file.” On Wednesday, as the client meeting got closer, he started thinking “I need something I can walk the client through.” By Friday, reality set in: “I need a deck because the CFO wants to see it in color.”

Every version is the same work, scoped up one layer. What feels like chaos to you is a partner thinking through his own deliverable, in real time, using your output as the draft.

Why it feels bad from where you’re sitting

Because you are the one redoing the document each time. The partner gets to say “actually, let’s also…” and move on. You go back and rebuild.

This is unfair in the moment and completely reasonable on the scale of a career. Your job, at your level, is to be the person who absorbs that iteration without friction. The alternative — a junior who pushes back on every change — gets dropped quickly.

What you can do is reduce how often this happens by anticipating where he’s going.

The two-question check-in

The technique that would change your week is a 90-second conversation at the start of each deliverable. Two questions:

1. “Who’s the end audience for this?” Internal file? Senior manager review? The client? The CFO?
2. “What decision or action does this enable?” Is it documentation, a judgment call, a discussion in a meeting, or a handover?

Those two answers change everything about what “done” looks like. A document for the file is a workpaper with ticks and notes. A document for a client discussion is a one-pager with the three things the client actually needs to know. Same facts, different objects.

Ask both questions at the start, and watch how much less rework you do.

The “sketch the endpoint” move

When you get a new task, before you do any real work, write down:

“If this goes well, the thing that lands on the partner’s desk is [X], it’s [Y] pages long, and the three things he’ll want to see when he opens it are [A], [B], [C].”

Then take it to him. Ninety seconds. “Before I go build this, can I sanity-check the shape? I was going to give you a two-page exec summary with the three numbers from the variance analysis on the first page. Make sense?”

He’ll either say yes or course-correct you in ten seconds instead of four hours. You’re cheap to course-correct early, expensive late.

This is the most underused move in the first-year toolkit. Seniors notice the people who do it.

What “not quite there” actually means

When a partner tells you a deliverable is “not quite there,” it’s rarely the technical work. Seniors would catch technical errors before it got to the partner. What’s “not quite there” is usually one of three things:

1. Format / length. Too dense, too long, the wrong object for the audience.
2. Framing. The first two sentences aren’t telling me what matters.
3. Judgment. You documented what you found but didn’t tell me what to do about it.

Next time you hear “not quite there,” ask: “is it the shape, the framing, or the judgment?” He’ll tell you. Once you know which of the three, you can fix it in ten minutes instead of redoing the whole thing.

The long game

This is an audit-specific version of a universal corporate pattern: work cascades. The person above you restates your work for the person above them. What you produce on Monday is raw material for what they need by Friday. The people who get promoted fastest are the ones who think one step ahead — who produce not just what was asked for, but the object the next audience will use.

—

A year from now, your first-year self won’t recognize the person you are when you’ve internalized this. The shift from “I executed what they asked for” to “I produced what they actually needed” is the entire arc from senior associate to manager. The partner doesn’t think he’s training you for that shift. He is.

For the weekly rhythm that exposes these misfires early, see the status update template. For the broader 1:1 structure where priority calls get made, see the Manager 1:1 agenda.

—

If you have a question like this, send it in. Anonymity guaranteed.