Ask a recruiter why a placement fell over and you will rarely hear about a sourcing failure. You hear that the candidate went quiet for nine days, that the client never got the availability they asked for, that nobody chased the second reference until the offer was already on the table.
Each of those started as a next action inside a conversation. It just never left the conversation.
Where follow-ups actually go missing
Not into a task list. Into six places that were never meant to hold work: the end of a candidate call, a line in a client email, a note in the ATS record, a half-written message in a chat, a scribble in a notebook, and memory. Every one of those is a place where a next action can technically exist while being invisible on the day it matters.
The common fix is a task manager. It helps for about a fortnight, then two things happen. Entering tasks twice, once in the conversation and once in the tool, competes with recruiting. And the tasks that do get entered lose the thing that made them actionable.
Why a generic task manager loses recruitment context
"Chase Amara" is a complete task in a to-do app and a useless one on Thursday afternoon. It is missing four things a recruitment action needs.
What a recruitment next action has to carry
- Why it exists: the reason the action was created, in the words used at the time.
- Which Role it belongs to: the search it moves forward, not just a project label.
- Which candidate or client it affects: the person on the other end.
- Which conversation created it: the call or note you can reopen to remember the detail.
With those four, "chase Amara" becomes "ask Amara for notice period and current base, raised in Tuesday's screening call, blocking the submission to Northwind". You can act on the second one in thirty seconds without reconstructing anything.
Next actions are more useful when they retain why they exist.
How should recruiters track candidate follow-ups?
Answer-first: capture the action at the moment the conversation creates it, attach it to the role, the person and the source, and review the whole set once a day rather than per-thread.
The daily review is the part that gets skipped. Recruiters look at their pipeline by role, which is the right lens for strategy and the wrong lens for follow-ups, because the things at risk are spread thinly across six searches. A single view of everything due today surfaces the two that are quietly rotting.
Where recruitment next actions come from
- Role workOpen questions from the brief
- ConversationsCandidate screens, client calls, debriefs
- Evidence reviewGaps to close before submission
A follow-up habit that survives a busy week
- Write the action before you leave the call, while you still remember why it matters. Two minutes then saves ten later.
- Phrase actions as the next physical step, not the outcome. "Send Northwind the two availability slots" beats "progress Northwind".
- Give anything blocking a submission or an offer a date, and treat everything else as unscheduled rather than overdue. A list where half the items are red stops being read.
- Review once, in the morning, across all searches.
How Creo Access implements this
Creo Actions is the next-action layer in Creo Access, and the design point is that actions are source-linked. An action created from a screening call keeps the call. An action created from an evidence gap keeps the requirement it came from. Opening it takes you back to the material, so you are not reconstructing context from an eight word title.
Actions arrive in three ways. Creo Capture turns a call, pasted notes or an uploaded recording into structured recruitment work and proposes the next actions it found, which you accept, edit or discard. Creo Evidence proposes actions for the questions a candidate's material left open. And you can write one yourself in a line.
A conversation turning into a proposed Role update
Apply or skip the proposed update to see what each choice does.
Nothing reaches the Role until you approve it, and the update keeps the conversation that produced it.
Read this figure as text
- Client call, 11 March, 06:20: Honestly, the payments background matters less than the ledger work. We can teach payments. What we cannot teach is someone who has never reconciled a ledger under pressure.
- Decision: The client relaxed a requirement and hardened another.
- Proposed change to Established requirement, from “Production Go in a payments domain.” to “Production Go with ledger reconciliation ownership. Payments becomes a preference.”.
- Applying in the product: In the product, applying this writes the change to the Role and keeps the call as its source. Here it only changes this figure.
- Skipping: Skipping leaves the Role exactly as it was. The conversation stays captured, so the same update can be proposed again later.
Today is the single daily view: what is due across every search, with the recent work you were in the middle of. Where an action is a piece of writing rather than a phone call, "Do it with Creo" drafts it using the Role context already recorded, so a follow-up message does not start from a blank box.
Asking what is outstanding across a search
Select a question to see the answer and the sources behind it.
The answer reads from the Role and the captured conversations. Where the information is not there, it says so instead of guessing.
Read this figure as text
- Answered from the Role: What has changed on this Role since I last looked?. Answer, Two things. Payments moved from a requirement to a preference after the 11 March call, and an open question about ledger ownership is still unanswered.
- Answered with its limit: Does this candidate meet the ledger requirement?. Answer, Partly. The CV describes ledger reconciliation at Novarail, but neither source says whether they owned it after release.
- Not enough information: Will the client accept a July start?. Answer, Nothing on this Role covers start dates. I cannot answer this from what is recorded. Ask the client and the answer becomes part of the Role.
None of this is task management for its own sake. It is continuity: the ability to pick up a search on Thursday and know exactly what it needs, without rereading a week of notes first.
Try it on this week's work
Keep the follow-ups that decide whether a search lands
Capture a call, review the actions it proposes and see them in Today. Start free for 14 days. Then choose monthly or annual billing. Cancel anytime.
Start 14-day free trial