Representation Agreement Template for Government ICT Roles
Get a representation agreement template with role-specific consent, named recipients and withdrawal steps for Australian Government ICT submissions.

A signed representation agreement is the advice most recruiters still hand around, and it is the weakest part of the file. A long evergreen authority, ticked once and filed, does not show that a candidate understood a particular submission. The Australian Public Service Commission privacy factsheet draws the line clearly: a privacy notice mainly gives transparency, while express consent needs a clear indication of agreement to a particular use, such as sharing details with another agency or a merit pool. For government labour-hire recruitment, agencies must obtain explicit informed consent before sharing merit-list details, and they must remove candidates who decline sharing.
For Australian Government ICT work, that distinction is the whole job of the document. A cloud engineer, a cybersecurity contractor, or a data role on a panel is not "representation in general". It is one requisition, one recipient, and one set of clearance and location facts. I would rather hold a short, role-specific approval with a timestamp than a twelve-month blanket form that nobody can audit.
Table of Contents
- Template Fields at a Glance
- Writing the Role-Specific Approval Clause
- Privacy Obligations the Template Must Record
- Preventing Double Representation
- Screening Fields for Government ICT Roles
- How to Run the Consent Record From Approval to Withdrawal
- Related Guides and Where the Template Fits
- Confirm Consent Before Your Next Submission
Template Fields at a Glance
Some searchers land here looking for guardianship or care arrangements. This guide is about the recruiter-to-candidate approval document used before a CV goes to an Australian Government ICT role, whether that is a government software engineer job, a government DevOps contract, or a cleared cloud role.
A usable representation agreement template is a set of fields you can complete the same way every time. Before you lock the wording, it is worth reading how lawyers spot red flags before signing, because a clause that looks routine can widen, without anyone noticing, who may receive a CV or how long the authority lasts.
- Template field — What to record — Example entry
- Parties — Recruiter or agency name, candidate full name, ABN where applicable — Ridgeline Talent Pty Ltd; candidate Jordan Lee
- Opportunity — Role title, agency and BuyICT or notice reference — Cloud engineer, named agency, notice reference from the listing
- Recipients — Named agency or panel supplier allowed to receive the CV — One named agency; no onward sharing
- Information to submit — CV version, referee details, citizenship and clearance status — CV version 3, two referees, clearance status stated
- Purpose — Recruitment for the listed role only — Submission to one listed role
- Consent scope — Submission approval, with future-role consideration recorded separately — Yes to submission; no to future roles
- Sensitive information — Health, criminal history or similar details, only with separate approval — Excluded unless separately approved
- Validity and withdrawal — Start date, end date and route to withdraw — Agreed end date; withdraw by written notice
- Record metadata — Timestamp, template version, channel and withdrawal status — 20 Nov 2026 10:15 AEDT; template v2; secure web form; not withdrawn
How to fill the rows
Parties stop the record being "the agency" in the abstract. Name the recruiting entity, the candidate, and the ABN where the submitter is a company. Opportunity pins the approval to a title plus a notice or BuyICT reference, not to "government cloud jobs" as a category. Recipients lists who may see the CV. If the panel supplier is the only party allowed to receive it, write that, and do not leave room for onward sharing to an unnamed host.
Information to submit is the packet, not a promise to send "whatever the client asks". Name the CV version, the referees, and whether citizenship and clearance status are included. Purpose stays narrow: recruitment for the listed role. Consent scope splits the yes for this submission from any later consideration for similar roles. A candidate can approve a .NET contract in one agency and refuse a later Java or Power Platform shortlist.
Sensitive information stays out unless a separate approval covers health, criminal history, or similar detail. Validity and withdrawal needs a start, an end, and a route that is usable, such as written notice. Record metadata is what makes the signature auditable: timestamp, template version, channel, and whether consent has been withdrawn.
Practical rule: Complete one approval record per role, not one record per candidate. A person chasing three Australian Government technology jobs needs three records, even when the CV file is the same.
Writing the Role-Specific Approval Clause
The core line should be specific and affirmative. Use wording the candidate can read in one pass:
I approve submission of my CV and listed details to [agency] for [role reference] only.
That sentence names the candidate's act, the recipient, and the limit. Around it, the clause still has to identify the candidate, the recruiter or agency, the specific role or requisition, the proposed client or Commonwealth agency where known, the information to be submitted, and the intended recruitment purpose. A government cybersecurity contract and a government data engineering contract are different approvals, even when both sit with the same panel supplier.
The OAIC's Australian Privacy Principles guidance on collection sets the test for valid consent: it must be adequately informed, voluntary, current, and specific, and it must be given by a person capable of understanding and communicating it. Consent can't be inferred because a privacy notice was supplied. Store the signed record with timestamp, version, consent scope, channel, and withdrawal status. A worked layout for that gate sits in this approval workflow example.
Unticked choices, one decision each
Bundling fails because the OAIC states that consent is not voluntary when the individual can't control which uses they accept. Leave these choices unticked, and let the candidate mark each one:
- Named submission: Yes or no to sending the listed packet to this opportunity only. This is the decision that authorises the CV to leave your inbox.
- Panel or government disclosure: A separate yes or no for disclosure to panel suppliers or government entities beyond the named recipient. Do not fold this into the submission tick.
- Sensitive information: A separate yes or no for health, criminal history, or similar detail. Default it to no.
- Future roles: A separate yes or no for later consideration. Declining this must not block the original submission.
- Overseas or third-party processing: A separate yes or no where a tool, referee check, or processor sits outside the named parties.
A decline can be one line: "I do not approve future-role consideration, overseas processing, or sensitive-information handling. I do approve submission of CV version 3 to the named agency for the listed role reference."
Individuals may withdraw consent at any time, and after withdrawal the organisation can't rely on the previous consent for future use or disclosure. Record the withdrawal on the same approval, with the time and the channel, so the file shows both the grant and the stop.
Privacy Obligations the Template Must Record
The Fair Work Ombudsman's workplace privacy guide states that the Australian Privacy Principles apply to personal information about unsuccessful job candidates, including resumes, contact details, references, and academic transcripts. A government software developer who is not shortlisted is still a privacy record. So is the transcript you attached "just in case" for a technical architect role.
The template has to record four boundaries before anyone treats the file as cleared to send. What information may be collected. The role or opportunity it may be used for. Which recruiter or agency may receive it. Whether the candidate authorises disclosure to a client, host employer, or panel supplier. If any of those four is blank, you don't have an authority. You have a CV in a folder.
Third parties sit inside the same fence. The Fair Work Ombudsman notes that third parties providing recruitment, human-resources, payroll, or related services under contract may need to comply with those principles. Name the payroll bureau, the screening firm, or the panel supplier's HR desk, and name the job they do with the data. "Our partners" is not a recipient.
Consent should be considered before personal information is disclosed when the individual hasn't already requested the disclosure, for example when providing a reference. Calling an unlisted referee on a Kubernetes role because the hiring manager asked is a disclosure, not a courtesy. The Privacy Act 1988 and the Australian Privacy Principles make this documentation a record of purpose, authority, and disclosure boundaries. A plain-language account of how personal data is collected is a useful comparison when you are checking whether your own notice says what the form then authorises.
Checklist before the CV leaves the inbox
- Collection: The record lists the CV version, contact details, referees, and any transcript to be sent.
- Purpose: The use is recruitment for the listed Australian Government ICT role, not a general talent pool.
- Holder: The recruiter or agency, and any contracted HR or payroll party, is named with its role.
- Disclosure: The candidate has authorised, or refused, disclosure to the client, host, or panel supplier, including any referee contact they did not already request.
Limit the approval to a specified role, agency, client, or time period. Ambiguity is what a later dispute will exploit.
Preventing Double Representation
The usual mess is simple. Two agencies submit the same candidate to one requisition, or an agency submits while the candidate has already applied directly. Commission clauses don't fix that. They argue about who gets paid after the damage is done.
Australian recruitment discussions, as set out by Gorilla Jobs, treat duplicate submissions by two agencies, or by an agency and the candidate directly, as a recurring representation problem. Most template content still chases commission protection and exclusive representation instead of a fair process for disputed ownership. A better record asks the candidate to disclose any live application or prior representation for the same employer, contract, requisition, or materially identical role. The recruiter names the specific opportunity before submission. The approval states whether consent is exclusive, non-exclusive, or limited to one submission, and it explains how conflicts will be resolved.
- Consent type — How it works — What the record shows
- Exclusive — One recruiter holds the candidate for the role for a stated period — Holder, role reference and end date
- Non-exclusive — Several agencies may submit, with disclosure recorded — Each submission and recipient logged
- Single submission — One named opportunity, one recipient, one approval — Role reference, recipient and approval date
Picking a type without trapping the candidate
Exclusive fits when a candidate wants one recruiter to run a named government cloud contract for a stated period. Write the holder, the role reference, and the end date. Don't let "exclusive" spill into every Azure or cybersecurity vacancy in Canberra.
Non-exclusive fits when the candidate is already talking to more than one panel supplier. Several agencies may submit, but each submission and each recipient is logged. The candidate still discloses live applications so two firms don't hit the same buyer on the same day.
Single submission is the cleanest default for Australian Government ICT contracting. One named opportunity, one recipient, one approval. The record shows the role reference, the recipient, and the approval date. A later Microsoft 365 role, or a separate machine-learning contract, gets its own line.
Privacy practice still applies underneath the commercial choice. Personal information should be collected only where necessary, applicants should be told the purpose and consequences of collection, and consent should be obtained before contacting an unlisted referee. For government recruitment, also specify who may receive the CV, how it will be stored, when it will be deleted, and how the candidate can request removal.
If two claims match, tell the candidate who submitted first, check the timestamps, and let the candidate decide what happens next. The candidate can withdraw before submission. The record keeps the time consent was granted. The working model is a consent ledger: each submission linked to one opportunity, one recipient, and one explicit approval.
Screening Fields for Government ICT Roles
A clearance field that says "cleared" tells a later reviewer almost nothing. The AGSVA Security Clearance Applicant Guide Book (September 2025 edition) sets the levels and access boundaries that screening has to name precisely. Check that edition again when you reuse the template, because clearance settings change.
- Clearance level — Covers classified resources up to — Template screening field
- Baseline — PROTECTED — Level sought or held, sponsor, citizenship confirmed
- NV1 — SECRET — Level sought or held, sponsor, citizenship confirmed
- NV2 — TOP SECRET — Level sought or held, sponsor, citizenship confirmed
The fields stay the same at every level. What changes is the classified ceiling the role can touch, so the column that matters on the record is the level sought or already held. Write "NV1 held" or "Baseline sought". Leave "cleared" to the job ad.
The fields you complete in order
Citizenship first. Applicants must be Australian citizens with a checkable background. Record citizenship as confirmed or unconfirmed, and don't infer it from a local phone number or a long APS contracting history.
Sponsorship second. Individuals can't apply independently; an employer or sponsoring organisation submits the clearance request. Name that sponsor on the template. If your agency isn't the sponsor, write who is, because a government project manager role and a labour-hire cybersecurity seat can sit under different sponsoring bodies.
Timing third. After submission, the applicant receives access to the myClearance system and a limited period to complete the application and upload the required documents. Record the date the request was submitted so the deadline is calculable on the same file as the role reference.
If the role needs no clearance yet, write that none is required and why, for example an unclassified digital delivery seat with no access to classified resources. An empty cell reads as "we forgot", a different problem from "not required".
Re-confirm citizenship, sponsor and level when the role's clearance requirement moves. A shift from an unclassified Python build into an NV1 environment gets a new screening entry with its own date. Pair the clearance line with the skill and location line in the job profile template so the approval and the vacancy describe the same person in the same seat.
How to Run the Consent Record From Approval to Withdrawal
Treat the file as a sequence, not a PDF you sign and forget. Each step exists so a later reader can see who approved what, and when that approval stopped.
- Record the approval first. Log the timestamp, template version, and channel before any submission. A CV sent at 9:00 and a form signed at 9:40 is a gap you can't talk your way out of.
- Confirm the role reference. Match the candidate and the requisition, including the opportunity's close date, against the notice. A retitled government technical architect ad is a different opportunity if the reference or the buyer has changed.
- Check live applications. Ask about prior representation for the same role before the CV goes. This is the moment double submission is still cheap to stop.
- Send only the listed packet. The named recipient gets the CV version and details the candidate approved. Extra certificates, an old referee, or a clearance pack that wasn't listed stay in the file.
- Log the send. Write the submission date and the recipient on the same record. The approval and the send should be readable as one line.
- Re-confirm when the facts move. A new client, a new clearance requirement, or a new recipient needs a fresh confirmation. Old consent doesn't stretch to cover the change.
- Record withdrawal and stop. Note the withdrawal and stop further use or disclosure under that consent. Silence after a withdrawal request is continued use.
- Set deletion and answer removal requests. Write when the CV will be deleted and how the candidate asks for removal, then act on the request. Storage "until we need it" isn't a rule.
The wider tests for what belongs in that record are set out in this guide to consent requirements.
What the finished line looks like
A complete ledger is one line per role: approval (yes, with time and version), recipient (named agency or panel supplier), submission date, and withdrawal status (not withdrawn, or withdrawn with the time). Three government ICT opportunities mean three lines, even when they share a candidate and a React or Java skill set.
If you can't read the line without opening a side email, the record isn't finished.
Related Guides and Where the Template Fits
The approval only works if it points at the right kind of opportunity. BuyICT identifies Digital Marketplace Panel 2 (DMP2) as an ICT Labour Hire marketplace, so buyers can engage candidates for short-term agency objectives. BuyICT's procurement guidance brings together ICT procurement options managed by the Digital Transformation Agency, including marketplaces, panels, and Coordinated Contracting Arrangements, and it lists DMP2 ICT Labour Hire among the mandatory arrangements.
That split is why a contractor search shouldn't be mixed up with a permanent APS vacancy. Agencies may source technology contractors through a panel marketplace, while the role can separately specify skill profile, location, timing, and security clearance. The template's role and clearance fields should match that notice, whether the stack is Azure, C#, TypeScript, or a data engineering brief.
- How Australian Government ICT contracting works is the page to read when you need the labour-hire path separated from an ongoing APS appointment before you name the parties.
- How to find government technology contracts in Australia is the page to read when you need the notice reference that belongs in the opportunity field.
- What security clearance an ICT job needs is the page to read when the ad states a level and you need to mirror it in the screening fields without guessing.
- Government ICT job search, opportunity listings, and agency pages on erecruit are where you check the role reference, location, timing, and clearance against the live notice before the candidate approves submission.
Confirm Consent Before Your Next Submission
The decision is binary. Send the CV only if a signed, role-specific approval already exists for that candidate and that opportunity. The consent gate requires a candidate's representation consent before that candidate is submitted.
Confirm three things before you look at match quality. The approval names the role reference. The named recipient matches the opportunity. The withdrawal route is recorded with the approval. Use the government ICT job search and the opportunity listings to check the role reference, closing date, and clearance requirement against the published notice. Each contract notice shown on erecruit links to the official AusTender record, so confirm the contract details there before you type the opportunity into the template.
- Check the reference. Put the notice reference next to the approval record and stop if they differ.
- One record per role. Open a new approval for each requisition instead of reusing last month's candidate form.
- Set the reminder. Re-confirm whenever the role, the clearance requirement, or the recipient changes.
This guide doesn't promise any placement outcome. It sets out the record that should exist before a CV leaves your inbox.
erecruit maps Australian Government ICT jobs, labour-hire requests, and procurement notices so you can see the role, clearance, location, and timing behind a submission before you ask a candidate to approve it. A representation agreement template only holds if the opportunity you name is the opportunity on the notice. Visit erecruit to check open government technology contracts and the ads panel suppliers are running against them.