ATS means applicant tracking system.
An applicant tracking system is software that organises applicants and their applications throughout hiring. For an employer, its central job is to connect a person to a role, show where that application stands, and preserve the work behind the next decision. Oracle’s ATS overview describes the same core category: tracking candidates through recruiting and hiring.
A useful way to think about it is a shared hiring record. The recruiter can see which applications need review. A hiring manager can find the context needed for an interview. The team can record why it moved an application forward or closed it, instead of reconstructing the story from a spreadsheet and several inboxes.
This guide is for employers choosing or adopting recruiting software. It is not a guide to making a CV “beat” an ATS. Systems differ in the features they include, and the presence of an ATS does not tell an applicant whether a particular employer uses automated ranking or rejection.
How an ATS fits into a hiring workflow.
The following example follows a fictional in-house team filling a customer support role. It is an illustrative process, not a customer case study or a promise that every system includes every step.
- 01 / Define
Agree on the role.
The hiring manager and recruiter define responsibilities, required evidence, interview stages, and the decision owner before publishing.
- 02 / Publish
Open the application route.
The team previews the role and application form. A test submission confirms that applications reach the expected job and queue.
- 03 / Review
Review each application.
The recruiter compares the application with the agreed requirements, records relevant notes, and assigns a next action.
- 04 / Evaluate
Collect interview evidence.
Interviewers evaluate the same job-related criteria. The team records examples from the interview and unresolved questions.
- 05 / Decide
Record the outcome.
The decision owner reviews the evidence and records an outcome with a reason. Candidate communication has an explicit owner.
- 06 / Reconcile
Close the loop.
The team checks outstanding applications, confirms accepted outcomes, and reviews its records against its own retention process.
The software can make this work easier to find and coordinate. The team still needs to decide who owns each step, which evidence matters, and what a timely response looks like. Adding more stages without that agreement can make an unclear process harder to operate.
ATS, recruiting CRM, and a spreadsheet solve different problems.
| Tool | Best starting question | What to check |
|---|---|---|
| Spreadsheet | Can one owner maintain a simple list reliably? | Stage consistency, duplicate records, access control, and how decisions reach the rest of the team. |
| Applicant tracking system | Who has applied to this role, and what happens next? | Application history, job-specific stages, evaluation, permissions, and the actual package limits. |
| Recruiting CRM | Who should we build a relationship with for future hiring? | Relationship history, sourcing context, follow-up ownership, and how a prospect becomes an applicant. |
| HR information system | How do we manage people after they join? | Which employee processes it handles and what data, if any, can move from the recruiting system. |
Product categories can overlap. An ATS may include talent pools or onboarding tasks; that does not establish that it replaces a dedicated CRM or every employee-management process. Verify the specific workflow you need. Our recruiting CRM guide explores the relationship-management side in more detail.
Where the software helps, and where it needs a team.
Shared context can reduce repeated coordination.
When the application, notes, and next action live together, a colleague has less context to reconstruct. Check this with a handover: can another operator understand an application without calling its owner? That is more useful evidence than a long feature list.
Consistent stages make a queue easier to review.
Agree what “screening” and “interview” mean before comparing counts. A report becomes misleading if one recruiter moves an application when an interview is booked and another moves it after the interview is complete. An ATS stores the events; your team supplies the definitions.
Software does not establish the quality of a hiring decision.
Interview questions, criteria, evidence, and a reviewable decision process still matter. A score without context can conceal disagreement. If a system offers AI summaries or ranking, ask what information it uses and how a person checks the output before acting on it.
Availability and integration are separate questions.
A feature shown in a demonstration may belong to a different package or depend on configuration. Check actual access, the setup required, supported languages, and who provides support. Confirm imports and exports using your proposed fields; do not assume that a CSV template establishes an available importer.
For TiLab specifically, Free supports two operators and five concurrent jobs: a plain ATS for a small hiring workload. Evaluate Free on what it includes today, and check what Basic and Growth add before planning around a limit. See the Free ATS guide and the pricing page.
Choose around a few observable requirements.
- Describe the workload. Count the people operating the system and the roles open at the same time. Include seasonal peaks and confidential hiring.
- Pick the three handovers that cause friction. For example: an applicant reaches review, a recruiter hands an application to a hiring manager, and a decision is recorded.
- Define a pass condition for each handover. “The hiring manager can find the agreed criteria and submit feedback” is testable. “Better collaboration” is not yet a test.
- Test with synthetic data and intended roles. Include an excluded user as well as someone who should have access. Confirm the package and configuration used.
- Record gaps alongside the score. A high average should not hide a mandatory requirement that failed or a workflow no one tested.
Use the evaluation scorecard to turn those tests into a decision record. For a regional rollout, also test names, job locations, languages, and time zones that reflect your team’s work. A translated marketing page does not establish a translated product interface or local support coverage.
A useful first-week test.
Choose one representative role and create five synthetic applications. Ask the recruiter to review them, ask a future collaborator to complete the expected handover, and record one forward decision and one decline. Then reconstruct the sequence from the stored records.
At the end of the exercise, answer four questions: can the team find the next action, explain the stage, identify the decision owner, and recover the relevant evidence? Log any gap before bringing real candidate information into the new process.
If the workflow fits, use the migration kit to plan data cleanup, field mapping, a small pilot, and a controlled cutover. A team starting with one well-defined workflow has something concrete to improve.