Twenty-five mechanics, with the failure mode printed beside each one.

• Pick two.

  A course running three mechanics well beats a course running nine, and the failure of a gamified course is almost never that it had too few points. It is that nobody maintained the thing after week four.

• Choose by the problem, not by the mechanic.

  Attendance, preparation, procrastination and shallow reading are four different failures. Points fix none of them by themselves.

• Build the maintenance into the estimate.

  Each entry gives a build time and a weekly upkeep cost. The upkeep number is the one that decides whether the mechanic survives the term.

Reluctance about gamification usually comes from a reasonable place: that it substitutes a scoreboard for a reason to care. That is a design failure with known causes, and the failure-mode line under each mechanic names the cause for that mechanic.

What these notes are written against

Click paths verified 6 September 2026. We recheck this file every September, before the northern-hemisphere term starts, and the verification date at the top of the page changes or the file comes down. A build guide with no verification date is a guess with formatting.

Three things that moved in Moodle 5.x and change where you click. The activity chooser is regrouped by purpose rather than by an alphabetical list, so an activity you found by scrolling in 4.x is now under a category tab. Courses carry an Activities overview page, which is where students now find every quiz or assignment of one type in one list. Course and activity settings pages have been reorganised, and Restrict access, Activity completion and Badges all keep their names and their behaviour.

If your institution is still on Original. Every mechanic in this file works there, and the route differs: Release conditions is Adaptive Release, Progress Tracking is the Performance Dashboard, and Achievements is an Original tool with no exact Ultra equivalent. Build it in Ultra if you have the choice, because anything you build in Original stops being editable on 1 January 2027.

Three lines that are not negotiable

• No leaderboard that publishes an individual student’s rank without that student opting in.
• No points that change a grade unless the conversion is stated in the syllabus before week one.
• Every visual mechanic needs a text equivalent, because a progress bar that only exists as a colour excludes part of your cohort.

The third line is also a procurement question. Public-sector institutions across the EU carry web accessibility obligations, and WCAG 2.2 is the standard most institutional policies now name. A gamified layer that adds colour-only status, a drag-only interaction or an unlabelled icon puts a course out of line with the institution’s own published statement, which is a conversation with a head of department rather than with a student. Check what your institution has committed to before you build anything visual.

1. 01 · Gated path

   Problem

   Students meet material out of order and arrive at the hard task without the prerequisite.

   Failure mode

   One gate breaks and the whole cohort emails you in the same hour. Always leave a manual override and tell students it exists.

   Build notes

   Moodle

   1. Open the activity. 2. Open Restrict access. 3. Add a restriction of type Activity completion. 4. Select the prerequisite activity. 5. Set the condition to “must be marked complete”. 6. If you do not want the locked item hidden, click the eye icon to make it visible but greyed.

   Canvas

   1. Open the Module. 2. Select Edit. 3. Add a requirement for each item. 4. Set “Students must move through requirements in sequential order”. 5. Add a prerequisite module.

   Blackboard

   1. Open the item menu. 2. Select Release conditions. 3. Add a performance or completion rule. 4. Save.

   Build time. 40 minutes for a 12-week course. Upkeep. 5 minutes a week.

2. 02 · Visible progress

   Problem

   Students cannot tell how much of the course they have completed, so effort feels unbounded.

   Failure mode

   A bar that counts clicks rather than learning teaches students to click. Tie completion to submissions and graded checks only.

   Build notes

   Moodle

   1. Turn on Activity completion in course settings. 2. Set completion criteria per activity. 3. Add the Course completion status block or the Completion progress block. 4. If the block list does not show the block, ask your administrator to enable it.

   Canvas

   1. Set module requirements. 2. Publish the modules. 3. Direct students to the Modules page progress indicators. 4. Add the Course Progress information to the syllabus page.

   Blackboard

   1. Turn on Progress Tracking for the course. 2. Confirm the student view shows the markers. 3. Read the staff view in the Gradebook.

   Build time. 60 minutes. Upkeep. None after setup.

