Key person risk

What happens to your month end close if one person quits?

Key person risk hides in the month end close: tasks only one person can do. How to find single-owner tasks and spread the know-how before it walks out.

Beaks · · 5 min read
Hands writing in a notebook beside a calculator and printed reports on a desk

Every finance team has a person whose resignation letter would quietly break the month end close. Not the whole close, just one part of it. The accruals spreadsheet with the formula nobody else understands. The intercompany recharge that only reconciles if you know which supplier invoices to strip out first. The client report that goes out on the fifth working day because one person knows where every number comes from. That is key person risk, and in most accounting firms and finance teams it sits inside the close, where it hurts most.

The usual response is to hope that someone will figure it out. Often they do, in the second week of the following month, with a late report, an unhappy client and a senior person doing a junior job at nine in the evening.

Key person risk is about tasks, not people

The phrase sounds like it is about people, which is unhelpful and a little unkind. Nobody chose to become a single point of failure. It happened because they were good at a task, did it every month, and nobody ever had a reason to learn it alongside them.

The useful unit is the task. A firm does not have key people so much as it has single-owner tasks: recurring pieces of work that exactly one person can do today. Count those and you have a real measure of the risk. It is also a much easier conversation to have with the team, because it is about the work, not about anyone's value.

Where single-owner tasks hide in the close

Take a hypothetical 30 person outsourced finance firm running monthly closes for 40 clients. If you walked through its close calendar task by task, the single-owner work would tend to cluster in a few predictable places:

  • The odd bank account. Most reconciliations are routine, but one client has a foreign currency account or a payment platform feed that only one person knows how to match.
  • Judgement calls dressed up as routine. Accruals, prepayments and provisions where the rule is "use last month's approach, adjusted for what you know", and only one person knows what to adjust for.
  • Spreadsheets with history. Workbooks built years ago, with hidden tabs and hard coded fixes, that produce the right answer as long as the right person runs them.
  • Client specific quirks. The client who wants the management pack in a particular order, or whose cost centres were reorganised in 2023 and still need mapping by hand.
  • Quarterly and annual tasks. The VAT return adjustments, the year end checks. They run so rarely that only the person who did it last time remembers how.

None of these look dangerous on a normal Tuesday. They become dangerous when the owner is ill in close week, goes on parental leave, or moves on, which good people eventually do.

Why "write it down" has not fixed this

Most firms have tried the obvious fix. Someone spends an afternoon writing up their process, it goes in a shared folder, and within a few months it no longer matches what they actually do.

There are three reasons this keeps failing:

  1. Writing documentation is a separate job on top of the real one, so it happens once, in a burst, and never again.
  2. The documentation is not attached to the work. Nobody opens the shared folder when they are doing the task, so nobody notices it is out of date.
  3. Nobody knows which tasks need it most. Without a list of single-owner tasks, the effort goes to whatever the most conscientious person decided to write up, not to where the risk is.

How to find and close the risk

The fix is less dramatic than a process mapping project. It has three parts, and they work best in this order.

1. List the close, task by task

Write down every recurring task in the close: what it is, when it runs ("third working day after month end"), and who does it. If you have never done this, our earlier post on why most firms have no list of what their team does explains why it matters and how to start. You cannot measure key person risk without it.

2. Count the names next to each task

For every task, ask one question: if the usual person were off tomorrow, who else could do this to the same standard, without phoning them? Write the names down. Be honest; "they could probably work it out" counts as no one.

The tasks with one name are your single-owner tasks. As an illustrative example, if the hypothetical firm above found 60 single-owner tasks out of 400 in its close, that 15 percent is the number to bring down, and it is a number you can track month by month.

3. Capture the know-how while the work happens

For each single-owner task, starting with the ones that would cause the most damage if they slipped, have the owner record the task once while they actually do it. Then attach that manual to the task itself, so the next person finds it where the work is, not in a folder. A second person then does the task once with the manual, with the owner checking. When they can do it alone, the task has two names.

This is the part worth getting right, because the captured know-how does more than cover for absence. The same manual that lets a colleague step in is what any new hire, or later an AI agent drafting the work for a person to approve, would need to run the task. Know-how that lives in one head cannot move to anyone. Know-how that is written down, next to the task, can move to whoever the firm chooses.

Make it a promotion, not an audit

How you frame this matters. If the team hears "we are documenting your job in case you leave", the manuals will be thin and the list will be incomplete. People protect what they think is being taken from them.

The better framing is also the true one. Spreading the routine half of a skilled person's work frees them for the work only they can do, takes the pressure off their holidays, and makes them promotable, because a person nobody can cover is a person nobody can move up. Tools like Beaks are built on that idea: capture the recurring work as it happens, show who can do what, and treat the know-how as the team's asset rather than a dependency.

One thing to do this week

Print your close calendar, or open the checklist your team actually uses. Next to every task, write the names of the people who could do it tomorrow without help. Circle every task with one name.

Then pick the three circled tasks that would hurt most if they were late, and ask their owners to record each one the next time they do it. Three tasks this month is a real start, and it is three fewer reasons to dread a resignation letter in close week.

← All posts

Know what your team actually does.

Beaks holds every recurring task, writes the manual as people work, and shows which work is ready for AI.

Request early access

Keep reading