In this guide 6 sections
Follow one learner through six steps: payment, automatic enrolment, access dates, a cohort seat check with a waitlist, completion records and a numbered certificate. Each step should remove one manual task. Think of the spreadsheet tick, the sticky note and the hand-typed certificate.
Payment clears and the learner is enrolled at once
Take one learner, a working accountant who pays for an evening batch late on a Sunday, and watch what the system does next. The gateway returns a success callback. The order turns paid, and she should be enrolled before she closes the tab, without anyone in your office opening a spreadsheet.
Enrolment is one row that links learner, course, cohort and start date, and saving it sends a welcome email with the login and the first lesson link. No more Monday bank matching. If the callback never arrives, a retry job should settle the order from the gateway’s records, because a paid learner must never sit locked out of a course.
Access runs from a start date to an end date
Decide what was bought. Lifetime access, ninety days and cohort-length access are three different promises, and each one needs its own end date stored on the enrolment. Lessons then open on schedule and close by themselves.
Add an extension rule. A learner who fell ill for two weeks may receive fourteen more days, entered once with a reason and shown on the record for later audits. Send a warning email a week before the end date, because a learner who is surprised by a lockout will blame you, not the calendar.
- Start date and end date on the enrolment
- Opening schedule for each module
- Extension reason, days added and approver
- Warning email a week before expiry
Seat limits and a waitlist protect each cohort
Live batches have hard limits. A room, a trainer or a lab only holds so many people, so set the seat count on the cohort and let checkout stop selling at that number. The thirty-first buyer for a thirty-seat batch joins a waitlist instead of paying for a place that does not exist.
When a paid seat is cancelled, the first name on the waitlist gets an offer that lapses after one day, and the next name follows if it goes unanswered. Without a rule, someone phones down a sheet. Keep the queue in strict order. Stamp every offer with a time.
Completion is recorded from what the learner actually did
Write the completion rule before the batch starts, for example every module viewed, every assignment marked and a pass mark on the final quiz. The system then counts for you. The trainer stops paging through attendance sheets.
For live classes, take attendance with a check-in code rather than a paper register, and record it against that session. A learner who missed two sessions sees the make-up class on the dashboard, not a surprise at the end of the term. Absence is data, not a verdict.
- Lessons opened and videos watched past the set point
- Quiz attempts and the best score
- Assignments submitted and marked
- Live session check-ins
A numbered certificate issues itself and can be verified
When the completion rule is met, the system builds a PDF with the learner’s name, course title, cohort dates and a serial such as ACC-2026-0147. A counter issues the serial. Two certificates can never share a number, and nobody has to retype a Word template at midnight before the graduation event.
Put a verification page at a short address. An employer types the serial and sees the learner’s name, the course and the completion date, which settles most doubts in seconds. Revocation happens there too, with a reason and a date, so a revoked serial shows as withdrawn instead of vanishing.
Run one test learner from payment to PDF before the next batch opens, and write down every spot where somebody had to step in by hand.
Learner journey tracker
Every stage sits on a separate row of one sheet. The columns name the event that starts the stage, the manual step it removes, the field it must save and the person who sees exceptions. The last line holds the serial format and the verification address, with space to paste one sample certificate.
Open a blank worksheet to printQuestions owners ask
Should access end when a course ends?
It depends on what you promised. Self-paced courses often give a fixed period and cohort courses may close with the batch, so say which applies on the sales page. Store the end date on each enrolment.
How do I handle learners who pay in instalments?
Link each instalment to the access rule. Decide how many grace days apply and what closes when a payment is late, then record every override with a reason so the exception can be explained later.
What should a certificate carry?
The learner’s name, the course title, the completion date, the cohort or batch, a unique serial number and a verification address. Name the issuer too, and add a signature image if your awarding body expects one.
What if a learner finishes after the cohort has ended?
Decide the rule in advance. Some institutes allow a late completion window of a few weeks, while others move the learner into the next batch and carry the progress across. Either way, record the new end date and the reason on the enrolment, so that the certificate date makes sense later.