Project Report One
This report should cover a specific project completed within the last two years of your professional career.
Must highlight recent technical decision-making.
Complete RPL Report Writing Service for ACS Skills Assessment
Prepare your own ACS RPL Project Reports with clearer evidence, stronger project choices, and better document consistency.
- Understand current ACS RPL report requirements.
- Choose two relevant and recent ICT projects.
- Connect experience with your ANZSCO occupation.
- Check report, reference, and evidence consistency.
Disclaimer: We do not write or edit ACS RPL Project Reports. Your reports must remain your own work.
Applicant-Owned
Requirement-Led
ANZSCO-Focused
Confidential
RPL pathway
What is the ACS RPL assessment pathway?
RPL stands for Recognition of Prior Learning. This pathway assesses ICT knowledge gained through professional work rather than tertiary qualifications.
ACS currently requires at least six years of relevant professional ICT work experience for this pathway. Your most recent experience must be active or completed within two years before submission.
Relevant employment must usually include at least 20 paid hours each week.
Who may need ACS RPL guidance?
- You rely mainly on professional ICT experience for your assessment.
- You need to select two strong and recent career projects.
- You are unsure how to show your personal technical contribution.
- Your job title differs from your intended ANZSCO occupation.
- Your reports and employment evidence need a consistency check.
- You need help organising Professional Currency Evidence.
Important: ACS decides whether your experience meets the pathway requirements. No third-party service can confirm or guarantee your assessment outcome.
Submission documents
What must an ACS RPL submission include?
A complete RPL application includes several evidence groups. The purpose is not simply to upload more documents, but to make sure each document supports the professional ICT experience you are relying on.
Document Group
Purpose
How We Support You
Identity evidence
Confirms your identity and name details.
We provide a document checklist.
Two RPL Project Reports
Shows how you applied ICT knowledge.
We guide project selection and readiness checks.
Work experience evidence
Verifies paid and relevant employment.
We check consistency across dates, roles, and duties.
Professional Currency Evidence
Shows current skills in your nominated occupation.
We help organise relevant evidence categories.
Optional vendor evidence
May support eligible DevOps or Cyber Security applications.
We identify where official verification is needed.
Official requirements
What ACS expects from two RPL Project Reports
ACS requires two Project Reports inside the official Recognition of Prior Learning form. Here is how your reports must be structured.
Project Report Two
This report should cover a significant project completed within the last four years of your working history.
Demonstrates sustained technical expertise over time.
Each report should show
Career Episode
A specific career episode from your professional history.
Personal Role and Actions
Your personal role, actions, decisions, and key responsibilities.
ICT Knowledge
Practical use of ICT knowledge in a real professional setting.
Recent Employment
A project directly connected with current or recent employment.
Depth and Breadth
Enough detail to demonstrate the depth and breadth of knowledge.
Clear Sources
Clear sources for quoted, paraphrased, or third-party information.
Non-project roles option
Applicants in non-project roles can describe relevant work situations and professional challenges to demonstrate their competency.
Applicant ownership
Looking for ACS RPL writing help?
ACS states that each RPL Project Report must be entirely your own work and must not be outsourced to a writing or editing agency. That is why our service is positioned as requirement guidance, evidence mapping, and readiness feedback.
Protect your authorship: Use your own project facts, decisions, explanations, and professional knowledge. Do not copy samples, duties, templates, or another applicant's wording.
Guidance coverage
What our ACS RPL guidance service covers
These support areas help you understand requirements, choose stronger evidence, and check whether your self-prepared material is clear enough before submission.
Guidance, not outsourcingYour project facts, decisions, and wording remain your own.
RPL Requirement Explanation
Understand pathway rules, evidence groups, report timing, and submission expectations.
Project Selection Guidance
Compare possible projects against recency, relevance, technical depth, and available evidence.
ANZSCO Relevance Discussion
Identify where your project work and duties connect with your selected occupation.
Evidence Planning
Organise facts, records, artefacts, and employer evidence before preparing your reports.
Readiness Feedback
Receive comments about missing context, weak evidence, or unclear personal contribution.
Consistency and Currency Checks
Review dates, titles, duties, technologies, project facts, and professional currency evidence.
Project selection
How to select strong RPL projects
Your project choices shape the evidence available across both reports. The strongest examples usually let you explain your own technical decisions, not only the project outcome.
Choose projects that are recent enough, evidence-backed, and clearly connected with your nominated occupation.
Recency
The project falls within the required time period.
Relevance
The work connects with current or recent employment.
Personal contribution
You can separate your actions from team activity.
Technical depth
You can explain methods, decisions, tools, and outcomes.
Evidence availability
You can support dates, responsibilities, and project facts.
ANZSCO connection
The work demonstrates skills relevant to the nominated occupation.
Distinct coverage across both reports
The two projects should show different knowledge, responsibilities, or challenges instead of repeating the same evidence twice.
Project report readiness
What we check in each self-written Project Report
These checks help you see whether a self-prepared report has enough context, technical substance, and evidence consistency before submission.
Clear project contextYour personal ICT contributionEvidence that matches documents
Project Context
The report should identify the organisation, project purpose, timeframe, environment, and business need.
Your Personal Role
The report should separate your responsibilities from team responsibilities.
Applied ICT Knowledge
The report should show what you analysed, configured, built, tested, secured, or improved.
Decisions and Problem-Solving
The report should explain why you chose specific methods, tools, standards, or controls.
Professional Practice
The report should reflect communication, risk awareness, quality, and responsibility where relevant.
Evidence Consistency
Project facts should match your references, employment dates, role titles, and supporting records.
ANZSCO relevance
How ANZSCO relevance affects your evidence
ACS assesses whether your work experience relates closely to your nominated ANZSCO occupation. A job title alone does not prove that relationship.
Your duties, project decisions, technical tasks, and level of responsibility provide stronger evidence than the title by itself.
The ACS portal may suggest occupations based on the skills you enter. You can currently select up to three occupations for assessment.
Our ANZSCO relevance check reviews
- Whether your project work supports your selected occupation.
- Whether your technical duties show professional ICT depth.
- Whether your responsibilities match the claimed level of work.
- Whether the evidence remains consistent across each document.
- Whether your project examples show enough occupation-specific detail.
- Whether duties appear copied from an occupation description.
Professional and employment evidence
Your evidence must support your RPL claims
Professional Currency Evidence and employment records should show that your skills are current, relevant, attributable, and connected with your nominated occupation.
Professional Training and Certification
This may include relevant vendor certifications, credentials, or non-degree training.
Professional Artefacts
This may include attributed code, scripts, applications, databases, publications, awards, patents, or websites.
Professional Development
This may include memberships, workshops, seminars, events, speaking activities, or industry engagement.
Employment evidence must support your reports
ACS uses employment references and payment records to verify relevant paid work experience. Your references should accurately describe each employment episode and the duties you performed.
Key reference details may include
- Company letterhead, employer name, address, and website.
- Your full name and the letter date.
- Employment start and end dates.
- Employment status, weekly hours, salary, and work location.
- Position title, duty statements, and authorised signatory details.
Duties copied directly from ANZSCO descriptions or another reference may not be accepted. Your RPL reports should not introduce work that your employment evidence cannot support.
Guidance process
Our ACS RPL guidance process
The workflow is built around applicant ownership. We clarify requirements, review evidence direction, and give feedback while your reports remain your own work.
Requirement check firstEvidence before wordingClear next step after review
Initial Requirement Check
Share your intended pathway, experience summary, and nominated occupation.
Project Comparison
Compare possible projects using recency, relevance, depth, and evidence availability.
Evidence Plan
Organise the facts and supporting records needed for each report.
Applicant Preparation
Prepare both reports yourself using your own knowledge and wording.
Readiness Feedback
Receive comments on evidence gaps, clarity, relevance, and consistency.
Applicant Revision
Update your own reports and documents before submission.
Service boundaries
What we do and what we do not do
What We Do
- Explain official RPL requirements.
- Guide project selection.
- Provide evidence planning checklists.
- Discuss ANZSCO relevance.
- Flag missing or inconsistent information.
- Review submission readiness at a general level.
What We Do Not Do
- Write your Project Reports.
- Edit or rewrite your Project Reports.
- Create project facts or evidence.
- Copy duties from ANZSCO descriptions.
- Provide migration or legal advice.
- Guarantee an ACS outcome.
Common gaps
Common gaps we flag during an RPL readiness review
- The report describes the team but not the applicant's personal contribution.
- The project contains business detail but limited ICT knowledge.
- The stated project dates fall outside the required period.
- The technical decisions lack reasons or professional context.
- The two reports repeat the same evidence and responsibilities.
- The nominated occupation does not match the demonstrated skills.
- Employment references and project facts contain conflicting details.
- Professional Currency Evidence is old, generic, or unrelated.
- Claims lack supporting records or attributable evidence.
- Third-party sources appear without proper acknowledgement.
Disclaimer and sources
Service disclaimer
We provide general ACS RPL requirement guidance, project selection support, evidence planning, and readiness feedback only; we do not write, edit, rewrite, prepare, or guarantee ACS RPL Project Reports. We are not affiliated with ACS and do not provide migration advice or guarantee assessment outcomes.
Official sources used for this page
ACS Recognition of Prior Learning Assessment PathwayACS RPL Project ReportsACS Professional Currency EvidenceACS Employment ReferencesACS Experience EvidenceACS IT Occupations and ANZSCO CodesAustralian Department of Home Affairs - Who can help with your applicationOffice of the Migration Agents Registration Authority
Check before submission
Check your self-written ACS RPL evidence before submission
Get structured guidance on project selection, ANZSCO relevance, professional currency, and document consistency.
Review with confidence
✓Project suitability feedback
✓Document gap guidance
✓ANZSCO relevance discussion
FAQ
Frequently asked questions
The ACS RPL pathway assesses professional ICT knowledge gained through relevant work experience. It does not assess tertiary qualifications.
ACS currently states that RPL requires at least six years of relevant professional ICT work experience, with recency requirements for the latest experience.
You need two Project Reports. One should cover a project within two years, and one should cover a project within four years.
No. ACS states that Project Reports must be your own work and must not be outsourced to a writing or editing agency.
No. We provide requirement guidance and general readiness feedback. You remain responsible for writing and revising your reports.
Yes. ACS states that applicants in non-project roles may describe work experience and professional challenges from their role.
Each report should show your personal role, applied ICT knowledge, technical decisions, problem-solving, and professional outcomes.
It is recent evidence showing current skills in your nominated occupation. ACS requires at least two relevant forms of evidence.
Not necessarily. ACS considers duties, skills, work complexity, and professional evidence, not only the job title.
ACS states that additional documents cannot be added after the application enters processing. Submit all intended evidence before final submission.
No. ACS makes the assessment decision. No adviser, consultant, or service can guarantee the outcome.
No. We provide document requirement guidance only. Contact a registered migration agent, legal practitioner, or exempt person for migration or visa advice.