Skip to main content

onCourse for TAFEs and education systems

A common platform. Local control.

Your learners need programs they can find and understand. Your local teams need manageable enrolment, delivery and communications. onCourse supports that work in dedicated institution environments, with ISH helping you agree the setup and reporting you need.

onCourse supports course discovery, enrolment, payment where applicable and day-to-day course administration. It can work alongside existing student, finance and learning systems through agreed integrations.

01

Why make skills easier to reach?

People turn to TAFE to enter work, build on their experience or prepare for a changing industry. Short courses and skill sets can provide a focused next step, while helping employers and communities develop the capabilities they need.

When training is easy to find and understand, people are better placed to choose a program that suits them. onCourse connects course publication, enrolment, communication and delivery administration, helping institutions respond to local needs with less repeated work.

How onCourse could help your TAFE team connect everyday work.

You need programs people can find and join, teams that can keep the work moving, and a clear view of enrolment and course activity. When information sits across different systems, too much time can go into keeping everything aligned.

onCourse gives course publication, enrolment and everyday administration a connected foundation. For administrators, that can mean less chasing between systems and a clearer way to keep course information and enrolments organised. For leaders, it means being able to see the activity behind the programs they are responsible for. We work with your team on the information, workflows and agreed system connections that would make the biggest practical difference.

Practical stages

02

How can participation develop in practical stages?

Begin with a useful first scope rather than assuming the final network design. ISH operates one established onCourse product with ongoing updates and support, while each participating institution retains a dedicated environment and agreed local responsibilities.

Three stages, with local boundaries retained

  1. Run the first two institutions well

    Dedicated environments. Validate each institution’s scenarios.

  2. Make further participation repeatable

    Local data boundaries. Institution-specific preparation and acceptance.

  3. Develop shared capabilities where agreed

    Identity, discovery and reporting separately scoped and validated.

Illustrative development path, not a shared database or a promise that every shared capability is included.
  1. 1

    Run the first two institutions well

    Support course discovery, bookings, enrolment, payment where applicable, communications, administration, agreed integrations and useful reporting. Validate each institution's real learner, staff and finance scenarios before extending the approach.

  2. 2

    Make further participation repeatable

    Use the common maintained product and a repeatable onboarding approach, with appropriate institution-specific branding, responsibilities, configuration and data boundaries. Each institution still completes its own preparation, testing and acceptance.

  3. 3

    Develop shared capabilities where agreed

    Treat shared identity, coordinated discovery and consolidated reporting as separate work. Define governance, data flows, permissions, metric definitions, reconciliation, support ownership and acceptance before relying on the shared service.

ISH-operated onCourse platformCommon operation, updates and support
  • Institution ADedicated environment, local data boundaries, settings and responsibilities
  • Institution BDedicated environment, local data boundaries, settings and responsibilities
  • Institution CDedicated environment, local data boundaries, settings and responsibilities
Illustrative operating model. Any shared administration, access or reporting is separately scoped and validated.

Start with an agreed first scope, then decide together what wider participation needs.

Open the capability and requirements matrix
03

How would it fit our existing systems?

Agree which system holds each record, who can use it and how information moves between teams. We work with you to define and test the required connections with finance, learning, identity and student systems.

That design work includes practical questions such as where course details are maintained, how payment information reaches finance, which learner information is exchanged and who investigates a failed transfer. Access and reporting requirements are considered with the institutions involved.

The handbook documents funded-training progression and funding invoices for a single enrolment under a configured non-fee-for-service funding contract. For programs where a learner does not pay a fee, the enrolment, payer, invoice, confirmation, reporting and reconciliation path should still be configured and tested. This does not establish funding eligibility or promise automated government claims.

The evidence

04

What evidence can you look at?

Explore handbook tasks for enrolment, delivery and reporting, alongside the historical Sydney Short Courses account of connections to institutional finance and content systems. Use these sources to frame the scenarios and separately scoped connections your own institutions need to test.

05

What does getting started involve?

Start with the institutions and programs selected for the first scope. onCourse is an established platform; we agree the local setup, required connections and checks, then support additional institutions through the same approach.

  1. 01

    Agree the first scope

    Define participating institutions, local responsibilities and acceptance criteria.

  2. 02

    Configure and test

    Prepare the setup and test any agreed migration or integration work.

  3. 03

    Prepare and launch

    Support teams into use, then onboard additional institutions with their own setup.

Clear decisions, prepared information and agreed responsibilities give the work a sound foundation. We plan the first scope together and retain each institution’s own environment and local control.

06

What would we discuss first?

We’ll talk through the institutions and programs involved, expected course activity, existing systems and the responsibilities each team needs to retain. From there, we can identify the best starting point and the evidence you need to assess the fit.