← Back to glossary index

Recruitment Glossary

Kanban view

A Kanban view is a visual board that displays work items as cards across defined workflow columns. In recruitment, cards commonly represent vacancies, candidates, offers, onboarding tasks, or service requests; movement should reflect real changes in status rather than becoming a decorative drag-and-drop display.

Recruiter Focus

Recruiters need explicit column entry and exit rules, owners, next actions, work-in-progress limits where useful, ageing signals, blocked reasons, permissions, and automation recovery. Candidate boards must protect personal information and distinguish a person’s status from the recruiter task attached to it.

Why Kanban view Matters

A shared board can expose bottlenecks and make hand-offs visible without opening every record. Poorly designed columns encourage stale cards, invented progress, excessive parallel work, and misleading reports when the visual state no longer matches the underlying evidence.

Terms Recruiters Commonly Compare

Hiring pipeline

A hiring pipeline represents candidate progress towards a hiring outcome. A Kanban view is a visual method that can display that pipeline or many other work types.

Task list

A task list records actions, often without showing flow. A Kanban board emphasises current state, movement, work in progress, and constraints.

Recruitment Example

A recruitment-operations board uses Ready, In progress, Waiting on stakeholder, Blocked, and Done for implementation requests. Each card has one owner and due date, while candidate selection remains in its separate controlled pipeline. Weekly review focuses on blocked and ageing work instead of counting cards moved.

Implementation Playbook

  • Choose one work-item type and map its actual start, flow, waiting points, completion, and cancellation.
  • Define every column, movement authority, required evidence, owner, and service expectation.
  • Separate active work from waiting and show why an item is blocked without exposing sensitive details.
  • Set work-in-progress limits where starting too much work delays completion.
  • Review ageing, blocked time, rework, throughput, and exceptions; simplify columns that users interpret differently.

Common Mistakes

  • Mixing candidates, vacancies, and internal tasks on one board.
  • Creating a column for every minor action until status loses meaning.
  • Moving a card to satisfy reporting before its entry condition is met.
  • Showing candidate names and sensitive status to users without a recruitment need.

Metrics to Track

Work in progress Time in active and waiting states Blocked items Completed items and rework

Questions Recruiters Ask

What should each Kanban card contain?

Include a clear work item, owner, current state, next action, relevant due or service date, and a link to the authoritative record. Keep personal details to the minimum permitted.

Should every recruitment stage be a column?

Only when it represents a meaningful, consistently understood workflow state. Minor actions can remain tasks within the record.

What is a work-in-progress limit?

It is an agreed cap on items in an active state, used to finish work and expose capacity constraints before more work is started.

Sources and Review

ATZ CRM Recruitment Editorial Review · Reviewed 2026-08-05

Put Kanban view Into Practice with ATZ CRM

Use ATZ CRM to convert glossary concepts into daily recruiter workflows with sourcing pipelines, automation, scorecards, and reporting built for staffing and recruitment teams.