The Complete Guide to ATS Candidate Workflows
An ATS candidate workflow is the set of stages, owners and rules that move a candidate from first contact to placement. This guide shows how to design one, choose a workflow style, and log status changes so reporting works.
An ATS candidate workflow is the defined set of stages a candidate passes through, from first contact to placement or rejection, along with the owner, rules and exit criteria for each stage. A good one makes every recruiter handle candidates the same way and produces data you can trust.
Designing one is mostly a decision exercise, not a software exercise. You decide which stages exist, who owns each, and how strictly the system enforces the order. This guide covers each decision.
Key Takeaways
- An ATS candidate workflow works best when every stage has one owner and a written exit criterion.
- Straight Path workflows prevent skipped steps, while Open Field workflows allow free movement between statuses.
- Every status change should be logged, because that history is the raw material for time-to-hire and recruiter reporting.
- A Kanban view such as BrightFlow turns the submittal workflow into swim lanes and cards that recruiters can update by drag and drop.
- Start with fewer stages than you think you need and add only when a stage changes who acts or what gets reported.
What Is an ATS Candidate Workflow?
An applicant tracking workflow is the path a candidate follows inside your system, expressed as statuses. Each status answers a plain question: where is this person, and what happens next?
In staffing and RPO, the workflow usually centers on the submittal, the record that ties a candidate to a specific job. Because the status lives on the submittal, the same person can be at different stages for different jobs. Your hiring pipeline is simply the sum of those submittals across all open jobs.
How Do You Design the Stages of a Hiring Pipeline?
Stage design starts with handoffs. Add a stage only when someone new has to act.
A useful test is to write one sentence per stage: "A candidate is in this stage while [owner] does [action], and leaves when [condition]." If you cannot finish the sentence, merge the stage with its neighbor.
What Should a Stage Table Include?
Each stage needs a name, an owner, an entry rule and an exit criterion. Treat this example as a template and adapt it.
| Stage | Owner | Entry rule | Exit criteria |
|---|---|---|---|
| New / Applied | Sourcer or recruiter | Candidate attached to a job | Resume reviewed, basic fit confirmed |
| Screened | Recruiter | Passed initial review | Phone screen complete, notes logged |
| Submitted to Client | Recruiter | Candidate approved for submittal | Client response received |
| Interview | Recruiter and hiring manager | Client requests interview | Feedback recorded |
| Offer | Account manager | Positive interview feedback | Offer accepted or declined |
| Placement | Recruiter | Offer accepted | Start details confirmed |
| Declined / Rejected | Whoever decides | Any stage | Reason recorded |
Who Should Own Each Stage?
Name one accountable owner per stage, even when several people touch it. Shared ownership is where candidates stall, because each person assumes someone else will act.
Owners also make delays traceable. If client feedback belongs to the account manager, a stalled candidate has a named person to follow up with.
Straight Path or Open Field: Which Workflow Style Fits?
BrightFlow offers two workflow styles. Straight Path uses a fixed sequence and prevents skipping steps. Open Field lets recruiters move candidates freely between statuses. The right choice depends on how much variation your work really has.
| Question | Straight Path | Open Field |
|---|---|---|
| Movement | Fixed sequence | Free movement |
| Skipped steps | Prevented | Allowed |
| Best when | Process consistency or compliance matters | Roles and clients vary widely |
| Main risk | Feels rigid for unusual placements | Inconsistent data across recruiters |
Teams with a repeatable process often lean toward Straight Path. Teams placing varied roles for many clients may prefer Open Field and rely on training.
How Does a Kanban Workflow View Help Recruiters?
In BrightMove, the BrightFlow view shows the submittal workflow as a Kanban board. Each status is a swim lane and each candidate is a card. Dragging a card to a new lane changes the status immediately, so the record is current without a separate data-entry step.
Default tiles are color-coded: green for Placement, blue for Submitted to Client or Sendout, red for Declined or Rejected, and gray for other statuses. Swim-lane colors can be customized. Hiring managers can optionally review submittals and give feedback in the visual view, depending on company settings. See BrightFlow for details.
How BrightMove Handles Workflow Configuration and Status Logging
In BrightMove, admins and Super Users with the "Manage Submittal Workflow" permission configure the workflow in Settings > BrightFlow Setup. Limiting that permission keeps the stage list from drifting.
Every status change is logged. That history supports reports on Time to Hire, Quality of Hire and Recruiter Analytics. If you want those reports to mean something, treat the status as a record of fact: move candidates when the exit criterion is met, not in batches at the end of the week.
How Do You Keep the Workflow Healthy Over Time?
A workflow is not a one-time setup. Review it on a schedule.
- Find the stages where candidates sit longest and ask why.
- Remove statuses nobody uses.
- Confirm rejected candidates carry a reason.
- Re-train recruiters whenever a stage definition changes.
For a broader look at pairing workflows with job distribution, read ATS with custom workflows and job board sync. To connect pipeline discipline to business value, see recruitment software ROI.
Frequently Asked Questions
What is an ATS candidate workflow?
An ATS candidate workflow is the sequence of statuses a candidate moves through in an applicant tracking system, from first contact to placement or rejection. Each status has an owner, an entry rule and an exit criterion. The workflow keeps handling consistent and creates a record for reporting.
How many stages should a hiring pipeline have?
Use as few as your process allows. Add a stage only when it changes who acts or what you need to report on. The right number depends on your clients and roles.
What is the difference between Straight Path and Open Field in BrightFlow?
Straight Path is a fixed sequence that prevents skipping steps. Open Field allows free movement between statuses. Straight Path favors consistency, while Open Field favors flexibility for varied roles and clients.
Why does status logging matter for reporting?
Reports such as Time to Hire, Quality of Hire and Recruiter Analytics depend on a timestamped history of status changes. In BrightMove every status change is logged, so accurate and timely updates lead directly to more reliable reports.
Who should be allowed to change the workflow?
Limit it to a small group. In BrightMove, admins and Super Users with the "Manage Submittal Workflow" permission can configure the workflow in Settings > BrightFlow Setup. Everyone else works within the stages that group defines.
Next Step
See how BrightMove's configurable submittal workflow fits your process: schedule a demo or explore BrightFlow.