How to Prove ICT Skills for ACS Assessment: 2026 Guide

If you are working out how to prove ICT skills for ACS assessment, start with one uncomfortable fact: your degree is not the proof. The Australian Computer Society (ACS) assesses whether your ICT skills are current and whether the duties you actually perform match the professional level of your nominated ANZSCO occupation. A ten-year-old computer science degree opens the door. It does not carry you through it. What carries you through is the evidence you build, and most shortfall findings come from evidence that names a job title and a set of dates but never shows an assessor a professional at work.

This guide is a construction methodology, not another document checklist. This guide is written for ICT professionals whose qualification is dated, who have pivoted into a different sub-field, or whose role does not map cleanly to an ANZSCO title; each step explains why an evidence type works and how to build it so it survives assessor scrutiny.

What ACS Assessors Actually Score in Your ICT Skills Evidence

ACS does not score employment duration. It scores whether the complexity and autonomy of your work match the professional level ANZSCO defines for your occupation. The lens for that judgment is SFIA, the Skills Framework for the Information Age, which the ACS assessment process page names as the framework underpinning every assessment. No competitor guide mentions it, yet SFIA is the reason a vague duty list fails: it gives assessors four dimensions to weigh, including depth of knowledge, level of autonomy, complexity of the environment, and scope of influence. "Maintained web applications" scores nothing on any of them. "Owned the release pipeline for a payments service handling 4,000 daily transactions, deciding rollback criteria without escalation" scores on all four.

How ACS maps your current role to an ANZSCO unit group

ACS ignores your job title and reads your duties. A person titled "Full Stack Developer" who spends most of their week designing system architecture may map better to 261313 Software Engineer than to 261312 Developer Programmer. Read the brief duty descriptors on the ACS IT occupations page, then choose the code your real tasks fit, not the one your business card suggests.

The three applicant risk zones

Evidence intensity is not the same for everyone. Your qualification-to-role gap sets how hard your evidence has to work. This matrix is built from the ACS qualification thresholds and ANZSCO classification logic:

Work out which zone you are in before you gather a single document. It decides your pathway and how much recent, technical proof you need.

Step 1: Match Your Day-to-Day Duties to an ANZSCO Occupation

Build the crosswalk first. Open your target ANZSCO unit group, list its duty descriptors down one column, and against each one write two or three real tasks you perform, naming the systems and the decisions you own. This document does not get submitted to ACS. It is your map: it shows you which duties you can prove and which are thin, so you know where to strengthen evidence before you collect it.

Find the right unit group when your title has no match

Strip your title away and describe your week in verbs and systems. A "DevOps Engineer" who mostly hardens infrastructure and runs incident response may fit a Cyber Security code better than a generic development one. Match on tasks, because that is what the assessor matches on.

Scope your experience with the Skill Level Requirement Met Date

This one date quietly costs applicants years of claimable experience, and no competitor page explains it. The Skill Level Requirement Met Date (SLRMD) is the earliest point at which you have completed both your qualifying credential and the minimum experience ACS requires. Employment before that date is excluded from Skilled Employment for migration points, however relevant it was.

Worked example: you complete your degree in January 2014 and your occupation requires two years of experience. Your SLRMD is January 2016, so the ICT work you did from 2014 to 2016 counts toward reaching the requirement but not toward points. Calculate this before you write anything, because it tells you which employment period actually earns you credit.

Step 2: Employment Evidence Built to Prove Technical Depth, Not Tenure

Employment reference letters are your primary evidence vehicle, and a single missing field can invalidate an entire reference. The ACS InfoHub specifies 13 mandatory elements, and most competitor lists stop at five or six. Note also that ACS gives fullest weight to recent work within your assessed period; older employment still counts toward your SLRMD calculation but may carry reduced assessor weight.

For a full list of which documents are required at each stage, cross-check our ACS skills assessment eligibility documents guide alongside this section.

The 13 elements a valid ACS reference letter must include

Every reference must carry all of the following:

1. Company letterhead showing employer name and address

2. Company website URL

3. Your full name

4. The date of the letter

