Skip to content
erecruiterecruit
shape
shape
Mike duffyOct 29 2026

Applicant Tracking System Explained for Government ICT

An applicant tracking system explained: core features, workflow, and the criteria Australian Government ICT recruiters should check before buying one.

Applicant Tracking System Explained for Government ICT

An applicant tracking system is software that stores each candidate record, moves every applicant through defined hiring stages, and logs who decided what at each stage.

Can yours explain why a candidate was submitted for a particular government ICT role, or does it merely show that someone uploaded a CV? That gap matters when an agency changes its requirements, a contractor withdraws approval or a team lead needs to reconstruct a shortlist.

For Australian Government ICT recruitment, the useful unit isn't the candidate alone. It's the candidate, the opportunity and the evidence supporting the decision to connect them.

Table of Contents

What an Applicant Tracking System Is and Why Government ICT Needs One

Think of an ATS as a hospital case file. Each entry shows where the person sits, what was decided and who decided it, so another authorised person can pick up the file without asking for the history.

A shared spreadsheet, inbox folders and a shortlist on someone's desktop can approximate that arrangement. They break down when recruiters run concurrent roles: someone updates the CV but not the spreadsheet, another recruiter contacts the same contractor, and the approval email stays in a private inbox.

Why the government ICT context changes the record

The APS Data, Digital and Cyber Workforce Plan records 7,556 ongoing ICT and Digital Solutions staff at 30 June 2024, up from 6,757 a year earlier, and 845 ongoing recruits in 2023–24 compared with 636 in 2022–23.

Contracting adds another dimension: the Australian Government's current-state workforce assessment reports that approximately one in every four dollars of APS departmental expenditure went to external labour services in 2021–22, with more than 40% of external-labour expenditure attributed to ICT and Digital Solutions, representing more than 6,000 full-time-equivalent employees, excluding Department of Defence expenditure data.

An ATS therefore needs to connect people with agency requirements, location, clearance and sometimes a specific contract, not just a job title.

Structure matters more than database size

ELMO's Australian HR Industry Benchmark Report found ATS use among 54% of enterprise organisations and 43% of mid-market organisations, compared with 19% of small and medium-sized businesses. Scale makes consistent workflows valuable, but a smaller government labour-hire desk can face the same coordination problem.

For product comparisons, JobTwine's explanation of the differences between recruitment platforms and ATS provides useful context. Judge the workflow underneath the category label.

If you can't say where each active candidate sits and why, you already have the problem an ATS solves.

Core Features and Evaluation Tests for Government ICT

Use the reference list below before watching vendor demonstrations. Mark each row must-have, should-have or nice-to-have for your desk, and treat a failed must-have as a deal-breaker rather than something a polished dashboard can outweigh.

Candidate storage and CV parsing are basic expectations. Role linkage, consent controls, searchable clearance fields and usable integration access determine whether the system supports government ICT labour hire.

Core applicant tracking system features and pass tests

  • Feature — What it does — Pass test for AU Government ICT
  • Candidate database and workspace — Stores each applicant once and shares the record across the team — Prior contact and CVs are reusable across roles, subject to permitted use
  • CV parsing — Extracts skills, roles, dates and clearance from resumes — Turns unstructured CVs into filterable fields
  • Role and contract linkage — Ties each candidate to an advert or BuyICT opportunity — Shows which agency role or contract each candidate was matched to
  • Pipeline stages — Moves candidates from unqualified to placed — Stages match the real hiring process and stay visible across concurrent roles
  • Matching with evidence — Ranks candidates and stores the CV text and criteria behind each score — Evidence is visible for every score, not a single number
  • Consent and submission gate — Records approval for a specific role before submission — Blocks submission until approval for that role is recorded
  • Search and filters — Finds candidates by skill, clearance, location or status — Filters by clearance, location and skill in seconds
  • Clearance tracking — Holds level, status and expiry as structured fields per candidate — Free-text clearance notes fail
  • Reporting and alerts — Shows open items, bottlenecks and changes to matched opportunities — Alerts fire on changes; manual searching fails
  • Integrations and API — Pulls opportunity, match and placement data by API or scheduled export — Data syncs with CRM and reporting tools; manual CSV only fails
  • Data retention and deletion — Deletes or ages out records on a set schedule — Retention rules support privacy obligations

