An Applicant Tracking System that lets a recruiter send a CV to a client before the candidate has agreed to that specific submission invites trouble: the candidate hears about a role they never wanted, two agencies present the same person to the same client, and nobody can show afterwards who approved what. Record the candidate’s consent per client and per vacancy in the Applicant Tracking System, and make that consent a hard step before any submission leaves the building. No vanity metrics, and no promise that artificial intelligence replaces recruiters.
This matters most for recruitment agencies, staffing, secondment and executive search, where candidates are presented to outside clients. In-house recruitment teams face the same question when they share a profile with another business unit. Your terms with clients and your privacy policy set the rules; the Applicant Tracking System has to make them visible and enforceable on every submission.
Why submissions without recorded consent go wrong
The problems are familiar to every desk:
- A recruiter sends a strong profile “on spec” and the candidate later says they never agreed to that client
- The candidate already applied directly or through another agency, and the client receives the same CV twice
- A client claims they knew the candidate already, and nobody can show when and with whose approval the profile was sent
- Consent was given by phone, but only the recruiter remembers it — and that recruiter is on holiday
- The candidate agreed to one vacancy, and the profile quietly travels to a second role at the same client
Each case costs trust with the candidate, the client or both. Recorded consent turns a verbal “yes, go ahead” into a fact the whole team can see.
What consent to a client submission means
Define it clearly in the Applicant Tracking System:
- Scope — consent for one client and one vacancy, not a blanket permission to send the profile anywhere
- Channel and moment — how and when the candidate agreed: by email, through a confirmation link, or by phone with a short written follow-up
- Prior contact check — whether the candidate already applied to this client directly or through another party, asked before the submission
- Named recruiter — the signed-in user who recorded the consent, consistent with recording who moved the candidate on every stage change
- What it is not — talent-pool consent to keep the record; that belongs with the retention date on the candidate record
How to make consent a hard step in the Applicant Tracking System
A policy in a handbook is not enough. In the Applicant Tracking System:
- Block the move to the “submitted to client” stage until consent for that client and vacancy is recorded
- Send the candidate a short confirmation with the client name and role, and store the reply on the candidate record
- Ask about earlier applications to the same client as part of the same step, and keep the answer next to the consent
- Merge duplicate candidates first, so a second profile cannot slip past a consent that sits on the first one
- Keep the candidate source recorded at first application, so ownership questions start from facts instead of memory
Consent and the client conversation
Once consent is recorded, the submission itself can move quickly. Log the submission with the date, the client contact and the version of the CV that was sent, and give it a response deadline so it does not disappear in an inbox. If the candidate withdraws consent, record that too and inform the client from the same record. Do not invent “consent rates” or similar scores; the useful view is simply which planned submissions are still waiting for the candidate’s confirmation, per desk.
Where artificial intelligence may help — and where it must not
Artificial intelligence may draft the confirmation message to the candidate, suggest that a profile looks like an existing record, or summarise a phone note for the recruiter to check. It must stay secondary. Artificial intelligence does not replace recruiters, does not decide that a candidate has agreed and does not send a profile to a client without a human confirming the recorded consent. The Applicant Tracking System stores the consent, its scope, who recorded it and when.
How this sits next to candidate and client relationships
- The candidate and client relationship records beside the pipeline show which clients a candidate has already been presented to, and with which consent
- Merging duplicates keeps one consent history per person instead of two incomplete ones
- Response deadlines on client submissions only make sense when every submission was allowed in the first place
A practical week to introduce submission consent
- Agree with your team and, where needed, your privacy officer or lawyer what counts as valid consent for a submission
- Configure the Applicant Tracking System so the submission stage requires consent for that client and vacancy
- Prepare one short confirmation message per language, with the client name and role filled in from the vacancy
- Review open submissions without recorded consent and confirm them with the candidates this week
- Add a weekly check per desk on planned submissions that are still waiting for confirmation
The extra step takes a minute per candidate. It saves the awkward calls when a client, a candidate or another agency asks who sent what, and when.
Ask first, then present
If your Applicant Tracking System lets profiles reach clients without recorded consent, every submission carries a hidden risk. Record consent per client and vacancy, make it a hard step before the submission stage, and keep artificial intelligence as a helper only. Then explore the product or book a demo — we walk through BoldATS submission discipline in your segment.