A common platform. Local control.

Help learners find and book the right course, give employers a clearer way to organise training, and keep your team’s enrolment, payment and delivery work connected.

For institutions working together, a common approach can make everyday processes more consistent while local teams remain responsible for their own programs. Start with representative courses and agree what success needs to look like.

• Courses easier to find and book
• Less repeated administration
• Employer and group bookings coordinated
• Course and financial activity visible

ISH operates one established core platform with common ongoing updates and support. Each participating institution has a dedicated environment with its own settings, staff permissions, business rules, administration, reporting, website branding and instance identity. Additional institutions join through supported onboarding and configuration.

Where shared access, overarching administration, single sign-on or consolidated reporting is required, ISH works with the organisations involved to scope and validate the arrangement.

Agree which system holds each record, who can use it and how information moves between teams. ISH works 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.

At University of Sydney, Sydney Short Courses, ISH connected onCourse with the University’s finance system and Adobe Experience Manager. The published example shows experience working with institutional systems and teams. Other customer stories describe course bookings, financial reporting and everyday administration.

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.

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.