Written by the AgileFever editorial team. Facts checked on November 13, 2026 against the official pages of the organizations named in this post. AgileFever sells training for some of the topics covered here, and we say so wherever it applies. Metric definitions are from the Kanban Guide. Every board, team size and number in this post is an illustrative design we built, not survey data or a client result.
HR teams usually meet kanban for HR through a recruiting pipeline picture: columns from Sourced to Hired. It does not say how many requisitions to carry, what happens when a hiring manager goes quiet, or where payroll queries fit. We already show one HR board in Kanban board examples for software, marketing, HR and support teams and we do not repeat it here. This post goes further: two flows, their columns and policies, WIP arithmetic, blocked work, service level expectations, the three flow metrics, and the privacy rules an HR board needs. It is a sibling of Kanban for marketing teams, which uses the same method for campaigns.
Kanban for HR: two flows, not one board
A recruiting requisition lives for weeks and passes through hiring managers and candidates. A payroll query lives for a day and passes through one or two people. Average them together and the cycle time describes neither, so split by flow and then by work item type.
| Recruiting flow | Employee-service flow | |
|---|---|---|
| Work item | A requisition, from approval to accepted offer | A request from an employee or a new joiner |
| Work item types | Standard hire, replacement hire, fixed-date hire, urgent offer | Onboarding, payroll query, policy question, offboarding |
| Who waits | Hiring managers, panel members, candidates, background check vendor | Employees, payroll, IT, finance |
Illustrative design. Candidate-level steps (screening notes, scorecards) stay in your applicant tracking system, and the board shows the requisition.
The Kanban Guide from Kanban University (May 2025, checked November 13, 2026) asks every Kanban system for a workflow with defined start and finish points, a WIP control method, explicit policies and a service level expectation. It does not name columns, classes of service or exit policies, so the choices below are ours.
Kanban for HR recruiting: columns, exit policies and limits
A recruitment kanban board needs six working columns with one queue in front. A requisition moves right only when its exit policy is true. Write the policy in the column header.
| Column | Limit | Exit policy: a requisition moves on when |
|---|---|---|
| Approved | None (queue) | Budget approved, role profile written, hiring manager named, interview panel named |
| Sourcing | 2 | At least 5 candidates meet the written must-have criteria |
| Screening | 2 | Recruiter screen done and shortlist of 3 sent to the hiring manager |
| Interviews | 2 | All panel rounds held and every scorecard submitted |
| Decision | 1 | Hiring manager and recruiter agree a candidate, compensation band confirmed |
| Offer | 1 | Offer sent, negotiated and accepted in writing |
| Accepted | None | Finish point. Date recorded, candidate and manager told, onboarding request created |
Illustrative design for 3 recruiters. Approved is a queue before the start point.
Classes of service for recruiting
| Class | Use it for | Pull rule | Limit |
|---|---|---|---|
| Expedite | An urgent offer: a competing offer is close, or a critical role just opened | Pull ahead of everything and replace a card, never add one | 1 requisition on the whole board |
| Fixed date | A hire tied to a date: a project start, a notice period ending, a batch of campus joiners | Pull when the latest start date arrives | One lane, sized to dated hires |
| Standard | Most hires | First in, first out | Column limits |
Class of service is not in the Guide, so write your own rules down, or every role becomes urgent.
WIP limits with worked Little’s Law numbers
The Guide asks members to control the number of work items in the workflow and sets no value. Little’s Law gives a way to choose one: average cycle time equals average WIP divided by average throughput, for a stable system. Our post on how to set WIP limits covers the method and its conditions.
- Three recruiters finish 8 requisitions in 8 weeks, so throughput is 1 a week.
- They carry 12 started requisitions. Average cycle time now: 12 / 1 = 12 weeks.
- Target of 8 weeks at the same throughput: WIP = 8 x 1 = 8 requisitions.
- Split the 8 across the columns: Sourcing 2, Screening 2, Interviews 2, Decision 1, Offer 1.
Cycle time = WIP divided by throughput. Throughput is held at 1 a week in every row.
Illustrative example: arithmetic on invented numbers, not data from any company. Throughput moves when WIP moves, so lower limits one column at a time.
Where the time goes
A pipeline before WIP limits. Interviews and Sourcing are the biggest bars.
Illustrative example: invented stage times that add up to 12 weeks, matching the arithmetic above.
A sample recruiting board
| Lane | Approved (none) | Sourcing (2) | Screening (2) | Interviews (2) | Decision (1) | Offer (1) | Accepted |
|---|---|---|---|---|---|---|---|
| Expedite (1) | |||||||
| Fixed date | REQ-25 | REQ-18 | REQ-14 | ||||
| Standard | REQ-23 REQ-24 |
REQ-21 REQ-22 |
REQ-19 | REQ-16 | REQ-12 | REQ-09 [B] | REQ-05 REQ-07 |
| Count | 3 | 2 of 2 | 2 of 2 | 2 of 2 | 1 of 1 | 1 of 1 |
Illustrative example, not a real team. [B] marks a blocked card: REQ-09 waits for the hiring manager to confirm the compensation band. Started work: 2 + 2 + 2 + 1 + 1 = 8 requisitions.
Employee-service board for HR: onboarding, payroll, policy and offboarding
Kanban for HR service work is about many small, mixed requests. One board with four work item types and a short column set handles them. Triage is its own column because most delay starts with a request nobody has read.
| Column | Limit | Exit policy: a card moves on when |
|---|---|---|
| New | None (queue) | Request logged with an ID, type and the date the employee needs an answer |
| Triage | 4 | Type set, owner named, class of service set, missing information requested |
| In progress | 12 | Action taken: payment query traced, policy answered, joiner tasks created, exit tasks started |
| Waiting | 10 | Dependency cleared: employee replied, IT or finance returned the item. Card carries a blocked reason and date |
| Check | 4 | A second person confirms the answer or the task against the policy document |
| Done | None | Finish point. Employee told, date recorded |
Illustrative design for a service desk of 3 people. Started work runs from Triage to Check.
| Class | Use it for | Pull rule | Limit |
|---|---|---|---|
| Expedite | A salary credit error, a joiner locked out on day one | Pull ahead of everything and replace a card | 1 card on the whole board |
| Fixed date | Onboarding for a set joining date, offboarding for a last working day | Pull when the latest start date arrives | Lane sized to dated joiners and leavers |
| Standard | Payroll queries, policy questions, document requests | First in, first out | Column limits |
Fixed-date example: new joiners need laptop, accounts and paperwork ready. Suppose the 85th percentile of past onboarding cycle time is 12 days. For a joining date of December 14, 2026, the latest start date is December 2, 2026. The card is pulled that day, whatever else is waiting.
Limits by Little’s Law, with invented numbers: 30 finished a week and 45 started gives 45 / 30 = 1.5 weeks. A 1-week target gives WIP = 30, split Triage 4, In progress 12, Waiting 10, Check 4.
A sample service board
| Lane | New | Triage (4) | In progress (12) | Waiting (10) | Check (4) |
|---|---|---|---|---|---|
| Onboarding | ONB-31 | ONB-27 ONB-28 ONB-29 |
ONB-24 [B] ONB-25 |
ONB-26 | |
| Payroll | PAY-89 | PAY-88 | PAY-85 PAY-86 PAY-87 |
PAY-80 [B] PAY-81 [B] PAY-82 |
PAY-84 |
| Policy | POL-53 | POL-52 | POL-49 POL-50 |
POL-45 [B] POL-46 |
|
| Offboarding | OFF-12 OFF-13 |
OFF-10 [B] | OFF-11 | ||
| Count | 2 | 3 of 4 | 10 of 12 | 8 of 10 | 3 of 4 |
Illustrative example, not a real team. Started work: 3 + 10 + 8 + 3 = 24 cards, under the total of 30.
Blocked work on a Kanban for HR board: hiring managers, checks and candidates
The Guide lists unblocking blocked work as part of managing a Kanban system, but it does not define blocked. Define it in your policies: a card is blocked when nobody on the HR team can move it forward. Keep blocked cards in their column, flagged, so they keep counting against the limit.
| Situation | Board treatment | Rule |
|---|---|---|
| Waiting for the hiring manager (feedback, compensation approval) | Blocked flag naming the manager, with the date | After 2 working days the recruiter asks; after 5 the hiring manager’s own manager is told |
| Waiting for a candidate (document, reply, notice period) | Blocked flag, reason and date | After 5 working days, decide to hold, replace with the next candidate, or close |
| Background check running at an outside vendor | Blocked flag plus the vendor’s promised date | Chase on the promised date; past it by 2 days, the owner tells the sponsor |
Illustrative policies. Pick day counts from your own cycle time data, and have your legal or compliance team approve checks on candidates.
Record blocked days per card and review them weekly. Ask what the dependency is, not who is slow.
Service level expectations for an HR kanban board
A service level expectation, as the Guide defines it, is a forecast of how long it should take a work item to flow from started to finished, with a period of elapsed time and a probability. Set one per work item type from past cycle times. With no history, a best guess will do.
| Work item type | Example SLE (illustrative) |
|---|---|
| Requisition | 85% finish within 15 weeks now, 10 weeks as the target |
| Onboarding | 85% ready within 12 days |
| Payroll query | 85% answered within 2 working days |
Illustrative examples. The right numbers come from your own finished items.
The three metrics, with a worked example
The Guide defines cycle time as elapsed time from start to finish, throughput as work items finished per unit of time, and work item age as elapsed time from start to the current date. For kanban for HR, read each per work item type. The charts behind them are in Kanban reports explained.
Cycle time
Take 8 finished requisitions, with cycle times in calendar days: 52, 61, 70, 77, 84, 91, 105 and 132. The median is the average of the 4th and 5th values: (77 + 84) / 2 = 80.5 days. The 85th percentile by nearest rank is the 7th value, 105 days (0.85 x 8 = 6.8, rounded up). That gives the first SLE: 85% of requisitions finish within 105 days, which is 15 weeks. The plain average is 84 days.
Throughput
| Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Total |
|---|---|---|---|---|---|---|---|---|---|
| Requisitions accepted | 1 | 1 | 2 | 0 | 1 | 1 | 1 | 1 | 8 |
Illustrative example: 8 requisitions in 8 weeks, 1 a week, which feeds the arithmetic above. This is a count of finished items, not velocity. See Kanban velocity vs throughput.
Work item age
Age applies to items still on the board, so it warns you before an item finishes late. Check it weekly, oldest first, against the SLE of 105 days.
| Requisition | Column | Age (days) | SLE | Action |
|---|---|---|---|---|
| REQ-21 | Sourcing | 18 | 105 | On track |
| REQ-14 | Interviews | 88 | 105 | 17 days left: confirm the last two scorecards this week |
| REQ-09 (blocked 6 days) | Offer | 112 | 105 | Past the SLE: escalate the compensation approval |
Illustrative example. To compute these from your own start and finish dates, use the free flow metrics analyzer.
Privacy and fairness on an HR kanban board
An HR kanban board holds information about real people. Treat the board as a shared view of flow, not a record of people. These are process rules, not legal advice: your privacy and legal teams decide what your law requires.
| Card field | Allowed | Keep off the board |
|---|---|---|
| Who it is about | Candidate ID such as C-104, employee request ID such as PAY-88, initials only if you must | Full names, photos, contact details, national ID, bank details |
| Reason for the request | A category such as leave policy, payroll correction, joiner setup | Health details, disability, pregnancy, religion, caste, ethnicity, age, gender identity, marital status, immigration status |
| Candidate assessment | Scorecards submitted: yes or no | Scores, comments about a person, reasons for rejection |
| Notes | Next step and date | Free-text discussion; keep it in the ATS or HR system with access controls |
Illustrative policy. Link each card by ID to the record in your HR system, where access is controlled.
- Who sees the board: the HR team and the hiring managers for their own requisitions. A board on a wall or shared screen in an open office shows only IDs.
A four-week rollout of kanban for HR
List the last 15 finished requisitions and 30 finished service requests with start and finish dates. Draw the columns from the path they took, not from the process chart. Agree the privacy rules for cards.
Write an exit policy per column. Set limits from the Little’s Law arithmetic. Name the escalation contact for hiring managers who do not reply.
Add classes of service, the blocked flag with reason and date, and a latest start date on fixed-date cards. Hold the first weekly review, oldest card first.
Compute cycle time by type, throughput and age. Write the first SLEs. Change one limit, then leave the board alone for two weeks.
For a blank board to copy, use the Kanban board template.
Mistakes HR teams make with a Kanban board
| Mistake | What it causes | Fix |
|---|---|---|
| Putting recruiting and payroll queries on one board | A cycle time that describes neither | Two boards, or lanes by work item type with metrics read separately |
| No hiring manager response time | Interviews and Decision become the longest queues | A written response time, a backup and an escalation rule |
Where AgileFever fits
We sell the Team Kanban Practitioner course, and the kanban for recruiting design here uses its ideas, so weigh our view accordingly. As listed on November 13, 2026, the Team Kanban Practitioner course costs $600 or ₹14,999, and the next listed batch is on November 20, 2026. Rupee prices are before the 18% GST we add at checkout for buyers in India. It suits a team that wants a trainer to review its own board.
Additional discounts are available. Contact us to know more.
Questions people ask
Can Kanban be used for HR?
Yes. Kanban for HR suits work that arrives continuously and waits on other people: hiring, onboarding, payroll queries and policy requests. Use one board per flow, set WIP limits, write exit policies per column and track cycle time, throughput and work item age per work item type.
What columns should a recruitment Kanban board have?
A recruitment board needs Approved as a queue, then Sourcing, Screening, Interviews, Decision, Offer and Accepted. Give each an exit policy, such as all scorecards submitted before a requisition leaves Interviews, and a WIP limit on every column between start and finish.
What should an HR Kanban card show?
Show an ID, the work item type, class of service, start date, next step and date, and a blocked flag with reason. Keep names, health information, protected characteristics, individual pay and assessment comments off the card, and link to the record in your HR system by ID.
