What Is ATS? Applicant Tracking Systems for Recruiters

You are staring at a shared inbox full of CVs for a cleared Azure role, and nobody can say who read which one. One colleague thinks the candidate was ruled out for location. Another thinks the CV never got opened. The hiring manager wants a shortlist by Friday, and the only trail is a pile of forwarded emails.

That mess is exactly what an ATS is built to stop. An applicant tracking system is recruitment software that stores every applicant's record and moves each candidate through the stages of a hire, from application to offer. It works like the operations desk of the team: every vacancy, every person and every decision gets logged, so when someone asks why a strong candidate was rejected, the answer sits in the system rather than in memory. Australian spending on this software is climbing, and most buyers now choose cloud platforms rather than software installed on a single office server.

Table of Contents

• What Is an Applicant Tracking System?
• How an ATS Moves a Candidate Through Hiring
• Core ATS Features and What Each One Does
  • Accessibility is an acceptance test
  • What the reports should show
  • Three checks before you buy
• How an ATS Differs From a CRM and Job Board, and What It Connects To
  • Who owns the record
  • Connections that keep the records consistent
• Common Misconceptions and Where an ATS Falls Short
• How an ATS Fits Australian Government ICT Hiring
  • Controls the record has to meet
  • Where a specialist layer sits
• Security Clearance Records an ATS Must Hold
  • Timeframes you should put on the requisition
  • What to store, and what to leave out
• Choose an ATS That Matches Your Hiring Workflow

What Is an Applicant Tracking System?

An applicant tracking system (ATS) is recruitment software that centralises job advertising, applications, candidate records, screening, interview workflows, communications, approvals, offers, and recruitment analytics. The IMARC Group market report values the Australian ATS market at approximately USD 62.49 million in 2025 and forecasts USD 122.21 million by 2034, a compound annual growth rate of 7.74% from 2026 to 2034. Cloud deployment accounted for 68.4% of that market in 2025, so organisations are increasingly adopting remotely accessible platforms rather than software installed on a single office server.

What an ATS does comes down to three jobs.

• It stores the person. Skills, location, clearance status, and consent sit on one searchable profile, not in three inboxes.
• It sequences the hire. Each candidate moves through stages such as applied, screened, interviewed, and offered.
• It records the decision. The system keeps who moved the candidate, when, and why.

Say a recruiter faces forty CVs for one government software engineer job and has no note of who reviewed them. A week later the buyer asks why a particular contractor was not submitted. Without a stage history, the honest answer is a guess. With an ATS, the answer is a timestamp, a reviewer name, and a reason tied to the requisition.

A job board mainly distributes vacancies and collects applications. An ATS keeps structured candidate data and supports screening, pipeline management, approvals, and analytics. That split matters in ICT labour hire, where you may run several government roles at once and need consent, clearance, and submission status in parallel.

Once a team manages more than a handful of hires a year, the record matters as much as the job advert.

How an ATS Moves a Candidate Through Hiring

Think of the pipeline as the path one requisition takes, with a log written at every step. Adecco's account of public-sector hiring technology describes an ATS as a system that collects applications, parses them into searchable records, and manages screening, shortlisting, interviewing, and onboarding. High volumes make manual triage expensive, which is why public-sector teams lean on it.

1. Publish the requisition. You post once, and the vacancy goes to job boards and career sites from that record. Log the requisition ID, the buyer or panel context, and the date it went live, so every later application hangs off the same role.
2. Capture each application. The ATS parses the CV into fields such as skills, location, and clearance status. Log the source and the time received. A bad parse is a data problem you can see, not a candidate who vanished.
3. Screen against must-haves. Separate must-have criteria from transferable skills before anyone is ranked. Log the criteria checked and the reviewer's name. A score with no criteria behind it cannot be defended.
4. Shortlist into review. Move the strongest candidates forward and leave a reason on the ones you hold. The reason is what you will need when a hiring manager asks why someone was skipped.
5. Schedule interviews. Book the panel and collect scorecards against the same criteria used at screen. Log who sat on the panel and what they scored, so two interviewers are not using two different job descriptions.
6. Route the offer. Send it to the approver and track acceptance or decline with name and date. An unsigned verbal yes is not a placement.
7. Hand over and close. Pass the placed candidate to onboarding and close the requisition. The closed record is the audit file for that hire.

