How to set up hiring stages in an ATS for structured recruiting

Hiring stages are the spine of your recruiting process. Set them up well and your ATS can show where candidates are stuck, trigger the right tasks, collect structured feedback and give candidates clearer updates.

Set them up badly and the software becomes a prettier spreadsheet. Recruiters skip stages, hiring managers forget feedback, reports stop matching reality and candidates sit in limbo because nobody owns the next step.

This guide explains how to set up hiring stages in an ATS for structured recruiting. It is a setup guide, not a best-of list, so the aim is to help you design the workflow before you worry about vendor demos.

What are hiring stages in an ATS?

Hiring stages are the steps a candidate moves through from sourcing or application to hire, rejection, archive or offer outcome. In most ATS products, each candidate belongs to one stage on one job at any given time.

A stage name is the label your team sees, such as Recruiter Screen or Final Interview. A stage type or stage group is the reporting category behind it, such as Applied, Interview or Offer.

That distinction matters. Workable recommends customising stage names while mapping them to standard stage types for reporting, because reports need consistency even when roles have different workflows.

Stages are different from interviews, scorecards and candidate-facing labels. A stage says where the candidate is in the process; an interview or scorecard says what evaluation happens there; a candidate-facing label says what the candidate can see.

The upside of a clear stage model is better ownership and cleaner reporting. The catch is that every extra stage creates admin, so each one has to earn its place.

What hiring-stage template should you start with?

Start with a simple template, then remove stages that do not fit the role. A sensible baseline is Sourced or Referred, Applied, Recruiter Screen, Hiring Manager Review, Skills Assessment or Take-Home, Structured Interview, Final Interview, Reference or Background Check, Offer, Hired and Rejected or Disqualified.

This is longer than a founder-led process needs. If one person screens CVs, interviews and makes the offer, three or four live stages may be enough.

Add a stage only when it changes the work. Good reasons include a new owner, a different evaluation method, a required scorecard, an approval, an automation, a candidate communication point or a reporting milestone.

Workable frames hiring broadly around planning, attracting candidates, selecting candidates and offering the job. Your ATS stages should sit inside that wider process, rather than pretending every role needs the same detailed funnel.

For entry points, use separate Sourced and Applied stages if you want to report outbound candidates separately from inbound applicants. If you do not source proactively, Applied may be enough.

For endings, keep Hired separate from Rejected, Disqualified or Archived. It sounds obvious, but mixing final outcomes makes conversion reporting a mess.

How do you set up hiring stages in an ATS?

Start with the role’s actual decision points, not a generic funnel copied from another company. Ask what must happen before a candidate can move forward, who owns that decision and what evidence they need.

Keep the pipeline short enough that people will maintain it. A precise 14-stage workflow is worse than a seven-stage workflow if recruiters leave half the candidates in the wrong place.

Map custom labels to standard reporting categories where the ATS supports that structure. This lets Sales Interview, Engineering Panel and Portfolio Review roll up into a broader Interview category without flattening the real process.

Attach scorecards, interview kits or evaluation forms to the stages where decisions are made. Paychex says an ATS can centralise documentation and create an audit trail, but that only works if feedback is captured at the right step.

Add automations after the workflow has settled. Automated emails, reminders and candidate movement save time, but they can also spread a bad process faster if your stage rules are unclear.

Use stage-ageing alerts or SLA reminders where candidates commonly stall. Greenhouse supports stage alerts for candidates who have been in a stage too long, which is useful if your bottleneck is feedback delay rather than sourcing volume.

Test what candidates can see. If your ATS has candidate-facing status updates or portals, make sure internal labels such as Hiring Manager Hold do not appear without context.

How should Greenhouse users build stages for structured hiring?

Greenhouse is strongest if you need formal structured hiring across many roles and teams. ATSLab ranks it #19 overall with an internal price marker from about $6k, so it is usually an enterprise fit rather than a small-team default.

Greenhouse uses Interview Plans to define the hiring flow for a job. Each plan includes candidate stages and evaluation details such as focus attributes and interview kits.

Every Greenhouse interview plan starts with Application Review and ends with Offer by default. The stages between those defaults are configurable, so teams can model panels, exercises and approvals without changing the basic endpoints.

Admins can add stages by choosing Edit stages and Add stage, then creating a new stage, selecting one from the Greenhouse library or copying a stage from another job. Copying saves time, but copying a messy plan also copies its reporting problems.

Greenhouse explicitly warns that too many inconsistent labels can hurt cross-job reporting. Using both Face-to-face and In person as separate labels may feel harmless, but it splits the data unless you standardise the naming.

For candidate communication, MyGreenhouse Stages lets teams map internal stages to standard candidate-facing stage names, add descriptions and show candidates where they are. The limitation is that somebody still has to maintain the internal workflow accurately.

How should Ashby users handle interview plans and grouped reporting?

Ashby is a good fit if your team is scaling and wants ATS, CRM and analytics in one system. ATSLab ranks Ashby #2 overall and best for scaling teams, with All-In-One Foundations listed at $400/month and annual commitments eligible for a 10% discount.

Ashby recommends setting up interview plans, interviews and schedule activities together. That matters because the pipeline, feedback process and scheduling prompts are connected in the hiring workflow.

Ashby interview plans are split into sections such as Lead, Application Review, Active, Offer and Completed. This gives teams structure without forcing every job to use identical stage names.

