Pre-Enrolment LLND Assessment for RTOs: What Must Happen Before Training Starts

Many RTOs still think of LLND assessment as an onboarding task that can be cleaned up after enrolment. That approach creates compliance risk. Current ASQA guidance for Outcome 2.2 says providers must review each prospective student's LLND proficiency and digital literacy in the context of the training product before enrolment or commencement.

The Standards do not prescribe one framework, but they do require the provider to be able to explain and evidence its process.

For LLND, that means your process needs to do more than collect a learner response. It needs to create evidence that the RTO:

1. understood the LLND demands of the qualification;
2. assessed the learner at the right stage of the journey;
3. analysed the result against the qualification demands; and
4. decided what support, adjustment, referral, or follow-up was required.

If those four steps happen late, or happen without records, your process becomes difficult to defend.

What "Pre-Enrolment" Should Mean in Practice

For most RTOs, pre-enrolment LLND assessment should happen after the learner has expressed interest and provided enough course context, but before the learner is fully locked into delivery. A sound sequence looks like this:

• the learner applies or makes an enquiry;
• the RTO identifies the qualification or course pathway being considered;
• the LLND assessment is issued in writing or online;
• the learner completes the assessment;
• the result is compared against mapped qualification demands; and
• the RTO records any support action before training starts.

This sequence matters because it shows that the assessment was not an afterthought. It was part of the enrolment decision and support planning workflow.

The Four Records Every RTO Should Be Able to Produce

1. Qualification LLND Demand Record

Before you assess a learner, you need a documented benchmark. This should show the peak ACSF or LLND demands of the qualification, and where relevant, the digital literacy expectations created by the workplace context or delivery mode.

2. Learner Assessment Record

This is the completed learner assessment itself. It should be clearly tied to the learner, the date, and the qualification context. For certain higher-level or funded courses, separate academic-suitability and application-record requirements may also apply.

3. Gap Analysis Record

This is where many RTOs fall short. A completed tool on its own is not enough. You need evidence that someone interpreted the responses and compared them with the qualification demands.

4. Support Decision Record

If the learner has gaps, document what happens next. That could include:

• additional learner support;
• reasonable adjustment planning;
• referral to an LLN specialist;
• a conversation about course suitability; or
• a decision to proceed with specific monitoring in place.

Common Failure Patterns

The most common pre-enrolment LLND mistakes are operational, not conceptual:

• the assessment is administered after training has already commenced;
• the learner completes a tool, but nobody records a gap analysis;
• the assessment is generic and not tied to a mapped qualification benchmark;
• support is discussed informally but not documented; and
• digital literacy is ignored even where the training environment clearly demands it.

Each of these gaps weakens your audit story because it breaks the link between learner needs, course demands, and the action taken by the RTO.

How to Make the Workflow Scalable

The operational challenge is scale. Once an RTO has multiple qualifications, multiple campuses, or multiple assessors, a manual spreadsheet-and-template workflow starts to fragment.

A scalable pre-enrolment LLND workflow should make it easy to:

• map the qualification once and reuse that benchmark;
• issue the right assessment for the right qualification;
• capture learner identity and completion date automatically;
• generate a visible gap analysis;
• record support decisions in the same system; and
• retrieve the full evidence chain later without relying on one staff member's inbox.

That is why many RTOs are moving away from static LLND templates and toward software that treats LLND as a process, not just a document.

A Practical Standard for Audit Readiness

If you want a practical test, pick five recent enrolments and ask:

1. Can we show the mapped LLND requirement for the qualification?
2. Can we show the learner completed the assessment before training started?
3. Can we show the result was analysed, not just collected?
4. Can we show what support decision was made?
5. Can we retrieve all of that without relying on scattered manual records?

If the answer is yes for every learner, your pre-enrolment LLND process is likely in good shape. If not, fix the workflow before your next review cycle exposes the gap.