Database opt-in
Confirm whether a candidate agrees to be stored and contacted about suitable roles.
Recruiter form guide
Candidate Consent Form for Recruiters
A candidate consent form records permission to store candidate details, contact the person about roles, share their profile with selected clients, and process data according to the agency’s policy.
Use this form when adding candidates to the database, preparing client submissions, or collecting personal information that needs a clear permission trail.
When to use it
Where this candidate consent form helps recruiters
This form gives recruiters a practical consent record without mixing every permission into one unclear statement.
Client submission permission
Record approval before sharing a profile, resume, or salary expectation with a client.
Talent pool communication
Clarify whether the candidate wants future role updates, newsletters, or nurture messages.
Form fields
What to capture in the candidate consent form
The form should separate different permissions so candidates understand what they are agreeing to.
1
Candidate identity and permissions
Capture consent in clear, plain language.
Candidate name, email, phone, location, consent date, and recruiter owner.
Permission to store profile, resume, notes, skills, salary expectation, and communication history.
Permission to contact the candidate about current and future roles through selected channels.
Candidate acknowledgement of privacy policy, data update rights, and withdrawal process.
2
Sharing and communication choices
Make client submission and talent pool preferences explicit.
Permission to share profile with named clients, suitable clients, or only after separate approval.
Consent for reference checks, background screening, or assessment sharing where relevant.
Opt-in or opt-out choices for talent pool updates, email campaigns, SMS, or WhatsApp messages.
Expiry or review date if the agency refreshes consent after a set period.
Recruiter workflow
How to use this form without slowing the desk
Use the form before storing sensitive details or submitting a candidate outside the agency.
1
Collect consent at profile creation
Attach consent to the candidate record before the database becomes the source of future outreach.
2
Confirm submission permission
Check whether the candidate approved sharing their profile with a specific client or role.
3
Refresh preferences over time
Update consent if the candidate changes communication channels, location, or availability.
Common mistakes
What to avoid with this form
Consent records fail when recruiters use one broad statement for many different activities.
Combining every permission
Database storage, client sharing, marketing updates, and screening checks should be easy to distinguish.
Forgetting withdrawal process
Candidates should know how to update preferences or ask the agency to stop contacting them.
Submitting without specific approval
Some candidates may permit database storage but still want role-by-role approval before client sharing.
ATZ CRM workflow
How ATZ CRM supports this form
ATZ CRM helps recruiters keep consent history, candidate preferences, communication notes, and submission activity in the candidate record.
FAQ
Questions recruiters ask about this form
Quick answers for using the candidate consent form in a live recruiting process.
Why do recruiters need a candidate consent form?
It records what the candidate has agreed to, including storage, contact, profile sharing, and related recruitment activities.
Is consent needed before submitting a candidate to a client?
Recruiters should confirm permission before sharing a candidate profile, especially when the candidate is passive or currently employed.
Can a candidate withdraw consent later?
Yes. The agency should provide a clear way for candidates to update preferences or withdraw consent according to its data policy.