Candidate Tracking Software: What It Is and How to Choose
Candidate tracking software explained for Australian Government ICT recruiters: features, clearance fields, pipeline stages and a vetting checklist.
Candidate tracking software is a system that keeps every candidate, the role they were considered for, their pipeline stage and the reason for each move in one record. With online job boards used by 58% of Australian employers in their most recent recruitment round in 2025, the practical job is connecting applications to decisions, not just storing CVs.
You've got a government cloud role approaching its closing date, applications arriving through agency advertisements and a shortlist that still needs clearance checks. Someone asks whether a candidate approved representation for this particular opportunity. The answer shouldn't depend on finding the right email thread.
For Australian Government ICT labour hire, the tracker should be a defensible decision record. It needs to show what the recruiter knew, what the candidate authorised and why the next action was justified.
Table of Contents
- What Candidate Tracking Software Does for a Recruiter
- How a Candidate Moves Through the Pipeline
- What Good Tracking Gives You Beyond Speed
- Pain Points and the Capabilities That Fix Them
- Clearance and Citizenship Fields for Government ICT Roles
- How to Vet a Candidate Tracking Platform Before You Buy
- Pick a Tracker Before Your Next Government ICT Round
What Candidate Tracking Software Does for a Recruiter
Candidate tracking software brings candidate identity, role history, application evidence and recruitment decisions into a shared record. Buyers also use applicant tracking system, or ATS, for this core category; candidate tracking puts the emphasis on the recruiter's working pipeline rather than the application form.
Think of a job board as the shop window that brings people in. The tracker is the stockroom ledger that records what happened to each person afterwards. Publishing an advertisement doesn't establish who screened an applicant, which contract they considered or whether they submitted the candidate.
A useful candidate workspace makes that history visible alongside the profile.
Connect sourcing to the hiring record
Online job-board use rose from 46% in 2016 to 58% in 2025, a 12-percentage-point increase; among employers that filled a vacancy, 40% identified online job boards as a method leading to a successful hire, according to Jobs and Skills Australia's recruitment-methods report. The operational implication is straightforward: source information needs to survive screening, communication and placement.
Spreadsheets become awkward when several advertisements feed an inbox and recruiters maintain separate copies. A candidate can appear against different opportunities without anyone knowing which record contains the latest availability.
Government technology hiring provides a substantial context for this work. The official workforce tables record 7,556 ICT and Digital Solutions employees at 30 June 2024, compared with 6,757 in 2023, an increase of 799, or approximately 11.8%, in the APS workforce data.
Run a quick visibility test:
- Active roles: Can you identify every open assignment?
- Candidate allocation: Can you see who sits under each role?
- Application source: Can you trace each candidate back to the advertisement?
If answering takes longer than a minute, your team probably hasn't achieved a genuinely central record.
How a Candidate Moves Through the Pipeline
Consider a hypothetical cloud engineer applying to a panel supplier's advertisement associated with a government labour-hire request. The candidate has relevant Microsoft Azure and Kubernetes experience, but the recruiter still needs to establish role suitability and availability.
The following flow illustrates the broad progression. The working tracker should expose approval and decision checkpoints within those stages, rather than letting a simple visual hide them.
Follow the candidate without losing the evidence
- Sourced. The recruiter records the agency advertisement, first-contact date and associated opportunity. If the engineer applies directly, the application date belongs here too, with the original advertisement preserved or referenced.
- Screened. The recruiter compares the CV against the actual cloud engineering criteria. Azure experience alone isn't enough: the record should identify evidence relevant to the advertised responsibilities and flag questions that still need an answer.
- Shortlisted. The recruiter advances the engineer after checking the supporting evidence. A useful note explains the judgement, such as relevant cloud architecture work demonstrated but commencement timing awaiting confirmation, rather than marking the candidate suitable with no explanation.
- Consent approved. Before representation, the recruiter records approval for the particular role and the scope of the proposed disclosure. Approval should be attributable to the candidate and tied to the relevant opportunity, not inferred from the existence of a CV.
- Submitted. The tracker captures the submission date, recipient and buyer's role reference. Store the submitted CV version and supporting response so later edits don't obscure what the buyer received.
- Interviewed and outcome recorded. Interview dates, panel feedback and the buyer's decision remain connected to the same application history. Separate confirmed buyer feedback from the recruiter's interpretation, particularly where the feedback is incomplete.
- Placed, rejected or withdrawn. The closing status includes its reason and any resulting action. Withdrawal shouldn't be recorded as rejection, and an unsuccessful application shouldn't erase evidence relevant to the recruitment decision.
Handle exits as carefully as progress
The engineer might leave before interview because the commencement date no longer works. That's a timing outcome, not evidence that their cloud skills were unsuitable. Keeping those distinctions helps the next recruiter avoid misreading an old application.
A candidate profile can serve several applications, but each opportunity needs its own decision history. The practical approach to recruitment pipeline management is to preserve those relationships without creating duplicate people.
Working rule: Every stage change should identify who acted, when they acted and the evidence they relied on.
What Good Tracking Gives You Beyond Speed
The strongest benefit isn't faster typing. It's being able to answer a buyer who asks, months later, why the agency prioritised a particular contractor.
The Australian Public Service Commission's AI-recruitment principles say agencies should be able to explain contracted providers' use of AI, the privacy and security assessments performed, and alignment with work-related qualities and merit requirements. That makes an unexplained ranking a weak operational record, even if recruiters find it convenient.
Make recommendations inspectable
Evidence beside the score lets a recruiter examine role alignment, clearance, location and timing separately. For a government DevOps role, a high technical match shouldn't conceal an unresolved requirement to attend the buyer's nominated workplace.
Unknown information must remain distinct from mismatch. A blank availability field means the recruiter needs clarification. It doesn't establish that the candidate can't start when required. Software that collapses both states into a negative score encourages avoidable exclusions.
Human overrides need a rationale. Suppose a recruiter advances an engineer whose CV uses different terminology from the advertisement but describes relevant delivery work. The tracker should retain the original recommendation, the recruiter's revised decision and the supporting explanation.
A ranking is a prompt for scrutiny, not a substitute for a recruitment decision.
Measure useful sourcing outcomes
Source reporting should connect advertisements to shortlists and placements, not stop at application totals. An advertisement attracting many loosely relevant CVs may deserve less attention than one producing candidates who satisfy the actual requirements.
Keep the comparison honest. An unsuccessful placement outcome might reflect a withdrawn request or changed commencement date rather than a poor sourcing channel. Record those distinctions before reallocating recruiter effort.
The trade-off is additional structure at the point of decision. Recruiters won't welcome a lengthy form for every move, so use concise reason categories with supporting notes where judgement matters. These benefits depend on recorded reasons, not a dashboard full of scores with no explanation behind them.
Pain Points and the Capabilities That Fix Them
Jobs and Skills Australia reported an IT-industry recruitment rate of 32% in 2025–26, against 49% across all industries, yet approximately 34% of recruiting IT employers received 20 or more applicants per vacancy, in its analysis of changing IT recruitment trends. Applicant volume and technical suitability are different problems.
For government ICT recruiters, that means triaging applications while checking the conditions that determine whether a candidate is actually viable. A CV mentioning Python, Java or cybersecurity doesn't resolve security eligibility, location or commencement timing.
The workspace needs to support that review, not merely display applications.
Test the workflow rather than the feature label
Use each row as a purchasing test. Run it yourself during a trial rather than accepting a presenter's demonstration with prepared records.
- Pain point — Capability to look for — Trial test
- Candidates scattered across spreadsheets and inboxes — One central candidate record with source and role fields — Import a real CV and confirm there is one record per person
- Too many applications to triage — Scoring against role criteria with visible reasons — Score five real CVs and check that each score shows its reasons
- Unclear which contract an advertisement relates to — Linkage fields for role, clearance, location and timing — Confirm the source notice is visible from the opportunity record
- Missed new matches after postings change — Alerts and re-scoring when postings change — Edit a test advertisement and check whether the score updates
- Several roles running in parallel with no priority view — Pipeline stages with a dashboard — Check stage counts per role on one screen
- Candidates submitted without consent — Representation approval recorded before submission — Attempt a submission without approval and confirm it is blocked
Use authorised candidate material for testing, with appropriate access and deletion arrangements. A trial isn't a reason to copy a production database into an unfamiliar service.
A keyword search isn't the same as role scoring with inspectable reasons. Likewise, a consent field isn't a submission control if a recruiter can leave it blank and continue. The practical distinction is whether the capability changes what users can do, not whether the vendor lists it.
Use the video alongside your own workflow checks, rather than as proof that a platform meets them.
For scoring-specific evaluation, the guide to CV matching software provides a related purchasing lens. Keep matching quality separate from pipeline usability: a persuasive recommendation doesn't compensate for a submission history nobody can reconstruct.
When assessing linkage to BuyICT opportunities, examine the evidence supporting the relationship between the notice and agency advertisement. Don't treat a suggested connection as confirmation just because the job titles resemble each other.
An unresolved workflow problem usually returns as a placement dispute, missed opportunity or privacy concern. Fixing the underlying control is more useful than adding another reminder to the recruiter's inbox.
Clearance and Citizenship Fields for Government ICT Roles
- Clearance — Highest classified access — Ongoing validity — Matching note
- Baseline — Up to and including PROTECTED — 15 years — Does not satisfy an NV1 or NV2 requirement
- NV1 — Up to and including SECRET — 10 years — Does not automatically satisfy an NV2 requirement
- NV2 — Up to and including TOP SECRET — 7 years — Sufficient for most roles with intermittent TOP SECRET access
The access ceilings come from AGSVA's March 2025 applicant guide; the 15-, 10- and 7-year validity periods and intermittent-access note are set out in Tasmanian Government protective-security guidance applying the Commonwealth framework. Those periods are planning references, not confirmation of an individual's current status; check current AGSVA guidance and verified candidate evidence before relying on them.
Separate eligibility from technical suitability
AGSVA's guidance says applicants normally need Australian citizenship and a checkable background, although the sponsoring entity may exceptionally waive either or both requirements. Clearance is obtained through a sponsoring government entity or approved organisation, not independently ordered by a candidate for general use.
A recruiter therefore needs more than a security-cleared checkbox. Store clearance level, recorded expiry, verification date and sponsor status separately from technical skills, and distinguish candidate-declared information from verified information.
Don't tell a technically strong applicant that they can just purchase the clearance needed for a government cybersecurity job. The practical questions are whether they meet the advertised conditions and whether the relevant organisation will support any required sponsorship.
Record location as an explicit condition
The government's current-state profile reports 7,876 ICT and digital employees, with 58.3% in the ACT; 87% of vacancies include the ACT, and 40% advertise it as the only location, according to the Australian Government ICT and digital workforce profile. These are workforce-profile figures, not a guarantee about today's advertisements.
For matching purposes, Canberra attendance and willingness to relocate need explicit answers. A national search for government software engineer jobs shouldn't silently become an assumption that every shortlisted engineer can work in the ACT.
Each role record should capture:
- Security requirement: Required clearance level and any stated sponsorship conditions.
- Eligibility evidence: Citizenship requirement and verification status.
- Clearance currency: Recorded expiry and date checked.
- Location commitment: Permitted locations and attendance requirements.
- Deployment timing: Proposed commencement and candidate availability.
The guide to security-clearance jobs in Australia supports candidate-facing conversations about these requirements without treating different clearance levels as interchangeable.
How to Vet a Candidate Tracking Platform Before You Buy
Don't assume the employee-records exemption covers everyone in your recruitment database. The Fair Work Ombudsman's workplace privacy guidance identifies unsuccessful applicants' resumes, contact details, references and academic transcripts as personal information covered by the Australian Privacy Principles.
That changes the purchasing conversation. You need controls for people who never become employees, including purpose limits, restricted access and deletion or de-identification when information is no longer required.
Ask for evidence of operational controls
- Criterion — What good looks like — Red flag
- Privacy and APP compliance — Purpose limits, role-based access and documented deletion or de-identification — One shared login and no retention rules
- Security controls — Encryption, MFA, least-privilege access and audit logs of CV views and exports — No audit log and no alert for bulk downloads
- Consent handling — Representation approval recorded per role before submission — Consent kept as a free-text note
- Explainable matching — Score shown beside its evidence, with human overrides logged — Score with no reason, or overrides not recorded
- Data sources — Named, documented sources with links back to the original advertisement — Vague claims about where candidates come from
- Integration — API or export to a CRM and reporting tools — Data that cannot be exported
- Pricing — Published per-user or per-plan price — Price only available after a sales call
Treat pricing opacity as a commercial warning rather than evidence of technical failure. Ask what imports, API access, storage and exit exports include before comparing plans.
The OAIC recorded 527 notified breaches in January–June 2024, with cyber-security incidents accounting for 38% of notifications, in its notifiable data breaches report and APP 11 discussion. Ask for incident-response procedures and evidence that they're tested, alongside tenant isolation, encryption and access-control documentation.
Buying discipline: A security webpage describes intentions. Demonstrable permissions, logs and response procedures show what your team can actually inspect.
Test withdrawal and reuse
The Administrative Review Tribunal's recruitment privacy statement illustrates future-vacancy and merit-pool handling with candidate choice. Don't interpret that as blanket authority for your agency to reuse every imported profile.
Require recorded consent and an opt-out mechanism appropriate to the proposed reuse. The vendor should demonstrate how withdrawal or changed preferences affect matching, cached records and onward disclosure.
Load three authorised real CVs, withdraw one candidate and check search results, pipeline views and exports. An audit history may need to remain, but the withdrawn candidate must be clearly distinguished from someone available for representation. Finally, export the trial records and confirm that decisions, attachments and approval histories are complete and readable.
Pick a Tracker Before Your Next Government ICT Round
A solo recruiter working through a panel needs a manageable pipeline, clearance fields and alerts worth acting on. Buying a complex configuration won't help if maintaining it takes attention away from candidate conversations.
An agency operating across panels needs shared records, permissions and reliable CRM exports. An operations manager should put particular weight on source reporting and the ability to reconstruct a decision without asking the original recruiter to remember it.
Turn the next assignment into a purchasing test
- List the live work. Record each active role's clearance requirement, location and closing date. Use the original government opportunity and agency advertisement together, preserving their references.
- Inspect the data structure. Confirm that clearance level and expiry sit separately from skills. A government technical architect with the right delivery background can still have an unresolved deployment condition.
- Run the authorised CV trial. Record what happened during matching, withdrawal and export. Keep the results as a purchasing record rather than relying on recollection after the demonstration.
- Challenge the approval control. Try to submit without recorded representation approval. Then change the opportunity and check that an earlier approval isn't silently treated as permission for unrelated work.
Choose the platform that passes your actual workflow tests, not the one with the busiest dashboard. Evaluate any product you're considering against the same criteria, and treat advertised capabilities as claims to verify during the trial.
The next useful action is to take a live government ICT assignment and build its decision record before applications arrive. That exposes missing fields and unclear responsibilities while there's still time to fix them.
For Australian Government ICT discovery, erecruit connects procurement opportunities with panel-agency job advertisements and offers CV matching, pipeline tracking and representation-approval tools. Use its job and opportunity search to identify a live assignment, then test its tracking workflow against the evidence, consent and clearance checks above.