3. 03 · Weekly streak

   Problem

   Work happens in two heroic weekends and nothing in between.

   Failure mode

   A streak that breaks once is abandoned for the term. Build in one planned rest week and say so at the start.

   Build notes

   Moodle

   1. Create a weekly Choice or a short Quiz called Check-in. 2. Set Activity completion to “student must submit”. 3. Create a badge with a criterion of completing all check-ins except one. 4. Set the badge to award automatically.

   Canvas

   1. Create a weekly ungraded New Quiz of the survey type, or a 1-point assignment. 2. Set the due date to the same weekday each week. 3. Use an Assignment Group called Check-ins. 4. Set the group weight to 0 if the check-in must not affect the grade.

   Blackboard

   1. Create a weekly Journal entry or a 1-point test. 2. Set a due date for each week. 3. Use the Gradebook to see the pattern. 4. Add a release condition on the full set to unlock the week-12 item.

   Build time. 90 minutes. Upkeep. 10 minutes a week.

4. 04 · Points layer

   Problem

   Low-stakes work has no visible value, so it is skipped for the graded work.

   Failure mode

   Points that do not buy anything are ignored by week three. Decide what points purchase before you award any — see mechanic 16.

   Build notes

   Moodle

   1. Install the Level Up XP plugin, or use a manual grade item. 2. If the plugin is not permitted, create a Gradebook category called XP. 3. Add manual grade items to that category. 4. Exclude the category from the course total.

   Canvas

   1. Create an Assignment Group called XP. 2. Set its weight to 0%. 3. Add point-only assignments to it. 4. Tell students where to read their total.

   Blackboard

   1. Create a Gradebook column called XP. 2. Set the column to not count towards the final grade. 3. Enter points manually or by rubric.

   Build time. 2 hours. Upkeep. 20 minutes a week — the highest-upkeep mechanic in the set.

5. 05 · Criterion badges

   Problem

   Skills that are practised but not graded stay invisible on a transcript and in the student’s own picture of themselves.

   Failure mode

   A badge for participation means nothing. Every badge names a criterion a stranger could check.

   Build notes

   Moodle

   1. Go to Course, then Badges, then Add a new badge. 2. Write the criterion in the description in one sentence. 3. Set the criteria to Activity completion or Course completion. 4. Enable the badge. 5. To make badges portable, connect a backpack in site settings.

   Canvas

   1. Use Canvas Credentials if your institution licenses it. 2. If it is not licensed, create an Outcome per skill. 3. Attach the Outcome to a rubric. 4. Report mastery through the Learning Mastery Gradebook. 5. Publish the criterion for each badge in one sentence students can read.

   Blackboard

   1. Check whether your instance has an achievements or badging tool enabled. 2. If it does, add one achievement per criterion with a release rule. 3. If it does not, create a Gradebook column per criterion and set it to not count towards the final grade. 4. Publish the criterion list to students in the course information area.

   Build time. 30 minutes per badge. Upkeep. None if automatic.

6. 06 · Levels

   Problem

   The middle of term has no visible landmarks between week 3 and the exam.

   Failure mode

   Levels that only reward volume push quantity over quality. Set each threshold on a quality gate, not on a count.

   Build notes

   Moodle

   1. Define three thresholds in the XP category from mechanic 04. 2. Create one badge per threshold. 3. Set each badge criterion to a grade condition on the category. 4. Announce the thresholds in week 1.

   Canvas

   1. Create three Outcomes named as levels. 2. Set mastery thresholds. 3. Attach them to the rubrics of the anchor assignments. 4. Publish the mastery view to students.

   Blackboard

   1. Create three content items named as levels. 2. Set each release condition to a Gradebook score. 3. Order them in the course content list.

   Build time. 90 minutes. Upkeep. 5 minutes a week.

7. 07 · Mastery retake loop

   Problem

   Students stop at the first passing score and never return to what they got wrong.

   Failure mode

   Unlimited attempts on the same questions teaches the answer key. Draw each attempt from a question bank of at least three times the items.

   Build notes

   Moodle

   1. Create a question bank with 3 items per learning point. 2. Create a Quiz. 3. Add Random questions from the bank. 4. Set Attempts allowed to Unlimited. 5. Set Grading method to Highest grade. 6. Set Question behaviour to Deferred feedback with a review after the close date.

   Canvas

   1. Create an Item Bank. 2. Create a New Quiz. 3. Add items by bank reference. 4. Set Multiple Attempts and keep the highest score. 5. Restrict the answer view until after the due date.

   Blackboard

   1. Create a Test. 2. Add Question Sets drawn from a pool. 3. Set Multiple Attempts to Unlimited. 4. Set the score to use the highest attempt. 5. Set the feedback to release after the due date.

   Build time. 3 hours for the bank. Upkeep. 15 minutes a week.

