Skip to content
Surhires

Australia ATS

Applicant tracking that carries the compliance fields

An agency pipeline has to survive twenty clients at once, and in Australia it also has to carry licensing and working-rights checks to the placement.

ATS software tracks a candidate from application through screening, submission, interview, offer and placement. Surhires runs that with stage machines you configure per client, coded outcome reasons rather than free text, and labour-hire licence and working-rights fields that can be required before a placement is allowed to close.

By Surhires Editorial · Published · Reviewed

The agency pipeline is not the corporate pipeline

In-house tracking systems assume one employer, one approval chain and one definition of a stage. An agency desk has a different client every few rows. One wants a formatted resume and a written summary. One wants three candidates presented together or none at all. One runs a technical task before any interview. One has an internal approval that adds a week and needs a stage of its own so the delay is visible.

Surhires lets the stage machine differ by client and by job type while the pipeline view stays consistent. A contract IT job might run sourced, screened, submitted, client interview, offer, contract signed, started. A permanent professional role might run longlist, screened, submitted, first interview, second interview, offer, placed, started.

The point of configurability here is not flexibility for its own sake. It is that a stage which does not match reality gets skipped, and a skipped stage means the pipeline report is wrong.

Submissions are records, not status flags

The moment that decides whether a desk bills is the submission, and most systems treat it as a status change. Here it is a record: which candidate, to which client contact, against which job, with which documents, at what rate or salary, on what date, and what came back.

That makes the two questions an owner actually asks answerable. How many submissions did this desk send last week, and what is the submission-to-interview rate per client? Both become reports rather than a spreadsheet somebody maintains on Friday afternoon.

It also protects the fee. A disputed introduction is a much shorter conversation when the record shows the date, the contact, the documents sent and the client's reply.

Licensing and working rights inside the stage machine

This is where an Australian agency pipeline differs from a generic one. Labour-hire licensing is state-based, so a firm placing across borders may sit inside more than one scheme, and a licence has an expiry that nobody notices until it has passed.

Licences are stored with jurisdiction, number, holder, issue date and expiry, with reminders ahead of the date. Working rights are recorded on the candidate as visa class, the conditions that matter, the expiry, and the date and outcome of the check you ran through the government verification service.

Both can be wired into the stage machine as required-at-stage rules: a candidate cannot be moved to placed until the working-rights check is on file, and a placement cannot close without a current licence for the relevant jurisdiction. That converts a policy into a field somebody has to complete, which is the only version of a control that actually holds under pressure.

  • Licence jurisdiction, number, holder and expiry stored as structured, reportable fields
  • Visa class, conditions, expiry and check outcome recorded against the candidate
  • Required-at-stage rules that block a placement without the check on file
  • Expiry reminders raised before the date rather than after the lapse

Outcomes are coded, not typed

When a candidate is rejected, the reason comes from a fixed list: failed technical screen, salary above budget, a better-qualified candidate selected, candidate declined, candidate accepted a counter-offer, role withdrawn. Free-text notes are still allowed; the coded reason is mandatory.

That is partly analysis and partly defence. Coded outcomes show you that one client rejects on salary in most cases, which is a conversation about the brief rather than about the candidates. And if a hiring decision is ever questioned, the record reconstructs what happened rather than offering an empty field and a vague memory.

Demographic data captured for equal-opportunity monitoring is held separately from the hiring record and is not visible to consultants, so it cannot influence a decision it exists to measure.

Interview coordination without the reply-all chain

Interview scheduling reads the panel's calendars, proposes slots, holds them, and sends the candidate a link. Reschedules update everyone rather than starting a new email thread. Reminders go out at a configurable interval before the slot through whichever channel the candidate agreed to, which on an Australian desk is frequently SMS or WhatsApp rather than email.

Feedback is captured on a scorecard rather than in a reply. Structured feedback is the only kind that compares across a panel and the only kind that supports a defensible decision afterwards. Interview kits give each interviewer the questions and the criteria rather than leaving the conversation to improvisation.

High-volume intake without losing the database

Board-led applicant flow produces volume, and volume is where a tracking system either builds a database or buries one. Bulk resume import parses a folder into structured records with duplicate detection running during the import. The Resume Screener normalises skills, seniority and location on the way in. AutoShortlist ranks an applicant list against the job with visible reasoning so a consultant reviews a ranked list rather than an inbox.

