top of page

You don’t need more recruitment technology.

Writer: Mike Bratby-Bale
Mike Bratby-Bale
Oct 27
4 min read

You need to use what you’ve got.


A candidate applies.


A recruiter reviews their application in the ATS, moves them to the next stage, opens a calendar, finds an appointment, sends an email, updates a spreadsheet and adds the interview to a tracker.


Then someone asks for an update, so they do another update.


None of those tasks takes particularly long on its own. Together, across dozens of vacancies and hundreds of candidates, they start to consume a remarkable amount of time.


And the frustrating part? The business may already be paying for tools that could handle some of that work.


The process has grown around the technology


Most recruitment processes weren’t designed in one sitting.

A spreadsheet was created because the ATS report didn’t show something the team needed. A shared inbox became the place to send interview invitations. A weekly tracker was added because somebody wanted a different view of the numbers.

Each addition made sense at the time.

But after a while, the process becomes a collection of steps that everyone follows because that’s how the work gets done. The same information appears in three places, and keeping those places updated becomes a job in itself.

Before buying another tool or adding another tracker, it’s worth asking a simple question:

What are we doing manually that our existing tools could already help us do?


Start with the work, not the software


Automation doesn’t have to mean a major transformation programme. It can start with one repetitive task.

Look at a typical vacancy and follow it from application to offer. Watch what happens between each stage.

Where does someone copy information from one place to another? Where are they sending the same message repeatedly? Where does a candidate or hiring manager wait for an action that could have happened sooner?

Then ask the team why those steps exist. There might be a good reason. There might also be a feature nobody knew was available, a setting that was never switched on or a workaround that has outlived the problem it was created to solve.

For example, if a recruiter spends time arranging telephone screens by email, a bookable calendar could let candidates choose from available slots. The recruiter still has the conversation. They just spend less time trying to arrange it.

If the same confirmation message goes out after every interview booking, a template or an automated notification might remove another repeated task.

Neither change needs to be revolutionary to be useful.


Busy doesn’t always mean productive


Recruitment teams are often measured by activity: calls made, interviews booked, applications processed and vacancies handled.

Those numbers can be useful. But they don’t tell you how much time is spent moving information around to make the activity happen.

Imagine a recruiter spends two minutes updating a tracker after every interview. That sounds minor. If they record 30 interviews in a week, that’s an hour spent on one administrative step.

Whether you can remove that hour depends on what the tracker is used for and what your other systems can provide. But it’s worth finding out.

Across a team, small tasks repeated throughout the week can add up to time that could be spent talking to candidates, supporting hiring managers or understanding why a role isn’t attracting the right people.

Activity is easy to see. The cost of the process behind it is often hidden.


Don’t automate a problem


There is a temptation to take an existing process and make it faster.

Sometimes that’s exactly the right thing to do. Sometimes the better question is whether the step needs to exist at all.

If a report is sent every Friday, who uses it and what decision does it support? If a recruiter enters the same information into an ATS and a spreadsheet, which record is relied upon? If an approval has three stages, what does each stage contribute?

Automating an unnecessary task means it happens more efficiently. It’s still unnecessary.

First, understand the purpose. Then decide whether to remove, simplify or automate the work.


Make space for the human bits


Candidates don’t benefit from a process that is automated from beginning to end and impossible to navigate when something goes wrong.

They do benefit from timely communication, clear information and an easier way to book an appointment. Hiring managers benefit when they can see what’s happening without chasing. Recruiters benefit when they have more time for conversations that need their judgement.

That means deciding where automation helps and where a person needs to step in.

An automated acknowledgement can reassure a candidate that their application has arrived. A complex question about the role may need a conversation. A booking link can make scheduling easier, but there should still be a way to respond when the available times don’t work.

Good automation supports the experience you want people to have.


Run a small test


Pick one repeated task your team carries out every week.

Ask:

  • How often does it happen?

  • How long does it take?

  • Why is it needed?

  • Could an existing tool remove or reduce the manual work?

  • What might go wrong, and how would someone get help?


Test a change with a small group or a single vacancy. Ask the people using it what worked and what didn’t. Then look at the result.

Did it save time? Did the information remain accurate? Was the experience better for candidates and hiring managers? Did it create another task somewhere else?

You don’t need to automate everything. You need to know whether the change made the work better.


What’s the verdict?


The answer to a stretched recruitment team isn’t always another platform, another subscription or another ambitious technology project.

Sometimes the opportunity is sitting in the systems you already use, waiting for someone to ask why a perfectly capable recruiter is spending their afternoon copying information between them.


Find one task. Test one change. See what happens.

Better can begin there.

 
 
 

Comments


bottom of page