8. 08 · Branching scenario

   Problem

   Students learn the correct procedure and never meet the judgement call it depends on.

   Failure mode

   A branch with an obviously correct path is a quiz with extra clicking. Every branch point needs at least two defensible options.

   Build notes

   Moodle

   1. Create a Lesson activity. 2. Add a Content page per decision point. 3. Add jumps to the pages for each option. 4. Add Question pages where a check is needed. 5. Set Re-takes allowed to Yes.

   Canvas

   1. Create a Page per decision point. 2. Link the options as internal links. 3. If Mastery Paths is enabled, use a differentiated assignment instead. 4. Publish all pages but keep them out of the Modules list. 5. Give every option a text link, not an image map, so the scenario works for a screen reader.

   Blackboard

   1. Create Content items per decision point. 2. Add release conditions on a test score. 3. Alternatively, build the scenario in H5P and embed it.

   Build time. 6 hours for one scenario. Upkeep. None within the term.

9. 09 · Escape-room assessment

   Problem

   The final exam measures what students can hold for a week and forget in three.

   Failure mode

   A puzzle that is hard to open rather than hard to solve tests patience. Every lock must be opened by domain reasoning and by nothing else.

   Build notes

   Moodle

   1. Create a section per room. 2. Add a Quiz whose correct answer is the code. 3. Add Restrict access on the next section, conditional on that quiz grade. 4. Set the quiz to Unlimited attempts. 5. Add a hint that costs a mark.

   Canvas

   1. Create a Module per room. 2. Add a New Quiz with a single short-answer item. 3. Set a module requirement of a minimum score. 4. Set sequential progress. 5. Add a prerequisite for the following module.

   Blackboard

   1. Create a Folder per room. 2. Add a Test with a password for the next folder. 3. Set the release condition on the test score. 4. Confirm the sequence in student preview.

   Build time. 10 to 14 hours for the first one. Upkeep. None, and it runs again next year.

10. 10 · Boss challenge

    Problem

    Weekly tasks stay separate and students never assemble them.

    Failure mode

    A challenge that arrives without warning reads as a trap. Publish it in week 1 and let students see it from the start.

    Build notes

    Moodle

    1. Create the challenge Assignment in week 1. 2. Set Restrict access with a date condition. 3. Untick the hide box so students see it locked. 4. Add the marking rubric at the same time.

    Canvas

    1. Create the Assignment. 2. Set Available from as the release date. 3. Publish it immediately. 4. Attach the rubric.

    Blackboard

    1. Create the Assignment. 2. Set Show on and Hide after dates. 3. Attach the rubric. 4. Confirm students see the locked item.

    Build time. 2 hours plus the rubric. Upkeep. Marking only.

11. 11 · Team quest with fixed roles

    Problem

    Two students do the work and four watch.

    Failure mode

    Roles without separate deliverables collapse back into one person doing everything. Each role submits something with its own name on it.

    Build notes

    Moodle

    1. Create Groups and a Grouping. 2. Create a Group assignment. 3. Set Students submit in groups to Yes. 4. Set Require all group members to submit to Yes. 5. Add a separate reflection Assignment per student.

    Canvas

    1. Create a Group Set. 2. Create a Group Assignment. 3. Untick “Assign grades to each student individually” only if a shared grade is intended. 4. Add an individual assignment for the role deliverable.

    Blackboard

    1. Create Groups. 2. Create a Group Assignment. 3. Add a Group Journal for the role log. 4. Add an individual submission column.

    Build time. 2 hours. Upkeep. 20 minutes a week.