5. Employment dates in DD/MM/YYYY format (use "current" for ongoing roles, with a position history table when you held several positions at the same employer)

6. Employment status: permanent full-time, part-time, or contractor

7. Minimum weekly hours worked

8. Annual pre-tax salary and benefits

9. Work location designation (Australia or Outside Australia)

10. Position or role title

11. Bullet-pointed duties, listed separately for each position held

12. A signature from an authorised representative, with their full contact details (name, position, phone, and work email)

13. A digital verification certificate confirming the signatory's identity and authority

The elements applicants forget most are the website URL, the pre-tax salary, and the digital verification certificate. Salary is not optional, and a scanned wet signature without the verification certificate is not enough. Either missing field, on its own, is grounds for rejection of the reference.

Write duties that parallel ANZSCO without copying it

Here is the single most preventable rejection trigger, and it is on the official page: ACS rejects any reference whose duties are copied directly from ANZSCO code text or lifted from another reference. Applicants who paraphrase the official descriptor to "sound right" get the whole reference invalidated. Write from your actual work instead, framed for SFIA.

Do not write "analyses and develops software solutions." Write "refactored a monolithic Java billing service into six Spring Boot microservices, owning the API contract and the cutover plan across a five-person team." That parallels the ANZSCO duty, proves autonomy and complexity, and copies nothing.

Corroborating documents (payslips, tax records, a promotion letter, an org chart) do the quiet work of backing a borderline claim, especially when a signatory is junior or the company is small.

Step 3: Write Project Descriptions That Show Current, Active Skill

A project description is where you demonstrate current competency in detail. Learning how to prove ICT skills for ACS assessment really means learning to write these well.

Worked example: AWS infrastructure migration (261313)

Here is how a Software Engineer (261313) might document an AWS infrastructure migration. Use it as a model, not a template to copy.

Situation: a legacy monolith ran on two on-premises servers with 45-minute manual deployments and frequent capacity failures at month-end.

Actions: you designed and led the migration to AWS, containerising the app onto EC2 behind an auto-scaling group, moving the database to RDS PostgreSQL with automated backups, and codifying the whole environment in Terraform so it was reproducible.

Your role: technical lead on a team of four, owning the architecture decisions and the rollback criteria.

Outcome: deployments dropped from 45 minutes to under 8, and month-end outages stopped.

Notice what makes this score: named technologies (EC2, RDS, Terraform), a defined role, a decision you owned, and a measurable result. Swap in your own real numbers; never invent them.

Handling contract, freelance, and short-tenure roles

For recruitment agency or contract placements, the reference must come from the host company where you did the work, not the staffing agency. Freelance or self-employed applicants need formal company statements from clients plus payment verification showing consistent income. When an employer refuses to write a detailed technical letter, a statutory declaration is the accepted fallback, written by you and witnessed, corroborated by payslips and tax records. Note that unpaid leave, unpaid internships, and volunteer work do not count toward the experience requirement.

Step 4: Add Certifications and Portfolio Evidence

Certifications strengthen a borderline case. They cannot replace documented paid employment.

Which ICT certifications ACS treats as current-skills evidence in 2026

Read this carefully, because the SERP gets it wrong. Vendor certifications supplement your submission but cannot replace the two project reports the RPL pathway requires. Under the RPL pathway, ACS looks for vendor certification evidence that demonstrates current knowledge, but it sits alongside your project reports rather than standing in for them. If you are a Software Engineer or ICT Business Analyst applying through the employment pathway, an AWS Certified Solutions Architect or Azure Administrator badge is supplementary context, not proof of current competency in your primary submission. Do not over-rely on it.

What GitHub portfolios and open-source work actually prove

A GitHub profile proves you write in specific languages and frameworks, keep an active commit history, and can collaborate in public. It cannot prove paid employment, business outcomes, or professional accountability, and ACS requires all three for full employment credit. Treat your portfolio as corroboration of technical currency, not as a substitute for a compliant reference letter.

Step 5: Use the RPL Pathway When Your Degree Does Not Match Your Role