The same reporting notes that an ATS can combine keyword rules, searchable fields, automated notifications, interview scheduling, and candidate-pool retention. Keyword matching on its own can produce false positives, or exclude someone who names the same skill differently. Role-specific criteria, explainable scoring, and a human review should sit on top of any automated rank.

A short walk-through of that flow is easier to picture than a feature list.

Every stage change should leave a trace the team can audit later. If a status moves and nobody's name is on it, the system has stored a CV, not a decision.

Core ATS Features and What Each One Does

Use this as the checklist you take into a demo. Each row is a feature, what it does on a live requisition, and the test that shows whether it actually records the work.

• Feature — What it does — What to check in a demo
• Job posting and multiposting — Publishes one requisition to several job boards and career sites — Whether the requisition ID stays linked to every applicant
• CV parsing and candidate database — Turns CVs into searchable structured fields — Parsing accuracy on your own sample CVs, including non-standard layouts
• Search and tagging — Finds candidates by skill, location or clearance status across past roles — Whether tags can be edited in bulk and reused
• Screening rules and scorecards — Applies must-have criteria and records scores against them — Whether each score shows the criteria behind it, not just a number
• Interview scheduling — Books panels and sends invitations — Time zone handling and calendar sync
• Email templates and notifications — Sends stage updates and candidate messages — Whether messages are logged against the candidate record
• Approvals and offer management — Routes offers to approvers and tracks acceptance — Whether approvals are recorded with name, date and decision
• Reporting dashboards — Shows time-to-fill, stage conversion and source of hire — Whether reports can be exported and filtered by role or team
• Accessibility — Supports keyboard use, contrast and labels on candidate screens — Conformance to WCAG Level AA on application and status pages

Accessibility is an acceptance test

For Australian Government-facing workflows, accessibility is a compliance requirement, not a polish item. The Australian Government Architecture standard on WCAG states that WCAG applies to all digital services and forms part of the Digital Service Standard, the Digital Inclusion Standard, and Commonwealth procurement requirements. Western Australian Government guidance names WCAG Level AA as the benchmark and recognises WCAG as ISO/IEC 40500:2012.

On an ATS that means keyboard navigation, visible focus states, sufficient colour contrast, accessible form labels and error messages, semantic structure, and non-text alternatives. Those controls stop a screen-reader or keyboard user from being locked out of an application, and they also make the captured data cleaner. Treat WCAG-conformant candidate and recruiter screens as a procurement acceptance criterion, next to an audit trail of matching decisions and consent.

What the reports should show

Time-to-fill and stage conversion tell you where a pipeline stalls. A raw application count does not. If forty people applied and three reached interview, you want the drop-off by stage, filtered by role or team, in a file you can export.

Three checks before you buy

Export the stage history for one closed role and see whether reviewer names survived. Log in as a junior user and confirm you cannot open records outside your roles. Change a status and confirm the audit log stores who did it.

Candidate mail inside the ATS should stay on the person record. Longer outbound nurture is a different product, and it is worth reading about email sequence software features and limitations so you don't expect the ATS to run a multi-step campaign. If parsing quality is the gap you care about most, our notes on CV matching software show what a score should expose before anyone is shortlisted.

How an ATS Differs From a CRM and Job Board, and What It Connects To

The decision that matters is which system owns the candidate record for a specific role. An ATS, a CRM, and a job board answer different questions, and mixing them up is how records fork.

• Dimension — ATS — CRM — Job board
• Primary purpose — Manages applicants through hiring stages for each role — Manages relationships with prospects, clients and contacts over time — Lists vacancies and collects applications
• Main users — Recruiters and hiring managers — Business development and account teams — Candidates and employers searching
• Candidate record — Structured record tied to a specific application — Long-term contact record, often including passive candidates — Profile or application tied to one listing
• Typical reporting — Time-to-fill, stage conversion, source of hire — Pipeline value, contact activity, follow-up rates — Listing views, application counts
• Compliance and audit — Stage history, reviewer and decision log — Activity log of contact and outreach — Limited audit of hiring decisions
• Main weakness — Weak for long-term nurturing of contacts — Not built around requisitions or stage approvals — Little screening or pipeline control

