An applicant tracking system is a centralised recruitment data and workflow system that captures applications, routes candidates through stages, coordinates checks and offers, and converts a successful candidate into an employee record. The UK Government Recruitment Service example attracts approximately 600,000 job seekers per month, showing why structured tracking matters when application volumes are high.
You may recognise the problem before you recognise the technology. A hiring manager asks for the latest shortlist, one recruiter is updating a spreadsheet, another is searching a shared inbox, and paper Right to Work evidence sits in a folder waiting for someone to record it. Meanwhile, a candidate has completed an interview, but the hiring manager's notes haven't reached HR, so nobody can say precisely what happens next.
An ATS replaces that fragmented process with a governed record of the hiring journey. For a UK HR director, its value isn't limited to CV parsing or job-board publishing. It can provide the controlled entry point to the employee lifecycle, connecting vacancy approvals, candidate decisions, compliance evidence, onboarding activity and workforce reporting.
Table of Contents
- What an Applicant Tracking System Actually Does
- The Core Workflow an ATS Replaces
- Core Features That Define a Modern ATS
- Right to Work Compliance Inside the ATS
- Converting a Candidate Into an Employee on Dynamics 365
- AI Screening, Fair Outcomes and Audit Evidence
- Structured Shortlisting, Data Protection and Practical Examples
- Choosing an ATS That Fits a UK Organisation
What an Applicant Tracking System Actually Does
An applicant tracking system, or ATS, centralises the end-to-end hiring workflow. It can publish vacancies, receive applications, record candidate progress, coordinate assessments and interviews, manage offers, organise pre-employment checks and retain an auditable recruitment history. The UK Government Recruitment Service privacy notice describes a centralised Civil Service Jobs ATS as containing “all the stages of recruitment on one platform”.
Consider a UK HR manager hiring several employees during a busy quarter. Applications arrive through a careers page, a recruitment agency and referrals. Interview invitations are sent from Outlook, notes are stored in Word documents, approvals happen in Teams messages, and check evidence is saved somewhere in SharePoint. The process may appear to work, but the organisation has no dependable single record of who approved a shortlist, which criteria were applied, or whether an offer should proceed.
An ATS turns those activities into structured records:
- Vacancy record: The role, department, approvers, job description and required criteria are recorded together.
- Candidate record: Contact details, applications, CV information, correspondence and current status are connected.
- Stage history: Screening, interview, offer and check activities have clear owners and timestamps.
- Decision evidence: Scores, comments, approvals and overrides remain available for review.
- Lifecycle hand-off: Accepted candidates can move into employee administration without re-keying information.
This is the practical distinction between a CV database and an ATS. A database stores documents. An ATS manages states, permissions, actions and decisions around those documents. If you're comparing platforms, understanding ATS integration is useful because the quality of the connections between recruitment, calendars, checks and HR records often matters as much as the visible candidate screen.
The right question isn't just "Can it read a CV?" Ask whether it can show what happened to an application, who made each decision, what evidence supports an offer, and how the successful candidate becomes part of the governed employee record.
The Core Workflow an ATS Replaces
A useful way to understand an ATS is to follow one candidate from an approved vacancy to onboarding. Suppose a recruiter, Priya, is hiring a finance administrator. The hiring manager approves the role, the job description identifies the essential criteria, and the organisation needs a clear record of each action.
From vacancy to application
The workflow begins with a vacancy record, not an email request. The record identifies the role, hiring manager, business unit, required approvals and selection criteria. Once authorised, the recruiter can publish the vacancy to the organisation's careers site and relevant boards, rather than copying the same advert into several systems.
When a candidate applies, the ATS creates or updates a candidate identity and links the application to the vacancy. The candidate's CV, application answers, source, consent information and communications are held in one place. If that person applies for another role later, the organisation can retain an appropriate history instead of creating disconnected records.
From screening to interview
The recruiter then moves the application through defined stages. A screening stage might check essential qualifications or application answers. A shortlist stage records the assessors, criteria, scores and decision. Interview scheduling connects the candidate and panel to available slots, while reminders and status changes reduce manual chasing.
The important design principle is that each stage creates an event-based record. The organisation can then see when the application arrived, when screening finished, how long the shortlist took, when interviews were arranged and when an offer was approved. Without those timestamps, a recruitment report is usually an estimate assembled from emails and spreadsheets.
From decision to employee
After the interview panel records its assessment, the hiring manager approves or rejects the recommendation. An offer workflow can route the proposed package to the authorised approvers, retain the decision and record acceptance. Pre-employment checks then become explicit tasks rather than notes hidden in a mailbox.
If Priya skips a stage, the consequences are predictable. The organisation may not know whether a candidate was rejected because of an essential criterion or an informal preference. A delayed reference may be mistaken for a completed check. HR may retype the candidate's details into an employee system, introducing errors at the point where accurate data matters most.
An ATS doesn't remove human judgement. It gives that judgement a controlled place in the process, with clear ownership and evidence.
Core Features That Define a Modern ATS
A sensible ATS assessment starts with operating requirements, not a long list of buttons. Four capability groups usually determine whether a system will support a controlled UK recruitment process.
Recruitment workflow and automation
The system should represent the organisation's actual stages, including vacancy approval, application review, shortlist, interview, offer and pre-employment checks. Rules can assign tasks, notify owners, request approvals and prevent a candidate moving forward when a required activity is incomplete.
The CIPD discussion of technology in hiring and onboarding describes automation for repetitive activities such as multi-board advertising, interview scheduling, offer approvals and background checks. It also identifies recruitment measures such as time to fill, candidate quality and applicant dropout rates.
In a Microsoft environment, Power Automate can provide workflow orchestration, while Dataverse holds the records and Power Apps can provide role-specific screens. The recruitment logic, stage design and UK-specific check controls usually need configuration or extension by an implementation partner. Microsoft provides the platform capabilities, not an automatically configured recruitment policy for every organisation.
Candidate management and communication
Recruiters need one candidate view showing applications, communications, interview activity, feedback and current status. Structured forms are valuable because they capture comparable information instead of forcing reviewers to interpret free-text emails.
Microsoft 365 tools such as Outlook and Teams can support communication and collaboration, but the ATS should remain the system of record. A Teams conversation can help a panel reach a decision, but the final score, decision and approval should be recorded against the candidate and vacancy.
Compliance and audit
Role-based access should ensure that recruiters, hiring managers, HR administrators and external participants see only the information they need. The system should retain a history of status changes, decisions, approvals and evidence access, with suitable controls over sensitive documents.
Dataverse provides tables, relationships, security roles and auditing capabilities that can support this structure. HRManagement365 configuration or custom development may be needed for specific policies, retention rules, check types, expiry reminders and exception handling.
Reporting and analytics
An ATS should answer operational questions without manual spreadsheet reconstruction:
- Which vacancies are awaiting approval?
- Where are candidates dropping out?
- How long does each stage take?
- Which sources produce applications and appointments?
- Are offers waiting for approval or acceptance?
- Do progression outcomes differ across monitored characteristics?
Power BI can report across recruitment and employee data when the data model and permissions are designed properly. A dashboard is only as reliable as the stage definitions, mandatory fields and decision records behind it.
Practical rule: Treat every workflow stage as a business record with an owner, a permitted outcome and a timestamp.
Right to Work Compliance Inside the ATS
Right to Work is a useful test of whether an ATS is designed for UK recruitment. Every employer must complete a prescribed check before employment and retain sufficient evidence to establish a statutory excuse. That means a tick box labelled “checked” isn't enough.
The Home Office guidance on employer awareness of Right to Work checks identifies three principal routes:
- Manual document checking for acceptable original documents.
- Digital verification for eligible British and Irish citizens.
- The online Home Office checking service for relevant non-British and non-Irish citizens.
Turning a legal control into workflow
For a candidate, the ATS should record the check route, check status, completion date, reviewer, evidence location, permitted work conditions and any follow-up date. The system can assign the task to an authorised reviewer and prevent offer approval or employee conversion until the required control is complete.
For time-limited permission, a follow-up date should trigger reminders and escalation. The reminder doesn't replace the employer's responsibility, but it makes the control visible instead of relying on a diary entry or memory.
The audit history should preserve what was checked, when it was checked, by whom and what decision followed. Sensitive immigration evidence also needs restricted access and secure storage. Outsourcing verification doesn't transfer accountability away from the direct contractual employer.
The HRManagement365 guide to Right to Work checks for employers provides further context for the operational process. Within a Microsoft stack, Dataverse can store the candidate and check records, while Power Automate can manage approvals, reminders and escalations. The specific Right to Work fields, evidence controls and expiry workflow are configured or extended by HRManagement365, rather than assumed to be a standard Dynamics 365 recruitment feature.
Compliance principle: A completed status should point to evidence, a responsible reviewer and the rule that determined the outcome.
This distinction matters during the move from applicant to worker. A candidate marked “hired” doesn't, by itself, demonstrate that the check was completed correctly. The ATS must preserve continuity between recruitment evidence and the employee record without exposing sensitive information to people who don't need it.
Converting a Candidate Into an Employee on Dynamics 365
A Microsoft-stack ATS becomes especially valuable at the point of acceptance. In a disconnected process, HR may copy the candidate's name, address, start date, role and manager from an email into an HR or finance system. Each re-keying step creates an opportunity for inconsistency.
A Dynamics 365 and Dataverse design can hold a single candidate identity linked to applications, vacancies, interviews, approvals, offers and checks. The candidate record can then be converted or mapped into an employee record once the organisation's approval and pre-employment conditions are satisfied.
The underlying architecture typically works like this:
- Dataverse: Stores candidate, vacancy, application, interview, approval, check and employee relationships in structured tables.
- Power Apps: Provides custom screens for recruiters, hiring managers, interviewers and HR administrators.
- Power Automate: Routes approvals, sends notifications, assigns tasks and starts onboarding activities.
- Dynamics 365: Connects recruitment and employee information to the wider HR and business environment.
- Business Central or Finance and Operations: Receives the employee information needed for workforce administration, finance, costing or payroll-related processes, subject to the customer's design.
- Power BI: Reports across vacancy, recruitment and employee lifecycle data where access permissions allow.
The Office for National Statistics estimated 781,000 UK vacancies in January to March 2025, with a quarterly fall of 26,000, or 3.2%, and a year-on-year fall of 125,000, or 13.8%. The ONS vacancies bulletin supports the need for vacancy ownership, live pipeline reporting, interview scheduling, offer tracking and reliable conversion into employee records.
The distinction between platform and solution is important. Microsoft supplies Dataverse, Power Apps, Power Automate, Power BI and Dynamics 365 capabilities. HRManagement365 configures and extends those capabilities for customer-specific recruitment processes, including custom fields, approval routes, employee-lifecycle hand-offs, integrations and applications for common UK scenarios such as visa expiry tracking or contingent worker onboarding.
Here is a practical demonstration of how recruitment and onboarding can be connected:
The hire-to-retire process is the wider operating model. Recruitment isn't an isolated front end. It is the controlled starting point for contracts, organisational structure, access, development, absence, performance and eventual leaver administration.
AI Screening, Fair Outcomes and Audit Evidence
The question “Does the ATS use AI?” is less useful than “Can the employer evidence that the recruitment process produces defensible outcomes?”
Automation can improve consistency, but it can also apply a poorly written job specification more consistently. A ranking rule may reproduce historic preferences, penalise career breaks or disadvantage candidates whose experience is described differently from the wording in the vacancy. The system needs governance around the automation, not just a label that says AI.
What the evidence should contain
The UK government responsible AI in recruitment guidance, published in January 2025, says organisations procuring or deploying AI in recruitment should use assurance mechanisms, documented processes and performance metrics to evaluate ethical, statutory and regulatory risks. It recommends comparing outcomes by sex and other characteristics across application, shortlist, interview and offer stages.
An ATS that supports this work should retain:
- Structured criteria: The vacancy records the requirements used for assessment.
- Scoring rules: Recruiters can see how applications or interviews were evaluated.
- Human decisions: Reviewers can record reasons, overrides and exceptions.
- Progression data: Reports show movement from application through shortlist, interview and offer.
- Monitoring fields: Equality monitoring information is separated and access-controlled appropriately.
- Audit history: The organisation can establish what changed, who changed it and when.
The purpose isn't to automate a legal conclusion. It is to give HR a reliable evidence base for reviewing whether the process works as intended. An organisation may decide that some roles require human review at every shortlist stage, while others can use automated checks for administrative eligibility.
A Microsoft solution can support this structure through Dataverse fields, security roles, Power Automate approvals and Power BI reporting. HRManagement365 can configure the process around the organisation's policies and extend it with custom applications or workflows. The automation in recruitment guidance is relevant where teams need to separate administrative automation from selection governance.
The strongest ATS evidence is not an automated ranking. It is a clear record of the criteria, the human review and the outcome at each stage.
Structured Shortlisting, Data Protection and Practical Examples
For a finance administrator vacancy, the hiring manager might compare candidates against experience, qualifications and defined role requirements. Acas recommends converting each point in the job description and person specification into a checklist, assessing every application against it and scoring applications consistently. Its guidance on choosing who to interview also recommends involving two or more people in shortlisting where possible.
HRManagement365 can configure vacancy-specific criteria, structured application fields, reviewer scorecards, interview questions and approval steps using Microsoft technology. In Dataverse, the vacancy, candidate, assessment and decision can be related records rather than disconnected files. Each reviewer records a score and decision, while the audit history captures who assessed the candidate and when. Power Automate can route approvals, and security roles can limit access to appropriate users.
Data protection applies to the application record throughout its life. Candidates should be told why their information is processed, how long it will be kept and whether it may be considered for future vacancies. The ICO recruitment and selection guidance covers secure application systems, restricted access, secure storage, and deletion or anonymisation under a retention schedule.
For a UK mid-market organisation using Business Central, an approved vacancy can connect applications, shortlisting, Right to Work evidence and employee conversion. Power BI can combine recruitment pipeline and workforce reporting, while Business Central receives the employee information defined by the integration design. Microsoft provides the platform structure; HRManagement365 configures the hiring process around organisational policy.
Choosing an ATS That Fits a UK Organisation
A UK organisation choosing an ATS should test four practical outcomes:
- Can it evidence UK controls? The system should record Right to Work routes and evidence, manage expiry dates, route approvals and retain audit history.
- Does it fit the Microsoft estate? Dataverse can relate vacancies, candidates, assessments and decisions, while Power Platform, Dynamics 365, Teams, Outlook and Power BI reduce duplicate entry when configured as one operating environment.
- Can it create the employee record without re-keying? The hand-off should preserve identity, approvals and relevant evidence, then apply permissions appropriate to the employee record.
- Can it support fair, lawful recruitment? Candidates need clear information about processing purposes, retention and protective measures. The ICO's data protection guidance provides relevant guidance.
HRManagement365 is a UK and EU HR solution powered by Hubdrive and Microsoft technology. Microsoft provides the platform foundation; HRManagement365 configures processes, workflows, Power Apps, Power Automate, integrations, employee-lifecycle automation and Power BI reporting, with connections to Business Central, Finance and Operations and Dynamics 365 where required.
HRManagement365 can connect vacancy approval, structured selection, Right to Work evidence and candidate-to-employee conversion. Visit HR Management 365 to discuss recruitment and hire-to-retire requirements, or call +44 1522 508096 today.
