Sourcing
Follow Up After a Recruitment Event
A follow-up queue for event leads, consent, and next steps.

A recruitment event follow-up process should make the request, the evidence, the owner, and the next action visible before a candidate is affected. A follow-up queue for event leads, consent, and next steps.
Set the recruitment event follow-up scope
Start by naming the event that creates a record. A record should enter because a defined condition occurred, not because someone remembered to add a task. Record the role, the candidate or request, the source, the owner, and the evidence expected at intake.
The main risk is that event leads can be collected without consent or a follow-up owner. A written rule keeps routine coordination separate from selection and hiring judgment. Use a timestamp and source link rather than a later summary.
Capture the evidence
A usable record includes lead, event, consent, interest, owner, and next action. Keep the source beside the record so another reviewer can reconstruct what was known and when.
The sourcing lead confirms the decision or exception. The recruiting support role can record the lead, check consent, and send approved follow-up, but it should not fill a gap with an assumption.
| Evidence | Why it matters | Owner |
|---|---|---|
| Source record | Shows what was known | Recruiting support |
| Current status | Shows the next action | Recruiting support |
| Decision note | Shows who approved an exception | Accountable owner |
Separate preparation from judgment
Decisions about selection and consent decisions remain with the authorized owner. Use three labels in the queue: proceed under the written rule, pause for missing evidence, and escalate for a decision.
Apply the labels to real examples. A capable coordinator should know when the next action is preparation and when it is a handoff.
Run the review
Review follow-up completion, opt-outs, and response. Sort by age, owner, and exception reason, and confirm that every open item has a next action.
For example, a career fair produces a list with no owner. The review should show what evidence was available, what question remained, and who owned the next step.
Pilot one workflow
Start with one event. Test the checklist on a small batch and review exceptions with the owner. Expand only after the workflow produces a reviewable record and a predictable review rhythm.
Explore the related service or continue with a related workflow.
Continue reading
Three related guides

Talent pools
Run a Candidate Rediscovery Campaign
A campaign record for past candidates, consent, relevance, and follow-up.
Read the article