Who owns the record

An ATS controls the requisition and its stage history for one role. A CRM tracks relationships with prospects, clients, and past contractors over months. A job board lists vacancies and collects applications, then stops.

Say a labour-hire recruiter screens an ICT contractor for a government cloud role. Submission, interview, and placement live in the ATS, because that is where approvals and the decision log belong. After placement, the same contractor is recorded in the CRM so the agency can re-engage them for a later contract. One system owns the hire. The other owns the relationship. A closer look at a CRM for recruiting helps if follow-up, not stage control, is what your revenue depends on.

Connections that keep the records consistent

• Job boards. Map every application back to the correct requisition ID. An unlinked apply is an orphan CV.
• Calendar and email. Handle time zones, and log every message against the candidate, not a personal inbox.
• HRIS or payroll. Take hire details only at onboarding, from the closed requisition, not from a side spreadsheet.
• CRM sync. Set duplicate-matching rules and a single sync direction. Two-way sync without rules creates two versions of the same person.
• Consent and checks. Record consent before any background check starts, and store only the outcome as a status.
• API access. Confirm it is included in your plan before you build dashboards on it.

An ATS is the core system when you manage roles and stages. A CRM becomes necessary when relationship follow-up is what brings the next placement.

Common Misconceptions and Where an ATS Falls Short

Three ideas about what an ATS is keep showing up in demos, and each one causes a bad configuration.

An ATS rejects candidates automatically. Rejection depends on how the rules are set. The greater risk is a false negative: a keyword rule drops someone who describes the same capability in different words, or who buried the relevant work in project descriptions. Configure rules to flag, then put a person on the review, rather than auto-declining on a missing phrase.

An ATS is just a CV database with search. Jobs and Skills Australia reports that only 32% of IT employers recruited in 2025–26, compared with 49% across all industries, while 34% of recruiting IT employers received at least 20 applications per vacancy. Plenty of ICT roles are not short of CVs. They are short of people with the precise technical, clearance, location, or delivery experience a government buyer wants. The system should help you tell whether the problem is too few applicants, unsuitable skills, or poor matching, and it should store the evidence for that call.

More matches means better hires. A long list of keyword hits is not a shortlist.

An ATS should make its matches explainable, not merely numerous.

In practice, each match should show the must-have criteria it met and the transferable skills behind it. Prioritise review. Don't let the software decline people on terminology alone.

There are also decisions the software cannot make. It cannot confirm a security clearance, current availability, or a candidate's consent to be represented. A high score is a prompt to check those facts, not a substitute for them.

How an ATS Fits Australian Government ICT Hiring

Australian Government technology buying is a multi-party process, not a straight line from employer to applicant. The Digital Marketplace Panel 2 is built for ICT labour hire: a seller sources a candidate, engages that worker, and supplies them to a government buyer under contract. A 2025 Australian Parliament inquiry reported that the Digital Transformation Agency had established six marketplace panels, covering hardware, telecommunications, software, cloud, digital services, and data centres, alongside seven arrangements coordinating common government technology purchases. The same inquiry described research with 932 buyers, 2,073 sellers, and 225 labour-hire candidates. Records have to survive that many hands.

Capability risk sits underneath the paperwork. The Digital Transformation Agency's 2026 managing projects report notes that 71% of APS agencies reporting on digital projects identified talent shortages as a high risk, and projections indicate a shortfall of more than 61,000 digital professionals across Australia over the next five years. In a market that tight, a wrong submission wastes a scarce person and a buyer's time.

Controls the record has to meet

