Learning Management
Monday, July 27, 2026 | 5:44 AM
A pivotal study can put 60 sites into motion on rolling IRB calendars over nine months, take on new sub-investigators at month four and month 11, and absorb a protocol amendment at month seven. Training for that study never arrives in one wave, because nothing else in the trial does either. GlobalLearn has handled the assignment side of that reality for years: map a course to a site and role, and enrollment follows. What it didn’t have was a controlled release step—a point where the study team decides that a specific course is ready for a specific site, and the system records the decision. I’ve watched study teams fill that gap themselves: courses pushed out by hand, status tracked in a side spreadsheet, someone’s personal diligence standing in for a control. That’s the point where clinical trial training management stops being a routine task and becomes a standing source of risk.
GlobalLearn 2.7 is our answer to that gap. We focused the release on three things: a governed release workflow, a single course lifecycle for every course type, and configurable compliance visibility. Each one takes something study teams were doing by hand and makes it a system behavior. The 60-site study above shows where.
Site Training Governance with a Real Release Point
Course release is now an explicit, governed action. When site 41 activates in month five, an authorized study user releases the study’s courses and learning plans to that one site, working from either the training library or the study’s Sites tab, and the 40 sites already mid-study are never touched. Bulk release across many sites is there for the moments that call for it, like amendment training going study-wide.
We also made release conditional. A course is eligible for release only when it’s published, its site and role mappings are configured, and the target site is marked Ready for Training. Each of those gates maps to a failure every study team has seen at least once: a course that looks finished but has no role mapping is released to site 41, no one gets enrolled, and the issue surfaces weeks later during a compliance review. In 2.7, that course never leaves the library.
Underneath the release sit the assignment rules. In 2.7, site and role mappings are standing rules: define once that a course applies to all CRAs and investigators, and the system calculates the eligible learners from the site roster, including at sites added later in the study. When site 41 joins in month five, nobody rebuilds anything. The rules created in month one already know who needs training. When a course genuinely does not apply, a per-site or per-role Not Applicable exception records that decision explicitly instead of leaving it implied.
Anyone who has managed site training through broad groups knows the alternative. The coordinator at site 12 ends up carrying investigator-only training because the group was easier to build broad than precise. Her compliance number drops for courses she was never meant to take, the study team chases completions that shouldn’t exist, and the training matrix quietly stops matching the delegation log—right up until a monitor asks about it. Overtraining isn’t a cosmetic problem. It spends site goodwill, buries real gaps under assignment noise, and turns a compliance dashboard into something you interpret instead of trust.
Mid-study change is the case we designed the rules against. When a sub-investigator joins site 12 in month 11, she can be released training individually, and learners mid-course elsewhere never notice. Once a course has been released to a site, its assignment rule becomes additive-only: new sites and roles can be added, but existing ones cannot be pulled out from under learners mid-course. Training groups haven’t gone anywhere; they’re still the right tool for cross-study and non-site-bound training. Assignment rules take over the site-bound work that used to be forced through them.
Once a course is released, enrollment runs automatically according to those rules. The Sites table displays a pending-release warning icon for any site with training awaiting release, alongside a Training Progress bar, making the status of every site visible from a single screen instead of requiring teams to reconstruct it from spreadsheets.
One Course Lifecycle, Start to Finish
Amendment training gets built under the worst possible conditions: mid-study, under time pressure, with sites waiting. That is exactly when setup errors happen, and it’s why we rebuilt the Course Wizard. A release gate only works if “published” means the same thing for every course—and before 2.7 it did not. Standard courses had no true Draft state and followed different rules than other course types, so the line between still-being-built and ready-to-assign was partly a matter of convention. Now every course type moves through the same lifecycle: Draft, Published, Inactive. The month-seven amendment course starts in Draft and can be published only after it passes validation, including a check that it contains at least one piece of content. However rushed month seven gets, an empty shell of a course cannot reach a site.
We consolidated enrollment setup the same way. Training Plan and Enroll/Unenroll, previously two separate enrollment paths, are now a single Users & Groups step inside the wizard, with validation at each stage and a Review & Confirm screen before anything takes effect. Every status change and assignment lands in the audit trail. None of this is the flashy part of 2.7, but release control doesn’t work unless course readiness is defined and enforced the same way everywhere—so this came first.
A Learning Management System Built for How Trials Run
That 60-site study will run for years through rolling activations, personnel turnover, protocol amendments, and audits. At every one of those moments, someone has to answer for the state of training. We built 2.7 around the three questions those moments raise: When does training reach a site? How consistently are courses built? Who sees which compliance data? Because GlobalLearn connects natively to the rest of the Trial Interactive eClinical platform, including eTMF and CTMS, training records stay tied to the systems the rest of the trial already runs on. For teams handling clinical trial training management across a growing roster of sites and studies, the payoff is fewer manual workarounds and a compliance picture that holds up when someone asks to see it.
Curious what GlobalLearn 2.7 could look like in your own studies? Reach out to your Trial Interactive representative to see the update in action.