Test retrieval, not field count

Say a recruiter is filling concurrent cloud architecture, cybersecurity and software development roles. Ask them to find candidates with the required clearance, delivery location and relevant technical evidence without opening every CV.

A database with extensive custom fields can still fail that task. Test combinations such as Microsoft Azure and Kubernetes, .NET / C#, or JavaScript / TypeScript with React / Next.js. Keep skills searchable without treating related technologies as interchangeable.

Require a dashboard that prioritises unanswered questions: an unverified clearance claim, an approaching close time or a changed requirement. Counts of uploaded CVs don't tell a recruiter what to do next.

Check the controls behind the interface

Use stages that reflect actual work: unqualified, screened, shortlisted, consent approved, submitted, interviewed, offer, placed and withdrawn. Record stage changes rather than overwriting the previous status without history.

For clearance preparation, AGSVA's application information guidance specifies five years of address, employment and education information for Baseline and ten years for NV1 and NV2; it also requires a previous address for all three levels, a previous employment record for NV1 and NV2, and may require financial information including gross and net annual salary and average fortnightly expenditure.

Test retention and deletion with the same care as search. A scheduled deletion must honour applicable retention requirements, and an export shouldn't recreate records that an authorised user has deleted.

Clearance History Fields an ATS Must Hold

Clearance preparation isn't the same as clearance verification. An ATS can help identify missing information, but a parsed CV claim doesn't establish that a candidate holds an appropriate current clearance.

  • Clearance level — Preparation record — ATS completeness check
  • Baseline security clearance — Address, employment and education history for the applicable Baseline period, including a previous address — Required categories and previous-address entry are present
  • NV1 clearance — Extended address, employment and education history, including previous address and employment records — Extended history is supported and previous records aren't omitted
  • NV2 clearance — Extended address, employment and education history, including previous address and employment records — Gaps are visible rather than hidden in uploaded documents
  • All listed levels — Financial information where required for the application — Preparation status is recorded and access is restricted

Store readiness without building an unnecessary vetting archive

Give each candidate a structured clearance record containing level, status, verification source, verification date and expiry where applicable. Distinguish candidate-declared, awaiting verification and verified information rather than presenting every imported field as equally reliable.

For history preparation, record the required coverage period and whether address, employment, education and financial information is ready. If your authorised process requires the underlying details, use restricted structured fields. Otherwise, record completeness without copying sensitive residential or financial documents into the general recruiter workspace.

Use this acceptance checklist:

  • History coverage: Confirm the tool supports the extended history required for higher clearance levels without truncating older entries.
  • Missing records: Flag absent previous-address and employment entries where relevant.
  • Verification: Keep clearance level, status and expiry distinct from the candidate's application-preparation status.
  • Access: Restrict sensitive details to people with a defined operational need.

Candidates exploring ICT jobs requiring security clearance should use eRecruit's government ICT job and security-cleared technology contractor searches to identify the requirement attached to the actual role. A government cybersecurity job and a government software engineer job shouldn't inherit identical clearance assumptions merely because both involve technology.

Privacy check: Store enough to establish readiness, not every document a vetting authority might eventually request.

Check the current AGSVA guidance at publication and before relying on a preparation checklist. Documentation requirements can change; an ATS configuration isn't an authoritative statement of Australian Government security clearance requirements.

How a Candidate Moves Through an ATS Workflow

A candidate's journey in an ATS is a sequence of stages, each with an owner and a record. For government labour hire, make representation approval and the destination of the submission explicit.

The general hiring journey looks like this:

