Hiring process flowchart template

Hiring works best as a decision flow rather than a swimlane, because the hard part is where candidates exit, not who holds the ticket. We recommend following this process:

1. List every stage a role passes through, from identified need to signed offer.
2. Write down the questions that move a role or a candidate forward: is headcount approved, did they pass screening, was the offer accepted.
3. Turn each question into a decision node with both exits drawn, including the rejections.
4. Give every no branch a destination, so no candidate path simply stops on the page.
5. Draw the diagram in the tool your audience already uses. A free template removes most of the layout work.

Each one routes the role or the candidate down a different path:

• Headcount approved: it decides whether the role opens at all. A no ends at request denied.
• Passed screening: the first candidate gate, before any panel time is committed.
• Offer accepted: the closing decision, sending the candidate to onboarding or to rejected.

Add a further decision for background checks, take-home assessments, or a second approval on senior roles; the branches stay attached as the diagram reflows.

Identifying the need, approving headcount, posting and sourcing, screening, interviewing, offering, and handing off to onboarding. This template covers all seven, with the three that can end the process drawn as decision nodes rather than steps.

Stages before hiring need workforce planning and budgeting, which usually sit with finance rather than with recruiting, which is why the diagram starts where it does.

Because a job posted without approved headcount is the most expensive mistake in recruiting; candidates are sourced, screened, and interviewed against a role that may never open, and the reputational cost lands on the recruiter.

Putting approval first, with an explicit request-denied exit, makes the gate visible to everyone who reads the diagram rather than assumed by the people who already know.

An interview loop is the full set of interviews a candidate goes through for one role, typically a hiring manager conversation, one or more skills interviews, and a panel or values round, scheduled as a block rather than sequentially.

It appears as a single shape here on purpose. Teams change the number of rounds constantly, and a diagram that has to be redrawn every time that happens stops being maintained. Expand it into separate shapes if your rounds are fixed.

Both rejection routes — failing screening and declining the offer — converge on a single candidate rejected shape. That is deliberate: one exit means one place to attach whatever happens next, whether that is a rejection email, a talent pool, or a re-engagement window.

Splitting them into two endpoints looks tidier on the page but makes the follow-up process harder to see.

PowerPoint can do it with SmartArt and the Shapes gallery, but the work is manual: you place each diamond yourself, label both exits, and reattach connectors every time something moves. For a flow with three decision nodes and converging exits, this becomes the reason the diagram stops getting updated.

A faster route is the Lucen Flowchart tab, which snaps connectors to shape anchors and reflows the diagram with Auto Layout when you add a branch. Either way, the result stays a set of native PowerPoint objects on your slide.

An ATS pipeline shows which candidates are in which stage right now. A flowchart shows how the process works and where it can end. The difference matters in practice:

• A pipeline hides the rules, so two recruiters screen the same candidate differently.
• A flowchart makes the gates visible, so a stalled role has a reason against it.
• A flowchart survives a headcount review, which is why it belongs in the deck rather than behind a login.

Most teams keep both: the flowchart as the process of record, the ATS as the per-candidate tracker.

Every branch in the diagram should terminate at a named owner. A common split:

• Hiring manager: identifying the need and defining the role.
• Finance or leadership: the headcount approval decision.
• Recruiting: posting, sourcing, screening, and scheduling the loop.
• Interview panel: the loop itself and the hire recommendation.
• HR / People Ops: the offer and the handoff into employee onboarding.

If you already run a RACI for hiring, the branches in this template map onto the accountable party for each gate.

The download is a free .pptx made of native PowerPoint shapes, so anyone can open, read, and edit it, and you can share it as you would any deck; recipients need nothing installed.

The smart connectors, Auto Layout, and Lucen AI come from the Lucen Flowchart add-in, which adds a Lucen Flowchart tab to the ribbon and runs on Windows with PowerPoint 2016 or later and with PowerPoint for Microsoft 365. PowerPoint for the web, Mac, and mobile are not supported. Setup and troubleshooting steps are in Lucen Support.