Delegation Wasn't What I Expected

Audit Senior Series #03

For audit seniors who ease up on review because of a junior's reputation

The Question He Didn't Have a Good Answer To

Have you ever given a junior a lighter review because other seniors said they were sharp, only to have something come back to bite you? Read on to find out where the line is between healthy delegation and stepping back too far.

Jacob was two weeks into a construction audit when the partner called him into a meeting room, laptop already open.

Partner: The financial ratios in this risk assessment look off. A few areas we'd normally expect to see flagged as risk… aren't. Did you go through this yourself?

Jacob felt his stomach drop when his partner asked that question. No, he hadn't gone through it himself, not properly. Zane, a second-year junior on the job, had prepared it.

Jacob: Zane worked on this one. I gave it a lighter review than usual, to be honest. He's known among the seniors as one of the fastest, sharpest juniors around, and he asked for the work himself. I didn't think I needed to sit over his shoulder.

Partner: Well, something's not adding up. And having a capable junior does not mean you can let go, it just means your review can be more efficient. Can you get back to me by tomorrow with a revised assessment?

Jacob promised his partner a revised assessment. But he was already hit by guilt and embarrassment. That night, he went through Zane's file line by line and revised whatever he needed to revise.

The issues were not hard to spot when he actually reviewed Zane's work more carefully. Zane had used an AI tool to speed up the analytics, something a lot of juniors were doing now. That itself is not wrong. What is wrong is that Zane had worked confidently using inputs he did not verify, and nothing about the output gave that away. Because the inputs were wrong, the risks that should have been flagged never got flagged. Nobody had lied. Nobody had cut corners on purpose. But the fact remained that the work produced was sub-standard and Jacob signed that off as the reviewer.

Two Gaps, Not One

Jacob's initial feelings of guilt and embarrassment later evolved to something closer to betrayal, and right behind it, a colder thought he didn't like having: had he made a mistake trusting Zane with the work?

He had said yes to Zane partly because Zane had asked for the work himself, and Jacob liked that. Initiative was supposed to be a good sign. He had also said yes because of what he had heard from other seniors about how capable Zane was. So, in Jacob's mind, Zane would not require the usual hand-holding and this would help lighten his workload. But the thing is that Jacob had never worked with Zane before. He had been relying on what other seniors said about Zane, not on anything he had seen for himself.

That realisation was uncomfortable in a specific way. Jacob had prided himself on being the kind of senior who trusted his juniors with real work, not the kind who hovered over every line because he couldn't let go. Now he was sitting with the uncomfortable possibility that what he had called trust had just been relief, relief at not having to review something closely for once. It's a hard thing to admit to yourself that the thing you were proud of might have just been the easier option wearing a nicer name.

Zane's part in this was real too, and it didn't erase Jacob's part, or the other way around. Zane had been careless. Just not in the way carelessness usually looks. He hadn't hidden that he'd used AI. But he'd treated a confident-looking output as though it were a finished piece of work, not something that still needed checking. A number he'd calculated by hand would probably have earned a second look out of habit. A number handed to him instantly by a tool, polished and convincing, didn't invite the same level of scepticism. He was doing what a lot of people do when something looks finished: he believed it.

What made this sting more than an ordinary review miss was that Jacob's review instincts weren't built for this. He knew how to spot a rushed section, copy-and-paste documentation, incorrect formulae, and other things that looked off. But he wasn't prepared for mistakes that were almost invisible because the output looked too polished to question. Nobody had taught him that polished outputs deserved just as much scepticism as messy ones. He hadn't known he needed to be taught that at all.

Sitting With It

The rework itself wasn't the hard part. Re-running the numbers, going back through the file properly, that was just hours. What Jacob couldn't shake was the partner's question, still sitting in his head long after the meeting: did you go through this yourself?

It wasn't really a question about Zane. It was a question about him, about whether he could be trusted with people under him yet. And underneath that, a more specific worry he couldn't quite shake: would this partner still take his sign-off at face value, or would every file with his name on it now get a second look it hadn't needed before? That kind of trust is slow to build and quick to lose, and Jacob had no idea which side of that line he was now on. He thought about the other seniors in the firm, the ones who always seemed to have everything under control, and wondered if any of them had ever sat exactly where he was sitting now, quietly working out how much damage one missed review had done to people's trust in their judgement.

There wasn't really anyone to say this to. He was supposed to be the one people came to when something went wrong, not the other way around. So he sat with it alone for a night, the way a lot of these things get sat with, before doing anything about it.

What Jacob Did Differently After

The next morning, Jacob didn't start with Zane. He started with himself.

He admitted, first just to himself, that he'd borrowed his confidence in Zane from other people's opinions instead of building it through his own judgement. That wasn't a mistake he could undo on this job, but it was one he could stop making on the next one. Trust in a junior, he decided, wasn't something you borrowed from other people's opinions. It was something you built by watching them work.

He also realised the gap wasn't really about AI at all, not underneath it. It was about a question he'd never thought to ask, of Zane or of himself: how do you know this is right, not just that it looks right? That question didn't exist for him before this. Now it did.

A few weeks later, briefing Zane on a new section, Jacob brought it up plainly, without reopening what had happened.

Jacob: Use whatever helps you work faster. That's not the issue. But before anything comes to me, tell me how you know it's right, not just that it looks right. If you can't answer that yet, it's not ready for review.

Zane: Even when the numbers look fine?

Jacob: Especially then. That's exactly when it's easiest for both of us to stop looking.

Jacob had wanted to give Zane a real chance, and some part of that instinct had been right. Juniors do need seniors willing to hand them something real. But Jacob had learned that giving juniors real responsibility and reviewing their work well enough to still catch what mattered were two different skills. He'd had the first for a while. He was still learning the second.

Your Audit Mentor