How to build an ATS hiring pipeline for multiple job openings

An ATS hiring pipeline is the stage-based process candidates move through from application or sourcing to offer, hire or rejection. For teams hiring across several openings, it also means the reusable talent pool they can return to when a similar role opens later.

That second part matters. A pipeline built only around one vacancy dies when the job closes, while a proper talent pipeline keeps qualified people, silver-medalist candidates and sourcing leads available for future roles.

This guide is about building that system inside an applicant tracking system. If you need the basic definition first, start with a general ATS explainer; here, the job is more specific: how to stop multiple openings turning into multiple messy processes.

What is an ATS hiring pipeline for multiple openings?

For multiple openings, an ATS hiring pipeline has two connected layers: a shared workflow and a reusable pool of candidates. The workflow tracks active hiring, while the pool keeps people organised for current or future roles.

The workflow layer is what most teams picture first. A candidate enters as sourced or applied, moves through review, interviews and offer, then ends as hired, archived or disqualified.

The talent-pool layer is easier to neglect. Pinpoint describes a talent pipeline as a living system teams return to when they hire, and JOIN defines it as qualified candidates for current or future roles.

The upside is continuity. You stop treating each job as a blank slate, but the downside is that your ATS needs clean tags, ownership and consent rules or the pool becomes stale and risky.

Why do multiple job openings break weak pipelines?

Multiple openings break weak pipelines because every hiring manager starts inventing their own process. One job has five stages, another has 14, and reporting becomes a manual clean-up job.

The damage shows up quickly. Recruiters cannot compare roles, leadership cannot read funnel reports, and candidates get different experiences depending on the department.

Workable’s own pipeline guidance gives a useful rule: create pipelines for types of jobs rather than one unique pipeline for every individual job. It also recommends designing a reporting pipeline first, so customised workflows still map to consistent reporting stages.

That does not mean every role must run identically. Executive searches, hourly hiring and engineering roles may need different steps, but those differences should sit underneath a shared reporting structure.

Start with one reporting pipeline

The first design decision is the reporting pipeline, not the job workflow. Define the common stages you want every role to report against before anyone customises steps by department, location or seniority.

A simple reporting pipeline might use Applied or Sourced, Review, Screen, Interview, Final, Offer, Hired and Archived. Those labels give leadership a shared view, even if the engineering team adds an assessment and the sales team adds a role-play.

Workable recommends building this reporting pipeline first for exactly that reason. The benefit is cleaner reporting, but the trade-off is that hiring teams must agree on shared language before configuring the ATS.

Keep the number of stages under control. Workable recommends 12 stages or fewer, which is a sensible ceiling because long pipelines are harder to maintain and easier to misread.

How many stages should an ATS hiring pipeline have?

Most multi-opening teams should use 8 to 10 active stages, with 12 as an upper limit. That leaves enough room for screening, interviews and offers without creating a stage for every small internal action.

A practical sample pipeline is: Sourced or Applied, Application Review, Shortlist, Phone Screen, Assessment, Hiring Manager Interview, Final Interview, Offer, Hired, and Archived or Disqualified.

That sample stays below Workable’s 12-stage recommendation. It also separates decision points from admin tasks, which keeps the board readable when several jobs are open at once.

Your ATS may start with a different default. Breezy HR’s default stages are Applied, Feedback, Interviewing, Made Offer, Disqualified and Hired, and paid plans can customise stages and add stage actions.

The upside of custom stages is precision. The downside is sprawl, especially if each manager adds personal steps that do not map back to reporting.

Build reusable pipelines by job type, not by requisition

The cleanest structure is to build reusable pipelines by role family or hiring motion. That usually beats making a fresh pipeline for every new requisition.

A startup might use one pipeline for sales roles, one for engineering roles and one for operations roles. A larger employer might split hourly location-based hiring, specialist corporate roles and executive searches.

Recruitment agencies may need client or discipline-specific pipelines. That can work well, but only if each client workflow still maps into common reporting stages.

Workable recommends creating pipelines for types of jobs rather than individual jobs. The benefit is consistency across several openings, while the limitation is that a rare senior role may still need a bespoke step.

Use exceptions sparingly. If every role is an exception, the ATS has become a prettier spreadsheet.

What ownership rules should you add to the pipeline?

Every stage needs a clear owner, especially when one recruiter is covering several roles. Decide who owns review, who books interviews, who gives feedback, and who approves offers.

A simple ownership model is recruiter for sourcing and review, hiring manager for shortlist and interviews, interviewers for feedback, and finance or leadership for offer approval. The benefit is accountability, but the downside is that unclear handoffs still cause delays.

Tags and filters matter once the open-role count grows. Use tags for role family, location, source, seniority, silver medalist status and future-fit notes, but avoid turning tags into a junk drawer.

Ashby is a good example of why scaled teams need more than a visual board. Its Candidate Pipeline view can show job considerations across open jobs a user can access, with filters including job, department, stage, tags and projects.

