Hiring Pipeline: How to Build One on a Kanban Board

A hiring pipeline is the path every candidate takes for one open role: application, screening, interviews, offer and hire. This guide covers the hiring process steps, a checklist for each stage, the research on which interview methods predict job performance, and a worked example of a recruitment pipeline on a kanban board. It ends with the privacy rules that apply when you store candidate data in WordPress.

Small teams often lose good candidates through slow replies and scattered notes. In its 2025 recruiting benchmarks, SHRM puts the median time-to-fill at roughly a month and a half for both executive and nonexecutive roles. The same page reports that 41% of organizations see more candidates “ghosting” them, which means candidates stop replying partway through the process.

Hiring process steps

These eight steps fit most roles at a small company. Each step becomes one stage on the board.

1. Applied. The application arrives with a CV, a portfolio link or form answers.
2. Screen. Someone checks the application against the must-have requirements in the job ad.
3. First call. A 20 to 30 minute call confirms salary range, start date, location and interest.
4. Structured interview. Every candidate gets the same questions, scored on the same scale.
5. Work sample. The candidate does a short piece of work like the real job.
6. Offer. You check references, agree terms and send the offer.
7. Hired. The candidate accepts, and onboarding starts.
8. Not moving forward. Candidates who leave the process at any step go here, so you can see who still needs a reply.

Write down what a candidate must show to leave each stage. “Has two years of editing experience” is an exit rule. “Seems good” is not. Written exit rules help you judge every candidate on the same job-related criteria. The US Equal Employment Opportunity Commission says that information gathered before hiring should generally be limited to what is needed to judge a person’s ability to do the job. The EEOC also says employers may not ask about disability before making a job offer.

Hiring process checklist

Use this checklist before the role opens, while the candidate pipeline is running and after the hire.

Before you post the role:

• Write the must-have and nice-to-have requirements, and keep the must-have list short.
• Agree on the salary range and the decision maker.
• Write the structured interview questions and a rating scale for each one.
• Choose the work sample and how long it should take.
• Decide how long you keep candidate data, and who can see it.

While the role is open:

• Reply to each new application within an agreed time, for example five working days.
• Record each interviewer’s scores before the panel discusses a candidate.
• Move every rejected candidate to Not moving forward and send a short reply.
• Review the board once a week for candidates who have waited too long in one stage.

After the hire:

• Close the role and reply to everyone still in the pipeline.
• Delete or archive candidate data when your retention period ends.

Use structured interviews

A structured interview asks every candidate the same questions, in the same order, and scores the answers on one rating scale. The US Office of Personnel Management describes this method in its structured interview guidance, and adds that a panel of interviewers agrees on each candidate’s ratings.

In 2022, Paul Sackett and colleagues re-analyzed decades of selection research, including the estimates in Schmidt and Hunter’s widely cited 1998 review. Their paper, “Revisiting meta-analytic estimates of validity in personnel selection” in the Journal of Applied Psychology, argues that earlier studies overcorrected their data and so overstated how well many methods predict job performance. A SIOP summary of the paper lists these revised mean validities, where a higher number means a stronger link with later job performance:

• Structured interviews: .42, the highest of all methods in the paper
• Job knowledge tests: .40
• Empirically keyed biodata: .38
• Work sample tests: .33
• Cognitive ability tests: .31

Structured interviews also showed a wide spread around their mean, so the way you build the questions and the scale matters. Two habits help keep scores consistent. First, base each question on a task the person will do in the role. Second, have each interviewer score answers alone before the panel talks, so the first opinion does not set everyone else’s score.

A work sample also predicts performance and shows the candidate what the job is like. Keep it short, and if it takes more than two hours, pay the candidate for their time.

How to improve your hiring process

These changes help most small teams and need no new software:

• Use one intake channel. Collect applications through one form, not a personal inbox, so nobody misses an application.
• Set reply times per stage. A due date on each card makes overdue replies visible on the board.
• Limit interviews in progress. If you can run four interviews a week, do not book eight. A work-in-progress limit on the interview stage shows when you have taken on too many.
• Collect feedback in one place. Each interviewer adds scores and notes to the candidate’s card, not to email threads.
• Reply to everyone. A Not moving forward stage shows who still needs an answer.
• Look at where candidates stall. If many candidates wait in one stage, that stage needs more interview slots or a faster decision.

A worked example: a hiring pipeline on a kanban board

