Consent Requirements for Government ICT Candidates
Consent requirements for recruiting into Australian Government ICT roles: what to record, when approval lapses and how to submit compliantly.

A panel supplier wants a cloud engineer by close of business, the CV is already in your inbox, and the role sits on an Australian Government ICT contract. Sending the pack now feels efficient. It is also the point where consent requirements either hold up or fall apart.
Approval has to be provable for this role and this recipient. Clearance status is its own consent item, not a line you infer from an old CV. If you can't name the documents, the recipient and the date, the submission stays in the inbox.
Table of Contents
- Consent Requirements by Type of Candidate Information
- Why Valid Consent Comes Before Every CV Moves
- When One Approval Does Not Cover the Next Role
- How Security Clearances Change the Consent Request
- What Your Consent Record Must Show
- How to Run a Compliant Submission Step by Step
- Common Breaches and Your Next Submission
Consent Requirements by Type of Candidate Information
A CV pack can contain several kinds of personal information, and each item needs a clear purpose and recipient before it is shared. Classify the documents first, then record what the candidate has approved for the submission.
- Information — Personal or sensitive — Consent needed before submission — Notes
- CV contact details and work history — Personal — Yes, for each named role and recipient — Name each document in the request and treat each panel supplier as a separate recipient
- Identity documents — Personal — Yes, for the named role and recipient — Collect only what the role needs
- Security clearance status — Personal — Yes, for the named role and recipient — Use the candidate's own disclosure, never assumptions
- Referee details — Personal — Yes, before contacting referees — Ask the candidate to confirm each referee
- Health information — Sensitive — Yes, express consent generally required — Keep separate from the CV pack
- Biometric information — Sensitive — Yes, express consent generally required — Applies to identity verification tools
- Racial or ethnic origin, religious or political beliefs — Sensitive — Yes, express consent generally required — Diversity data should never be bundled into the CV
How to read a mixed pack
CV contact details and work history are personal information. Name the role and recipient in the approval request. If another panel supplier is to receive the CV, record approval for that recipient too.
Identity documents are also personal information. Request a passport or driver licence only when the role requires it. A software developer role that does not ask for photo ID does not justify including a passport scan “just in case”.
Sensitive information needs separate attention. Health information, biometric information, racial or ethnic origin, and religious or political beliefs generally require express consent before collection. Keep diversity questions and health declarations out of the general CV approval.
A pack containing a CV, passport copy and health declaration has three distinct document categories. The health declaration carries the stricter express-consent requirement. Referee details need separate approval if you intend to contact those referees.
Practical rule: Name every category of information in the pack before submission.
For a disputed employment-check result, background check dispute steps for employers may help frame the discussion. Keep the candidate's approval aligned with the information collected and shared, and refer to erecruit's privacy information for details about its handling of personal information.
Why Valid Consent Comes Before Every CV Moves
A recruiter tells a candidate, "we'll share your CV", and the file goes to a panel supplier the same afternoon. The candidate never heard the recipient, the role, or what happens if they refuse. That approval doesn't hold.
The Office of the Australian Information Commissioner sets the test under the Privacy Act 1988. Under Australian Privacy Principle 3, an organisation may collect only personal information that is reasonably necessary for its functions or activities, while an Australian Government agency must collect information that is directly related to its functions. Sensitive information, such as health information, biometric information, racial or ethnic information, and political or religious beliefs, generally requires the individual's consent before collection.
The same guidance names four conditions. Consent is valid only when the person is adequately informed, consents voluntarily, gives consent that is current and specific, and has the capacity to understand and communicate the decision.
Test the four conditions in order
- Adequately informed: Did the candidate know the recipient, the purpose, the documents, and the consequences of refusing?
- Voluntary: Could they say no without losing other work you'd already agreed?
- Current and specific: Does this approval cover this submission now, not a general "keep me on file"?
- Capacity: Can the candidate understand the request and communicate the decision?
A consent record should identify what will be collected, why it's needed, who may receive it, and how long the authorisation applies. Research settings use a similar standard of naming purpose and consequences, which Documind's guide to informed consent sets out in plain terms you can borrow for the wording.
Rewrite one standard request this week so it names the recipient, the role, the documents, the purpose and the duration. If it fails any of the four conditions, it isn't the request you send.
When One Approval Does Not Cover the Next Role
Express consent and implied consent aren't interchangeable, and neither one lasts for every later role.
The OAIC's guidance on consent states that express consent may be given openly in writing, verbally, or through an electronic or voice signature. Implied consent for non-sensitive information needs a reasonable basis. Informing someone that their information will be handled doesn't, by itself, establish implied consent unless an appropriate opt-out mechanism exists. A request must explain the purpose and be as specific as possible, including the consequences of consenting or refusing.
Individuals may withdraw consent at any time, and the withdrawal process must be easy and accessible. Once consent is withdrawn, you can't rely on the earlier consent for future use or disclosure.
One candidate, two roles
Candidate A approved a submission to Panel Supplier X for a cloud engineering role in March. In July a data role appears at Supplier Y. The March approval doesn't cover July, and the Supplier X approval doesn't carry to Supplier Y. Recording the candidate, role, recipient, scope, date, method and withdrawal status shows that gap without you reconstructing the email thread.
I would set these renewal triggers in the pipeline.
- A new role, even with the same supplier.
- A new recipient, meaning a different panel supplier, end client or agency.
- A new document, such as a clearance letter or passport that wasn't in the original approval.
- A review date that has passed, so the approval is no longer current.
Give the candidate a withdrawal route they can use in one step, such as a reply address a coordinator checks daily. Remove a withdrawn candidate from active pipelines the same day.
How Security Clearances Change the Consent Request
A candidate can't apply for an Australian Government security clearance on their own. The AGSVA applicant guide states that the clearance must be sponsored by a government or business entity, and where a role requires a new clearance the employer submits the request to the Australian Government Security Vetting Agency. Standard eligibility requires Australian citizenship and a checkable background. A sponsoring entity may waive those requirements for an exceptional business need following a risk assessment, and a waiver doesn't guarantee approval.
The written approval therefore covers more than the CV. The candidate agrees that clearance history, sponsorship status and checkable background information may be disclosed to the sponsoring entity and assessed for the named role. Clearance details are never published on erecruit, and the panel agency verifies the clearance level with the vetting authority.
According to AGSVA's security clearance definitions, Baseline permits ongoing access up to and including PROTECTED, NV1 permits ongoing access up to and including SECRET with limited temporary access to TOP SECRET in specified circumstances, and NV2 permits ongoing access up to and including TOP SECRET. AGSVA's revalidation guidance revalidates Baseline every 15 years, NV1 every 10 years and NV2 every five to seven years, and a clearance is cancelled if the holder doesn't complete the required revalidation.
- Level — Ongoing access — Revalidation
- Baseline — Up to and including PROTECTED — Every 15 years
- NV1 — Up to and including SECRET, with limited temporary TOP SECRET access in specified circumstances — Every 10 years
- NV2 — Up to and including TOP SECRET — Every five to seven years
Say a cloud engineer holds Baseline, with revalidation due in two years. The consent record notes the level the candidate disclosed and that revalidation date. You don't treat a current Baseline as support for an NV1 cybersecurity role. How the levels map to government software, cloud and data work is set out in our guide to Australian security clearance levels.
Does your record show the clearance level the candidate holds, and the date its revalidation falls due?
What Your Consent Record Must Show
A candidate can approve one submission and later challenge another. Keep a separate, auditable record for each candidate, role and recipient, tied to the specific documents approved.
The consolidated APP guidelines support treating consent for one disclosure separately from any later sharing. Seek approval again for each new recipient. Record the details that let a reviewer establish exactly what the candidate agreed to.
- Field — What to record — Example
- Candidate — Full name and your candidate reference — Priya Sharma, candidate reference C-1842
- Role — Role title and the opportunity or ad reference — Cloud engineer, opportunity reference from the ad
- Recipient — Panel supplier or end client receiving the CV — Named panel supplier, with ABN
- Documents — Each document disclosed, with version — CV version 3, referee list
- Purpose — Why the information is disclosed — Assessing fit for the named role
- Method — How consent was given — Email reply, recorded verbal consent, e-signature
- Date and expiry — When consent was given and when it lapses — Given 14 May, review after 90 days
- Status — Active, withdrawn or expired, with date — Withdrawn 2 June, removed from pipeline
- Obtained by — Recruiter who collected the approval — Recruiter name and role
Why the person who asked matters
Use the same record structure for each submission. For example, Priya approves by email on 14 May the disclosure of CV version 3 and a referee list to one named panel supplier, for one cloud engineer opportunity. The record states the purpose and review date. If she withdraws consent on 2 June, update the status and stop using that approval.
A panel supplier or agency may ask who obtained consent and what the candidate was told. A shared inbox entry marked “approved” does not answer either question. Name the recruiter who requested approval so a reviewer can identify the person responsible.
Can you retrieve every field for a submission from last quarter within a few minutes? If not, the record is not audit-ready.
How to Run a Compliant Submission Step by Step
Run the send as a sequence. Skipping a step is how a technically strong Azure or .NET candidate becomes a compliance problem.
- Confirm the opportunity names the role and the recipient. A label such as "DevOps, government" can't be scoped, so any approval you collect against it won't be specific. Use the ad title and the panel supplier's legal name.
- Classify each document as personal or sensitive before you draft the request. A mixed pack needs every category named. A health form or a biometric identity check doesn't hide inside the CV filename.
- Send the request with the purpose, the recipient, the documents, how long you'll keep them, and what happens if the candidate refuses. Leave any of those out and the request isn't informed. Offer a genuine no.
- Record the response with the date, the method and the person who obtained it. An unrecorded yes can't be proved when a panel supplier asks in three months. Paste the candidate's words, don't paraphrase them into "all good".
- Check the record matches this recipient and this role. If it doesn't, go back and seek a fresh approval. An earlier yes for a Java role at another supplier doesn't transfer to a Kubernetes role here.
- Submit only the documents named in the record, then log the submission date. An extra passport scan exceeds the approval even when it would help the panel. If a contract PDF is too large to send cleanly, compressing HR contracts with PDFWix keeps the file manageable, but the version you attach must still be the version you recorded.
- Set the review date. On withdrawal, remove the candidate from active pipelines and from any cached profile the same day. Withdrawn consent can't support a later match to a new government cloud contract.
A candidate pipeline only helps if consent status sits on the same card as the submission. On file, a compliant send has four pieces that agree with each other. The request, the response, the record, and a submission log that lists the same documents and the same date.
Common Breaches and Your Next Submission
The breach that creates the most risk is sending the CV because the candidate applied. An application isn't representation consent for a named panel supplier or a Commonwealth agency.
- Breach — Risk — Fix
- Submitting a CV before any approval exists — Unlawful disclosure of personal information — Hold the submission until approval is recorded
- Relying on a verbal yes with no record — Cannot prove approval was informed — Record date, method, wording and the person who obtained it
- Sending to a new panel supplier on old approval — Approval scope exceeded — Obtain fresh approval for each recipient and role
- Continuing to use a candidate after withdrawal — Use after consent is withdrawn — Remove from active pipelines and caches, and log the withdrawal
- Matching a cached profile to new roles without renewal — Stale approval — Set review dates and reconfirm before each submission
A verbal yes with no wording, no date and no name is the next failure. You may remember the call. An auditor won't. Scope fails the same way when last month's approval for Supplier X is used for Supplier Y, or for a different cybersecurity contract at the same firm.
A withdrawn candidate who is still on a live card, or still sitting in a cached profile that your matching runs against, is still being used. So is a candidate you match to new roles months after the approval, with no renewal. Both need the same remedy. Take them out of active use, and don't put them back until a fresh approval exists.
Each quarter, sample five submissions. Each one needs a matching record with role, recipient, documents, date and status. Treat any gap as a stop-and-fix item, not a note for the next team meeting.
Before the next submission, confirm the record matches the role and the recipient, review anything older than its review date, and check that every withdrawn candidate is off active pipelines. The consent gate requires a candidate's representation consent before that candidate is submitted. You can source candidates, track them from unqualified to placed, and gate submissions on consent, then apply that same check to each Australian Government ICT role you shortlist.
The record is only as good as its weakest entry. One missing recipient, or one stale date, is the entry a reviewer will find.
erecruit maps Australian Government ICT procurement opportunities to the live job ads that tender-panel agencies are running, and the consent gate sits in that workflow so a candidate isn't submitted until representation consent is recorded. If you place cloud, cybersecurity, data or software contractors onto government panels, start with the opportunities already linked to the ads. Visit erecruit and run the next shortlist against a record you can defend.