Occupation Fit
Match your project with the duties of your nominated ICT occupation. A technical job title alone is not a good reason to choose it.
ACS RPL Project Selector & Strategy Blueprint
List out every ICT project you can think of, then let a 5-step filter — recency, ANZSCO fit, technical depth, your role and your evidence — narrow them down to the strongest pair, complete with a writing blueprint for each.
100% private — nothing leaves your browser
About 5 minutes to complete
Free, no sign-up needed
Not Sure Which ICT Projects Belong in Your RPL?
Add everything from your work or study history — the selector checks each one against ACS rules on dates, occupation fit and technical depth, then surfaces the two candidates worth writing up.
Step 1 of 5
List Your Projects
Choose your nominated occupation, then enter 2–6 projects. More candidates give the funnel more to compare, so it can pick a genuinely strong pair.
This selector is a planning aid. It is not an official ACS decision. Every score comes from what you type in. Use only real projects from your own work, study, or ICT experience in your RPL report.
How This ACS RPL Project Filter Works
Each step removes weak projects. A project must pass all five checks before we recommend it. This is the same way an ACS assessor reviews your report.
-
01
Project Dates
One project must finish within 3 years. A second project must finish within 5 years. Older projects are removed.
-
02
ANZSCO Match
We compare your summary and tech stack with your ANZSCO occupation duties. You lose points for words like we or our team.
-
03
Project Complexity
We score the size of your system, your design decisions, and your work method. This gives your project a depth score.
-
04
Your Role and Proof
We check how much of the work was truly yours. We also check if you can prove it with a reference or document.
-
05
Best Project Pair
The tool picks your two highest scoring projects. It checks the date rule and rewards a mix of different skills.
Still Looking for the Right ACS RPL Project?
Compare your ANZSCO occupation with the ICT duties you actually did. Do not rely only on your job title.
List several real projects so the tool has enough to compare. Enter correct start and end dates. Recent projects count as primary. Older ones count as secondary.
Write your summary using I, such as I designed or I configured. Do not use we or the team.
List the real tools, platforms, languages, databases, and frameworks you used. State your true role, such as sole builder, lead, core contributor, or team member.
Note what you can prove, such as a reference letter, a contract, project files, screenshots, or payslips. Then check the scale, design decisions, and method used in each project.
Pick two projects that use different skills. Together, they should cover more of your ANZSCO duties. Use the blueprint as your outline, then add your own technical detail.
Why It Matters
Why the Right Project Choice Matters
The projects you choose affect how well you can prove your ICT knowledge in an RPL report. The wrong project makes it hard to show technical depth, your input, your tools, your decisions, and your results.
Real ICT Work
Choose a project with real technical tasks, such as systems, software, databases, networks, cloud, cyber security, data, support, or business technology.
Your Own Contribution
Pick a project where you can explain your own part clearly. Describe the work you did, the decisions you made, and the problems you solved.
Proof You Can Show
Choose projects you can support with records. Evidence links your written report to work you actually did.
A Clear Result
Choose projects with a clear result, such as faster performance, less manual work, better security, better reporting, or quicker fixes.
Who Gets the Most Out of This Selector?
This tool suits ICT professionals who need real project examples before they write their RPL report. It helps you weigh your qualifications, ANZSCO occupation, evidence, technical work, and personal contribution.
No ICT Degree
Choose projects that show how you used ICT knowledge on the job. Link real workplace tasks to the occupation you are nominating.
Choosing a Project Topic
Pick a topic that shows the ICT tools you used, the technical decisions you made, and the results you achieved for your ANZSCO occupation.
Multiple ICT Projects
Compare each project by technical tasks, evidence, personal contribution, and ANZSCO relevance. Keep only your strongest two projects.
Support & Troubleshooting Roles
Choose work that shows configuration, fault diagnosis, or service improvement. Avoid routine helpdesk tickets with no technical decisions.
Where ACS RPL Project Choices Go Wrong
A project fails when it does not show real ICT tasks, a clear personal contribution, or evidence to support it. Check your project against this list before you start writing.
Mistake 01
Thin on Technical Detail
Avoid projects that only list general duties. Choose work with real technical tasks, tools, decisions, and results.
Mistake 02
Leaning on the Job Title
Do not pick a project only because your job title sounds relevant. Match it to the ICT work you actually did.
Mistake 03
Overlooking ANZSCO Fit
Avoid a project that does not support your nominated occupation. Keep the project, duties, and evidence pointing the same direction.
Mistake 04
Burying Your Own Role
Do not let the company or the team take over your report. State what you personally analysed, designed, built, configured, tested, or fixed.
Mistake 05
Nothing to Back It Up
Avoid a project you cannot support with proof. Use documents, screenshots, test records, references, or proof of payment.
Mistake 06
Recycling Someone Else's Sample
Do not copy project ideas or content from online samples. Use your own real project and your own true ICT contribution.
Want a Second Opinion on Your Shortlist?
Get your chosen ACS RPL project checked before you start writing. A writer will review the title, ANZSCO fit, technical tasks, personal contribution, evidence, and overall direction.
FAQs
Clear answers on choosing ACS RPL projects, collecting evidence, matching your ANZSCO code, and getting ready to write.
An ACS RPL project is real ICT work you were personally part of. It should show your role, the technical tasks you handled, the tools you used, the problem you solved, and the final result.
ACS expects two projects. One must finish within the last three years. The other must finish within the last five years. Each report must show your ICT knowledge, your personal input, and evidence to support it.
Yes, if it clearly shows ICT knowledge and a technical contribution that was truly yours. A paid workplace project is usually stronger because it is easier to support with real evidence.
Not always, but recent projects score better. Aim for one project within three years and another within five years. Older projects score lower unless the skills are still current.
It should match as closely as possible. Choose projects where the tasks, tools, and responsibilities match the duties listed under your ANZSCO code.
A project becomes weak when it lacks technical detail, a clear personal contribution, or proof. It also weakens when it does not match your nominated occupation, or when you write we built instead of I built.
No. This selector is a planning aid, not an official ACS decision. It helps you shortlist and compare projects before you spend time writing the full report.
Yes. A reviewer can check occupation relevance, technical depth, evidence, and personal contribution before you spend hours writing the full RPL report.
Copied