How to run a cohort-based course, week by week

A self-paced course is a library: learners start whenever they like and finish if they keep going. A cohort course is a class: everyone starts on the same date, moves through the material together, and has deadlines. The group and the schedule do the motivating, which is why cohorts tend to feel more like a program than a product.

The trade-off is your time. A self-paced course is built once and sold many times. A cohort needs you, or someone on your team, present every week. Price it accordingly, and only choose the format if you want to be in the room.

Size depends on how much individual feedback you promise. If you review every assignment yourself and each review takes 15 minutes, a 40-person cohort means 10 hours of reviewing per assignment. That is the number to calculate before you set a cap: learners × minutes per review × assignments per week. Math example, not a customer outcome.

For a first cohort, 15 to 30 people is a sensible range. It is enough for discussion and peer energy, and small enough to notice when someone is falling behind. Grow the next cohort by adding teaching assistants or peer review, not by doing twice as much yourself.

Length: four to eight weeks covers most skills. Shorter than four and there is no time for practice between sessions; longer than eight and life gets in the way for a growing share of the group. If the material needs twelve weeks, split it into two cohorts people can take in sequence.

Predictability is what makes cohorts work. Use the same shape every week. Monday: the week's lessons open, with a short video or post from you on what matters this week. Midweek: one live session (60 to 90 minutes) for teaching, questions and working through examples. Thursday or Friday: the assignment is due. Weekend: feedback goes out, and pods meet on their own.

Publish the full calendar on day one, with every live session, every deadline and the graduation date, in the learner's time zone. Most cohort drop-off happens quietly, when someone misses one session and loses the thread. A visible schedule makes it easy to see where to rejoin.

Split the cohort into pods of four to six people who check in with each other weekly. Give them a simple script: what did you finish, what are you stuck on, what will you do before next week. Pods take ten minutes for you to set up and do more for completion than any feature, because people show up for people they know are expecting them.

Mix pods by time zone first and experience level second. A pod that cannot find a common hour will not meet.

Watch pods in week two. If a pod has gone silent, merge its members into active pods rather than waiting for them to recover; a pod of two quiet people is worse than no pod at all. Ask one confident learner in each pod to start the weekly check-in thread, so the habit does not depend on you remembering to prompt every group.

Assignments are what separate a cohort from a group webinar. Each week should end with something learners make: a draft, a plan, a working version. Feedback on that work is what people are really paying for.

Keep feedback structured so it scales: one thing that works, one thing to change, one question to think about. If you add peer review, give reviewers the same three prompts. Grade against a short rubric you publish in advance, so nobody is surprised.

Make the end visible and worth reaching. A final project, a short showcase where learners present to each other, and a certificate that can be verified by anyone who sees it. A certificate should say what someone actually did, not just that they attended.

Tell people on day one what graduation requires: for example, at least five of six assignments submitted and the final project complete. A clear bar raises completion and makes the certificate mean something.

The worst moment in a cohort is the week after it ends, when a group that has met every week for two months suddenly has nowhere to go. Plan the next step before graduation: an alumni space, a monthly alumni call, an advanced cohort, or a membership. Graduates are the people most likely to buy from you again and to recommend you, so give them a home.

Here is the checklist to screenshot: fixed start date, fixed weekly rhythm, one live session a week, pods of four to six, a real assignment every week, a published graduation bar, and an alumni path ready before the last session.

HiveLearn keeps the course, the group and the calendar in one place. Drip and scheduled lessons release each week's material on your schedule. Course capacity caps enrollment, and expiry dates and enrollment keys let you run separate intakes. Live sessions are events with reminders and calendar sync, run through the Zoom integration. Assignments come with instructor review and a gradebook, so the weekly feedback loop has a home.

For pods and cohorts, member tags and segments let you group learners and message each group, and discussions with categories give each cohort or pod its own thread. At graduation, certificates are issued as a PDF with a public verification page (hivelearn.app/verify/<code>) and a share image. Because the community lives in the same product, the alumni space is a space you already have, not a new tool to set up. See the pricing page for which plan includes each feature.

If you only ever sell self-paced courses and have no plans to run live sessions, a dedicated course host such as Teachable or Thinkific is a reasonable, simpler fit; both are mature at self-paced delivery.