Applicant tracking system: what it does, and what it does not decide

An applicant tracking system is the system of record for your hiring. It collects applications into one place, holds the stage every candidate is at, and keeps the trail of who said what. If more than one person touches a pipeline, you should own one, and this page starts with what to look for. What an ATS does not do is read. It stores and routes applicants, it does not decide, so if the reason you are searching is that six hundred people applied and nobody has had time to look at them, the software will hand you a tidier queue of the same six hundred.

What an applicant tracking system actually does

Strip away the feature grids and an ATS does four jobs. Everything else in the category is a variation on them.

One pipeline, many sources

Applications from your careers page, the job boards, referrals and agency submissions land in a single list per role, deduplicated, instead of in four inboxes belonging to three people.

Stage and ownership

Every candidate has a stage and a person responsible for moving them. This is the mechanism that stops a strong applicant sitting untouched for three weeks because everyone assumed somebody else had it.

A structured record

Notes, scorecards, interview feedback and the reason for a rejection attach to the candidate rather than to somebody's memory. This is also the part that matters if a hiring decision is ever questioned.

Reporting on volume and flow

How many applied, where they came from, where they stall, how long each stage takes. It reports the shape of your funnel accurately, which is a different thing from telling you whether the people inside it are any good.

What an ATS does, next to the screening work

These two are not competitors and this table is not a scoreboard. One is software you should probably own. The other is work somebody has to do inside it.

Dimension	An applicant tracking system	The screening work
What you buy	Software. One place where applications, stages and decisions live.	Judgement. Somebody deciding which applicants are worth your calendar, and able to say why.
Cost structure	A subscription, usually scaling with seats or with hiring volume, payable whether or not a role closes.	A flat engagement covering the roles you have open.
Incentive alignment	Clean. The vendor is paid for the seat and has no stake in who you hire or what you pay them. That is a genuine advantage software holds over any placement fee.	A flat fee earns nothing from a larger offer, which is the same alignment arrived at from the other direction.
Capacity	Unlimited storage and zero reading. It will hold ten thousand applicants as easily as ten, and will not read one of them.	Finite and explicit. Somebody reads, calls and verifies, and the hours that takes are the real constraint in hiring.
Continuity	Excellent as a record. Every application and decision stays searchable long after the people involved have left.	The bar itself carries forward, so a rejection this month changes how the next batch is screened.
What it structurally cannot do	Decide. Keyword filters and knockout questions match text the candidate wrote, and candidates learn to write whatever the filter rewards.	Replace your system of record. The decision trail still belongs in your ATS, and that is where it should stay.

If your ATS reports look healthy and hiring still feels stuck, the constraint is hours rather than software. Put your own funnel numbers through the hiring efficiency analyzer and look at where the time actually goes.

Who should buy an ATS, and what to check first

A spreadsheet is a system of record that lies quietly. If more than one person touches a pipeline, buy the software. Before you do, check these five, because they are what teams regret afterwards rather than anything on the feature grid.

Can a hiring manager leave feedback without a paid seat and without a training session. If feedback needs a licence, feedback will arrive by email and the record will be wrong within a month.
Does it publish to the boards you actually use, in the countries you actually hire in, without a separate integration invoice.
Does scheduling happen inside it, including the reschedules. Scheduling is where pipelines lose days, and a tool that logs interviews without booking them has moved the work rather than removed it.
Can you export everything, including notes and rejection reasons. Candidate history is the one hiring asset that compounds, and it should never be hostage to a renewal.
Do the stages match how you already decide. Configuring a tool around a process you do not actually run produces accurate reports about fiction.

The three things an ATS will not fix

These are not gaps in any particular product. They follow from what software is.

Volume: An ATS makes an applicant pile navigable. It does not make it smaller and it does not add anybody to read it. A role drawing hundreds of applicants has an hours problem, and a tidier queue can make that worse by rendering the backlog visible without making it shorter.
Filtering that survives contact with candidates: Keyword matching and knockout questions operate on text the applicant wrote and can edit. Anything a filter rewards becomes something applicants learn to include, so over time the filter stops selecting for the thing it was built to select for and starts selecting for familiarity with filters.
The reason a good applicant was passed over: The system records that somebody was rejected at screening. Whether that was right is not in the data, and no report will surface the person you should have called. That is a judgement question, and it is the expensive one.

The figure worth holding against your own ATS reporting is how many of the people you actually meet become the hire. Ours, with the sample it comes from and the conditions on it, is published rather than asserted.

Where a talent acquisition function sits relative to your ATS

The function is the reading, calling and scoring that has to happen between an application arriving and a hiring manager opening their calendar. Software holds the record of it.

The brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role, so screening runs against the job rather than against the posting text.
Applicants are screened on 40+ signals, called and verified, and scored against the role, so what reaches a hiring manager is a decision with its reasoning attached rather than a queue.
Each rejection changes how the next batch is read, which is the one thing a static filter cannot do.
The decision trail belongs in your system of record, alongside the audit trail and the reporting you already run.

Continuity1 is not an applicant tracking system. It does not store your pipeline, it is not somewhere to configure stages, and nothing here replaces the software. If you do not have an ATS, buy one. Treat this page as the honest account of what you will still be holding once you have.

How Continuity1 runs this funnel

The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.

The first figure is the reading that has to happen somewhere. An ATS is where the record of it lives, and it is not capacity to do it.

2 per 100: Profiles reviewed that reach your shortlist; The industry rule of thumb is 8 to 12. We send 2, and the filtering never lands on your calendar.; 4 Corner Resources
1 in 3: Shortlisted candidates you meet who become the hire; Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.; Continuity1 tracked engagements
~3: Interviews your team sits in, per hire; Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.; Ashby talent-trends report
20 to 49%: Shortlist-to-interview rate over one engagement; The industry curve points the other way; interview load keeps rising.; Continuity1 tracked engagement

Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.

You review a scored shortlist and make the calls. The filtering never lands on your calendar.

Share a role See the workings and the citations

Questions buyers ask

Does an applicant tracking system screen candidates?

It filters. Filtering and screening get used interchangeably and they are different jobs. A filter matches strings in a document the candidate wrote. Screening is reading, calling, and forming a view you can defend. An ATS runs the first and records the second, and buying one in the belief that it does the second is the most common disappointment in the category.

Will an ATS reduce our time to hire?

It reduces coordination loss, which is real and worth having. Candidates stop falling through gaps, feedback stops living in inboxes, and scheduling stops being a chase. It does not reduce the time somebody has to spend reading applications, and on high-volume roles that is the larger share of the delay.

We have an ATS and hiring is still slow. What now?

Look at where candidates sit longest. If the wait is between application and first human contact, the constraint is reading capacity and no configuration change will move it. If the wait is between screen and interview, the constraint is calendars. If the wait is after the final round, the constraint is a decision nobody wants to own, which is not a tooling problem at all.

Should a small team buy an ATS or bring in recruiting help first?

They answer different sentences. The tool answers "we keep losing track of people". Recruiting capacity answers "nobody has read these". Teams that buy the tool for the second sentence end up with a well organised backlog. Work out which sentence is yours before spending on either.