The Seek connector is in development rather than live, so today applicants arrive by email capture and bulk import. Posting to LinkedIn and Indeed ships now, and multi-board posting from a single form is in build for the Wave 1 release.

  • Bulk resume import with duplicate detection during the import, not afterwards
  • AutoShortlist ranking with the reasoning shown for each candidate
  • Coded disposition on every rejection so volume still produces usable data
  • Talent pools so a strong unsuccessful applicant is retained rather than lost

An audit trail that survives a question

Every stage change is immutable: who moved it, when, from what to what, and with which coded outcome. Notes can be edited; the stage history cannot be rewritten. Licence and working-rights fields carry their own change history with dates.

For agencies supplying government, health or resources clients, that trail is often exactly what procurement asks about. It is also what turns a disputed placement fee into a two-minute conversation instead of a fortnight of email archaeology.

What sits outside the tracker

Surhires is not an HRIS, a payroll system, a pay and bill engine, a background-check provider or an assessment platform. It records the placement, the rate, the margin and the fee and raises the placement invoice. Timesheets, award interpretation, superannuation and payroll run elsewhere.

The client portal, where a client reviews and dispositions submitted candidates themselves, is in build for the Wave 1 release rather than live. So is the Chrome extension. Australia is a supported market rather than a launch market: support runs on US Eastern hours, and Australian dollar pricing is an unconfirmed conversion.

What you get

Configurable stage machines

Pipelines defined per client and per job type while the reporting view stays consistent.

Submission records

Candidate, contact, job, documents, rate, date and outcome captured rather than a status flag.

Coded outcomes

Rejections recorded from a fixed list so patterns are reportable and decisions auditable.

Required-at-stage rules

A placement cannot close without the licence and working-rights checks on file.

Labour-hire licence fields

Jurisdiction, number, holder and expiry per licence, with reminders before the lapse.

Working-rights records

Visa class, conditions, expiry and the date and outcome of the check you ran.

Immutable stage history

Who moved a candidate, when, from what to what and why, with no rewriting after the fact.

Interview scheduling

Panel calendars read, slots proposed and held, reschedules propagated without a new thread.

Scorecards and interview kits

Structured feedback and set questions so a panel can be compared rather than averaged.

AutoShortlist ranking

An applicant list ranked against the job with the reasoning shown for each candidate.

Bulk resume import

Folder import parsed into structured records with duplicate detection during the import.

Separated demographic data

Equal-opportunity data held apart from the hiring record and hidden from consultants.

Talent pools

Strong unsuccessful applicants retained as a working list rather than lost at rejection.

Pipeline dashboard

Submissions, interviews booked and slipped, offers live and placements closed, from live records.

Questions recruiters ask

Can the pipeline differ for each client?

Yes. Stage machines are configured per client and per job type, so a client that runs a technical task before interview and one that wants three candidates presented together can each have a pipeline that matches reality. The reporting view stays consistent across them, which is what makes cross-client comparison possible.

Can we stop a placement closing without a working-rights check?

Yes, through a required-at-stage rule. The candidate cannot be moved to placed until the check is recorded with its date and outcome, and a placement can be blocked without a current labour-hire licence for the relevant jurisdiction. The product enforces the rule you configure; it does not perform the verification itself.

Does it post to Seek?

Not yet. The Seek connector is in development. LinkedIn and Indeed posting ships today and multi-board posting from one form is in build for the Wave 1 release. In the meantime applicants arrive through email capture and bulk resume import, both live, with duplicate detection running as the import happens.

Can clients review candidates themselves?

Not today. The client portal, where a client contact reviews submitted candidates and records a decision directly, is in build for the Wave 1 release. Until it ships, candidates are submitted by email from the record and the client's reply is filed against the submission, which keeps the audit trail intact.

How is equal-opportunity data handled?

Demographic data is stored separately from the hiring record and is not visible to consultants at all, so it cannot influence the decision it exists to measure. Outcome reasons are coded from a fixed list rather than typed, which means a reporting question about how decisions were made has a real answer.

What happens to unsuccessful applicants?

They stay in the database as structured records with a coded outcome, and strong ones can be added to a talent pool so the next matching brief surfaces them. In a market where the same candidates recirculate, treating a rejection as the end of the record is how agencies end up paying twice to find the same person.

See it against your own reqs

Bring one live role and three resumes. In twenty minutes you will see the match scores, the shortlist and the placement invoice that comes out the other end.