How to Write an ACS RPL Report: Structure and Pitfalls to Avoid

ACS RPL (Recognition of Prior Learning) is the assessment pathway for people who do not have a formal ICT qualification but have practical experience in technology. Unlike Skills Match (which relies on qualifications), RPL requires you to write a report describing your professional experience in detail.

Structure of the RPL report

ACS specifies a clear three-part structure:

Part 1 — Background Summary

This is an overview of your ICT career. Write it in a narrative style, around 200–300 words:

How you started working in ICT
Your main career stages
The technologies, programming languages, or fields you specialise in
Your total years of ICT experience

This is not the place to describe each project in detail — that is part 2.

Part 2 — Core ICT Activity

This is the most important and longest part of the report. You must describe at least 2 real ICT projects (people usually write 3 to be safe), each around 1,000–2,500 words.

Each project needs to fully cover these elements:

1. Project/Role Overview:

The project name and timeframe
Context: what the organisation is, its size, the project’s goals
Your role in the project

2. Employer or Client:

Who benefited from your output (an internal team, an external client)
Your relationship with them

3. Your Specific Role:

Write in the first person: “I did…” — not “we did…”
List specifically what you personally carried out, not the team
Which technical decisions you made
Which problems you solved and how

4. Technology Used:

Programming languages, frameworks, databases, cloud platforms, DevOps tools
Versions and the reasons you chose that technology (where a technical decision was involved)

5. Outcome and Impact:

Specific measurable results (reduced processing time by 40%, increased uptime to 99.9%, served 10,000 users)
The impact on the business or organisation

Part 3 — Summary

Connect the overall picture between the experience you described and the requirements of the occupation you want assessed. Around 150–300 words.

Overall length

An RPL report is usually 3,000 to 6,000 words in total (in English). Too short and it will lack detail — ACS needs enough information to assess. Too long but lacking substance is no help either.

Common mistakes to avoid

Writing “we” instead of “I”

The most common mistake. ACS wants to know what you did — not what the team did. If a reader of the report cannot tell what your individual contribution was, ACS cannot assess your capability accurately.

No technical detail

Writing “I developed a website” is not enough. You need: “I built a REST API using Node.js 16 + Express, used PostgreSQL for the backend and React 18 for the frontend, and deployed on AWS EC2 with an auto-scaling group and an ALB.”

Copying from a job description

ACS can recognise template language. The report must describe specific reality, not generic responsibilities lifted from a job description.

Unclear outcomes

“The project was a success” is not enough. You need specific results: numbers, time, performance, or at least a clear qualitative description.

Lack of continuity between parts

The Background must be consistent with the projects in the Core ICT — you should not describe relevant work experience meeting an IT management requirement while the projects describe pure coding only.

The language for the RPL

The RPL report must be written in English. If your written English is not strong enough, you can ask someone with better English to help with the drafting — but the content must be your own real experience.

Cost and time

Cost: Fees vary by assessment type (for example skills assessment, RPL) and over time — check the official fee schedule on the ACS website.
Processing time: Assessment times vary by assessment type and application volume — check the current timeframes on the official ACS website.

See ACS: choosing the right pathway — Skills Match, RPL or Post-Study to determine whether RPL is the most suitable route for you.