A practical consent log for recruitment coordination

The route-local operating guide

A consent log should answer a simple operational question: may the recruiting team use this channel for this purpose now? It should not become a store for extra personal detail that the workflow does not need.

Use the client's approved consent language and retention rule. Coordinators can record a candidate's stated preference and stop contact after a withdrawal, while legal interpretation and unusual cases go to the named privacy or recruiting owner.

Before any campaign or scheduling batch, check the current consent state against the intended channel. Count blocked, withdrawn, and unclear records so managers see how much of the list was actually eligible.

Set the record and cutoff

Use one controlled record containing candidate identifier, contact source, consent basis, permitted channels, restrictions, recorded time, withdrawal, retention state, and owner. Link to permitted source systems instead of copying restricted data into working notes.

Name the population, starting state, and cutoff before processing begins. Record unknown and conflicting information as explicit states so another reviewer can reproduce the result.

Keep authority visible

The specialist may prepare records, perform documented checks, and route exceptions. Approval and policy judgment remain with the recruiting or privacy owner.

Write the pause condition beside the normal path. When evidence conflicts, preserve the competing observations and their timestamps until the named owner decides.

Verify the resulting state

Completion requires evidence in the destination system or confirmation from the accountable owner. A sent message, prepared draft, or checked task is an intermediate state.

Review completeness, age, rework, and exception reasons for this candidate communication coordination. Report counts with denominators and do not treat one queue as proof of individual performance or wider business impact.