Only one interview plan can be assigned to a job at a time, and every job requires one. That keeps each role clear, but it also means teams need to choose the right plan before candidates start moving through it.

If you have multiple workflows, Ashby recommends grouped interview plans. Grouped plans map job-specific stages into consistent reporting groups, which helps a scaling team compare roles without banning useful local differences.

Ashby added Multiple Offer Stages in 2026 for post-offer steps such as background checks, reference checks, physicals and pre-hire training. That is useful for complex hiring, but small teams may not need that level of offer tracking.

How should Breezy HR users set up visual pipelines?

Breezy HR is the best starting point if a small team wants a capable visual ATS without per-seat fees. ATSLab ranks Breezy HR #1 overall, and Breezy’s Startup plan is $157/month on annual billing or $189/month on monthly billing.

Breezy treats each step in the recruiting process as a stage, and each stage appears as a column in the pipeline. That makes it easy for founders and hiring managers to see where candidates are at a glance.

Breezy’s default pipeline stages are Applied, Feedback, Interviewing, Made Offer, Disqualified and Hired. The defaults are simple enough for many small teams, but they may be too blunt if you need separate recruiter screens, panel interviews and reference checks.

Paid Breezy customers can customise pipeline stages and set stage actions. Growth, Business and Pro customers can create and customise multiple pipelines, which matters if sales, engineering and operations hire in different ways.

The main setup warning is deletion. Breezy says deleting a stage with candidates in it moves those candidates to a temporary Missing Stage until they are manually reassigned, so clean up live pipelines with a migration plan.

Breezy also offers Applicant Insights as a paid AI-powered Breezy Intelligence feature, with 0–10 match scores and rules that can move candidates based on score. That can speed up triage, but automated movement needs clear review rules before it affects candidate outcomes.

How many hiring stages should you use?

Use as few stages as you can while still showing the real work. For low-volume or founder-led hiring, a short pipeline is easier to maintain and less likely to drift away from reality.

A five-stage process could be Applied, Screen, Interview, Offer and Hired or Rejected. It will not satisfy a regulated enterprise process, but it may be enough for a small company hiring one or two roles at a time.

Add granularity when it changes ownership or evaluation. Recruiter Screen, Hiring Manager Review and Panel Interview should be separate if different people act at each point and different feedback is required.

Avoid creating separate stages for every internal status update. Labels such as Maybe, Waiting, Follow-up and Needs Chasing usually become dumping grounds unless they trigger a real action.

If your ATS supports stage groups, use them. They let a technical role have System Design while a marketing role has Portfolio Review, with both rolling up to Interview for reporting.

Which ATS plan features matter for structured recruiting?

The first feature to check is support for multiple pipelines or interview plans. You need this if departments hire differently, but a single standard pipeline is simpler if every role follows the same path.

The second is stage automation. Emails, tasks, reminders, scorecards and candidate movement can reduce manual work, but automation should support human decisions rather than replace structured evaluation.

The third is structured feedback. Scorecards, interview kits and evaluation forms matter more than cosmetic pipeline settings because they decide whether hiring decisions leave a useful record.

The fourth is stage-ageing and stalled-candidate reporting. These features are useful when candidates wait too long for feedback, but they will not fix a team that ignores its own SLAs.

The fifth is candidate-facing status. Candidate portals and public stage names can improve clarity, but they require careful mapping so internal workflow labels do not confuse people.

The sixth is offer-stage flexibility. If your process includes references, background checks, approvals or pre-hire training, make sure the ATS can model those steps without hiding them in notes.

AI screening and scoring can help with volume if the rules are controlled. Breezy’s Applicant Insights can sort, filter and move candidates by AI score, but teams should be cautious about automating rejection or advancement without review.

Which ATS fits your stage-design need?

Choose Breezy HR if you are a startup or small business that wants a visual pipeline, straightforward stage customisation and transparent entry pricing. It is ATSLab’s #1 ranked tool overall, but complex enterprise governance is not its main use case.

Choose Ashby if you are scaling hiring volume and need structured interview plans, grouped reporting and stronger analytics. It costs more than low-price small-business tools, so it makes most sense when reporting quality and workflow consistency are already painful.

Choose Greenhouse if you are an enterprise team that wants mature structured hiring, interview kits, scorecards, candidate-facing stage mapping and workflow governance. The trade-off is price and implementation weight, with ATSLab recording it from about $6k and the vendor using custom pricing across Core, Plus and Pro plans.

If you are still choosing an ATS, design your ideal stages before demos. A vendor can look impressive in a generic walkthrough, then struggle with the exact approval, interview and reporting structure your team needs.

Common stage-setup mistakes to avoid

The first mistake is building the pipeline around recruiter habits instead of candidate decisions. A stage should describe where the candidate is in the process, not where a recruiter last left a note.

The second is renaming stages without checking reporting impact. Greenhouse warns about inconsistent labels for this reason, and the same principle applies in any ATS that reports across jobs.

The third is adding automations too early. Wait until recruiters and hiring managers follow the workflow reliably, then automate the repeatable parts.

The fourth is deleting or heavily changing live stages without moving candidates first. Breezy’s Missing Stage warning is a good reminder that pipeline clean-up can create manual repair work.

The fifth is hiding offer steps in notes. If background checks, references or approvals decide whether someone starts, model them as offer stages or tasks where your ATS supports it.