How do I show my individual contribution to a team project for RPL?

A successful team project can be strong evidence of your experience, but an RPL assessor needs to understand your part in it. The question is not simply whether the project went well. It is what you personally planned, did, decided or checked, and how the evidence supports those claims.

You do not need to pretend you completed the whole project alone. Being precise about where your responsibilities began and ended makes your account more credible.

Start with the skills you need to demonstrate

Recognition of prior learning (RPL) assesses existing skills and knowledge against the requirements of a qualification or unit of competency. Before collecting project files, identify the relevant units and read their requirements on training.gov.au, the national training register. An RTO assessor determines what evidence is needed and whether it meets those requirements.

Look for tasks you actually performed. If a unit requires you to plan work, communicate with stakeholders and monitor outcomes, a finished team deliverable may show the outcome but not necessarily how you carried out those tasks. Your job is to make that connection clear.

Write a short account of your role

Choose one project and describe it in plain language. Include its purpose, dates, your position, the size of the team and the outcome. Then separate team activities from your own. First-person statements help: “I prepared the initial schedule” is clearer than “We managed the schedule.”

For each significant responsibility, answer:

• What task was I responsible for?
• What did I personally produce, decide or approve?
• Who else was involved, and what did they do?
• What problem arose, and how did I respond?
• Which record could help verify my account?

Be equally clear about what you did not do. If a colleague signed off the final design, say so. You can still explain the research, drafting or review you completed before that approval.

Pair your account with evidence of your work

A finished report or product may have several contributors. Where available, add records that connect you to particular tasks or decisions. Depending on the work, these could include:

• Drafts showing your edits or version history.
• Project plans, task allocations or job records naming your responsibilities.
• Emails or messages in which you provided technical advice or coordinated a task.
• Meeting notes recording your recommendations, actions or follow-up.
• Work samples you prepared, such as calculations, designs, schedules or inspection records.
• A statement from a supervisor or colleague who directly observed your work.

Label each item with a short explanation: what it is, when it was created, your role in it and the skill it helps demonstrate. For example: “Project schedule, March 2025: I drafted the task sequence and updated it after the client changed the deadline.” This saves the assessor from having to guess why a document matters.

What if the records only name the team?

That is common. Explain which parts you completed and seek supporting evidence where possible. A supervisor might confirm your duties and the work they observed, while dated messages or draft files may provide another point of reference. A colleague’s statement should describe firsthand knowledge, not simply repeat your account.

If records are missing, tell the RTO. Its assessor may consider other ways to check your skills, such as a discussion, practical demonstration or further evidence. The assessment method and outcome are the RTO’s decisions; a written explanation alone does not automatically establish competency.

Protect confidential project information

Do not upload client details, personal information or commercially sensitive files without permission. Ask your employer or client what you may share. Where appropriate, use approved redacted extracts and retain enough context for the assessor to understand your contribution. If you cannot share the original material, explain the restriction to the RTO and ask what alternatives it will accept.

Keep your evidence accurate and easy to follow

Use genuine records and describe your involvement without inflating it. Avoid backdating documents or asking someone to confirm work they did not observe. A simple evidence list can help: give each item a number, name your contribution and note the relevant unit requirement. Dates and project stages also help show how your work developed.

Australia’s vocational education regulator, ASQA, oversees the national VET framework. The RTO remains responsible for assessing your RPL evidence and, where requirements are met, issuing the qualification or statement of attainment. If you want help organising your experience before approaching an RTO, an RPL support service can help you identify possible evidence, but it cannot make the assessment decision.

Your strongest account is usually a straightforward one: here is what the team achieved, here is what I personally contributed, and here is the evidence that supports it.