The operational sequence for a labour-hire desk

  1. Role intake. Log the advert, agency, location, clearance requirement, headcount and close date, together with the source opportunity. Missing the close time or its time zone can make an otherwise suitable submission unusable.
  2. Sourcing. Candidates arrive through applications, imports or external searches and enter the shared workspace. Resolve duplicates before outreach, or colleagues may contact the same contractor with inconsistent descriptions of the role.
  3. Parsing and matching. Extract skills, employment dates and clearance claims, then compare them with the role criteria. A parser can mistake a project requiring NV1 for proof that the candidate holds NV1, so preserve the original text for inspection.
  4. Review. Assign a recruiter to assess shortlist and needs-review items, and log corrections with their reasons. Editing a field without retaining its previous value leaves the team unable to explain why the recommendation changed.
  5. Consent. Record representation approval for this specific role and submission destination. General permission to keep a CV isn't a substitute for the operational approval needed to represent the person on that opportunity.
  6. Submission. Send the approved candidate package to the agency or panel supplier and update the stage. Retain the document version and destination, rather than relying on a sent email whose attachment might differ from the current CV.
  7. Interview and offer. Record interview outcomes and offer decisions with dates and accountable owners. Keep an agency's positive feedback separate from an actual offer so reporting doesn't overstate progress.
  8. Close. Record placement or withdrawal and update reporting. Close the candidate's relationship with that opportunity, not their entire profile, unless their instructions or your retention process require broader action.

Assign approval ownership before automation

Use an approval workflow example to define who can approve progression, who covers an absent reviewer and which actions require escalation. A stage name alone doesn't establish authority.

The highest-risk points are parsing and matching, where software may misrepresent suitability, and consent, where a recruiter may act beyond the candidate's approval. Automate reminders and routing around those decisions, but don't hide the responsible person behind a system status.

Using Automated Matching Without Losing Human Judgement

How can a recruiter use an automated match without letting a score make the decision? Treat the ATS as an evidence and audit record: the tool can surface relevant candidates, while a recruiter checks whether the evidence supports action. The Merit Protection Commission's guidance on AI-assisted and automated recruitment tools recommends combining automated outputs with traditional assessment methods for a balanced ranking.

Keep the source material in view during review:

A score isn't an explanation

A match score alone cannot establish that a candidate meets a mandatory requirement. A useful recommendation separates technical experience, clearance, location and employment history, then shows the CV evidence behind each assessment. For a closer look at what to assess, use this CV matching software guide.

Confidence should reflect the strength of the available evidence, not just apparent suitability. If a profile is incomplete, route it for review even when the candidate ranks highly. For example, a data engineer may describe relevant work as ETL development, a non-standard CV may separate dates from employers, or a Python reference in an artificial intelligence or machine learning project may not show the candidate's own responsibility.

Require a reviewable decision trail

Check that the tool retains:

  • Source advert: The opportunity and requirement version used for assessment.
  • Criteria applied: Mandatory conditions, preferences and configured weighting.
  • CV evidence: Passages that support or contradict the recommendation.
  • Confidence level: Missing, ambiguous or conflicting information.
  • Reviewer: The accountable person and their decision.
  • Override reason: Why the human assessment differed from the recommendation.
  • Candidate notification: What the candidate was told about automated processing.

The APSC principles for agency use of AI in recruitment set an expectation for agency-specific policies by 1 June 2026 and say vacancy materials should explain whether and how AI will be used. Record where automation contributed to a decision, rather than applying a generic AI label to the entire process.

In erecruit, users upload CVs and see which candidates match each role, with the reasons why. Use a video alongside the evidence review, not instead of checking the advert, criteria and supporting CV material. The reviewer should be able to explain the match in a sentence using the stored evidence before taking action.

Require recruiter review before rejection or submission. If the evidence does not support a clear explanation, keep the candidate in review rather than letting the score decide.

Can your team show what a candidate agreed to, what was submitted, and who made the decision? Consent is a process, not a checkbox. Permission to hold a CV does not automatically cover reusing it, disclosing it, or representing the candidate for another government opportunity.

The APSC factsheet on protecting privacy in recruitment explains that recruitment activities require a privacy collection notice and personal information should generally be used or disclosed for its original or primary purpose unless an exception applies. Treat consent records as part of the decision trail, alongside the evidence and approval for each submission.

Make approval specific enough to use