12. 12 · Peer review tournament

    Problem

    Feedback is read once and never used.

    Failure mode

    Anonymous review without a rubric produces “good work, well done”. Give three criteria and require one sentence per criterion.

    Build notes

    Moodle

    1. Create a Workshop activity. 2. Write the assessment form with 3 criteria. 3. Set the submission and assessment phases with dates. 4. Set the number of reviews per student to 2. 5. Run the allocation before the assessment phase opens.

    Canvas

    1. Create the Assignment. 2. Tick Require Peer Reviews. 3. Set Automatically Assign, with 2 reviews per student. 4. Attach a rubric and tick “Use this rubric for assignment grading” only if the rubric scores the work.

    Blackboard

    1. Create the Assignment with Peer Review enabled where the version supports it. 2. If peer review is not available, use a Discussion with a posting rule. 3. Attach the rubric to the Gradebook column.

    Build time. 2 hours. Upkeep. 30 minutes per round.

13. 13 · Team leaderboard, opt-in

    Problem

    A cohort with no visible collective momentum feels like 90 people working alone.

    Failure mode

    An individual public ranking demotivates everybody below the top five and is the single most damaging mechanic in this file when built wrong. Rank teams, never named individuals, and let students opt out.

    Build notes

    Moodle

    1. Create Groups. 2. Use the group aggregation view in the Gradebook. 3. Post a weekly summary table in an Announcement. 4. Do not publish individual names.

    Canvas

    1. Create a Group Set. 2. Export group scores from the Gradebook. 3. Post the standing as a Page updated weekly. 4. Do not enable any individual ranking tool.

    Blackboard

    1. Create Groups. 2. Use Gradebook filtering by group. 3. Post the standing as an Announcement.

    Build time. 45 minutes. Upkeep. 15 minutes a week, and it is manual.

14. 14 · Predict before you see

    Problem

    Students read results without ever committing to an expectation, so nothing is surprising and nothing sticks.

    Failure mode

    Grading the prediction destroys the mechanic. Score the reasoning and never the accuracy.

    Build notes

    Moodle

    1. Create a Choice activity with the candidate outcomes. 2. Set Publish results to After the activity closes. 3. Set Allow choice to be updated to No. 4. Reveal the real result in the following item.

    Canvas

    1. Create an ungraded New Quiz of the survey type. 2. Set it to show results after submission. 3. Post the actual result on the next page.

    Blackboard

    1. Create a Survey. 2. Set the results to release after the due date. 3. Add the real result as the following content item.

    Build time. 20 minutes per use. Upkeep. 10 minutes each week you run it.

15. 15 · Two-stage assessment

    Problem

    The test ends and the learning ends with it.

    Failure mode

    A group stage that carries too much weight rewards being in a strong group. Cap the group stage at 15% of the combined mark.

    Build notes

    Moodle

    1. Create Quiz A as individual. 2. Create Quiz B with the same questions, set to a Grouping. 3. Set Restrict access on Quiz B by Quiz A completion. 4. Weight the two items in the Gradebook.

    Canvas

    1. Create the individual quiz. 2. Create the group version as a Group Assignment. 3. Set a module requirement so the individual quiz comes first. 4. Set the assignment group weights.

    Blackboard

    1. Create the individual Test. 2. Create the group Test with a release condition on the first attempt. 3. Set the Gradebook weights.

    Build time. 2 hours. Upkeep. Marking only.

16. 16 · Points that buy something

    Problem

    Points with no exchange rate stop meaning anything by week three.

    Failure mode

    Selling marks for points corrupts the assessment. Points buy time, choice and access, never grades.

    Build notes

    Moodle

    1. Publish the exchange list in the course summary. 2. Create a Choice activity called Spend. 3. Restrict each option by the XP grade condition. 4. Record redemptions in a Gradebook column.

    Canvas

    1. Publish the exchange list on the syllabus page. 2. Create an ungraded New Quiz called Spend. 3. Use differentiated due dates to apply an extension. 4. Log the redemption in a 0-weight column.

    Blackboard

    1. Publish the exchange list in the course information area. 2. Create a Survey for redemption requests. 3. Apply exceptions in the Gradebook per student.

    Build time. 90 minutes. Upkeep. 20 minutes a week.

