For the past twelve months onCourse development has been focused on improving and revising the online enrolment experience and now we are ready to move into a new phase of development focusing on brand new features, particularly features for our RTO (Registered Training Organisation) clients.

Right now, we are designing and developing a feature called Training Plans.

In a nutshell, this new function will allow you to create a delivery schedule in the class, assigning different start and end dates for each of the units of competency you set within the course. Right now, you can do this on an outcome by outcome basis for each student enrolled in the class, but this can be a tedious process if you have lots of students or lots of outcomes. Also, by setting up the training plan by class, when you roll over a class to create a new instance, the training plan can be rolled over too.

By linking units of competencies to class sessions, you can also provide additional information to students and tutors about what content will be delivered on each day of the class.

Currently, onCourse sets the start and end date for all units assigned to the class to the first and last class session dates. This does not allow some people to easily meet the reporting requirements of their government funding bodies which expect staggered start and end dates for units across the duration of the class.

This is how it will work: 1. By default, all units assigned to the class will be given the start and end date of the class (the same as it works currently) 2. Optionally, you can then link a session to one or more units from the course. In that case the unit start/end dates are inherited from the session(s). 3. If a unit is listed in many sessions its start date is the first session, end date is end of last session. 4. Outcomes inherit start and end dates from the units, but they can still be overridden manually when a single student is granted an extension, or completes a unit early.

These screen shots are some early mockups of what we are working on. We’d love to hear your feedback and suggestions