Every ACS RPL non-ICT degree applicant starts in roughly the same spot: a genuine ICT work history, a degree in something else, engineering, accounting, applied science, or commerce, and no clean answer to whether the two combine into a passable skills assessment. Most people stall right here. They either assume Recognition of Prior Learning (RPL) is closed to anyone without a computing degree, or they act on secondhand advice about "how many years you need."
The reality is duller and far more useful than either fear. For RPL, the discipline printed on your testamur barely matters. What decides your path is whether you hold any degree at all, and whether your work reads as real ICT experience. That one reframe can save months of misdirected research and a wasted $625 fee. Here is how the classification, the threshold, and the narrative actually connect.
How ACS Classifies Your ACS RPL non-ICT Degree
ACS grades qualifications by how much computing content they carry. Under the General Skills pathway (not RPL), a bachelor's degree is assessed as ICT Major when at least 33% of it is ICT content, as ICT Minor when computing content is lighter, and as carrying insufficient ICT content when there is very little. A software engineering degree usually clears the Major bar. A pure accounting, law, or nursing degree typically lands as insufficient ICT content.
For RPL purposes, ACS sorts every qualification into three broader tiers: ICT degree, closely related (engineering, applied science), and unrelated. These are the tiers that matter for RPL eligibility and narrative strategy.
Where engineering, business, and science degrees usually land
ACS does not publish a discipline-by-discipline map, so treat any placement as an interpretation rather than a rule. Engineering and applied science degrees often carry enough programming, systems, or numerical-methods units to register as closely related. Business, commerce, and accounting degrees usually read as unrelated on their own.
That distinction drives something no competitor page separates cleanly: this ICT/closely related/unrelated classification governs the General Skills pathway, where ICT content sets how many years of experience get deducted. RPL is a different route. ACS's own RPL page states the pathway "does not assess any tertiary qualifications." For an RPL case, whether your degree is closely related or unrelated changes nothing about your threshold. Think of the degree as an entry ticket, not a seat assignment: it gets you into the RPL room, but your experience picks the occupation.
The Experience Threshold for a Non-ICT Degree
The ACS RPL non-ICT degree threshold is six years of relevant ICT work experience, per the ACS RPL pathway page. That is the only threshold ACS publishes, and its FAQ adds that any variation by qualification level can only be determined at the time of formal assessment. Third-party migration services commonly cite eight years for applicants who hold no tertiary qualification at all, but ACS's own site does not confirm that figure. Discipline never moves the published threshold.
A nursing graduate and a mechanical engineer with the same ICT history face the identical six-year bar. For how the pathway options compare, see our pathway comparison guide.
Six years for any completed degree
Six years applies to holders of any completed degree, in any field. Two conditions ride alongside it: your most recent qualifying work must be active or completed within the last two years, and each episode must be full-time, which ACS defines as at least 20 hours per week of paid work. Part-time work below that threshold is assessed as unsuitable.
What counts as ICT work when your title wasn't ICT
A non-ICT job title does not disqualify the experience. ACS uses the Skills Framework for the Information Age (SFIA) to judge whether each employment episode is "closely related and at the appropriate skill level" to your nominated occupation. A "Business Systems Lead" or "Process Automation Engineer" can absolutely count, provided the actual duties map to SFIA skills for the code you claim.
The job title is a label. The SFIA-aligned duties are the evidence.
Building an RPL Application Without an ICT Degree
An ACS RPL non-ICT degree application succeeds or fails on one thing the assessor is actively looking for: a clear line from your academic background into your ICT work, with duties that read as ICT at the right level. A list of job responsibilities is not sufficient on its own.
Bridging your non-ICT background to ICT work
Your cover material and project narratives should name the connection explicitly rather than leaving the assessor to infer it. An accounting graduate who moved into ERP implementation should explain how financial-systems literacy fed directly into configuring and delivering ICT solutions. An engineer should trace how systems methodology and quantitative modelling carried into software work.
The bridge is the argument, not decoration. Assessors are reading for it.
Projects that show ICT skills, not domain expertise
RPL requires two project reports: one completed within the last two years and one within the last four. Choose them for their ICT content, not your proudest business outcome. A project where you saved a department money matters far less than one where you designed, built, or integrated a system.
If your roles were non-project by nature, ACS permits submission of work experience details and challenges faced instead. For the format those reports must follow, see the ACS RPL project report requirements guide before you begin drafting.
Where AWS, Cisco, and Microsoft certifications actually fit
A stack of vendor badges will not buy back a single year of the six. AWS, Cisco, and Microsoft certifications serve as one of the two required forms of evidence demonstrating current skill in your nominated ANZSCO code. That is real value, but it is a currency signal, not a threshold reducer.
Anyone selling certifications as a shortcut around the experience requirement is misreading the rule.
ANZSCO Codes Non-ICT Degree Holders Claim Most
Degree background does not change your threshold, but it shapes which occupation you can defend most credibly. The matrix below maps degree type against the uniform six-year threshold and the most defensible ANZSCO code for each background. This is our reading of ACS's published RPL criteria, not an ACS-published table.
Degree background | Years required | Most defensible ANZSCO code | What the RPL narrative must prove |
|---|---|---|---|
Business, commerce, accounting | 6 | 261111 ICT Business Analyst; 135111 ICT Manager | Requirements gathering, stakeholder analysis, and ICT project leadership as your core work, not finance or operations |
Engineering, applied science | 6 | 261313 Software Engineer; 261312 Developer Programmer | Software design and build across the lifecycle, with systems or quantitative methodology carried into code |
Unrelated (nursing, law, arts) | 6 | 261111, or the code matching your actual duties | An ICT work history that stands entirely on its own, since the degree adds nothing to the case |
Business and commerce degrees: 261111 and 135111
Business, commerce, and accounting graduates have the most natural fit with 261111 ICT Business Analyst, because requirements, process, and stakeholder work translate directly. Senior candidates with delivery ownership can reach 135111 ICT Manager. Both codes let you turn domain knowledge into a strength rather than treating it as a liability.
Engineering and science degrees: the 261313 route
An engineering or applied science graduate can credibly claim 261313 Software Engineer, but it is the least forgiving code to claim without an ICT degree. The assessor expects deep, hands-on software evidence across the development lifecycle. A shallow scripting history will not carry it.
If your build experience is thinner than your systems-analysis experience, 261112 Systems Analyst or 261111 ICT Business Analyst may be the safer target.
Rejection Patterns Specific to Non-ICT Degree Applicants
The ACS RPL non-ICT degree applicants who get knocked back rarely fail on years. They fail on framing, and on bad information absorbed before they applied.
"Not sufficiently ICT-focused" and how to pre-empt it
The leading rejection reason for this group is experience judged not sufficiently ICT-focused. It typically means the duties described sounded like domain work with some technology attached, rather than ICT work in its own right.
The fix is to describe each role in the SFIA vocabulary that matches your code, foregrounding design, build, analysis, and management of systems over business results. Our rejection-reasons self-audit guide walks through this check episode by episode.
The wrong numbers circulating online
Two contaminated figures are still circulating on ranking pages and derailing applicants before they start. One page states the fee as AUD $550 and the non-ICT degree threshold as four years. Both are wrong. As of the fee schedule effective 3 November 2025, the ACS RPL assessment fee is AUD $625, and the experience threshold for any degree holder is six years. See our fee guide for the current schedule.
Processing time is another myth worth correcting. Competitor pages routinely quote eight to twelve weeks, while ACS lists standard processing at four to six weeks for complete applications. Budget on the real numbers.
Frequently Asked Questions for Non-ICT Degree Applicants
Does a software engineering or electrical engineering degree count as an ICT degree for ACS RPL?
For the RPL pathway, it does not need to. RPL does not assess your degree at all, so whether ACS would grade software or electrical engineering as ICT Major, closely related, or unrelated has no effect on your six-year threshold. A software engineering degree does often carry enough ICT content to be graded as ICT Major or closely related, but that only matters if you switch to the qualification-based General Skills pathway instead.
If I hold a business degree but have 7 years of ICT work experience, which experience threshold applies to me?
Six years. Any completed tertiary degree, in any field, places you on the six-year RPL threshold, so at seven years you clear it with a year to spare. That assumes your most recent qualifying work falls within the last two years and each episode reads as genuine ICT work under SFIA standards.
Can AWS, Microsoft, or Cisco certifications reduce the experience requirement for a non-ICT degree holder?
No. Vendor certifications count as one of the two forms of evidence ACS asks for, but they cannot reduce the six-year threshold by a single year. Treat them as proof you are current in your nominated occupation, not as a substitute for lived experience.
Which ANZSCO codes are most commonly approved for applicants without an ICT degree?
261111 ICT Business Analyst is the most accessible, particularly from a business or commerce background. 135111 ICT Manager suits candidates with genuine delivery ownership. 261313 Software Engineer and 261312 Developer Programmer are reachable from engineering and applied science backgrounds but demand the strongest hands-on software evidence.
Can I apply under ACS RPL if my degree is in a completely unrelated field such as nursing, law, or arts?
Yes. Because RPL ignores the discipline of your degree, an unrelated qualification still puts you on the published six-year threshold. Your entire case then rests on the ICT work history and the two project reports, so the narrative bridge from your actual duties to SFIA skills matters even more.
Your next step before drafting the report
Confirm which threshold and ANZSCO code fit your background, then build the evidence to match. Read the ACS RPL project report requirements guide to see exactly what your written evidence must include before you start drafting a single page.