Identifying a Gap Is Only Half the Job
Many RTOs administer an LLND assessment, identify that a learner needs support, and then stop at the finding. That is where compliance risk begins.
An LLND process is only complete when the RTO can show what happened after the gap was identified. In practice, that means a learner support plan or equivalent support record that links the assessment result to a real response.
What a Learner Support Plan Should Answer
A support plan does not need to be bureaucratic, but it does need to be specific. At minimum, it should answer:
- Which skill areas were below the qualification demand?
- How material were the gaps?
- What support, adjustment, or referral was offered?
- Who is responsible for delivering or monitoring that support?
- When will the learner's progress be reviewed?
If those questions cannot be answered from the record, the plan is too vague.
Core Elements of a Defensible Support Plan
Learner and Qualification Context
State the learner, qualification, date, and assessor or staff member responsible for the decision.
Gap Summary
Summarise the gap in practical terms. For example:
- Reading below required level for complex workplace procedures
- Numeracy below required level for multi-step calculations
- Digital literacy gaps likely to affect LMS navigation and online submissions
Planned Support Actions
Support actions should be concrete. Examples include:
- extra orientation for digital systems;
- plain-English learning materials;
- scheduled literacy or numeracy support sessions;
- LLN specialist referral;
- additional check-ins during the first weeks of delivery; or
- modified instructions or reasonable adjustments where appropriate.
Timing and Ownership
Each action needs an owner and a review point. Otherwise the plan becomes a generic note rather than an operational document.
Learner Acknowledgement
Where appropriate, keep a record that the learner was informed of the support available and that the conversation took place.
The Difference Between Support and Exclusion
LLND assessment is meant to inform support, not create automatic exclusion. That is why your support planning language matters. The record should demonstrate a reasoned response to the learner's needs, not a simplistic pass-or-fail gate.
There will be cases where the gap is so significant that course suitability needs a deeper conversation. Even then, the documentation should show a fair, evidence-based process.
Common Support Plan Mistakes
The most common issues are:
- using generic wording such as "extra support as needed";
- failing to link the support action to a specific skill gap;
- not recording who owns the action;
- not reviewing whether the support actually happened; and
- keeping the plan in a separate place from the assessment evidence.
These mistakes make the record hard to defend later because they weaken the connection between assessment, decision, and action.
What Good Looks Like at Scale
For RTOs running multiple cohorts, support planning needs to be operationally simple. A good system makes it easy to:
- generate the initial support recommendation from assessment data;
- edit it to reflect trainer judgement;
- assign responsibility;
- store the record with the learner's assessment evidence; and
- review patterns across cohorts.
That last point matters. If multiple learners need the same support intervention, you may have a cohort-level issue rather than an individual one.
A Practical Benchmark
Pick three learners with identified LLND gaps and review their files. For each learner, can you find:
- the gap analysis;
- the support plan;
- the owner of the support action; and
- evidence that the action was delivered or reviewed?
If the answer is no, your learner support process is still too dependent on memory. Tighten the record now, before an audit exposes the gap.