PAWE for Students and Young People: Protecting Your Future

For claimants who were in full-time education (School, TAFE, or University) at the time of the accident, the insurer must consider what you likely would have earned. While your immediate weekly statutory benefits might be based on current part-time work, your long-term entitlements must reflect your intended career path.

If you have only been in the workforce for a few weeks or months, a 52-week average (including many "zero" weeks) would be inaccurate. In these cases, the insurer should calculate your PAWE based on your actual period of work or the rate of a person in a similar role.

One of the most complex areas of CTP law is determining the financial loss for someone who hasn't yet established a peak career. Insurers often try to "cap" their liability by assuming a young person would have only ever earned a minimum wage. Proving a higher potential capacity requires vocational evidence and academic records.

Student and early-career PAWE disputes usually turn on whether the file shows a realistic earning pathway rather than a snapshot of low casual income. Evidence often matters most where it proves:

• Enrolment and study progression: university, TAFE, apprenticeship, traineeship, or school records showing what course or pathway you were actually following.
• Part-time and casual work history: payslips, rosters, payroll summaries, bank deposits, and employer letters showing that limited historical earnings do not tell the full story.
• Expected graduation or qualification timing: records that show when you were due to complete study, move into full-time work, or step into a higher-paid role.
• Career-specific progression evidence: apprenticeship rates, graduate programs, award rates, industry pay scales, or comparable-entry roles showing likely earnings once training finished.
• Consistent capacity evidence: certificates, treating records, and rehab material that explain how the accident interrupted study, training, placements, or the transition into work.

Where the insurer only focuses on a low pre-accident payslip average without confronting that broader trajectory, the review should answer that reasoning directly.

These matters are often weakened by avoidable framing problems. Common mistakes include:

• Relying only on future hopes: broad statements about wanting a better career are weaker than actual enrolment, results, apprenticeship, or employer evidence.
• Ignoring the insurer's calculation method: a good challenge explains exactly why the averaging period or comparator used is legally or factually wrong.
• Separating PAWE from capacity evidence: if the insurer is also questioning work capacity, certificates and treating opinions need to stay aligned with the earnings argument.
• Waiting too long to collect records: casual employers, colleges, and placement providers may not keep detailed records forever.
• Undervaluing long-term loss: early statutory benefits and later damages issues should be considered together, especially where the injury disrupts qualification-based career progression.

Because a young person's claim often represents 40+ years of potential lost income, the stakes are incredibly high. A small mistake in the early PAWE assessment or a failure to properly document your career goals can cost hundreds of thousands of dollars in future damages. Contact us to ensure your future is protected.

1. Get the insurer reasons in writing: identify whether the underpayment is about averaging period, missing earnings components, or rejected future-pathway evidence.
2. Build a one-page pathway map: set out your study/work timeline, expected transition point, and where each supporting document sits.
3. Separate streams: keep earnings-method issues separate from treatment/capacity issues so the review forum can decide the right question quickly.
4. Lodge before deadline: file a core pack first if time is short, then supplement with additional education/employer records.
5. Prepare PIC-ready indexing: keep evidence paginated and cross-referenced so escalation does not require rebuilding the file.