17. 17 · Grace tokens

    Problem

    One bad fortnight ends the term for a student who was doing well.

    Failure mode

    Unlimited extensions remove the schedule for everybody. Issue exactly two tokens, and require the student to spend one before the deadline, not after.

    Build notes

    Moodle

    1. Publish the rule in week 1. 2. Create a Choice activity called Use a token. 3. Set it to allow 2 responses per student. 4. Apply a User override on the assignment for each request.

    Canvas

    1. Publish the rule on the syllabus page. 2. Create an ungraded New Quiz called Use a token. 3. Assign a differentiated due date to that student. 4. Keep the log in a 0-weight column.

    Blackboard

    1. Publish the rule in the course information area. 2. Collect requests through a Survey. 3. Set a Gradebook exception per student.

    Build time. 45 minutes. Upkeep. 15 minutes a week, and it removes far more email than it creates.

18. 18 · Weekly retrieval quiz

    Problem

    Students meet each topic once and never again until revision.

    Failure mode

    A quiz that only tests this week’s material misses the point. Draw 30% of items from earlier weeks.

    Build notes

    Moodle

    1. Build one question bank category per week. 2. Create a Quiz per week. 3. Add 7 random questions from this week and 3 from earlier categories. 4. Set Attempts to 2. 5. Set the grade to 2% of the course total.

    Canvas

    1. Build an Item Bank per week. 2. Create a New Quiz per week. 3. Add items by bank reference in a 7 to 3 ratio. 4. Set the attempts to 2.

    Blackboard

    1. Build a Pool per week. 2. Create a Test with two Question Sets. 3. Set the counts to 7 and 3. 4. Set the attempts to 2.

    Build time. 4 hours for the term. Upkeep. 10 minutes a week.

19. 19 · Students write the questions

    Problem

    Students study by rereading, which is the least effective method available to them.

    Failure mode

    Unmoderated items enter the bank with wrong answers. Review every item before it is used, and say that you do.

    Build notes

    Moodle

    1. Create a Database activity with fields for stem, options, answer and source page. 2. Set Approval required to Yes. 3. Export approved entries. 4. Import the best items into the question bank.

    Canvas

    1. Create a Discussion or a form linked from a Page. 2. Set the submission format in the instructions. 3. Move approved items into the Item Bank by hand.

    Blackboard

    1. Create a Journal or a Discussion for submissions. 2. Approve items in a weekly pass. 3. Add approved items to a Pool.

    Build time. 90 minutes. Upkeep. 30 minutes a week for moderation.

20. 20 · The planted error

    Problem

    Students read to agree, which is not reading.

    Failure mode

    An error that is too subtle produces silence and an error that is too obvious produces nothing. Plant one of each and say how many there are.

    Build notes

    Moodle

    1. Upload the document with the errors. 2. Create a Forum with one thread per error found. 3. Set the Forum type to Q and A so students post before they read others. 4. Award the badge from mechanic 05.

    Canvas

    1. Post the document on a Page. 2. Create a Discussion. 3. Tick “Users must post before seeing replies”. 4. Attach a 1-point participation grade.

    Blackboard

    1. Post the document as a Content item. 2. Create a Discussion with Post first enabled. 3. Grade the thread.

    Build time. 2 hours to write the errors. Upkeep. 15 minutes a week.

21. 21 · Rotating discussion roles

    Problem

    The same four students post and the rest read.

    Failure mode

    Roles that repeat weekly become a chore by week five. Rotate every week and retire the mechanic after six.

    Build notes

    Moodle

    1. Create Groups named after the roles. 2. Create a Forum with Separate groups off. 3. Post the rotation table in week 1. 4. Change group membership each week, or use Groupings to pre-build the rotation.

    Canvas

    1. Create a Group Set named Roles. 2. Post the rotation on a Page. 3. Create the weekly Discussion. 4. Reassign group membership each week.

    Blackboard

    1. Create Groups for the roles. 2. Post the rotation in the course information area. 3. Create the weekly Discussion. 4. Edit membership weekly.

    Build time. 60 minutes. Upkeep. 10 minutes a week.

