A new hire class of eighteen reps starts Monday. Without batches, an admin assigns the same course eighteen times, then opens eighteen individual progress pages to see who's behind. With a batch, the admin assigns it once and watches the cohort move as a group.
Why this matters
Onboarding classes, regional certification rollouts, and department-wide compliance refreshes share a shape: the same content, going out to a defined group, on a shared timeline. Assigning that content one person at a time, then piecing together status by opening each learner's record individually, doesn't match how these programs actually run. A training manager rolling out a certification to a region isn't tracking one person's progress, they're tracking whether the region is on schedule as a whole, and which pocket of the cohort is falling behind.
How it works
A batch lets an admin run the same course for a different group of learners on its own timeline, without duplicating the course itself. Instead of building a second copy for a new cohort, the admin creates a new batch under the existing course: same content, new timeline, different participants.
Batches live under Manage > Courses. An admin opens the course they want to reuse and goes to the Batches tab.
To create one, the admin clicks Add Batch, names it (for example "June Onboarding" or "Q3 APAC"), and sets a timeline, either fixed start and end dates or a set duration counted from each learner's start date. Participants are assigned as specific users, whole teams, or all reportees under a given manager. Once saved, the course appears in each learner's Courses section with that batch's specific deadline. The same bulk-assignment approach applies to Call Blitz sessions, so a manager can put an entire cohort into a shared practice block rather than adding reps one at a time.
Tracking happens at the batch level. Each batch has its own progress view, completion rates, pass rates, and individual learner status, filterable so a manager sees one cohort's results without them blending into an earlier run of the same course. The Coaching and Performance dashboard carries this through to a dedicated Batches tab, showing completion and performance data filtered by cohort.
A few mechanical details matter for planning. A learner can only be active in one batch of a given course at a time. If the course content changes, that change applies to future batches but leaves batches already in progress untouched. And completed batches stay visible in the Batches tab afterward, so a manager can pull up last quarter's onboarding results without them being replaced by the current run. Full mechanics are in managing course batches.
What this unlocks
An L&D lead onboarding a new hire class can assign the full curriculum to all eighteen new reps in one action, set a two-week deadline from each person's start date, and check the Batches tab each morning for completion at a glance instead of clicking through individual records.
A regional sales director rolling out a certification requirement can stagger it: APAC gets a batch with an August deadline, EMEA gets a separate batch with a September deadline, and each region's completion and pass rate stay visible without one muddying the other's.
A compliance manager running an annual refresher across a department can launch it as a single batch tied to the fiscal year. When audit season comes around, that batch's historical completion record is still sitting in the Batches tab, unchanged by whatever training is running now.
The bigger picture
A training program stops being an administrative burden once it's tracked the way it's actually run, as a cohort moving together, not as a stack of identical assignments an admin has to manage one by one.
See it in Action
Tell us what you're working on, whether that's sales calls, support tickets, or leadership coaching, and we'll show you how it fits.
Talk to Sales