Practical guide
Record a Candidate Withdrawal Without Rewriting History
Keep the candidate message, pipeline status, and follow-up boundary distinct.
Published
Table of contents
Scope and operating boundary
Start with a case record containing the message identifier, received time, channel, candidate identifier, role, and pipeline stage. Keep corrections as dated events instead of overwriting the earlier state.
Use explicit states such as received, incomplete, conflicting, ready for review, accepted, returned, and cannot determine. A status needs a source event, not an assumption based on silence or familiarity.
Workflow and evidence controls
Coordination support can collect evidence, compare declared fields, maintain the queue, and route one precise question. The authorised owner decides withdrawal reasons, future eligibility, retention, or hiring outcomes.
Store private material in the approved restricted system and point to it from the operating record. Do not copy sensitive values into a shared tracker or public message.
Quality review and exceptions
Close the check only when the recruiting owner accepts the status and conflicting reminders are cleared. Record the source used, action taken, verification result, next owner, and date.