Scheduled cohorts with seat caps
Course outline, runs with dates, price, cap, waitlist and enrolment deadline.
Solutions · Cohort learning
Learners will pay several times the price of a recorded course to finish something alongside other people, on a schedule, with someone who checks their work. This model is built for that: instructors open cohorts with start dates and seat limits, learners move through live sessions and assignments together, and the platform settles each instructor once the cohort has run.
Professional plan. Enterprise customization is quoted on scope.
Cohorts with start dates and seat caps
Live sessions tied to the curriculum week
Instructor payout after the cohort runs
V1
Course outline, runs with dates, price, cap, waitlist and enrolment deadline.
Material released per week, one assignment type with file or text submission, and grading by the instructor.
Live sessions linked to an existing meeting tool, attendance captured on the platform and recordings attached to the week.
One commission rate, one refund window and a statement for each instructor after the cohort ends.
Operating loop
An instructor publishes the course outline once, then schedules runs of it: start date, weekly session times, seat cap, price and an enrolment deadline. Each run is its own record, so one course can have a waitlisted spring cohort and a half-empty autumn one.
Checkout reserves a seat, takes payment or a deposit, and drops the learner into the cohort’s calendar and discussion space. Once the cap is reached, new sign-ups join a waitlist that is offered seats automatically if someone asks for a refund before the start date.
Material unlocks on a schedule rather than all at once. Each week pairs a live session, a recording for anyone who missed it, an assignment with a due date and a small peer group that comments on each other’s work before the instructor or a teaching assistant grades it.
A learner who attends enough sessions and passes the graded work receives a certificate carrying the cohort dates. When the refund window closes, the platform releases the instructor’s share, less commission and assistant fees, on a settlement statement for that cohort.
Roles
Wants to know exactly when sessions happen, what is due this week and how far behind they are. Most drop-off happens in week two, so their home screen is the week’s plan, not a library of lessons.
Designs the curriculum, runs the live sessions and sets the pass mark. Needs a roster showing attendance and submission status per learner, so a quiet student can be nudged before they disappear.
Grades against the instructor’s rubric, answers questions in the cohort channel and flags learners at risk. Sees only the cohorts they are assigned to and never the instructor’s earnings.
Approves instructors, sets commission and refund policy, resolves complaints about a cancelled session and watches fill rates across upcoming cohorts to decide what to promote.
Hard parts
A 7 pm session in London lands close to midnight in Delhi. Store every session in UTC, show it in the learner’s local time, warn at checkout when sessions fall at unsociable hours, and show instructors where their applicants live before they fix the schedule.
Some learners enrol after week one or ask to move to the next run. Decide whether late joiners get earlier recordings and extended deadlines, and whether a deferral carries progress and payment into the next cohort, before support has to improvise.
Random pairing sends work to classmates who have already gone quiet. Pair only learners who have submitted their own work, cap reviews per person, and let the instructor override a peer grade without it turning into a dispute.
Whether sessions run in an embedded video room or an existing meeting tool, attendance has to be recorded on the platform, recordings must attach to the right week on their own, and a dropped call must not mark a learner absent.
A learner who leaves in week three has used part of what they bought. Pro-rated refunds, who funds them and how they reduce the instructor’s payout need rules the ledger applies consistently, not one-off decisions.
Operator controls
Sample lessons and credentials are reviewed before an instructor can sell, then completion rates and learner ratings are tracked per cohort so a weak run is visible early.
Every upcoming cohort with its fill rate, waitlist length, start date and instructor, so the team can merge two thin cohorts or add a second run of a sold-out one.
Refund windows per course, deferral rules and the split of refund cost between instructor and platform, applied automatically when a request is approved.
Every issued certificate with a public verification link and the cohort it came from, plus the ability to revoke one if misconduct is proved.
Revenue
A share of every seat sold, usually higher than on recorded courses because the platform supplies the learners, the scheduling and the certificate.
Expensive cohorts fill faster when learners can pay in parts. The platform can charge a small fee for the plan or absorb it to lift fill rates.
Employers buy several seats in one cohort for their staff, invoiced to the company, with a manager view of attendance and completion.
Later
Add them when instructors ask, because pairing only works once cohorts are large enough to have several active learners per group.
Build your own live room only after attendance data shows the linked meeting tool is costing you completions.
Worth the effort once team seats are a real share of revenue.
Next decision
Still choosing between cohorts, an open course marketplace and institutional training? Start with the category overview.
Open registerWhen instructors upload recordings that learners can start any day, the open course marketplace model fits better than scheduled cohorts.
Open registerWhen an employer assigns courses and needs records for auditors, an organisational learning platform fits better than a consumer marketplace.
Open registerReady to build? The edtech development service sets out who would work on your cohort platform, in what order, and what you own at the end.
Open registerA guide to offline lessons, progress sync, assessments and subscriptions in mobile e-learning apps.
Open registerLive demo
Open each app or panel in a new tab and sign in with the demo login shown. The demos run on shared sample data, carry our demo product names, and show the ready-made product before any customization.
Student App
user@demo.com | User_321Instructor App
instructor@demo.com | Instructor_321Browser Demo
the two phone-app logins work here tooAdmin Console
ask the team for the credentialsArtifact register
Reference screens illustrate workflows, not a contracted feature list. Sample prices, data, and responses are demonstration content; confirm the current scope during a walkthrough.
Deployable Product Architecture
Product decision workflow / system register
Delivery team
Team discussion for platform product decisions
Define
Assemble
Deliver
Review
Deployable Product Architecture
Healthcare workflow systems / system register
Care workflow
Healthcare app user workflow for patient platform planning
Verify
Schedule
Deliver care
Audit
Deployable Product Architecture
Product engineering delivery / system register
Product delivery loop
Product team reviewing engineering delivery
Discover
Blueprint
Build
Operate
Deployable Product Architecture
Video streaming platform planning / system register
Content platform
Cinema screen for video streaming product content
Publish
Discover
Deliver
Moderate
Recorded courses compete on price because their content is easy to copy and most buyers never finish. A cohort sells something different: a fixed start, people to learn alongside and someone who notices when you fall behind. The course page has to make that promise visible, with dates, session times, group size and the instructor’s involvement, or buyers will compare it with cheap videos.
That is why the cohort, not the course, is the unit you sell, report on and pay out. Fill rate per cohort, week-two attendance and completion per cohort are the numbers that tell an operator whether the model is working.
Enthusiasm carries learners through the first session. Week two, when the first assignment is due and their job gets busy, is where cohorts lose people. Reminders tied to each learner’s own deadline, a peer group that notices absence and a roster that highlights missing submissions do more for completion than badges or streaks.
Build the at-risk signal early: a learner who missed a session and has not opened this week’s material should appear on the teaching assistant’s list the same day, with a one-tap message.
Seats, waitlists, deferrals, partial refunds and instructor payouts all touch the same ledger. Write the rules down before design starts: when a seat is held, when it returns to the waitlist, who funds a refund in week three and when the instructor sees the money. A rule written in advance costs a day; one discovered in support costs trust with learners and instructors at once.
FAQ
A course marketplace sells recordings that anyone can start at any time. A cohort platform sells a seat in a run with a start date, live sessions, deadlines and a group, so it needs scheduling, attendance, grading and seat inventory, and it can charge far more per learner because more of them finish.
Yes. The outline is written once and each run is a separate cohort with its own dates, cap, price, learners and payout, which lets you compare runs and retire the weak ones.
They watch the recording attached to that week, and attendance is marked missed or excused according to the instructor’s rule. If certificates require a minimum attendance, say so at enrolment.
Most platforms hold the instructor’s share until the refund window closes, often a week or two into the cohort, and settle the remainder after it ends. Paying earlier leaves the platform funding refunds it cannot recover.
No. Linking sessions to an established meeting tool and recording attendance on your side is enough to prove the model; an owned live room is a later investment.
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
Specification for verifiable digital credentials such as course certificates.
The calendar format used for session invitations learners add to their own calendars.
Accessibility requirements for lesson pages, captions and assessments.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.