How to Prepare an ACS RPL Report: Structure, Projects and Evidence

The RPL pathway is for applicants who either don't have an ICT qualification, or have an ICT qualification that doesn't meet the standard for the general-skills pathway. It relies on demonstrating ICT competencies through documented professional experience and two written project reports.

Applicants with a strong, closely-related ICT degree usually don't need RPL — the general skills assessment covers them. Choose RPL when it's the only realistic pathway for your background.

You need to write two project reports covering different projects you've personally worked on. Each report should be around 2,000–3,000 words, describing what the project was, what your role was, what technical competencies you demonstrated, and how the project outcome contributed to the business or user need.

The reports must be written in your own words. ACS runs plagiarism checks and rejects reports with copied content. They also spot AI-generated writing — the safest approach is to write from your genuine experience.

Pick projects that (a) you were personally central to — not team observer, not distant client, (b) demonstrate substantial ICT competencies, (c) had a clear beginning and outcome you can describe, and (d) span different types of work between the two reports (e.g. one design/build, one implementation/support).

The two projects should cover, between them, the ACS competency areas ACS expects for your nominated ANZSCO code.

Section 1 — Identification: Project name, dates, employer, your role and reporting line.

Section 2 — Business opportunity/problem: What was the business or user need? Why was the project greenlit?

Section 3 — Solution architecture and technology: What was the solution? Which technologies, methodologies and standards were used? Why those choices?

Section 4 — Your personal contribution: This is the heart of the report. Specific tasks, specific decisions you made, specific outputs you produced. First person, active voice.

Section 5 — Project outcome: Did the project succeed? What was delivered? What did you learn?

Along with the project reports, RPL applicants need to demonstrate the required years of relevant, post-qualification ICT experience. Employment evidence follows the same standards as the general ACS pathway — reference letters on letterhead, specific duties, dates and hours, supporting payslips/contracts where available.

1. Reports read like resume entries. Bullet lists of responsibilities rather than a substantive narrative of what you did and why.

2. Team pronouns. 'We designed…' says nothing about what you did. Every RPL sentence about your contribution should use 'I'.

3. Copied text. ACS rejects reports with copied methodology descriptions, framework definitions, or any lifted content.

4. Weak project choice. Projects where your role was peripheral or where the technical substance is thin.

Migration First coordinates the preparation of ACS RPL reports through independent ICT specialists. We help you select the right projects, structure the narrative, and quality-review the writing to ensure it reads as authentic, substantive and personal.