People talk about AI and redundancy as though one leads straight to the other. The honest answer is narrower. AI takes hours out of tasks. What you do with those hours is a management decision, not a technical one. The software doesn’t make that call, and it can’t tell you what the right one is.

Your team is already asking the question privately, so it deserves a proper answer rather than silence. That answer gets easier to give once you can describe what changes inside a role, task by task, and what carries on exactly as it did before.

The honest answer about AI and redundancy

Start with what the technology does. It shortens tasks that repeat and follow a pattern. Sorting an inbox is one. Drafting the first version of a letter is another. So is pulling figures out of a supplier invoice. It doesn’t remove a role, because a role is a bundle of tasks, judgement and relationships.

So the hours come back to you, and you decide where they go. You can take the saving as headcount. You can push more work through the same team. Or you can hand the time back to the work nobody ever finishes properly. All three are legitimate choices, and only one of them involves redundancy.

The choice that isn’t legitimate is pretending there was no choice.

Hours come off tasks, not off roles

That distinction between a task and a role matters more than it sounds, because savings arrive scattered rather than stacked. A saving of 4 hours a week across 3 people is not a vacancy. It is 4 hours sitting in 3 different diaries.

AI and redundancy only become the same conversation when you deliberately gather those hours into one place. That gathering is a decision you make, and you can make it well or badly, but you cannot blame it on a tool.

Before you gather anything, check the saving is real. A figure somebody feels is different from a figure somebody has counted, which is why measuring a soft win properly comes first.

What actually shrinks, and what stays

Once you trust the saving, look at a single role and split it in two. Write out the tasks in the job as they really happen this month, not as the job description has them. Do it on paper with the person who holds the role. They know which parts of the week eat the time, and the exercise itself lowers the temperature.

The tasks that shrink share a shape. They repeat, they run on text or numbers, and a rule or a template governs how they turn out. Drafting a standard response, formatting a report, and checking a purchase order against a delivery note all sit in that group.

The tasks that stay involve a decision with consequences, or a relationship somebody has built. Some of them depend on knowledge that lives in one person’s head and nowhere else. Most roles come out of this exercise looking thinner in the middle and unchanged at both ends.

The new work that appears

That split leaves something out, because AI adds work as well as taking it away. Somebody has to read the output, compare it against the source, and decide whether it goes out.

Checking is real work with a real time cost. It tends to land on your most experienced person, who is usually the one you can least afford to load up. So write the checking step into the role rather than treating it as a favour. It also needs an owner, which is why the question of who owns the job turns up so early.

Count that new time against the hours saved. A job that saves 5 hours and creates 2 hours of checking has saved 3. Quote that figure to your team, because it is the one that holds up.

Have the conversation before the rumour

With the change described in that much detail, you can talk about it openly, and you should do so early. People spot a new tool within days, and they draw conclusions long before you announce anything.

In the absence of an explanation they write their own, and the version they write is worse than the truth almost every time. A quiet team is rarely a relaxed team.

Keep the conversation specific. Name the tasks the tool now handles, name the checking it creates, and name the person who owns it. Vague reassurance invites more suspicion than a plain description of the work.

Pick the moment with some care. A meeting where you explain the tool and take questions on the spot works better than an email. People forward emails to each other with their own commentary attached.

What do you say when you haven’t decided?

Tell them exactly that, because uncertainty stated plainly lands better than false comfort. Promising that nothing will ever change is a promise you may have to break, and one broken promise costs you every future conversation.

Three commitments are worth making even while the outcome is open. You will tell people before you make a decision rather than after. Nobody’s position depends on how enthusiastic they seem about the tool. The checking work counts as proper work, not as something squeezed in around the edges.

Those three cost you nothing if the answer turns out to be good news, and they protect you if it doesn’t.

If redundancy is genuinely possible

Sometimes the answer isn’t good news, and a role may genuinely go. Then the process matters as much as the decision, so start with the entitlements, because they set the floor. Statutory redundancy pay applies to employees with two years’ continuous service.

Below 20 proposed redundancies, the law sets out no consultation procedure to follow. Consulting properly before you reach a decision is what stops a dismissal counting as unfair, so treat consultation as protection rather than paperwork. Collective consultation rules apply once you propose 20 or more dismissals at one establishment within 90 days. The gov.uk guidance on redundancy consultations sets out the timings.

Employment law moves, and the detail depends on your circumstances. Check the current position with your solicitor or HR adviser before you act on any of this. Keep a note of what you considered, and when. If anyone ever tests the decision, that note shows you consulted with an open mind.

The decision you are actually making

Behind that process sits the decision itself. AI and redundancy meet at a choice you would have faced anyway. It would simply have arrived more slowly, the first time any part of the work got easier. The hours are real, and so is the pressure to convert them into a saving on the payroll.

What you do with them says more about how you run the business than about the software. Some owners buy back the work that keeps slipping. Others take on more work with the same team, and a few decide the shape of the team has to change. Whichever way you go, say it out loud, and say it first.