If your qualification does not meet the closely-related standard, or you have no ICT degree at all, RPL is your route. It requires a minimum period of relevant work experience and carries a fee; confirm the current experience requirement and fees on acs.org.au before applying. Our pathways comparison walks through which pathway fits which profile.

Structure your RPL project episodes around recent work

Get the recency right, because competitor blogs get it wrong. The official ACS RPL page requires two project reports: one completed within the last two years and one within the last four, with your most recent work active or completed within the last two years. Several third-party sites circulate three-year and five-year windows; those figures conflict with the official page, and submitting a project outside the real window risks immediate rejection.

Structure each episode around SFIA dimensions: describe the situation, the actions you personally took, the technologies you applied, and the verifiable outcome, written in the first person so your individual contribution is unmistakable.

Five Evidence Mistakes That Trigger an ACS Shortfall Finding

1. Duties copied from ANZSCO text. The fastest way to invalidate a reference. Write from your real work instead.

2. Vague, tenure-based duties. "Responsible for development" tells an assessor nothing about complexity or autonomy.

3. Missing salary or website data. Two of the 13 mandatory elements applicants most often omit; either omission alone can sink the reference.

4. Agency reference instead of host company. For contract roles, the host company must sign, not the recruiter.

5. Missing digital verification certificate. A signature alone does not meet the requirement; both the signature and the certificate are independently mandatory.

Our self-audit guide to RPL rejection reasons goes deeper on the patterns behind these findings.

How to Self-Check Your Evidence Before You Submit for Assessment

No documentation can be added after submission, so your package must be decision-ready on day one. Run a final crosswalk: map every claimed duty to a specific ANZSCO descriptor, confirm all 13 reference elements are present in each letter, and verify your Skilled Employment period starts after your SLRMD. If a duty could describe any developer at any company, it is too vague. If the letter has dates and a title but no named systems or owned decisions, it reads as tenure, not skill.

Warning signs your reference letter will not survive scrutiny

Check for these before you submit:

• Generic duties with no named systems, languages, or platforms

• Employment dates without the SLRMD calculation to confirm they fall within your assessed period

• A signatory whose contact details cannot be independently verified

• Salary or pre-tax compensation left blank

• No digital verification certificate alongside the signature

If any of these apply, the fix is straightforward. What is not straightforward is discovering the gap after your submission is lodged.

Frequently Asked Questions

Does ACS require my ICT skills to be current if my degree is more than 10 years old?

Yes. ACS assesses current competency, not qualification age. A dated degree makes recent, detailed employment and project evidence more important, not less. Your Skill Level Requirement Met Date will also restrict which employment counts toward your assessed period, so confirm that date before scoping your evidence.

Can a GitHub portfolio or open-source contributions count as evidence of current ICT skills for ACS?

Only as supporting evidence. A portfolio can show active use of specific languages and frameworks and a live contribution history, but it cannot prove paid employment, business outcomes, or professional accountability, all of which ACS requires for full employment credit. Use it to corroborate a compliant reference letter, not to replace one.

What should I do if my employer refuses to write a detailed technical reference letter for ACS?

Use a statutory declaration, which ACS accepts when an employer reference is unavailable. You write and sign it before an authorised witness, then back it with corroborating documents such as payslips, tax records, and an employment contract. The declaration must still convey specific technical duties, not just employment dates.

How many recent projects do I need to document to satisfy ACS current-skills requirements?

For the RPL pathway, exactly two project reports: one from within the last two years and one from within the last four. For General Skills, focus on employment references that cover work within your assessed period. Well-documented projects strengthen those references, but the formal project reports are an RPL-specific requirement.

Does an AWS, Azure, or Google Cloud certification count as proof of current ICT skills for ACS in 2026?

Not on their own. Under the RPL pathway, ACS looks for vendor certification evidence of current knowledge, but certifications sit alongside the two required project reports rather than replacing them. Through the employment pathway, treat a cloud certification as supplementary evidence of currency, not as standalone proof of professional competency. The paid, documented work in your reference letters remains the core of your submission.

Before you apply, review the ACS skills assessment document checklist to confirm every evidence type in this guide is present in your submission package, and read our pathways explained guide if you are still deciding between General Skills and RPL.