Twelve years of production systems behind you, no transcript to show for any of it. An ACS RPL without degree application exists for exactly that situation: it converts documented ICT experience into an Australian skills assessment that migration accepts in place of a university qualification. The route is winnable. It is also stricter than most guides admit, because the whole file has to carry weight a degree would normally carry, and that changes how you count your years, what evidence you gather, and how you write your project reports.
What an 8-year ACS RPL pathway lets a non-degree applicant do
An ACS RPL without degree assessment produces the same output as any other ACS result: a positive skills assessment for your nominated ANZSCO occupation, which feeds the SkillSelect Expression of Interest behind the skilled visas. ACS is deciding one thing: whether your experience sits at a professional ICT level equivalent to the qualification you do not hold.
The visa outcomes this experience-only route feeds
A positive result lets you claim your nominated occupation in a SkillSelect EOI for the points-tested skilled visas (subclasses 189, 190, and 491). ACS assesses the skill; the Department of Home Affairs assesses the visa. A clean ACS outcome is the gate to the first step.
8 years without a degree, or 6 years with a non-ICT diploma
Here is the fork that sends people into the wrong guide. Hold no recognised tertiary qualification of any kind, and ACS assessment requirements set the bar at 8 years of relevant ICT experience. Hold a non-ICT AQF Diploma or higher, and the bar drops to 6 years, placing you in the non-ICT degree pathway instead. One diploma in any field moves you a full two years down the requirement, so confirm which lane you are in before you count a single month. The 6-year versus 8-year mechanics live in our dedicated experience-rule article; this guide assumes you have nothing to declare academically.
Check eligibility before you open the ACS portal
Confirm eligibility before you pay.
The 8-year rule and the 10-year currency window
Two rules decide whether your history qualifies. The first is the 8-year minimum. The second, less obvious one is the 10-year currency window: ACS assesses experience from the 10 years preceding your submission date, and everything older is excluded. ACS states this window explicitly for its General Skills pathway and applies it consistently to RPL files. Submit in August 2026, and your clock starts in August 2016. Work you did in 2013 is real, but for this assessment it does not count.
That combination is the trap. You need 8 countable years inside a 10-year window, so a long career with early gaps can still fall short. ACS also counts only paid work of at least 20 hours a week, performed after you turned 18, and your most recent qualifying role must be current or have ended within the last two years. Review the eligibility document requirements before you start assembling anything.
Mapping your work to one ANZSCO occupation code
You nominate the ANZSCO occupation code your experience maps to, and ACS judges the fit on the duties you performed, not your job titles. A "Systems Engineer" whose actual work was business analysis gets assessed as a business analyst. You can nominate up to three codes in a single submission at one fee, which is worth doing when your career straddles two roles.
Counting and mapping your 8 years of ICT experience
Counting sounds trivial until two roles overlap or a payslip is missing. Start by plotting every ICT role on one timeline: start and end dates to the month, employer, and hours per week.
Concurrent and part-time roles count once, at 20 hours
Concurrent roles count as one period, not two. Running a 25-hour employed role alongside a 15-hour freelance contract in the same six months gives you six months of experience toward your total, full stop. Sequential part-time roles are different: each counts independently toward your total, provided each role independently cleared 20 hours a week and was genuinely ICT-focused rather than a general job with incidental tech duties. The distinction matters most when you are stitching together a timeline from short stints.
A worked 8-year timeline with a gap and a freelance stint
The timeline below is our worked reading of ACS's published counting rules, not a real assessed case. Picture an applicant submitting in August 2026 and nominating Software Engineer (261313):
Network Administrator, employed, February 2012 to November 2016. Only August to November 2016 (four months) falls inside the 10-year window; everything before that is excluded.
Gap, December 2016 to March 2017 (four months between contracts).
Systems Analyst, employed, April 2017 to July 2020: 40 months.
Freelance developer, self-employed, August 2020 to September 2022: 26 months.
Software Developer, employed, October 2022 to present: 46 months.
Countable experience totals 116 months, a little over nine and a half years, comfortably clearing the 8-year bar even after the window discards the early network years. The gap is handled with a statutory declaration, not ignored. Leave it unexplained, and the four-month hole reads as a hidden inconsistency, casting doubt across the entire file.
The 2-plus-6 split and your migration points
Not all 8 years have to map to your nominated code. The six years ACS counts toward your SkillSelect migration points must align with the nominated ANZSCO occupation. Your years seven and eight, the extra two the no-degree pathway demands, can be adjacent ICT work that does not match the code exactly, and those two years earn zero migration points. In the timeline above, the development-heavy roles anchor the Software Engineer nomination, while the older network-administration months fill the year-seven-and-eight requirement without needing to match and without inflating your points.
Building your evidence package without an academic transcript
In an ACS RPL without degree file, every claim rests entirely on employment evidence. Build it role by role, and use the ACS document checklist to confirm nothing is missing before you upload.
Reference letters and payment evidence, role by role
Each role needs an employment reference letter carrying all 13 ACS-mandated fields: company letterhead with URL, your legal name, the dated employment period in DD/MM/YYYY, status, weekly hours, annual pre-tax salary, location, exact title, bullet-pointed ICT duties, and the signatory's verified signature, name, title, and direct contact. If you contracted through a recruitment agency, the letter must come from the host company where you actually worked, never the agency.
Beyond the reference, ACS wants at least two types of payment evidence per role, with at least one from a non-employer source. For employed periods, ATO notices of assessment and income statements are the strongest corroboration, because they are independent of your employer entirely.
Statutory declarations for self-employment and gaps
Self-employment is where most no-degree files break, and it usually breaks on one rule: who writes the declaration. For an employed role for which no reference letter is available, a managerial or supervisory colleague who witnessed your duties must write it. A self-written declaration for an employed role is rejected outright. For self-employment, you write your own sworn declaration covering business start and end dates, your occupation, the nature of the work, and staff numbers.
That declaration alone is not enough. Back it with your business registration certificate, a letter from your accountant or legal representative confirming the business, client statements on official letterhead describing the work and dates, and invoices matched to bank statements or tax records. Declarations fail on predictable errors: missing the sworn witness wording ('Sworn Before', 'Signed Before', or 'Witnessed Before'); an attested date range that does not match the employment period you are claiming; or ANZSCO duty descriptions copied verbatim from the code definition instead of written in your own account of what you actually did.
Writing ACS RPL project reports without a degree
Two RPL project reports are still required, and this surprises people who assumed the experience record replaces them. It does not. One report must document a project from your last two years, the other from your last four. In a degree application, the transcript signals your technical level, and the projects confirm it. Without a degree, the projects carry that signal alone.
Assessors read specificity as the proxy for seniority. A report that names the actual stack, explains why you chose it over the alternative, states the team and system scale, and reports a measurable outcome reads as senior. A report that lists tasks reads as junior, regardless of how many years sit behind it. Choose projects where you made system-level decisions, not ones where you executed someone else's design. Both reports must be original, first-person, and citation-clean; ACS runs them through plagiarism detection, and a lifted paragraph sinks the file.
Submitting your ACS RPL application and the current fee
Once your evidence and reports are assembled, submission is the short part. Finalise your ANZSCO nomination first, because changing it after upload means re-arguing duties across every document. Upload your identity documents, reference letters, payment evidence, statutory declarations, and project reports, then pay to initiate assessment.
The ACS fee schedule lists the RPL application fee at AUD $625 for a standard assessment; confirm the exact current figure on the ACS website before you pay, since ACS revises fees periodically. Completed applications that need no further information are assessed in about four to six weeks.
Why no-degree RPL applications get returned before submission
Most ACS RPL without degree rejections are self-inflicted and visible before you submit. Undocumented gaps are the classic one: a hole nobody explained reads as something hidden, and the doubt spreads to sections that were fine. Date mismatches between your CV and a reference letter do the same damage. An ANZSCO code whose duties your evidence does not actually support, a statutory declaration that copies the ANZSCO description verbatim, and a concurrent-role period counted twice to pad a thin total are all common failures. Run your file against our RPL rejection self-audit before you pay, not after ACS sends it back.
FAQs
Can I qualify for ACS RPL without degree if some of my 8 years is freelance or self-employment?
Yes. Self-employment and freelance periods count toward your 8 years if the work was genuine, remunerated ICT work at 20 or more hours a week. The difference from an employed role is the paperwork: you write your own statutory declaration and back it with business registration, an accountant's letter, client statements on letterhead, and invoices matched to bank statements or tax records.
Does part-time ICT work count toward the 8-year experience requirement?
Yes, provided each role independently met the 20-hours-a-week minimum, was paid, and was genuinely ICT-focused. Work below 20 hours a week does not count. Two part-time roles running at the same time count once as one period, not twice; roles held sequentially each count independently toward your total.
Can I include ICT experience gained outside Australia in my 8-year claim?
Yes. ACS assesses overseas ICT experience the same way it assesses Australian experience, against the duties of your nominated ANZSCO code, inside the same 10-year window. The evidence standard is identical: reference letters with all 13 fields, or statutory declarations plus payment evidence where a reference is unavailable.
What happens if I have an employment gap somewhere in my 8-year ICT history?
A documented gap is fine; an unexplained one is the danger. Cover any gap longer than a normal job transition with a statutory declaration or supporting evidence explaining it. Left unexplained, a gap makes ACS doubt the dates across your entire file, even the well-evidenced roles.
Do I still need to submit RPL project reports if I have no tertiary qualification at all?
Yes. Two project reports are required regardless of qualification status, one from your last two years and one from your last four. Without a degree, they carry more of the assessment, because your project narratives are what signal your technical level in the absence of a transcript.
If your case rests entirely on experience, the project reports are where it is won or lost. Explore our RPL report writing service to see how we help applicants without a degree build a credible, specific case from work history alone.