Manage your pipeline
Run the kanban board day to day — advance, hold, and decline candidates, work in bulk, and keep the board the live truth of the search.
Prerequisites: a published job with candidates; Member role or above to act on candidates.
The kanban view
Each job's pipeline is a kanban board with one column per stage. The default stages are Applied, Screening, Interview, Assessment, Offer, and Hired; your job may use custom stages. Each card is a candidate at that stage, and the board is the live state of the search — no separate status spreadsheet to maintain.
Advance a candidate
When you advance a candidate, you record more than a column change:
Choose advance
Open the candidate and choose to advance. Pick the target stage.
Record signals
Rate the signals that justified the decision — skills match, culture fit, and communication — and select the highlights that stood out. These inform future matching and give the next reviewer context.
Add notes
Notes are optional, but Club AI uses this context to learn what excellent looks like for this role. A sentence of specifics beats a blank field.
Hold, move back, and decline
Not every decision is forward:
- Hold keeps a candidate parked at their stage while you wait — on a reference, a budget decision, another candidate's loop — without losing their place or context.
- Move back returns a candidate to an earlier stage when a step needs redoing.
- Decline removes a candidate from the running with structured feedback. This flow has its own discipline — see Decline candidates well.
Internal review and ratings
Your team can rate and discuss candidates internally before committing to a pipeline decision. Internal reviews stay inside your company — candidates never see them — and they surface alongside the candidate so the eventual advance or decline is informed rather than impulsive.
Bulk actions
Select multiple items to act once instead of many times — for example, publishing, closing, or archiving several jobs together, or processing a batch of new applications in one pass. Bulk actions apply the same rules as individual ones: anything that needs feedback still gets it.
Duplicate detection
The platform flags likely duplicates when a candidate is added — for example, a profile with the same LinkedIn URL already in your pipeline. Resolve the duplicate before working the card so feedback and history accumulate on one profile, not two.
Permissions
Advance and decline are role- and assignment-gated. If you cannot act on a candidate, your job assignment does not include that permission — see Roles and permissions.