If you work in IT, you may already have useful evidence sitting in a ticketing system or project folder. A network diagram can show how you documented an environment. A help-desk ticket can show how you investigated and resolved a problem. Both may support a recognition of prior learning (RPL) portfolio, but neither proves competence on its own.
RPL is an assessment process that considers skills and knowledge gained through work and other experience. The registered training organisation (RTO) assesses the evidence against the requirements of the relevant qualification or units of competency. You can explore current qualifications and unit requirements on training.gov.au; the exact requirements depend on the units being assessed.
What can a network diagram show?
A diagram may help demonstrate how you documented network components, connections, addressing or security boundaries. Its value increases when an assessor can understand your role in creating or maintaining it. For example, a diagram accompanied by a short explanation might identify the problem you were asked to solve, the changes you proposed and the checks you completed afterwards.
Include a version date and, where possible, evidence of how the diagram was used: a change record, implementation notes, testing results or feedback from a supervisor. A polished diagram without that context could just as easily be a template or a team document. Be clear about which parts were your work.
What can help-desk tickets demonstrate?
Tickets can provide a dated record of day-to-day IT work. Depending on the unit requirements, they might help show how you gathered information, troubleshot an issue, communicated with a user, escalated a problem or confirmed a resolution. A useful selection shows a range of tasks and decisions, rather than dozens of near-identical password resets.
For each ticket you select, briefly explain what you personally did. If the ticket passed between teams, separate your actions from those of your colleagues. Where a closure note says only “resolved”, add an accurate account of your diagnostic steps and the outcome. Do not rewrite the original record or claim work you cannot substantiate.
Protect information before you share anything
IT evidence often contains information that should not leave the workplace. Before including a diagram or ticket, check your employer’s policies and obtain any required permission. Remove or mask customer names, contact details, IP addresses where sensitive, credentials, security configurations and other confidential information. Keep enough context for an assessor to understand the task without exposing a live environment.
If you cannot share a document, ask whether an authorised supervisor statement, a redacted extract or a discussion of the work would be suitable. Do not upload production data or create a realistic-looking replacement and present it as an original record. An assessor may ask follow-up questions or seek other evidence to establish what you know and did.
How to make the portfolio easier to assess
Start with the qualification and units you are seeking, not with a folder of everything you have saved. Then create a simple evidence list:
- Identify the item: Give each diagram or ticket a date and a short, non-sensitive description.
- Explain your contribution: State your role, the decisions you made and whether anyone else contributed.
- Connect it to the requirements: Note which skills or tasks the item appears to demonstrate.
- Support the record: Where appropriate, add change approvals, test results, workplace procedures or a supervisor statement.
- Check permissions: Confirm that the version you intend to submit can be shared.
Evidence needs to do more than look relevant. An RTO assessor must decide whether it meets the applicable assessment requirements and whether further evidence or an assessment activity is needed. The Australian Skills Quality Authority (ASQA) is the national regulator for vocational education and training; its guidance is a useful starting point for understanding RTO assessment responsibilities.
A practical next step
Choose two or three examples that show different aspects of your work and write a few lines of context for each. If you are unsure what you can share, resolve that with your employer before preparing an RPL submission. RPL Access Australia can help you organise and discuss potential evidence, but the RTO—not an RPL support service—decides whether it satisfies the unit requirements and whether to issue a qualification or statement of attainment.