Say you are hiring a part-time content editor. Here is how to set up the hiring pipeline in KanbanWP, a free kanban plugin that runs inside your WordPress admin.

Create the stages

KanbanWP’s board screen moves cards between stages, but it does not add or rename stages. The quickest way to start with your own stages is a CSV import. In the KanbanWP admin, open Import / Export, upload a CSV file and enter a board name. KanbanWP creates a new board and adds each stage it finds in the stage column, in the order the stages first appear. See exporting and importing for the full column list.

This file creates the eight stages, with one guide card in each:

title,stage,description
Exit rule: meets all must-have requirements,Applied,New applications start here.
Exit rule: requirements confirmed,Screen,Check against the must-have list.
Exit rule: salary and start date agreed,First call,20-30 minute call.
Exit rule: panel score of 3 or more,Structured interview,Same questions and scale for everyone.
Exit rule: work sample reviewed by two people,Work sample,Pay if it takes over two hours.
Exit rule: references checked and offer sent,Offer,Record the offer date.
Exit rule: accepted and start date set,Hired,Start onboarding.
Exit rule: candidate has received a reply,Not moving forward,Reply to everyone.

Keep each guide card at the top of its stage so interviewers can see the exit rule.

Set up the cards

Each candidate is one card. Use these fields:

• Title: the candidate’s name and the role, for example “A. Rivera, content editor”.
• Due date: the date of the next action, such as a reply or an interview. The calendar view then shows the week’s interviews.
• Assignee: the person who owns the next action.
• Labels: for example Referral, Strong portfolio and Needs follow-up.
• Custom fields: a name and value pair per field, such as Source, Interview score and Salary range.
• Comments: each interviewer’s scores and notes, with @mentions to ask a colleague a question.

Send applications to the board

KanbanWP has a forms integration. A form plugin can create a card by firing the kanbanwp_form_submission action with a board ID and a title. KanbanWP adds the name, email and any extra fields to the card description and puts the card in the board’s first stage, Applied. Connecting a form plugin to this action needs a short code snippet, which the forms guide shows.

Limit work in progress

A WIP limit on Structured interview shows the stage count against the limit, for example 5/4, and marks the stage when it goes over. The limit warns but does not block a move. Set the limit with the ⋯ button in the stage header.

Run the weekly review

Once a week, look at the board in the kanban view and check these points:

• Cards with an overdue due date, which mean someone is waiting for a reply
• Candidates in Structured interview with no scores in the comments
• Cards in Offer that are waiting on you
• Cards in Not moving forward that have not had a reply

Onboard on a second board

When a candidate accepts, onboarding begins. Build one onboarding board with stages such as Before day one, Week one, Month one and Done, and add the standard tasks with checklists. For each new hire, duplicate the board. The copy keeps the stages, labels, tasks and checklists.

Keep candidate data private

A hiring board holds personal data, so plan access and retention before the first application arrives.

Who can see the board. KanbanWP gives each board its own members, with the roles admin, member, viewer and client. A user who is not a member does not see the board. WordPress administrators are the exception: they have the plugin’s manage capability, so they can open every board. Keep the number of administrators small, and add interviewers as members. See permissions and roles.

Attachments. KanbanWP stores card attachments in the WordPress media library. Files in the media library are saved in the site’s uploads folder, and anyone who has a file’s link can usually open it. For CVs, you may prefer to store a link to a private folder in your file storage instead of uploading the file. When you delete a card, its attachments stay in the media library, so delete those files separately.

Data that leaves your site. KanbanWP’s Slack and Discord webhooks are site-wide settings, so they also post activity from the hiring board to your channel. Outgoing webhooks and email notifications send task details to their recipients too. If you use the AI features, task text goes to the AI provider you choose. Check these settings before you add candidates, and do not create a public link for a hiring board.

How long you keep it. In the US, 29 CFR 1602.14 requires covered employers to keep personnel and application records for one year from the date the record was made or the personnel action was taken, whichever is later. If someone files a discrimination charge, the employer must keep the relevant records until the charge is resolved. UK data protection law sets no fixed period. The Information Commissioner’s Office says in its guidance on keeping recruitment records that you must decide and document a period yourself, and keep data no longer than you need it. When the period ends, delete the cards. Deleting a card in KanbanWP also deletes its comments and activity entries.

For more on running teams on a board, see KanbanWP for project management, why kanban works and the task best practices.