Occupation Fit
Line the project up with the duties tied to your nominated ICT occupation — a technical-sounding title alone isn't a reason to pick 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, not an official ACS decision. Every score comes from what you type in — only bring real projects from your own work, study, or ICT experience into your RPL report.
How the 5-Step Funnel Filters Your Projects
Each step removes weaker candidates. A project has to clear all five before it earns a recommendation, the same lens an ACS assessor reads your report through.
-
01
Date Guardrails
One project needs a finish date inside 3 years, another inside 5 years. Anything older gets dropped from contention.
-
02
ANZSCO Keyword Match
Your summary and tech stack are compared against your nominated occupation's duties, with points lost for team-speak.
-
03
Complexity & Scale
The size of the system, the architectural calls made, and the methodology used all feed into a depth score.
-
04
Ownership & Proof
How much of the work was genuinely yours, and whether you can back it up with a reference or paperwork.
-
05
Best Combination
The engine pairs the two highest scorers that satisfy the date rule and rewards a spread of different skills.
Still Hunting for the Right ACS RPL Project?
Ten practical checks to run against every candidate project before you commit it to your RPL report.
Match & Shortlist
Line your ANZSCO occupation up against the ICT duties you actually performed, not whatever your job title happened to say.
List out several real candidates so the funnel has enough to filter and compare properly.
Get your start and end dates right. Recency is what separates a primary project from a secondary one.
Write It Right
Write your contribution summary in first person ("I designed", "I configured"), never "we" or "the team".
Name the actual tools, platforms, languages, databases and frameworks each project used.
Be honest about your role: sole builder, lead, core contributor, or team member, so the score reflects reality.
Prove & Finalise
Note what you can actually prove: a reference letter, a contract, project files, screenshots, or payslips.
Run the depth check to confirm each candidate's scale, architectural decisions, and methodology.
Favour two projects that lean on different skills, so together they cover more of your ANZSCO duties.
Treat the blueprint as your outline, then flesh it out with the real technical detail only you can supply.
Why the Right Project Choice Matters
Which projects you pick shapes how easily you can prove your ICT knowledge in an RPL report. The wrong choice makes it hard to show technical depth, personal input, the tools you used, decisions you made, or what came of it.
Genuine ICT Work
Choose projects with real technical tasks — systems, software, databases, networks, cloud, cyber security, data, support, or business technology.
Your Individual Part
Pick projects where you can clearly explain your own contribution — the work you did, the calls you made, the problems you solved.
Proof You Can Show
Stick to projects you can back up with records. Evidence is what ties your written description to work you actually did.
A Measurable Result
Favour projects with a clear payoff — faster performance, less manual effort, tighter security, better reporting, quicker fixes.
Who Gets the Most Out of This Selector?
It suits ICT professionals trying to settle on real project examples before drafting their RPL report, weighing qualifications, ANZSCO occupation, evidence, technical work, and personal contribution.
No ICT Degree in Hand
Pick projects that show how you put ICT knowledge to use on the job, tying real workplace tasks to the occupation you're nominating.
Deciding Between Project Topics
Go with topics that show the ICT tools you used, the technical calls you made, and the results you delivered against your ANZSCO occupation.
Juggling Several ICT Projects
Weigh each one on technical tasks, evidence, personal contribution and ANZSCO relevance, then keep only the strongest pair.
Support & Troubleshooting Roles
Choose work that shows configuration, fault diagnosis, or service improvement — not routine helpdesk tickets with no technical decisions behind them.
Where ACS RPL Project Choices Go Wrong
Projects fall flat when they can't show real ICT tasks, a clear personal contribution, or evidence to back them up. Run yours through this list before you start writing.
Mistake 01
Thin on Technical Detail
Skip projects that only list general duties. Pick work with real technical tasks, tools, decisions, and outcomes behind it.
Mistake 02
Leaning on the Job Title
Don't pick a project just 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 nothing to support your nominated occupation. Keep the project, duties, and evidence pointing the same direction.
Mistake 04
Burying Your Own Role
Don't let the company or the team take over the story — spell out what you personally analysed, designed, built, configured, tested, or fixed.
Mistake 05
Nothing to Back It Up
Steer clear of a project you can't support. Look for documents, screenshots, test records, references, or proof of payment.
Mistake 06
Recycling Someone Else's Sample
Don't lift project ideas or pre-written content from online samples. Use your own real project and your own actual ICT contribution.
Want a Second Opinion on Your Shortlist?
Have your chosen ACS RPL project checked before you start drafting — title, ANZSCO fit, technical tasks, personal contribution, evidence, and overall direction, with a writer looking it over.
FAQs
Quick answers on choosing ACS RPL projects, gathering evidence, matching your ANZSCO code, and getting ready to write.
An ACS RPL project is a genuine piece of ICT work you were personally involved in, described so an assessor can see your role, the technical tasks you handled, the tools you used, the problem you solved, and how it ended.
Two. ACS wants one finished within the last three years and a second finished within the last five years, and each report needs to demonstrate your ICT knowledge, your personal input, and evidence you can back it up with.
It can be, as long as it clearly shows ICT knowledge and a technical contribution that was genuinely yours. A paid workplace project is usually the stronger option because it's easier to back up with real evidence.
Not automatically, but recency carries weight — aim for one project inside three years and another inside five. Anything older tends to score poorly unless the skills involved are still clearly current.
As closely as you can manage. Pick projects where the tasks, tools and responsibilities line up with the duties listed under the ANZSCO code you're nominating.
Missing technical detail, no clear personal contribution, no way to prove it happened, or a mismatch with your nominated occupation. Writing "we built" instead of "I built" also quietly weakens the claim that it was your work.
No — this selector is a planning aid, not an official ACS decision. It helps you shortlist and compare projects before you commit time to writing the full report.
Yes. A reviewer can sanity-check occupation relevance, technical depth, evidence, and personal contribution before you spend hours drafting the full RPL report.
Copied