Job Search Kanban Board: Turn Your Pipeline Into a System That Tells You What to Do Next

The short answer

A job search kanban board is one column per stage and one card per role. It only works if every card also names the next action and a date. Copy the columns and fields below into Trello, Notion, or Sheets — then open the board to see what to do today, not a museum of applications.

Why most job-search boards go stale

Kanban started as a way to see flow and limit work in progress, not as a prettier status list. Atlassian's overview of kanban is explicit about that: visualize the work, cap how much sits in each stage, and keep cards moving. A job search is a pipeline with the same failure mode as a software board that never finishes stories — cards pile up in Applied, Interview quietly overflows, and you stop opening the board because it only reminds you of waiting.

The fix is a field most templates skip: next action plus a date. Status tells you where the company is. Next action tells you what you will do on Tuesday morning. Without that pair, Trello and a spreadsheet decay at the same speed. This is also why later-stage confusion shows up as rejections you can't diagnose: if you never recorded which stage died, you can't tell a resume problem from an interview problem.

Column bank (copy these names)

Match columns to the path a real application takes, including the two endings people avoid labeling: rejected and silence. JobCommand uses inbox → applied → interview → offer / rejected / no_answer on the in-app pipeline; the names below are the same idea in generic tools. Don't add a Wishlist of 80 companies. Inbox is saved roles you will apply to or discard this week.

Card-field bank (every card, every tool)

Columns without fields are just buckets. Paste this field list onto every Trello card description, every Notion property set, or as spreadsheet headers. Fill them the day something changes — not Sunday night when you can no longer remember who asked for a take-home.

Trello, Notion, and Sheets — same board, three pastes

You do not need a special job-search app to start today. You need the same six columns and the same fields. Pick the tool you already open. If you later want the board connected to tailored resumes and rejection notes, the JobCommand pipeline is that version already built — Free includes unlimited tracking. Until then, copy one of these.

Trello

1. New board named Job search. Create the six lists above, in that order.
2. Card title = Role — Company. Description template: URL, dates, next action, next-action date.
3. Add a Checklist named Next action (one item). Due date = the next-action date. Filter the board by due date in the morning.
4. Labels optional: remote / onsite, referral, take-home. Don't let labels replace the next-action line.

Notion

1. New database, Table view first. Properties: Status (select with the six names), URL, Date saved, Date applied, Next action (text), Next-action date, Stage-died-at.
2. Add a Board view grouped by Status. That is the kanban.
3. Add a second view: Table, filtered to Next-action date is on or before today, sorted ascending. That is the daily work list.

Google Sheets

Row 1 headers, left to right: Role, Company, URL, Status, Date saved, Date applied, Next action, Next-action date, Stage-died-at, Notes. Status uses data validation with the six column names. Filter view "Due today": Next-action date ≤ today AND Status is not Offer. To mimic columns, create a tab per status with FILTERfrom the master sheet, or just sort by Status. A sheet is a board if you can answer "what do I do this morning?" in under ten seconds.

A five-minute daily pass

Open the board once a day, not whenever an email arrives. Move anything that changed. Rewrite next action for every card that moved. If Interview is over the cap, Inbox is frozen. If a take-home assignment lands, it stays in Interview with a next action of "score the brief before starting" — the card is not done when you receive the prompt, only when you've decided to proceed, push back, or decline.

Once a week, look at Rejected and No answer together. You are not counting failures; you are counting stages. A pile that died in Applied is a different problem than a pile that died after a take-home. The board's job is to make that obvious without opening twenty email threads.

What to do next

Create the six columns today and migrate only the jobs that are still alive — not the entire history. Put a next action on each card before you add another listing. If the board still feels like a status museum after a week, the missing field is almost always the date, not a prettier tool. When you want that same pipeline tied to the resume you actually sent, it's already the default view after you create a free JobCommand account.

Sources: column design and the next-action rule cross-checked against how kanban is defined as a flow system in Atlassian's kanban guide, September 2026. Product stage names verified against JobCommand's live pipeline (inbox → applied → interview → offer / rejected / no_answer). Free plan remains $0 with unlimited tracking; Pro is $15/month.