Job statuses & job health
Use job statuses, closed reasons and the job header to run an honest job list.
Job statuses
Every job carries a workspace-defined lifecycle status that drives lists, dashboards and reports. Keep it current — your Jobs page is only as useful as its statuses are true. Moving a job to any terminal status requires a Closed Reason — Filled, Cancelled, Lost to competitor, Role withdrawn, Budget removed, Duplicate or Other — which feeds win/loss reporting. Admins can rename those options or add their own. Statuses themselves are configured under Settings → Job statuses.
The job header
The top of each job shows its status, client, core details, opened date, candidate count and placed count. Open Pipeline for stage distribution and movement detail.
Working your job list
- Build a saved view of open jobs sorted by priority for your daily run-through.
- Use kanban mode grouped by status for a board-level view of the desk.
- The dashboard surfaces open roles that need attention, each with the reason why. See Understanding the dashboard.
Statuses vs stages — don't mix them
The job status describes the vacancy (open, on hold, closed). Pipeline stages describe each candidate within it. A job stays open while its candidates move; close the job when the role itself is done.