• Procurement context. Link each role to the contract or delivery setting it belongs to.
• Consent. Store an explicit consent record before anyone is submitted.
• Status history. Keep every stage change, with a name and a date.
• Access controls. Limit who can see clearance notes and candidate files.
• Human review. A person checks automated scores before a name goes to a buyer.

A high score is not proof of eligibility, security clearance, availability, or consent to representation. Automation increases operational risk when it strips out that provenance.

Where a specialist layer sits

A general ATS holds candidates and stages. It does not, on its own, tell you which government contract a public job ad relates to. At erecruit we link Australian Government ICT procurement opportunities on BuyICT to live job advertisements published by tender-panel agencies, so you can see which contract is behind which ad. Those ads are matched using evidence on role, clearance, location, and timing. BuyICT is the Australian Government ICT procurement portal, not a job board.

The question the ATS has to answer is simple: what did it record so you can explain why a candidate was prioritised, and confirm the submission was authorised? Placement is only the start of delivery, which is why the handoff into a documented onboarding process belongs on the same requisition, not in a separate trail of emails.

Security Clearance Records an ATS Must Hold

Clearance level decides the highest classification an ICT worker may access. The AGSVA Security Clearance Applicant Guide sets three levels. Eligibility requires Australian citizenship, as determined by the sponsoring entity, and a checkable background assessed by the Australian Government Security Vetting Agency. Individuals cannot sponsor themselves. When a role needs clearance, the employer submits the request to AGSVA on the applicant's behalf.

• Clearance — Highest access — AGSVA assessment target — History required
• Baseline — PROTECTED — 20 business days — 5 years of address, employment and education
• NV1 — SECRET — 70 business days — 10 years of address, employment and education
• NV2 — TOP SECRET — 100 business days — 10 years of address, employment and education

Timeframes you should put on the requisition

AGSVA's application information gives the applicant up to 20 business days after an invitation to complete the pack and upload documents. Stated assessment targets, counted from the agency's acceptance of the completed application, are 20 business days for Baseline, 70 for NV1, and 100 for NV2. AGSVA also allows 5 to 10 business days to issue the application. These are AGSVA's stated targets. Check them against current AGSVA guidance before you publish a start date to a buyer.

History periods differ by level: five years of address, employment, and education information for Baseline, and ten years for NV1 and NV2.

What to store, and what to leave out

Keep the clearance level required on each requisition, the sponsorship request status and date, the clearance status as the sponsor recorded it, and the date of each AGSVA milestone. Don't store the vetting file itself in the ATS. The outcome and the dates are what the pipeline needs. The case file stays with the sponsoring entity and AGSVA.

A role that needs NV1 has to plan for up to 70 business days of assessment after acceptance, on top of the applicant's own 20 business days to lodge. Start dates and contract planning should reflect that clock, or the requisition will show a placed candidate who cannot yet start.

Choose an ATS That Matches Your Hiring Workflow

Test any ATS against the work you really do. Five questions are enough to say yes or no.

• Stage history. Does it keep reviewer names and reasons on every move?
• Access and consent. Can you limit records by role, and store consent before submission?
• Connections. Does it link to your job boards, calendar, and HRIS without breaking the requisition ID?
• Reporting. Can you see time-to-fill and stage conversion, exported by role or team?
• Accessibility. Do candidate-facing pages meet WCAG Level AA?

If you place ICT labour-hire candidates into Australian Government roles, add a specialist layer beside the ATS. We track 2,548 live ads from 14 labour-hire agencies against Australian Government ICT contracts. Before you spend a day on a role, confirm which BuyICT opportunity sits behind the ad and whether the buyer has invited your agency to respond, then write that contract reference onto the requisition. erecruit is a platform that helps technology professionals, contractors, recruiters, and businesses discover Australian Government ICT jobs, contracts, tenders, and procurement opportunities.

Browse the live roles, and check the linked contract before you commit a shortlist.

erecruit maps Australian Government ICT jobs and BuyICT opportunities to the contracts behind them, so the record in your ATS starts from the right requisition. If you place technology contractors into government work, that link is what keeps clearance, consent, and submission tied to a real contract. Visit erecruit to see current government ICT jobs and opportunities before you open the next role.