A useful consent record identifies the candidate, role or client, date given, scope of use, expiry where applicable, and withdrawal status. Keep the approval message or captured response, not only a recruiter-entered tick. A later reviewer should be able to tell what the candidate authorised and whether that approval still applies.

Role-specific representation approval is a practical control, though it does not by itself establish that every privacy obligation has been met. A consent gate in an ATS helps prevent submission before approval is recorded; it is one part of compliant handling, not proof of compliance.

For ongoing administration, candidate management software can help keep records and approvals connected. Set permissions against their purpose so another recruiter can distinguish reusable candidate information from approval limited to a particular submission.

Apply withdrawal to the actual submission

If a contractor approves representation for an NV1 role at an agency, that approval should not automatically cover a different role identified later. Similar technology and clearance requirements do not make the submissions identical. Obtain fresh approval for the new opportunity.

If the candidate withdraws after submission, stop further progression under your control and notify the recipient that representation has been withdrawn. Record the event, then assess what the applicable retention schedule requires you to delete or retain.

  • Stop further action: Block additional submissions and progression covered by the withdrawal.
  • Record the event: Capture its date, scope, and the person responsible for implementing it.
  • Assess retention: Determine what must be deleted and what must remain under the applicable retention schedule.

Withdrawal does not necessarily mean deleting evidence that a submission occurred. Retain only what you have a valid reason to keep, restrict access, and document that decision.

Audit drill: Pull a submitted candidate and demonstrate their approval, match evidence, and reviewer within five minutes.

That is a practical retrieval target, not a statutory deadline. For automated processing, keep the decision trail clear: record the personal information used and the human decision that followed.

Choose an ATS That Connects Opportunities to Candidates

Choose the tool that can prove what happened to each candidate on each government opportunity, not the one that stores the most records. A large database won't repair a broken link between a role, its source requirement and the person authorised to progress it.

Run a controlled buying process

  1. Test the must-haves against a live role. Take a small shortlist of tools and run the same opportunity through each. Use realistic CVs with appropriate permission, include an ambiguous clearance claim, and test whether a failed requirement blocks progression.
  2. Map the integration fields. Match ATS fields to buyer, delivery state, invitation posture, close time and source reference. Decide which system owns each field and how changes are reconciled, particularly when a public advert and procurement record describe the opportunity differently.
  3. Pilot with two live roles for two weeks. Track staff hours spent, submissions with approval recorded and human overrides of automated recommendations. Treat those as pilot measures, not promised performance improvements.

Confirm API access, export options, permissions and plan details in writing with each vendor. A demonstration of an integration isn't confirmation that your subscription includes it or that it exports the decision history you need.

Connect discovery with execution

Opportunity intelligence can sit alongside an ATS rather than replace it. eRecruit.io is an Australian platform helping technology professionals, contractors, recruiters and businesses discover Australian Government ICT jobs, contracts, tenders and procurement opportunities.

Our users can source candidates, track them from unqualified to placed and gate submissions on consent. Our Agency plan includes everything in the Recruiter plan, plus API access for opportunities and matches; getting started takes three steps: sign up, upload a CV and let the matcher do the rest.

Use the job, opportunity, government-buyer and search views for different questions. Someone seeking government DevOps jobs needs a role-level view; a supplier pursuing government cloud contracts needs the procurement context and source opportunity.

Technology searches should remain specific to the work. Microsoft 365 and Power Platform delivery, Java development, data engineering and government technical architect roles require different evidence, even when the opportunities belong to the same buyer.

No tool replaces the reviewer who accepts responsibility for the decision.

Write your must-have list and test it against a live role this week. If the tool can't reconstruct the candidate's path without searching private inboxes, it hasn't passed.

eRecruit connects Australian Government ICT opportunities with the live roles panel agencies are advertising, alongside CV matching and candidate workflow tools. Visit erecruit to explore relevant opportunities and assess how evidence-backed matching fits your recruitment process.

Mike Duffy
Mike DuffyFounder, erecruit Founder of erecruit, where he works daily with BuyICT procurement records and the labour-hire job ads published behind them. Writes about what the contract data shows about Australian Government ICT hiring.