Applicant Tracking System

Category Description

Applicant tracking software helps organizations manage the end-to-end process of hiring: collecting and organizing job applications, moving candidates through defined evaluation stages, coordinating interviews, and communicating with applicants. The core value proposition is replacing ad-hoc tracking (spreadsheets, email threads, shared folders) with a structured, collaborative system of record that keeps hiring teams aligned and candidates moving efficiently through the pipeline. These products typically serve as the operational backbone of a company's recruiting function, from the moment a job is posted to the moment an offer is accepted.

Example Implementations

Lever
Breezy HR
Workable

Target Audience

Small to mid-sized businesses — typically 10 to 500 employees — that are hiring actively enough to outgrow spreadsheet-based tracking but are not large enough to need an enterprise HRIS suite. Primary users are HR managers, recruiters, and talent acquisition specialists who manage the day-to-day pipeline, with secondary users being hiring managers who review candidates and provide feedback but are not full-time recruiters. The software is used in-house (not by staffing agencies) and is expected to support anywhere from a handful of simultaneous open roles to a few dozen.

Core Requirements

Job requisition management: Users must be able to create job openings within the system, specifying at minimum a job title, department, location (including a remote option), and employment type (e.g., full-time, part-time, contract). Open jobs must be listable and filterable. Jobs must be closeable or archivable without permanent deletion.
Customizable hiring pipeline: Each job must support a pipeline of stages representing the candidate's progress through the hiring process (e.g., Applied, Phone Screen, Interview, Offer, Hired, Rejected). Administrators must be able to define, rename, reorder, and delete stages. The system must support at least one distinct pipeline configuration per job or per job template.
Candidate profile and application storage: Each candidate must have a profile that stores their personal contact information, resume or CV file, application date, and current pipeline stage. Candidate profiles must persist beyond the lifecycle of a single job and be searchable. When a resume is uploaded, the system must compute and display a match score between the resume and the job posting, using either keyword matching or semantic (embeddings-based) similarity; the match score must be visible on the candidate profile and usable as a sort or filter criterion within the pipeline.
Application form customization: Hiring teams must be able to add custom questions to the application form for a given job, beyond the standard resume/contact fields. Custom questions must support at minimum: short text, long text, single-select (dropdown or radio button), and yes/no types; questions must be configurable as required or optional. This mechanism — rather than resume parsing — is the required approach for capturing structured qualification data (e.g., years of experience, specific skills, EEO fields) from applicants.
Application intake via career page: The system must provide a hosted, publicly accessible career page listing open jobs. Each job listing must have a unique URL and an application form that candidates can complete without an account. The career page must be configurable with at minimum a company name and logo.
Multi-board job posting: Users must be able to distribute a job posting to at least 3 external job boards (e.g., Indeed, LinkedIn, Glassdoor) from within the application. The system must aggregate inbound applications from these boards into the candidate's pipeline, regardless of source.
Candidate stage management: Users must be able to manually move candidates between pipeline stages using a drag-and-drop or equivalent interface. The system must display candidates grouped by stage, and must show the candidate's current stage and history of stage transitions.
Candidate sourcing and manual entry: Users must be able to manually add candidates to a job pipeline (i.e., without requiring the candidate to submit an application through the career page). At minimum, this requires entering a candidate's name, email, and optionally a resume file.
Collaborative candidate evaluation: Multiple team members must be able to leave structured notes or scorecards on a candidate profile. At minimum, the system must support a text comment and a rating (e.g., thumbs up/down, 1–5 stars, or a defined set of options). Team members must be able to see each other's evaluations. Comments must be timestamped and attributed to the reviewer.
Email communication with candidates: Users must be able to send emails to candidates directly from within the application, using the candidate's stored email address. The system must support email templates that can be reused across candidates and jobs. Outbound emails must be sent from the application's own email infrastructure (not via Gmail or Outlook integration) with a reply-to address that routes through the application. When a candidate replies, the reply body must be stored on the candidate's profile and must trigger an in-app notification to the user who sent the original email; the notification must include the body of the reply. The application may optionally support allowing the original sender to reply to the candidate by replying to the reply-to address from their email client, with that reply routed through the application to the candidate in the same fashion. Sent and received emails must be logged on the candidate's profile.
Automated candidate communications: The system must support configuring at least one type of automated email trigger — for example, sending an acknowledgment email when a candidate applies, or sending a notification when a candidate is moved to a specific stage. Automation must be configurable per pipeline stage and must not require manual action from a recruiter to execute once configured.
Candidate disqualification and rejection: Users must be able to mark candidates as rejected or disqualified at any pipeline stage. Rejected candidates must be distinguishable from active candidates in the pipeline view. The system must support sending a rejection email to the candidate, optionally using a template.
Candidate search and filtering: Users must be able to search across the candidate database by name and keyword. Within a job pipeline, users must be able to filter candidates by at minimum pipeline stage and date applied.
Team member access and permissions: The system must support inviting multiple team members to the application. At minimum, three permission levels must exist: an administrator who can configure the system, a recruiter or hiring manager who can manage candidates and jobs, and a limited reviewer who can view candidates and submit evaluations but cannot modify job or candidate data. Access must be controllable per job or globally.
Offer stage tracking: Users must be able to advance a candidate to offer-related pipeline stages — at minimum: verbal offer extended, written offer extended, and offer accepted. These stages must be distinct, selectable states within the hiring pipeline and must be visible on the candidate's profile. No structured offer data fields (compensation, start date) are required; the stage label itself is the record of offer progress.
Basic recruiting analytics: The system must provide at minimum the following metrics, viewable by an administrator: total number of applications per job, number of candidates at each pipeline stage per job, and time elapsed between key stages (e.g., time to first response, time to hire). Metrics must be filterable by date range and by job.
Candidate source tracking: The system must record where each candidate originated (e.g., which job board, referral, career page direct). Source data must be visible on the candidate's profile and must be aggregated in the analytics view so that hiring teams can see which sources are producing the most applicants.