22. 22 · Difficulty ladder with choice

    Problem

    Strong students coast and struggling students drown, in the same task.

    Failure mode

    Students self-select downwards when the higher tier carries more risk. Cap the mark on the lower tier, and never make the higher tier the only route to a good grade.

    Build notes

    Moodle

    1. Create three Assignments named Tier 1, 2 and 3. 2. Set the maximum grade per tier. 3. Add a Choice activity for the declaration. 4. Restrict each assignment by the choice.

    Canvas

    1. Create three Assignments. 2. Use differentiated assignment to assign each tier to a section or a group. 3. Or enable Mastery Paths and set the source assignment thresholds.

    Blackboard

    1. Create three Assignments. 2. Use release conditions on a declaration survey. 3. Set the points possible per tier.

    Build time. 3 hours. Upkeep. Marking only.

23. 23 · Quest log

    Problem

    The course requirements live in six places and students hold none of them.

    Failure mode

    A log nobody updates is worse than no log. Automate the ticks from activity completion.

    Build notes

    Moodle

    1. Turn on Activity completion. 2. Add the Course completion status block. 3. Create a Page listing the required items and the optional ones. 4. Link each item to its activity.

    Canvas

    1. Create a Page called Quest log. 2. List required and optional items with links. 3. Set module requirements so the Modules page mirrors the log. 4. Pin the page to the course home.

    Blackboard

    1. Create a Content item called Quest log. 2. List the items with links. 3. Turn on Progress Tracking.

    Build time. 2 hours. Upkeep. 5 minutes a week.

24. 24 · Reflection gate

    Problem

    Feedback is collected and never acted on, by students or by you.

    Failure mode

    A reflection prompt with no consequence produces three words. Gate the next item on a submission of at least 60 words, and answer two of them publicly each week.

    Build notes

    Moodle

    1. Create an Assignment with Online text. 2. Set a word limit minimum in the instructions. 3. Set Activity completion to require a submission. 4. Restrict the next activity on that completion.

    Canvas

    1. Create a text-entry Assignment worth 1 point. 2. Set the module requirement to Submit the assignment. 3. Set sequential order in the module.

    Blackboard

    1. Create a Journal or a text Assignment. 2. Set a release condition on the next item. 3. Confirm in student preview.

    Build time. 45 minutes. Upkeep. 20 minutes a week, and this is the mechanic that pays it back fastest.

25. 25 · Live retrieval duel

    Problem

    The first fifteen minutes of a session are spent waiting for the room to arrive and settle.

    Failure mode

    A points race rewards speed over accuracy and the fast students win every week. Score in teams, and score the explanation rather than the answer.

    Build notes

    Moodle

    1. Create a Quiz with a short open window. 2. Set the timer to 6 minutes. 3. Set Attempts to 1. 4. Set the grade to count towards the XP category only.

    Canvas

    1. Create a New Quiz with a time limit of 6 minutes. 2. Set Available from and until for the session window. 3. Assign it to the XP group with 0 weight.

    Blackboard

    1. Create a Test with a 6-minute timer. 2. Set the availability window to the session. 3. Set the column to not count towards the final grade.

    Build time. 30 minutes per session. Upkeep. 30 minutes a week.

The answer depends on where your students actually fall away, which shows in the syllabus structure, the assessment timing and the LMS layout rather than in a list.

Course Engagement Audit — the syllabus and LMS layout reviewed, lecture analysis up to 90 minutes, a week-by-week Design-Risk Map, five plug-and-play mechanics chosen for your course, LMS-specific implementation notes, and tenure-ready teaching artefacts. Single Course with a 30-minute live call and 14 days of email questions, €399. Async Audit with a recorded 25-minute walkthrough, €299. Turnaround 7 to 10 days. No student data required, and no scoping call, because the scope is fixed and published.

Departments running up to four courses together: from €1,549, with the cross-course consistency report and a faculty session. Quoted and invoiced against a purchase order.

Or take the free route. Read the Design-Risk Map method, build two of the twenty-five above, and run the week-4 checkpoint yourself. If the answer is that your course does not need us, that is a fine outcome and we say it often enough to be worth asking for a brief.

No ghostwriting, ever · Human-led, PhD-signed