Almost nobody rips out Cornerstone OnDemand. The contracts run for years, the implementation cost is buried, it is wired into the HRIS, and it is the system of record for compliance. Replacing it is a programme, not a project.
Yet a large number of organisations running Cornerstone are also running their instructor-led training on spreadsheets, shared calendars and email. That is not because their administrators are disorganised. It is because Cornerstone models instructor-led training as a type of learning object rather than as an operation, and the gap between those two things is where trainer scheduling, room booking, resource management, external provider billing and utilisation reporting all fall through. We looked at the general version of this problem in why instructor-led training fails at scale.
This guide covers what Cornerstone actually does for instructor-led training, where it runs out, and the two realistic responses. For most organisations the answer is not replacement. It is running a training management system alongside Cornerstone and writing completion records back, which Cornerstone’s own APIs support and which there is working precedent for.
First, the economics: why replacement is usually the wrong question
Worth being concrete, because the decision hinges on it.
Published contract data puts the median Cornerstone agreement around 27,400 US dollars a year, with three-year terms typically preferred and priced 10 to 25 percent below annual terms. Implementation commonly runs 15 to 30 percent of first-year subscription, more where global rollouts or significant integration work are involved. Renewal escalators of 3 to 5 percent a year are normal.
So a typical customer is part-way through a multi-year commitment, has already spent heavily on implementation, has trained administrators over months, and has the platform integrated with HR systems that other processes depend on.
Against that, the ILT problems described below are real but bounded. They affect the training operations team, not the compliance record.
Replacing a platform to fix a bounded problem is how organisations end up two years into a programme that has not yet delivered the thing it was started for. The proportionate response is almost always to keep Cornerstone doing what it does well and add capability where it is missing.
That said, if you are approaching a renewal and genuinely reassessing, the sections below on export routes will be useful. Just make the decision on the full picture rather than on ILT frustration alone.
How Cornerstone models instructor-led training
Understanding the object model explains most of the limitations, because they follow directly from it.
Everything in Cornerstone Learning is a Learning Object, usually shortened to LO, each with a unique LOID. A course, a video, a curriculum and an instructor-led event are all learning objects with different types. This is elegant for a catalogue and awkward for an operation.
Instructor-led training is structured as:
- Event: the reusable container, effectively the course definition
- Session: a scheduled instance of that event, with dates, location and instructor
- Part: a component within a session, which is how multi-day training is represented
- Roster: the list of registered learners on a session, and where attendance and completion are recorded
- Learning Assignment: the registration linking a user to the LO
- Transcript: the learner’s record of everything they have taken
Around this sit Instructors, Facilities and Locations, Vendors representing external training providers, Waitlists, Interest Tracking for demand that has no scheduled session yet, and Express Class for recording training that happened without a formal session. Availability and seat allocation are controlled through Organizational Units, or OUs, which is Cornerstone’s hierarchy for departments, locations, grades and so on.
The model is coherent. The friction comes from the fact that a session is fundamentally a catalogue entry with dates attached, not a logistical event with resources, costs and a trainer’s diary behind it.
Where Cornerstone runs out for ILT operations
These are documented behaviours and consistently reported user experiences, not opinions about the product’s quality.
Waitlists behave in ways that surprise people
Cornerstone’s own waitlist documentation sets out several constraints. A user can hold only one waitlist request per event, so granting a place on one session automatically denies their requests on the others. Waitlists expire, moving to a Waitlist Expired status, and this happens without an obvious prompt. Seat allocation by organizational unit can push users onto a waitlist even when general seats remain available, which is confusing for everyone involved. And instructors cannot view an empty waitlist, which removes a useful signal about demand.
None of these are bugs. They are design decisions that suit a compliance-driven enrolment model and sit badly with a training operation trying to fill sessions.
Roster updates are constrained by design
Per the Session Roster API documentation, sessions must be past-dated before a roster can be updated, so you cannot close out a session early or record attendance as it happens. Only one roster submission is permitted per request, which makes bulk processing awkward. And where a minimum number of sessions must be completed before a record marks as complete, that threshold cannot be overridden through an integration.
That last one matters if you are planning to write completions in from another system. Test it specifically.
There is no real instructor management
Cornerstone has an instructor object. It does not have trainer availability, qualification tracking that prevents assigning someone to a course they are not approved to teach, conflict detection when the same person is scheduled twice, workload or utilisation views, or trainer cost and pay rates. For an organisation with a handful of internal trainers this is manageable. For one running a trainer pool across regions, it is the single biggest gap, and it is what dedicated instructor management exists to solve.
Facilities and resources are thin
There is a facility object. There is not a resource booking system covering rooms with capacities, equipment, catering, or the logistics that go with running physical training at scale. Most organisations track this outside Cornerstone, particularly those managing training across multiple locations.
External providers and cost are not really modelled
Vendors exist as records. Budget tracking, purchase orders, provider invoices, cost per session, chargeback to business units and margin analysis do not. If you buy training from external providers and recharge it internally, that process is happening in finance systems and spreadsheets.
Administration is genuinely heavy
Reviewers describe back-end functions as complex and unforgiving, with one noting it takes about a month to train a new administrator. Permissions run to hundreds of individual settings. Bulk actions are inconsistent, available on some screens and not others. Versioning is widely described as confusing, with mistakes that cannot be reversed.
This is the tax on Cornerstone’s configurability, and it is why organisations are reluctant to keep reconfiguring it to chase ILT requirements.
Reporting is capable but hard work
Consistently described as confusing and clunky, with dashboards difficult to maintain. Cross-curriculum certification reporting is described as cumbersome. The data is there. Getting a straight answer out of it takes effort.
One technical caveat worth knowing
There are reported cases of failed xAPI assessments being recorded as complete in Cornerstone. If your compliance position depends on pass or fail fidelity, test this specifically in your own configuration rather than assuming.
The two options
Option one: coexist. Keep Cornerstone as the system of record for learning, compliance and the transcript. Add a training management system that owns the operational layer for instructor-led delivery. Write attendance and completion back into Cornerstone so the transcript stays complete and your compliance reporting is unaffected.
| Owned by the training management system | Owned by Cornerstone |
|---|---|
| ILT catalogue as operations sees it | The transcript and learner record |
| Session scheduling and calendars | Compliance and certification reporting |
| Instructor allocation, availability and qualifications | E-learning content and SCORM |
| Rooms, facilities and resources | Curricula and learning paths |
| Registrations and waitlists | HRIS integration and user hierarchy |
| Joining instructions, reminders and attendance | Learner-facing catalogue, where you want one front door |
| External providers, cost tracking and chargeback | Enterprise reporting on the whole learning estate |
Option two: replace. Reasonable if you are at renewal, if Cornerstone’s wider talent modules are not being used, if ILT is the overwhelming majority of your delivery, and if the total cost genuinely no longer justifies itself. Covered further down.
How the coexistence architecture actually works
This is not theoretical. Cornerstone publishes the APIs, and there is an existing integration between Cornerstone and at least one training management system that works this way, which is useful evidence that the pattern holds.
The Session Roster API is the centrepiece. It writes attendance and completion back to the learner’s transcript. It requires the roster management permission, so make sure that is provisioned before anyone starts building.
The Learning Object API handles the catalogue side, creating and maintaining the event and session objects that the roster then attaches to.
The vILT Connector handles virtual delivery, and the Online Content Connector handles content, if either is in scope.
Cornerstone Extend and the Edge marketplace are the integration platform through which all of this is configured and managed.
The working pattern, based on an existing production integration between a training management system and Cornerstone, maps roughly like this.
| Training management system | Cornerstone |
|---|---|
| Organisations or accounts | Organizational Units |
| Contacts | Users |
| Course templates | Event learning objects |
| Scheduled events | Sessions |
| Registrations | Learning Assignments |
| Attendance and pass or fail | Roster updates, written to transcript |
Authentication is OAuth 2.0, and the sync is bidirectional in practice: users and structure flow from Cornerstone, operational scheduling happens in the training management system, and completions flow back. Check what your candidate platform supports through its integration capability before you scope the build.
What to test before you commit
Do not accept a general assurance that integration is possible. Test these five things specifically, in your own environment.
- Roster write-back on a real session, including the requirement that sessions must be past-dated before the roster updates.
- The completion threshold, since a minimum-sessions rule cannot be overridden by an integration. If your programmes depend on partial completion logic, establish exactly how it behaves.
- Pass and fail fidelity, given the reported xAPI issue. A failed assessment must record as failed.
- OU mapping, because Cornerstone’s hierarchy controls availability and seat allocation and rarely maps cleanly onto how a training operations team thinks about customers or departments.
- User provisioning direction. Decide which system creates people and which consumes them, and make sure everyone building the integration knows the answer.
This is a build, not a switch. Scope it with a named owner on both sides, a test environment, and a defined set of records that must reconcile. Ask any vendor you are evaluating to show you a working Cornerstone integration rather than describing one.
If you are genuinely replacing Cornerstone
The export position is better than most people expect.
The Data Exporter API and the Real-Time Data Warehouse provide bulk access to core objects. This is Cornerstone’s documented route for getting data out at volume, and it is a genuine capability rather than a support ticket.
The Learning Object API and Session Roster API cover the learning and ILT layer in detail.
Reporting exports provide an independent cross-check on API extracts, which is worth doing.
What generally does not transfer is your configuration, which is the largest single asset you have built. Permission structures running to hundreds of settings, OU hierarchies, availability rules, curriculum logic, notification triggers, report definitions and dashboards. None of it exports, and rebuilding it is the bulk of the work in any replacement. Also expect to leave behind email history, audit trail, and the version history of learning objects.
A full Cornerstone replacement for a mid-to-large enterprise is realistically a six to twelve month programme, with the data migration a minority of the effort. Anyone quoting you eight weeks has not seen your permission model. Our LMS migration guide covers the wider programme shape.
Validating either path
Whether you integrate or replace, set numeric criteria and test against them.
- Transcript integrity. Completion records must appear correctly for a test population, with the right dates, the right status, and the right pass or fail outcome.
- Compliance reporting unchanged. Run your standard compliance report before and after and reconcile it line by line. This is the one that matters to your risk function.
- Certification expiry dates intact, checked individually where regulatory requirements apply.
- Waitlist and seat allocation behaviour producing the outcomes operations expects, not just the outcomes the configuration technically implies.
- A full end-to-end test: schedule a session, register a learner, deliver it, mark attendance, confirm the transcript updates, confirm the certificate issues, confirm the compliance report picks it up.
Have someone from the compliance or risk side sign off the transcript testing. They are the people who will find out first if it is wrong. For heavily regulated environments, our white paper on regulatory training at scale goes further.
Suggested Reading : SimpliTrain vs Cornerstone OnDemand: 2026 Comparison
Where SimpliTrain fits, and where it does not
This guide has argued at length that most organisations should not replace Cornerstone, so it would be inconsistent to end with a pitch to replace Cornerstone. What follows is where a training management system alongside it genuinely earns its place, and where it does not.
Against the gaps named earlier, SimpliTrain covers: an instructor directory holding qualifications, availability and conflict detection, so a trainer cannot be assigned to a course they are not approved to teach or booked into two places at once; rooms, facilities and equipment as bookable resources with capacity; waitlists that behave the way an operations team expects rather than the way a compliance enrolment model requires; external training providers with cost tracking, purchase orders and chargeback to business units; trainer pay rates and cost per session; multi-location and multi-entity scheduling; and utilisation reporting on trainers, rooms and programmes. Completion and attendance write back to the Cornerstone transcript, so compliance reporting is unaffected.
This is worth looking at if you have a trainer pool rather than two or three internal facilitators, if you book physical rooms or equipment, if you buy delivery from external providers and recharge it internally, or if anyone on your team is maintaining a scheduling spreadsheet outside Cornerstone. That last one is the clearest signal, because the spreadsheet exists precisely where the platform stops.
It is not worth looking at if your instructor-led training is a small number of sessions a year, delivered virtually, by internal people, with no rooms, no external providers and no chargeback. Cornerstone handles that adequately, and adding a second system would be overhead without a return.
One commercial note relevant to Cornerstone customers specifically. Cornerstone is priced per user, so a common worry about adding any second platform is paying twice for the same population. SimpliTrain is priced flat-rate on administrators and instructors, with unlimited learners, so the cost is driven by the size of your operations team rather than your headcount. That is usually the difference between this being affordable alongside Cornerstone and not.
Frequently asked questions
Does Cornerstone OnDemand support instructor-led training?
What is the difference between an Event and a Session in Cornerstone?
How do Cornerstone waitlists work, and why do they behave oddly?
Why can’t I update a session roster in Cornerstone?
How do I export data from Cornerstone OnDemand?
Can I integrate a training management system with Cornerstone?
Should I replace Cornerstone or add a system alongside it?
How long does it take to replace Cornerstone OnDemand?
What does Cornerstone OnDemand cost?
Where to start
Count how many hours a week your team currently spends on instructor-led scheduling outside Cornerstone: the spreadsheets, the room emails, the calls to check whether a trainer is free. That number is the actual size of the problem, and it is usually the argument that settles whether to build an integration or carry on as you are.
Book a demo to see how SimpliTrain handles instructor allocation, resource booking and ILT operations alongside Cornerstone, and to work through the five integration tests above against your own environment.