Cross-Cutting Requirements

Multi-tenancy: The application must support multiple independent organizations (tenants), each with isolated data.
Authentication: Users must authenticate with email/password at minimum. SSO and OAuth are not required.
Role-based authorization: The application must support at least three roles — administrator, manager, and standard user — with distinct permission levels appropriate to the category.
Data persistence: All user data must be persisted across sessions in a database.
Web application: The application must be accessible via a web browser. Native desktop or mobile applications are not required.
Concurrent users: The application must support multiple users within the same tenant using the application simultaneously without data corruption or loss.
Responsive design: The web application must be usable on both desktop and mobile browsers. A native mobile app is not required.

Scope Boundaries

Candidate relationship management (CRM) / talent pipeline for passive candidates is not required. Nurturing passive candidates who have not applied to a specific role, building long-term talent pools, and running outreach campaigns to non-applicants are not required.
Native video interviewing is not required. Integrated asynchronous or live video interview recording within the platform is not required; linking to a video conferencing tool (Zoom, Google Meet) for scheduling purposes is sufficient.
Interview scheduling is not required. Sending calendar availability links, self-scheduling flows, and generating calendar invitations are not required.
AI-powered candidate scoring or matching is not required. Algorithmic ranking of candidates against job requirements beyond the keyword/semantic match score required in req 3 is not required.
AI resume screening or automated shortlisting is not required. Auto-advancing or auto-rejecting candidates based on AI-evaluated criteria is not required.
Resume parsing is not required. Automatically extracting structured data from a resume file and pre-filling candidate profile fields is not required. The required mechanism for capturing structured data is the customizable application form (see req 3).
Gmail or Outlook integration for email is not required. Syncing sent or received emails with a recruiter's external email client is not required. The application must handle outbound email natively and route replies back through its own infrastructure (see req 9).
Chrome extension or browser-based sourcing tool is not required. A plugin for sourcing candidates directly from LinkedIn or other sites is not required.
Employee referral program management is not required. Tracking referral bonuses, referral submission portals, or referral workflows are not required.
Background check integration is not required. Native or integrated background screening workflows are not required.
Assessment or skills testing integration is not required. Connecting to third-party assessment platforms or delivering in-app candidate assessments is not required.
Offer letter generation with e-signature is not required. Producing a formatted offer document and capturing a legally binding digital signature is not required.
Structured offer data capture is not required. Recording compensation amount, start date, or other offer terms within the ATS is not required; the offer pipeline stages (verbal offer, written offer, accepted) are sufficient.
Onboarding workflows are not required. Post-hire onboarding tasks, document collection from new hires, and new hire checklists are not required.
HRIS or payroll integration is not required. Syncing new-hire data to an HR information system or payroll provider is not required.
DEI (diversity, equity, and inclusion) analytics is not required. Reporting on demographic data, diversity of applicant pools, or blind hiring features are not required.
EEO / EEOC compliance reporting is not required. Generating government-mandated equal employment opportunity reports is not required, though EEO fields may be included as custom application questions.
Multi-language career page is not required. Displaying the career page or application form in more than one language is not required.
Custom career page with full branding control is not required. Beyond a company name and logo, extensive visual customization of the career page (fonts, layout, CSS, custom domains) is not required.
Candidate self-service portal is not required. A logged-in portal where candidates can check their application status, upload additional documents, or message the recruiter is not required.
SMS / text messaging with candidates is not required. Sending and receiving text messages with candidates natively or via integration is not required.
Staffing agency or client portal features are not required. Multi-client management, client-facing dashboards, or billing workflows for external staffing use cases are not required.
Headcount planning or job requisition approval workflows are not required. Budget approval chains, headcount forecasting, or requisition sign-off workflows before a job is opened are not required.
Native mobile application is not required. A dedicated iOS or Android app is not required; mobile responsiveness of the web application satisfies this.
Two-way calendar sync is not required. Real-time bidirectional sync of recruiter calendar events with an external calendar system is not required.
Advanced workflow automation beyond stage-triggered emails is not required. Complex multi-step automation sequences, conditional branching logic across multiple triggers, or automation builders with drag-and-drop logic are not required.
Job posting to more than 3 external boards is not required. Integration with more than 3 job distribution channels is not required.

Spec Metadata

Version: 1.0
Created: 2026-03-17
Last Updated: 2026-03-17 (v1.1)
Status: Draft