Recruitment process map
A swimlane map of hiring from the moment a role is defined to the moment an offer is accepted, with the hiring manager, HR and talent, finance, the candidate and the interview panel in separate lanes. It carries six decision points, because recruitment is mostly decisions and the steps in between are logistics.
Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.
What is in this map
20 steps across 5 swimlanes and 5 phases, with 6 decision points.
- Swimlanes (who does the work)
- Hiring manager, HR / Talent, Finance, Candidate and Interview panel
- Phases (left to right)
- Role definition, Sourcing, Screening and shortlist, Interview and assessment and Offer
Why map this process
Time-to-hire is the metric everyone tracks and almost nobody can decompose. The reason is that the delay is rarely inside a step; it is between them: a shortlist sitting in an inbox, a panel that cannot find a shared hour, an approval that needs a budget holder who is on leave. A lane map puts every one of those handoffs on the page as a line crossing from one lane to another, which is where you look when you want to find the fortnight that went missing.
The candidate lane is what makes this map different from an internal workflow diagram. Candidates drop out, decline, and accept elsewhere, and every one of those is a real branch in your process, not an exception. Drawing the candidate as a participant rather than an object forces the map to answer what happens next in each case.
Every step in the map
This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.
| # | Step | Shape | Swimlane | Phase | Goes to |
|---|---|---|---|---|---|
| 1 | Vacancy identified | Start | Hiring manager | Role definition | 2 |
| 2 | Define role and *success profile* | Process | Hiring manager | Role definition | 3 |
| 3 | Confirm grading and salary band | Process | HR / Talent | Role definition | 4 |
| 4 | Headcount **approved**? | Decision | Finance | Role definition | 6 (Approved), 5 (Declined) |
| 5 | Vacancy put on hold | Reject | Hiring manager | Role definition | End |
| 6 | Publish advert and source candidates | Process | HR / Talent | Sourcing | 7 |
| 7 | Submit application | Process | Candidate | Sourcing | 8 |
| 8 | Screen applications against criteria | Process | HR / Talent | Screening and shortlist | 9 |
| 9 | Meets **essential criteria**? | Decision | HR / Talent | Screening and shortlist | 11 (Yes), 10 (No) |
| 10 | Application unsuccessful | Reject | Candidate | Screening and shortlist | End |
| 11 | Suitable shortlist agreed? | Decision | Hiring manager | Screening and shortlist | 12 (Yes), 6 (Reopen) |
| 12 | Run competency interviews | Process | Interview panel | Interview and assessment | 13 |
| 13 | Complete role-related assessment | Process | Candidate | Interview and assessment | 14 |
| 14 | Panel **recommends** a hire? | Decision | Interview panel | Interview and assessment | 15 (Yes), 11 (No) |
| 15 | Complete reference and *right-to-work* checks | Control | HR / Talent | Interview and assessment | 16 |
| 16 | Prepare offer against salary band | Process | Hiring manager | Offer | 17 |
| 17 | Offer within **salary band**? | Decision | Finance | Offer | 18 (Within band), 16 (Above band) |
| 18 | Issue written offer | Document | HR / Talent | Offer | 19 |
| 19 | Offer accepted? | Decision | Candidate | Offer | 20 (Accepted), 11 (Declined) |
| 20 | Offer accepted and start date agreed | Success | HR / Talent | Offer | End |
The decision points
Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.
-
4. Headcount **approved**?
Owned by Finance · Role definition
- Approved → step 6
- Declined → step 5
-
9. Meets **essential criteria**?
Owned by HR / Talent · Screening and shortlist
- Yes → step 11
- No → step 10
-
11. Suitable shortlist agreed?
Owned by Hiring manager · Screening and shortlist
- Yes → step 12
- Reopen → step 6
-
14. Panel **recommends** a hire?
Owned by Interview panel · Interview and assessment
- Yes → step 15
- No → step 11
-
17. Offer within **salary band**?
Owned by Finance · Offer
- Within band → step 18
- Above band → step 16
-
19. Offer accepted?
Owned by Candidate · Offer
- Accepted → step 20
- Declined → step 11
Notes on specific steps
These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.
- 2. Define role and *success profile*
- Agree the essential criteria and the interview scorecard before anyone writes the advert. If the panel cannot score against the profile later, it was never specific enough.
- 11. Suitable shortlist agreed?
- This is the reopen loop. Before re-advertising, change something: the band, the essential criteria, the sourcing channels or the advert. Reposting the same role unchanged returns the same shortlist.
- 15. Complete reference and *right-to-work* checks
- Right-to-work evidence is verified before the first day, not after it. State here whether the written offer is conditional on references, and who chases them.
- 17. Offer within **salary band**?
- Anything above the band is re-priced or escalated for a documented exception. Record the reason, because unexplained exceptions are what pay-equity reviews pick up later.
Making it yours
Start at the finance lane. The budget-approval decision early in the map is what most teams omit and then discover mid-process, and it is a single row with two branches. After that, adapt the interview phase: the number of interview rounds is the thing that varies most between companies, and adding a round is one row plus one edit to the previous row's Line to column.
What to watch out for
- If you delete the 'candidate declines' branches because they are unpleasant, you also delete the only route back to sourcing, and the map will imply that a declined offer ends the process rather than restarting it.
- The screening decision and the shortlist decision are not the same. One filters applications against criteria; the other picks who to actually see, which is a judgement about capacity as much as fit. Companies that merge them end up with no record of why a qualified applicant was not interviewed.
- Keep the offer approval separate from the offer itself. The step where someone confirms the salary band is what makes an offer defensible later, and it disappears the moment the two are drawn as one box.
Frequently asked questions
Why is the candidate a swimlane rather than just an input?
Because they take actions your process has to wait for and can refuse: applying, attending, accepting, withdrawing. A lane for them makes those waits visible and gives every candidate-initiated exit somewhere to go. Treating the candidate as an input produces a map that only describes the path where everything goes well.
How do I adapt this for a role with a take-home task or assessment?
Add the task as one row in the candidate lane and its review as a second row in the interview-panel lane, then point the screening decision at the first of them. Keeping the doing and the reviewing as two rows is what lets you see the turnaround time on the review, which is usually the part that stalls.
Does this cover internal applicants?
Not as drawn: internal candidates skip most of the sourcing phase and add a manager-notification step that external ones do not have. Add a decision immediately after the role is opened that branches on applicant source, and let the two paths rejoin at the interview phase.
Open the map and start editing
The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.