Skip to main content

Best Practices for Delivering Courses

Learn how to get your course to your learners at the right time, with schedules, delivery methods, and enrollment working together.

Platform access level: Org Admins, Managers, and Distributors (anyone who delivers courses).


In Arist, you deliver a finished course to your learners in a tool they already check, at a pace that gives the lessons a chance to stick. Once you know who the course is for, you set up a schedule, pick the delivery methods, enroll learners, and confirm every lesson arrived. This guide walks that path in order and points you to a step-by-step guide for each part.

animated series intro: The right people, the right time (Who + When converge into Deliver, learners light up)

1. Know who the course is going to

Delivery starts with an audience, and in Arist that is a cohort, a reusable named group of learners you can send many courses to over time. You can build one from a CSV upload, from dynamic rules that keep their own membership current, or by adding learners by hand for a small pilot. You can also skip managing the list and let learners enroll themselves with a shared link or code, which is covered in Sharing Courses for Self-Enrollment.

Building that audience and keeping it accurate has its own guide. Start at Best Practices for Managing Cohorts and Learners for cohorts, learner profiles, and the enrollment statuses that tell you delivery worked. The rest of this page assumes you have an audience and covers getting the course to it.


2. Set up the schedule

The schedule controls when lessons arrive. Naming it after the audience and cadence, like "Sales reps M-W-F", makes the Delivery tab readable at a glance.

  • Basic: This is the default type, and it offers two cadences. An instant cadence is self-paced, where each learner reply triggers the next lesson. A scheduled cadence sends on delivery days you pick. A required-response toggle can hold the next lesson until the learner answers a question.

  • Custom: You set an exact date for each lesson, or a set number of days after the previous one. Custom schedules include a built-in catch-up mode that automatically brings late enrollees up to speed, which fits teams where learners join mid-launch.

Note: Spacing lessons out is what makes them stick, so match the cadence to how much practice the behavior needs, not to how fast you can send. The full setup, field by field, lives in Scheduling and Delivering Courses.

Every schedule you create lives on the Delivery tab, which is also where you start a new send.

the Delivery tab in Table view: columns for Status, Name, Channel, Cohorts, Cadence, Enrolled, and Created, with the Create new button top-right

If your organization uses teams (currently in Beta), the Delivery, Cohorts, and Learners lists show only the team you have selected, so switch teams to see the schedules that belong to another one.


3. Choose the delivery methods

Arist delivers over SMS, WhatsApp, Email, Microsoft Teams, Slack, and Arist Messenger, so a course reaches learners in an app they already check instead of one more place to log in. You pick the delivery methods when you build the schedule, and your team's enabled methods live in Team settings under Delivery methods.

  • Pick the methods per schedule: Choose one or more delivery methods as you set up the send. See Using Delivery Methods.

  • Know how learners opt out: Replying STOP opts a learner out on SMS, WhatsApp, and Email. On Microsoft Teams and Slack, STOP does not cancel an enrollment, which matters when the training is required or compliance related. See Using System Keywords.


4. Enroll learners and launch

With the cohort and schedule set, enrollment starts delivery. Add the cohort to the schedule, review the recipient list, and enroll.

Tip: Add yourself to the schedule before you launch, so you experience the course exactly as your learners will.


5. Track delivery and impact

After launch, confirm delivery reached your learners and act on anyone who stalls. The delivery tracker sorts every learner by enrollment status, so an Error or a stalled learner is visible while there are still lessons to come. Reading those statuses and acting on them is covered in Best Practices for Managing Cohorts and Learners.

The fuller picture of engagement and impact lives in Reviewing Analytics, which closes the loop back to the outcome you set when you built the course.


Related articles

Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].

Did this answer your question?