Complete a recorded pre-delivery review before enrolling learners. The review should cover the exact unit package, the implemented Catapult LMS setup and the way your RTO will train and assess its cohort.
Appoint one person to coordinate the work. Product setup, compliance review and trainer preparation often involve different staff.
If your organisation is setting up Catapult for the first time, see How to get access to Catapult LMS.
Confirm the resource
Follow Identify your Catapult product type and unit release. Record the Catapult product type from the current catalogue or purchase record and any displayed product version. Confirm the training package, unit code, title and release against training.gov.au. If the unit is contextualised, record its edition code or edition title.
If any of these details conflict, stop the setup and contact Customer Support on (08) 8275 9333 or support@catapult-elearning.com to confirm the intended package.
Assign the review work
The accountable manager should name the people responsible for:
- confirming purchase scope and delivery fit
- reviewing the training and assessment materials
- configuring Catapult LMS access and submissions
- preparing trainers and assessors
- checking workplace, simulation and equipment arrangements
- approving contextualisation and release for delivery
Use role names that make sense in your RTO. One person can complete several parts of the review.
Review the learning and assessment
Follow the unit as a Learner would. Use Previewing units in the Catapult LMS to open the review enrolment. Open every topic, assessment section and referenced document. Review each supplied print output.
Do not save assessment answers while reviewing the Learner view unless you intend to test submission or marking. Saving an answer can make the review enrolment chargeable and prevent an automatic credit when the enrolment is deleted.
Check what evidence the assessor will receive, where benchmarks are kept and how practical performance will be observed. Record any requirement for a workplace, simulation, third party or specialist facility.
Your RTO's responsibility: Review the assessment tools before use. Mapping and supplier documentation support that review but do not replace it.
Check learner and assessor files
Create a file list with its audience and purpose. Pair each learner workbook, checklist or template with the relevant assessor guide, solution, benchmark or observation record.
Open the files. Their names might not show the audience, document links or version details.
Assessor-only: Confirm that model answers, completed workbooks, benchmarks, marking guides and assessment decisions are unavailable to learners.
Configure Catapult LMS
Test the implemented unit using Learner, Trainer and Admin accounts. Check:
- enrolment and assigned trainer details
- learner navigation and section availability
- assessor access to guidance and submissions
- file upload types and size limits
- video, website and external service links
- progress, completion and submission behaviour
- email or notification settings used by your organisation
Record the test account, date and result. Remove test submissions if your records procedure requires it.
Confirm supported uploads and limits in What file types can be uploaded into Catapult LMS?. Review Changing the automated notification templates if your organisation uses customised messages.
Prepare trainers and assessors
Give trainers and assessors enough time to work through the unit before delivery. They should know where to find instructions, benchmarks, mapping and evidence records. Use Prepare trainers and assessors to use a Catapult resource as the readiness checklist.
Discuss any unit-specific judgement points, observation requirements and learner support arrangements. Keep a record of the briefing and any decisions that affect delivery.
If the review identifies a need to adapt the resource, see How Catapult supports contextualisation, What is Edify? and Contextualise a Catapult resource safely before making changes.
Approve the unit for delivery
The sign-off should identify:
- the approved product type, unit code and unit release
- the edition code or edition title, where applicable
- reviewers and approval date
- contextualisation completed
- unresolved conditions or local instructions
- next review date and change triggers
Comments
0 commentsPlease sign in to leave a comment.