Ashby also supports bulk actions such as changing stage, archiving, emailing, enrolling in a sequence, transferring, considering for another job and sending data consent requests. That is powerful at volume, but it also raises the cost and process discipline required.

How do you build a reusable candidate pool?

Build the candidate pool alongside the active job pipeline, not after a role closes. Otherwise strong candidates disappear into archived jobs where nobody searches properly.

Start by tagging silver-medalist candidates, promising sourced leads and people who opted into future contact. Then add useful context, such as target role family, location, seniority and why they were not hired last time.

This is where the talent-pipeline idea becomes practical. The pool gives recruiters a starting point for future openings, but it only works if notes are factual, searchable and kept up to date.

Be careful with consent and retention rules. A reusable pool is valuable, but candidate data should not be kept or reused without a clear basis and internal policy.

Which ATS fits a multi-opening pipeline?

Breezy HR is the best fit if you are a startup or small business that wants a capable ATS without per-seat fees. ATSLab ranks it first overall, and its Startup plan is listed at $157 per month on annual billing.

The pricing model is a real advantage for small teams because Breezy HR paid plans include unlimited users, candidates and customer support. The catch is plan fit: Bootstrap is limited to one active position or candidate pool at a time, so it is a poor fit for multiple simultaneous openings.

Breezy HR paid plans can customise pipeline stages and add stage actions, while Growth, Business and Pro can create and customise multiple pipelines. That makes it stronger once you need reusable pipelines, but you should check the plan carefully before assuming every feature sits on Startup.

Ashby is the better fit if your team is scaling and needs ATS, sourcing, scheduling, analytics and cross-job pipeline control in one platform. ATSLab ranks it second overall, and Foundations is listed at $400 per month for up to 100 employees.

The strength is depth across structured hiring and reporting. The limitation is cost and plan complexity, because Plus and Enterprise pricing depends on company size, usage and commitment, and Ashby does not advertise a permanent free ATS plan.

Workable fits if your bottleneck is finding candidates rather than only tracking them. ATSLab ranks it fourth overall, and Standard is listed at $299 per month for the 1–20 employee bracket.

Workable’s Standard plan includes a candidate sourcing suite, ATS, report builder and unlimited active jobs subject to fair usage limits. The downside is that pricing is employee-count based, and several useful features sit behind add-ons or credits.

How much should you budget beyond the base ATS price?

Do not compare ATS options only by base subscription price. Multi-opening hiring often uses add-ons for sourcing, AI, texting, onboarding, assessments or interview tools.

Breezy HR’s Startup plan is recorded at $157 per month on annual billing, but extras can change the maths. Breezy Intelligence credits start at $30 for 100,000 credits, SMS/Text Messaging credits start at $41 per month, and Breezy Onboard starts at $49 per month.

Those add-ons may be worth paying for if they replace separate tools. The catch is that unused Breezy Intelligence credits are not refunded if a plan is cancelled, and credits can become another thing to track.

Workable’s Standard plan starts at $299 per month for 1–20 employees, and every paid account starts with 1,000 free Workable Agent credits. Workable Agent uses one credit per candidate worked by the agent, with listed bundles from $600 for 5,000 credits.

Workable also lists Standard add-ons including Texting+ at $89 per month, Video interviews+ at $109 per month, Assessments+ at $59 per month and Performance reviews+ at $39 per month. That gives flexibility, but the bill can rise beyond the headline price.

Ashby Foundations is $400 per month for up to 100 employees, with a 10% discount available for annual commitments. Advanced Scheduling and AI Notetaker are listed as optional add-ons, but Ashby does not publish public dollar amounts for those add-ons.

Where should AI fit into an ATS hiring pipeline?

AI should support specific pipeline jobs: sourcing, screening, routing, candidate communication or interview records. It should not be added as a vague feature requirement.

Workable says Workable Agent can search more than 400 million profiles, evaluate inbound candidates against up to 14 job criteria, and route candidates into a shortlist with logged, reversible actions. That is useful for sourcing-heavy teams, but it needs clear review rules.

Ashby’s AI Notetaker is more relevant to interview records and consent. Ashby introduced affirmative opt-in recording consent policies on 18 June 2026, including default policies, overrides and consent capture in application forms and scheduling workflows.

The practical rule is simple: involve legal or compliance teams before using AI screening, automated outreach or interview recording. Product controls help, but they do not replace your own policy.

The pipeline checklist before you configure the ATS

Before configuring software, write the pipeline on one page. Include the reporting stages, reusable role-family pipelines, owners, tags, candidate-pool rules and any AI or consent controls.

Then test it against three real openings. If a sales role, an engineering role and a location-based role all map cleanly into the same reporting view, the structure is probably sound.

If you are a small team, Breezy HR is the first tool to test because it ranks first on ATSLab and avoids per-seat fees. If you are scaling, Ashby is stronger for cross-job control; if sourcing is the pain, Workable deserves a close look.

The right ATS hiring pipeline is boring in the best way. It makes every open role comparable, keeps future candidates findable, and stops process design restarting with every requisition.