Recording outcomes — placed, rejected, withdrawn

Close out applications with a reason, keep the stage history, and reopen when circumstances change.

When a candidate's journey on a job ends, record an outcome instead of dragging their card away. The outcome stamps how it ended while preserving the stage they reached — so "rejected at Interview" stays distinguishable from "rejected at Screen" in your reporting forever.

The three outcomes

OutcomeMeaning
PlacedThey got the job. Kepler prompts you to record the placement so fees and dates are captured while fresh.
RejectedThe client or you ended it.
WithdrawnThe candidate pulled out.

How to record one

  • On the board — start dragging a card and drop it on the Reject… or Withdraw… zone that appears.
  • In the application drawer — open the application and use Mark as placed, or the menu's Reject / Withdraw….

The reason dialog

Rejections and withdrawals always capture a reason:

  • Reason type — Client rejection, Candidate declined / withdrew, Internal rejection, or Role closed. Choosing Candidate declined / withdrew turns the dialog into a withdrawal.
  • Rejecting from stage (or Withdrawing from stage) — the stage the candidate is on is pre-selected; correct it if the exit really happened earlier.
  • Notes — optional context ("base too low, wants 95k+").
  • Keep viable for other roles — adds this instruction to the outcome notes for future reference; it does not change the candidate's status.

Closed applications show a banner — e.g. "Rejected at Interview" — and the reason stays editable if you learn more later.

Reopening

Circumstances change: the client reopens the role, the candidate comes back. Use Reopen in pipeline in the application drawer — the outcome is cleared and the card resumes at the stage it had reached.

Reasons feed your win/loss reporting. "Client rejection" vs "candidate withdrew" tells you whether to fix qualification or candidate experience — but only if you record it every time.

Read as Markdown