Closing the loop: candidate communication as a workflow, not a courtesy

Very few hiring teams decide to leave applicants without an answer. It happens because the process makes silence the default state and communication an extra task at the end of a long week — and because the person who would send the message is not the person who made the decision.

Attach the message to the decision

The fix is structural. When a candidate's stage changes, the message goes out as part of that change rather than as a separate task somebody remembers later. If your process cannot do that, the backlog will keep reappearing no matter how much goodwill the team has.

Three moments that matter most

• Receipt — the application arrived and roughly when they will hear more.
• Not proceeding — said plainly, reasonably soon, with a reason where you have one.
• Change of plan — the role was paused, rescoped or filled internally. This is the silence candidates find hardest to forgive.

A reason is worth more than an apology

'We went with someone who had run this process at a larger scale' is short, honest, and useful. It is not a debate invitation, and it does not require a template of consolation. Where you cannot give a specific reason, say that clearly rather than padding it.

Set the expectation you can actually meet

Two weeks that you honour beats one week that you miss. If timelines slip, a single line saying so buys more patience than teams expect.

How Rice & Bean handles it

Stage changes notify the candidate and are recorded as dated timeline events on the application. Rejections can carry a reason and optional feedback. Internal notes stay internal — candidates never see them. Messaging is scoped to the application, so the conversation stays with the context that produced it.