Two ACS RPL project reports can come from the same employer. The current ACS rule requires two reports with different recency windows; it does not say the projects must come from two different companies. For ACS RPL projects from the same employer, two genuinely different technical problems provide clearer evidence than two reports that merely rename one implementation.
If one of your strongest projects falls outside the permitted recency windows, age—not employer diversity—becomes the real issue.
One report should document a project completed within the last two years and the other a project from within the last four years. Applicants in non-project roles can instead explain relevant work experience and challenges. The selection question is therefore not “How many employer logos do I have?” but “Do these two career episodes reveal enough distinct ICT knowledge?”
Employer variety is not the same as evidence variety
A long-term employee can have a strong project pair inside one organisation. A finance-system replacement and a later identity-and-access redesign may involve different problems, stakeholders, constraints and knowledge even though the employer is identical.
The reverse is also possible. Two projects from two different employers may be almost interchangeable if both reports describe the same implementation pattern, the same responsibilities and the same outcomes.
Use six axes to test whether the pair is genuinely different
| Axis | Question to ask |
|---|---|
| Problem | Are the business/technical problems materially different? |
| Personal role | Did your responsibility or professional level change? |
| ICT knowledge | Do the episodes demonstrate different knowledge areas or different depth? |
| Decision type | Are you explaining different trade-offs and decisions rather than repeating a method? |
| Stakeholder/system context | Does the second project operate in a meaningfully different environment? |
| Outcome | Does each episode have its own verifiable result, limitation or lesson? |
The hidden weakness: same employer, same program, same story
Two phases of one implementation are not automatically two strong reports. “CRM rollout — phase 1” and “CRM rollout — phase 2” may be distinct projects operationally, but if the applicant’s role, decisions and technical problems are effectively identical, the second report adds little information.
Do not manufacture differences with synonyms. If the only distinction is that one report says “gathered requirements” and the other says “elicited business needs”, Google-style anti-duplication logic is not the issue — evidence quality is. ACS needs two credible reports, not two paraphrases.
When two projects from one employer can be especially useful
- They show genuine career progression from analysis to solution ownership, or from implementation to technical leadership.
- They expose different systems, risk profiles or knowledge domains inside a large organisation.
- The employment reference clearly supports the project dates and the role held in each episode.
- The applicant has strong personal knowledge of both projects and can write each report independently in their own words.
When to choose a different employer instead
A project from another employer can be useful when the best same-employer pair is too repetitive, when one project falls outside the required recency window, or when another career episode demonstrates a missing area of ICT knowledge more clearly. Employer diversity is a tool, not a rule.
A project-pair selection workflow
- List all plausible career episodes inside the four-year window before choosing anything.
- Mark which can satisfy the two-year report and which can satisfy the four-year report.
- Remove episodes where your personal contribution is too weak or cannot be reconciled with employment evidence.
- Compare the remaining pairs across problem, responsibility, knowledge, decisions and outcome.
- Choose the pair that creates the greatest truthful information difference, even if both projects belong to one employer.
Authorship is non-negotiable
ACS states that RPL Project Reports must be exclusively the applicant’s own work and cannot be outsourced to a writing or editing agency. Guidance can help you understand requirements or test whether evidence is coherent; it cannot replace the applicant’s own project narrative.
The useful rule
Same employer is acceptable. Same evidence story is the problem. Choose two reports because they expose different parts of your ICT capability, not because they satisfy a cosmetic “two companies” rule that ACS does not publish.
Different projects are easier to defend than different project names
Two RPL reports from one employer can be legitimate, but they should document distinct episodes of applied IT knowledge rather than repackage one continuous system implementation. Consider an engineer who built a payment reconciliation service and later migrated customer identity infrastructure. Those projects involve different business problems, risk profiles and personal decisions. By contrast, describing the design phase and testing phase of a single deployment as unrelated projects may create unnecessary doubt. The ACS project-report instructions specify timing and authenticity expectations; applicants should verify how the projects fit those requirements before drafting.
Make the chronology unmistakable
A project summary should give enough context to establish when the work occurred, the applicant’s role and the actual duration of their contribution. When both projects were delivered in the same organisation, shared infrastructure and recurring teammates are normal. Explain the overlap instead of disguising it. A chronology can distinguish a six-month identity migration from a twelve-week incident-response automation project, even if the second began before the first was entirely closed. The point is not to create artificial separation but to show two evidence-rich contexts in which technical judgment was exercised.
What each report needs to reveal
Focus one report on the technical problem, the constraints, alternatives considered, your implementation and observed outcome. The second should reveal a different capability set or decision environment: for example, working with distributed event processing rather than access-control policy. If both reports contain the same generic description of requirements gathering, testing and documentation, it will be difficult to see the distinct learning. Use concrete examples such as recovering from message duplication, correcting an authorization flaw, designing data migration rollback or reducing manual operational steps. Quantified outcomes can help, but only where the measurement is genuine and attributable.
Ethical authorship is a substantive requirement
A colleague may help you remember dates or technical terminology, but the assessment account should be written from your own knowledge. Using polished third-party text that introduces decisions you never made defeats the purpose of an RPL assessment. Remove confidential business data and identify material that must be paraphrased or attributed. If you cannot answer a technical follow-up about a claimed design decision, the report is probably overstating your contribution. A candid description of difficult trade-offs and lessons learned will usually convey more authentic competence than a perfect-sounding account of a project without setbacks.
The RPL pathway and project timing pathway describes the two-report obligation; the ACS knowledge framework hub gives current supporting-document guidance. If employment records or certifications are used to support professional history, check employment-reference documents and professional currency proof instead of trying to make the project narrative prove everything.
