Recruitment admin problems: what to check before automating

Talisman2 min read

Cut-paper records and messages follow three coloured paths through a separator into distinct trays — conceptual illustration

The candidate sent an updated CV. Your colleague is reading an older version. Before adding another reminder, follow the information: where did it arrive, which record changed and who checked it?

Use these checks when missing details, unanswered messages or disputed reports keep interrupting your desk. Start with an actual example and record where the process becomes unclear.

An outdated record: trace the latest information

Find the latest CV or conversation and compare it with the record your consultant uses. Check the candidate identity, contact details, availability and the source date. Ask who should confirm anything that conflicts.

Talisman's recruitment CRM keeps candidate records and activity together. Its CV handling supports review before information is committed. Test the intake route your agency uses, including an existing candidate sending updated details.

Agree which information the team treats as current and how corrections are made. A newly received document and a checked record are different stages of the work.

A missing reply: follow the conversation

Choose a message that someone expected to be answered. Check the recipient, sending time, destination for replies and person responsible for responding.

Then read the conversation in order. Did the candidate answer through another channel? Did the booking or interview change? Was the next action assigned to a colleague?

Fix the unclear responsibility or missing context before adding a follow-up. Test the process with a reply, an unanswered message and a changed instruction. The consultant picking it up should be able to explain what happens next.

A disputed report: inspect the records behind it

Start with the question the report is meant to answer. Check the period, team, status filters and definition of the measure. Compare a few included records with the activity they represent.

Dashman supports filtered reporting and detail behind the headline figures. Use that detail to investigate a discrepancy before changing the target or drawing a conclusion about a consultant.

Record the agreed definition and any correction needed. Check whether the issue is the source record, the report selection or two people asking different questions.

A repeated document chase: check the starting condition

Take one requested document through the process. Who requested it, where can the candidate submit it and who checks what arrives? Keep missing, submitted and reviewed information distinguishable.

If you introduce an automatic reminder, agree which records qualify, the message, timing and person handling exceptions. Test a completed request as well as an outstanding one before switching it on.

Our recruitment automation guide explains triggers, actions and review. Use automation around an agreed process, with a clear place for questions and corrections. The first task is finding where the information or responsibility went missing.

Where this happens in Talisman