Six years of solid ICT experience, a folder full of certificates, and you still cannot say which ones qualify as ACS RPL professional currency evidence. That gap is what this guide closes. The recency rule is tighter than most consultant pages admit, and the artefacts that survive assessor scrutiny are far more specific than a vague line about keeping your skills current.
Assessors reading an RPL application are looking for proof that you still practise the skills your nominated occupation demands, not that you once did. Get the evidence type wrong, or the dates wrong, and an otherwise strong application stalls in review.
What Professional Currency Means in an ACS RPL Application
Currency and experience are two different tests, and applicants routinely conflate them.
How ACS separates currency from general work experience
Your employment history proves depth. The RPL pathway asks for six years of relevant experience, with your most recent role active or within the last two years before submission. Professional currency proves something narrower: that the skills are still live right now. ACS asks for at least two forms of currency evidence, and its InfoHub page sorts the acceptable material into three categories: professional training and certification, professional artefacts such as code and applications, and professional development and industry engagement. Two employment references, however detailed, do not satisfy this requirement on their own.
The 2-year recency window and your reference period
Every currency item must be completed within the last two years. That is the operative rule the ACS InfoHub states, and it is where the biggest misconception creeps in. Submit in September 2026, and your currency evidence needs to fall inside the window from roughly September 2024 onward. A certification earned in 2021 sits outside it and carries little weight on its own.
Do not confuse this window with the RPL project report timeframes, which are a separate requirement entirely. For the two project reports, ACS asks that one document work from the preceding 24 months and the other from the preceding 48 months. Those windows govern your written project narratives. The two-year currency window governs your certificates, artefacts, and CPD records. Same application, different clocks.
Formal Evidence ACS Accepts for Professional Currency
Formal evidence is the easiest to verify and, when recent, the strongest element in your bundle.
Vendor certifications from AWS, Microsoft, Cisco, and CompTIA
Named vendor credentials are the cleanest currency signal you can offer. AWS Certified Solutions Architect, Cisco CCNA, CompTIA Security+, and Microsoft Azure Administrator all sit squarely inside the professional training and certification category. ACS explicitly flags vendor certifications as relevant for DevOps and Cyber Security occupations, which signals how much weight these credentials carry for the right ANZSCO code. A certification earned or renewed inside the two-year window is worth more than an older one, so lead with your freshest credential.
University short courses and graduate certificates after your degree
A graduate certificate or a university short course completed after your primary degree reads as deliberate, current upskilling. These items land well because they carry an academic transcript and a completion date that an assessor can check in seconds. A part-time cloud computing certificate finished in 2025 does double duty: it proves currency and signals continued investment in the discipline.
Documenting an in-progress certification without a completion date
An in-progress certification can count, provided you show active movement toward it rather than a vague intention. Include the enrolment confirmation email or a portal screenshot, the exam booking confirmation with its scheduled date, and a study log or partial exam attempt record. That combination demonstrates genuine engagement. An in-progress item works best as a supporting piece behind at least one fully completed recent credential, not as your only proof.
Non-Formal Evidence That Still Satisfies the Currency Rule
Some of the most persuasive evidence never came with a certificate.
GitHub commit history and open-source contributions
GitHub commit history and open-source contribution logs are accepted as professional artefacts, and for a working developer they can be the most authentic proof of currency in the whole bundle. One practical constraint shapes how you present them. ACS-focused advisory analysis indicates that assessors reviewing code artefacts look at design documentation, problem-solving approach, and project management artefacts rather than reading source lines. So do not submit a bare repository link. Pair your commit history with a clear README, an architecture diagram, and short design notes explaining what the project solves and how. The commits prove recency; the documentation proves competence.
Conference attendance and ICT-specific CPD records
Continuing professional development counts when it is genuinely ICT-specific and properly documented with dates and provider names. Events like AWS re:Invent, Microsoft Build, or a local event like YOW! Conference all qualify as CPD evidence, as do vendor workshops and technical seminars. A registration confirmation, a badge scan record, or a certificate of attendance turns a CV line into verifiable evidence. A conference you cannot date or name is an assertion, not evidence.
Internal training records and employer-issued certificates
Employer-run training and internal certificates are valid, though they sit lower in the pecking order because they are harder for an assessor to independently verify. Present them on company letterhead with a date, a course title, and the trainer or platform named. They work as corroboration around a stronger anchor, not as the centrepiece.
How Your ANZSCO Code Shapes Which Evidence Carries Weight
The same certificate does not carry the same assessor weight for every applicant. Match your strongest artefacts to the skills your nominated occupation actually demands. What follows is our reading of the public ANZSCO skill descriptors alongside ACS InfoHub guidance.
Software Engineer and Developer Programmer (261313, 261312)
Recent code artefacts carry the most weight for Software Engineer (261313) and Developer Programmer (261312). A GitHub profile with active commits, a deployed application, and an AWS or Azure developer certification map directly onto the design, build, and testing skills these occupations describe. A network certification, however current, does comparatively little for a 261313 application because it speaks to a different skill set.
Network and ICT Infrastructure roles (263111, 263112)
Network Administrator (263111) and Network Analyst (263112) applicants should invert that priority. A current Cisco CCNA, a cloud networking specialisation, or documented infrastructure project artefacts carry the most weight here, because they evidence the configuration, monitoring, and troubleshooting skills these occupations are built on. A general programming course is peripheral rather than central for these codes.
ICT analyst and management occupations (135111, 261111)
ICT Project Manager (135111) and ICT Business Analyst (261111) sit further from raw technical certification. Evidence that speaks to methodology, stakeholder engagement, and delivery aligns better with what these occupations assess: a completed agile or PRINCE2 course, a professional membership, or a conference presentation fits more naturally than a vendor infrastructure credential. A vendor certification still contributes, but it is not the natural centre of gravity.
Ranking Evidence Strength for a Software Engineering RPL
Competitor pages list accepted evidence in flat, unordered lists without ranking them. Based on our analysis of ACS InfoHub weighting language, here is how common ACS RPL professional currency evidence types stack up for a typical Software Engineer (261313) application, strongest first:
1. Active vendor certification aligned to the occupation, earned or renewed inside the two-year window (for example, a current AWS Certified Solutions Architect). Independently verifiable and occupation-matched.
2. A recently lapsed certification paired with a current recency item, so the expiry is offset by live proof of the same skill area.
3. GitHub with real commit history plus a README and design notes. Authentic and current, and stronger when the documentation does the explaining.
4. An in-progress certification backed by enrolment confirmation and a study log. Credible momentum, best as a supporting piece.
5. A dated, named conference or CPD record, such as a Microsoft Build attendance certificate or a YOW! Conference registration.
6. An internal training certificate. Valid, but the hardest for an assessor to verify independently, so it anchors nothing on its own.
The pattern across all six tiers: verifiability and occupation fit move an item up, while anything an assessor cannot check independently drifts down.
What ACS Rejects or Weights Poorly
Weak evidence does more than fail to help; it can drag an application into review.
Expired certifications with no recency item alongside them
The single most common self-inflicted wound is a bundle of expired certifications with nothing current beside them. A CCNA that lapsed in 2022, submitted alone, tells ACS your skills were current three years ago and says nothing about today. If you want to include a lapsed credential, place at least one item from inside the two-year window next to it.
Generic LinkedIn endorsements and platform badges
LinkedIn skill endorsements, gamified platform badges, and auto-issued micro-credentials carry almost no assessor weight. They require no verification and prove no sustained engagement. Treat them as profile decoration rather than application evidence.
Work history statements with no supporting artefact
A reference that describes you as staying current, unaccompanied by a single certificate, repository, or CPD record, asserts currency without demonstrating it. ACS reserves the right to reject currency evidence that does not meet the required standard or align with the professional level of your ANZSCO code. Generic descriptions with no concrete technical specifics attract the same outcome.
Assembling Your Currency Evidence Bundle
A strong bundle is deliberate, not a shoebox of PDFs. Aim for at least two forms of evidence; in practice, three to four well-chosen items give an assessor room to be satisfied without wading through clutter. Lead with your strongest, occupation-matched artefact, then support it. Label every file plainly with the item type, the date, and the issuing provider, so an assessor never has to guess what they are looking at. Confirm each item falls inside the two-year window before it goes in.
Building your ACS RPL professional currency evidence around your specific ANZSCO code, rather than including every certificate you own, is what separates a clean pass from an assessor query. If you are still weighing which ACS skills assessment pathway applies to your situation, confirm that first before assembling your currency bundle, since the RPL and qualifications pathways carry different evidence expectations. Check your eligibility documents are in order at the same time. Then run the whole bundle through the ACS RPL document checklist to confirm every currency item is formatted and labelled correctly, and cross-check it against the common RPL rejection reasons while you still have time to fix a gap.
ACS RPL Professional Currency Evidence: Frequently Asked Questions
Does GitHub activity count as ACS RPL currency evidence?
Yes. GitHub commit history and open-source contributions are accepted as professional artefacts. Present them with a README and design notes rather than a bare link, because assessors reviewing code look at your design documentation and problem-solving approach, not your source code line by line.
How strict is the 2-year recency window?
Professional currency evidence must be completed within the last two years, per the ACS InfoHub, and older items carry little weight on their own. This is separate from the RPL project reports, where one report must cover work from the last 24 months and the other from the last 48 months. The currency window governs your certificates and artefacts; the project windows govern your written narratives.
Can an in-progress certification count toward professional currency?
Yes, if you document active progress. Include the enrolment confirmation, the exam booking with its scheduled date, and a study log or partial exam record. An in-progress item is most persuasive when it sits behind at least one fully completed recent credential.
Do vendor certifications need to be currently active?
A current or recently renewed certification is stronger. An expired one can still contribute, but only when a current recency item accompanies it. An expired certification submitted alone demonstrates past currency, not present currency, which is the whole point of the requirement.
Does professional currency apply to the qualifications pathway?
Professional currency is central to the RPL pathway. The ACS skills assessment pathways page explains how evidence expectations differ by application type; confirm the exact requirement for your pathway on the ACS InfoHub before you submit.
How many professional currency items does ACS expect?
ACS sets the floor at a minimum of two forms of evidence. In practice, three to four well-documented, occupation-matched items give an assessor enough to be satisfied without diluting your bundle with weak or unverifiable material.
Ready to submit? Run your full document bundle through the ACS RPL document checklist to confirm every professional currency item is formatted and labelled correctly for assessors before it reaches ACS.