Pipeline & Velocity

The drag-and-drop kanban board sits at the bottom of Jobs → Overview, where you work on your jobs. The velocity stats (the numbers) live on Reports → Pipeline. Each column is a status bucket; drag a card between columns to change its status. /pipeline redirects to /jobs.

TL;DR — Drag cards on Jobs → Overview to update status; watch the velocity panels on Reports → Pipeline for low conversion. Stale Pending Review auto-archives to Not Relevant after 30 days (admin-configurable).

What changed (27MAY2026). The old separate "Pipeline Velocity" and "Job Pipeline" Reports tabs were merged into one Pipeline tab — they answered the same question ("what's in my pipeline and where's it stuck?"), so they belong together. Old ?tab=velocity links redirect to the merged tab.

What changed (05OCT2026). The kanban board moved from Reports → Pipeline to the bottom of Jobs → Overview. The board is where you act on jobs, and Reports is for looking back, so Reports → Pipeline now shows the velocity stats only.

Each kanban column is a status bucket (Radar → Interested → Applied → Interviewing → Offer). Cards within a column show title, company, last-status-change date, and a colored tag.

Quick start

  1. Open Jobs (or /pipeline, which redirects). Overview is the first tab, and the board is at the bottom of it
  2. Scan the kanban columns left-to-right — anything stale jumps out because the cards show how long they've been in the current status
  3. Drag a card between columns to change its status (same effect as clicking the quick-action buttons on the detail drawer)
  4. Click a card to open the full Job detail drawer for that posting — same drawer as on the Job Search page
  5. For the numbers (activity, conversion rates, funnel, time-in-stage), open Reports → Pipeline

What the columns mean

A job always has one of ten statuses. The kanban shows the five active ones as columns. The other five are outcomes: they end a job's journey, so they have no column. You set them from the job's details, and you can still see and filter them on the Job Search page. The velocity funnel on Reports → Pipeline counts the outcomes too.

| Status | On the board? | What it means | |---|---|---| | Radar (Pending Review) | Column | Newly fetched, not yet triaged | | Interested | Column | Shortlisted for application | | Applied | Column | Submitted, waiting to hear back | | Interviewing | Column | Active interview process | | Offer | Column | Decision time | | Rejected | Outcome | The employer said no | | No Response | Outcome | You applied and never heard back (use Mark No Response) | | Closed | Outcome | The role closed or you withdrew | | Not Relevant | Outcome | Not a fit; stale Pending Review jobs also land here | | Out of Region | Outcome | Location doesn't work |

Why "a pipeline from first look to offer" and not "9-stage". Earlier marketing called this a "9-stage pipeline", counting the nine statuses that existed then. No Response was added in June 2026, which made ten. Neither count matched the board, which shows the five active columns. An older version of this guide also listed Rejected as a column, but it is an outcome. We now describe the pipeline without a number.

Auto-archiving stale Pending Review

Jobs that sit in Pending Review (the Pending Review status) longer than a threshold are automatically moved to Not Relevant by the scheduler, so an un-triaged inbox doesn't accumulate forever and skew your funnel. The default is 30 days; an admin can change it (or disable it by setting 0) at Admin → Settings → System Parameters (jobs.pending_review_auto_archive_days). Auto-archived jobs get a StatusHistory entry like any manual change, so the move is auditable.

Velocity panels (Reports → Pipeline)

The velocity stats have the Reports → Pipeline tab to themselves:

  • Activity in window — jobs added, applied, interviews, offers, rejections
  • Conversion rates — response rate (interviews / applications), interview → offer, apply → offer
  • Pipeline funnel — current snapshot of where every relevant job sits
  • Time-in-stage — how long jobs typically sit in each bucket before moving forward (or out) — Pro

If your conversion from Applied → Interviewing is unusually low, that's a signal the postings you're applying to don't match your profile, or your application materials need work. The numbers don't lie.

Drag-and-drop nuances

  • Dragging across the kanban writes the same StatusHistory row that the quick-action buttons would — so the goal counter (jobs.applied) ticks up correctly when you drag into Applied
  • Dragging into Rejected prompts for a brief reason (optional) so you can scan past rejections and look for patterns
  • The kanban respects the same Pending Review default filter — old jobs you've triaged out won't reappear when you visit

Card density

The card layout is compact by default — 5–6 cards visible per column without scrolling. If you have a heavy pipeline, scroll within a column. On a wide screen all five columns fit side by side. On a narrower screen or a phone, the board scrolls sideways inside its own area; the rest of the page stays put.

Tips

  • Daily 30-second scan. Open Jobs → Overview, look for any column with age outliers (cards stuck >30 days), make a decision on each.
  • Don't let Interested grow. If you have 20+ cards in Interested, you're hoarding rather than searching. Either apply or move them to Closed.
  • Don't let Pending Review rot. If you ignore the inbox, the auto-archiver eventually clears stale cards to Not Relevant — but triaging them yourself keeps your funnel honest.

Related

  • Job Search — list view of the same data
  • Reports — the Pipeline tab holds the velocity stats
  • Goals — application + interview goals draw from this pipeline's StatusHistory