Why Your Last Audit Engagement Basically Ran Twice

An audit engagement is the block of weeks an accounting firm spends checking a company's financial records before signing off on them. Every firm has one that went sideways: the plan called for six weeks, and it stretched to nine.

Nobody can point to the exact day it went wrong. It's just a slow drift into overtime that everyone blames on a busy season.

Look back through the timeline and you still won't find the moment. A Provided by Client (PBC) item got re-sent. A file came back late.

None of it looks unusual on its own. Reviewers stay late anyway once things get busy.

Here's what nobody says out loud: that engagement didn't run long. It ran twice.

Meet the Rework Cycle

There's a name for this, and once you know it, you'll spot it on every audit engagement you staff. The Rework Cycle is what happens when one unclear request, made early, forces the team to redo work that should've only happened once.

Say it starts with the PBC list. Someone asks for the "Accounts Payable (AP) aging report." It sounds simple to the person who wrote it.

But the client has three reports that could go by that name: one sorted by vendor, one by invoice age, one pulled straight from the Enterprise Resource Planning (ERP). Nothing tells them which one was meant. They guess, and guess wrong.

Three days pass before anyone notices, because the file just sits in a queue behind six other open items. Now the client has to pull the right report, and the team has to reopen a workpaper it already closed. One vague line means days of second effort.

Where Your Audit Engagement Breaks Down

Trace almost any rework loop back far enough and it starts in the same place: one request that didn't say enough.

• The request goes out short, because most requests are. "Send the depreciation schedule" sounds complete to whoever wrote it, since they already know which year, which format, and which one they mean.
• The client reads that same sentence with none of the context in the room. They don't know which schedule, which period, or which format. So they guess.
• The guess is close, but not right. Nobody catches it, because it looks like an ordinary document in an ordinary queue.
• Days later, a preparer or reviewer finally spots the mismatch. By then, other work has stacked on top of it.
• The request goes back out, spelled out this time. The client redoes their half. The team redoes its half.

Why the Rework Cycle Stays Invisible

Firms don't catch this in real time because the second round of work never looks like a mistake. It looks like a follow-up email, a re-uploaded file, a reviewer comment that says, "please confirm." That's normal on any engagement, so none of it stands out, even to the partner scanning the status report.

It also hides inside the parts of the process everyone already expects to run slow. Clients are always a little behind on PBC items. Review always takes longer than planned.

Add three extra days to something that was already going to take five, and nobody notices the three. They just noticed it took eight days, the same as most years.

By the time the engagement closes, the rework is baked into the actuals. It never shows up as its own line. It just shows up as a number bigger than the budget, and everyone moves on to the next engagement without asking why.

The Takeaway

The Rework Cycle starts with one unclear sentence, sent before anyone thinks twice about it. It ends with an audit engagement that ran twice. Once you know what to look for, you'll see it everywhere.

Want to see what this actually costs a firm over a full season? See the full cost of rework cycle breakdown.