Every course builder lets you drag lessons into an order. Far fewer make that order mean anything. If the player will happily open lesson nine for a student who has not watched lesson two, what you have built is a playlist with numbers on it.
This guide covers when to enforce order and when not to, how to build the alternating lesson-and-quiz pattern that most taught courses want, and the one misconfiguration that can lock every student out of the second half of a course. Everything below is how Alva Courses behaves — the Shopify app that builds, sells and delivers courses natively inside your store.
A curriculum a student can skip through is not sequenced
You ordered the lessons for a reason. If the player lets a student open lesson nine before lesson two, that order is a suggestion, and the ones who most need the sequence are exactly the ones who ignore it. Enforcing order turns a playlist back into a curriculum.
There is a second reason, and it is the one people discover late. A padlock drawn in the interface is decoration unless the course also refuses to record progress out of order. Otherwise a determined student can mark lessons complete they never opened, walk their progress to the end, and collect a completion certificate for a course they skipped — which is a problem for them, and a much bigger one for whoever trusts the certificate.
When to enforce order — and when not to
Enforce order when later material is unsafe, meaningless or misleading without earlier material: technique that builds on technique, regulated procedure, anything assessed at the end. Leave it open when the course is a reference library, when students arrive with very different backgrounds, or when the buyer paid for an immediate answer.
Sequence it
- Skills that compound — languages, instruments, movement, code, anything where week four assumes week three.
- Safety and regulated practice — where doing step five before step two is not merely unhelpful but wrong.
- Assessed and certified courses — the credential is a claim about the whole curriculum, so the whole curriculum has to have happened.
- Programmes with checkpoints — where each module ends in a quiz or a piece of work you want completed before the next begins.
Leave it open
- Reference libraries — people come for one answer and should be able to reach it.
- Mixed-ability audiences — forcing an experienced buyer through beginner material is how you earn a refund request.
- Bonus and appendix material — extras should never sit behind a gate the student cannot see the point of.
Two ways to enforce order in Alva Courses
There is a course-wide setting and a per-lesson one. The course setting requires every lesson to be completed in order, so nothing can be skipped anywhere. The per-lesson checkbox gates only what comes after the lesson you tick, which is right when one lesson is a genuine prerequisite and the rest are not.
The interaction between them is the thing worth remembering: the course-wide setting overrides the per-lesson checkboxes. With it on, lessons stay locked even where the individual box is unticked. That is deliberate — it removes the failure where one forgotten checkbox quietly exempts a lesson from a sequence you thought was strict — but it does mean the two settings are not additive, and the course-level one wins.
On the student's side a gated lesson is visible but locked, with a line telling them what to finish first, naming the lesson where it can. It names the lesson that is actually blocking them rather than the one immediately before, so a student three lessons past a checkpoint is sent back to the checkpoint instead of into a chain of padlocks.
The Lesson → Quiz → Lesson pattern
The most useful sequence in a taught course alternates teaching and checking. A quiz step is a lesson containing only a quiz: students must pass it to complete that lesson, and the next lesson stays locked until they do. Teach, check, teach, check — and each check is a gate passed on merit.
Build it by adding a quiz step where a module ends, then writing the questions into it. The quiz itself carries the controls that make the checkpoint fair: a passing score, a limit on attempts or unlimited retries, whether correct answers are shown after each question, and whether the quiz is required to complete the lesson at all.
A worked module usually looks like this:
- Lesson 1 — teach. Video plus notes. Nothing gated; this is where the student starts.
- Lesson 2 — practise. An exercise or a reflection prompt, so the idea gets used before it gets tested.
- Quiz 1 — check. A quiz step with five or six questions, required to complete the lesson, passing score set where you would actually draw the line.
- Lesson 3 — build on it. Locked until the quiz is passed, so it is safe to assume the earlier material landed.
- Repeat per module, and keep the bonus material outside the chain.
Keep checkpoint quizzes short and set the passing score honestly. A twenty-question gate at ninety per cent is not rigour, it is attrition. If you want a stricter guarantee at the end rather than at every step, there is also a course setting requiring all quizzes to be passed before the course counts as complete. More on building the quizzes themselves in adding quizzes and assessments to a Shopify course.
The failure mode: a required quiz with no questions
A quiz marked as required to complete the lesson, with no questions in it, can never be passed. That lesson can never be completed, and every lesson after it stays locked forever. It is the single most damaging misconfiguration in a sequenced course, and it is trivially easy to create.
It happens the same way every time. You add a quiz step where a checkpoint belongs, intend to write the questions after you have recorded the videos, get pulled into something else, and publish. Nothing looks wrong in the builder: the lesson is there, the quiz is there, the sequence reads correctly. The course is simply impossible.
Alva Courses will not let that ship quietly. The course screen raises a banner naming the lessons that require a quiz with no questions, and publishing is refused with an explanation rather than allowed with a warning. There are exactly two fixes, and the banner states both: add at least one question, or turn off the requirement that the quiz be passed to complete the lesson.
Take the same care with the reverse case. A quiz that is not required to complete the lesson is a practice exercise, not a checkpoint — students can skip it and move on. That is a perfectly good choice, as long as it is the choice you made rather than a box you forgot to tick on the one quiz that was supposed to be the gate.
Sequencing is not scheduling
Order and timing are different controls solving different problems. Sequencing decides what a student may open next; drip scheduling and publish dates decide when material exists for them at all. A lesson that has not been released yet is never the next lesson for anybody, so the two stack rather than fight.
In practice most structured programmes use both. Draft hides material you have not finished making, a scheduled date releases a module to everyone on the same morning, a drip releases it a set number of days after each student enrols, and sequencing governs the order they work through whatever has arrived. Drip-feeding course content covers the timing half in detail; add a deadline that actually expires and the programme has an end as well as a beginning.
A sequencing check before you publish
Run the course once as a student before anyone buys it. Most sequencing faults are invisible in the builder and obvious in the player: a gate on a lesson you meant to leave open, a required quiz nobody can pass, and a bonus section stranded behind a prerequisite the buyer was never told about.
- Open every quiz that is required to complete a lesson and confirm it has questions.
- Check the passing scores against how hard the questions actually are.
- Walk the course in preview from lesson one and see where you get stopped.
- Check the bonuses are outside the gated chain, or say on the product page that they are not.
- Say the structure out loud on the sales page — buyers who know a course is sequential do not ask why lesson nine is locked.
Getting started
Decide the shape first, then set two switches. For the exact steps, read Require lessons in order. If you are still assembling the course, the online course launch checklist covers the rest of what to verify before the first student arrives.
Frequently asked questions
Enforce order when later material is unsafe, meaningless or misleading without the earlier material, and when the course ends in an assessment. Leave it open for reference libraries, quick-win courses and audiences who arrive with very different backgrounds and expect to jump straight to the part they need.
The course setting makes every lesson a gate, so nothing anywhere can be skipped. The per-lesson checkbox gates only after the lesson you tick it on. The course setting overrides the checkboxes: with it on, lessons stay locked even where the per-lesson box is unticked.
The lesson stays visible in the course list, marked as locked, with a line telling them what to finish first — naming the lesson where possible. It points at the lesson that is actually blocking them, not simply at the one immediately before.
The usual cause is a quiz marked as required to complete the lesson that has no questions in it. An empty quiz cannot be passed, so that lesson can never be completed and everything after it stays locked. Add at least one question, or turn the requirement off on that quiz.
No. Gating only ever looks forward. A lesson a student has already completed stays open for as long as they have access to the course, so they can go back and rewatch, re-read or retake anything behind them at any time.
Yes, and they answer different questions. Drip scheduling and publish dates decide when a lesson exists for a student; sequencing decides what they may open next among the lessons that have arrived. A lesson that has not been released yet is never treated as the next one.