Skip to main content

🎓 Lesson 13: Question Pools, Results & Scoring

You've written good questions. Now let's make the assessment fair, repeatable, and reportable: draw random questions from a pool so no two learners see the same quiz, set a clear pass mark on a results slide, and understand exactly what score gets recorded — the plumbing that later reports to a Learning Management System.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Explain what a question pool (or bank) is and why random questions make an assessment fairer and harder to cheat
  • Set up a results slide with a pass/fail threshold
  • Understand scoring — points, attempts, and what "passing" means
  • Describe what data a scored quiz reports, and how it connects to SCORM/xAPI (set up here, published in Lesson 15)
  • Configure sensible retakes

⏱️ Estimated Time: 35 minutes

🎯 Project: Create a small question pool, set a pass score, and add a results slide to your course. All-New

In This Lesson

🎲 Question Pools & Random Draws

Picture a compliance quiz that every employee takes at the same desks, on the same day. If it shows the same ten questions in the same order to everyone, the answers travel down the hallway in about five minutes. A question pool fixes that. You write a bank of questions once, then tell Captivate to draw a random subset for each learner — say, "pick 5 from this pool of 20." No two people get the same quiz.

🎯 Why pools are worth it

Fairness & integrity. Random draws mean sharing answers doesn't work — everyone faces a different mix.

Retakes that mean something. If a learner fails and retakes, they get a fresh draw rather than memorizing the same ten questions.

Reusability. Build one solid pool and reuse it across a large group, or across multiple courses on the same topic.

The mechanic is simple: a pool holds many questions; a random question slot in your quiz says "draw one from that pool at runtime." Line up a few random slots and each learner gets a unique, fairly sampled quiz:

graph LR P["🗂️ Question pool
20 questions"] --> R["🎲 Random draw
pick 5"] R --> Q["📝 The learner's quiz
5 unique questions"] Q --> S["📊 Results slide
score vs pass mark"] S --> RP["📤 Reported to LMS
(SCORM / xAPI)"] style P fill:#c7d2fe,color:#1e293b style R fill:#fde68a,color:#1e293b style Q fill:#bfdbfe,color:#1e293b style S fill:#bbf7d0,color:#1e293b style RP fill:#f1f5f9,color:#1e293b

Figure 1 — A pool feeds a random draw, which fills the learner's quiz; the results slide scores it, and the score can report out to an LMS.

⚠️ A pool needs enough good questions

Random draws are only fair if every question in the pool tests roughly the same objective at roughly the same difficulty. Don't mix a trivial true/false in with a tough multi-part question and draw randomly between them — one learner gets a gift, another gets a grind. Write a pool of comparable, well-aligned questions (using everything from Lesson 12), and make the pool comfortably bigger than the number you draw.

💡 Pools are a historical Classic strength. Classic Deep, flexible random-question pools have long been a Captivate Classic specialty, and the all-new tool has been catching up. Because this is exactly the kind of feature Adobe keeps moving into the all-new Captivate release by release, check what your current version supports — and if you need industrial-strength pooling today, Classic (Part 4) may still be the surer bet.

🔢 Scoring: Points, Passing & Attempts

Scoring is how a quiz turns clicks into a number a system can act on. Three settings do most of the work, and they're worth understanding as a set rather than in isolation.

Setting What it controls How to think about it
Points per question How much each question is worth toward the total. Weight harder or more important questions higher if it matters; keep it simple otherwise.
Pass threshold The score a learner must reach to pass (a percentage or a point total). Set it to reflect real stakes — a safety course may demand a high bar; a primer, a gentler one.
Attempts How many tries a learner gets — per question and/or on the whole quiz. Balance fairness with integrity; combine with pools so retakes aren't just memorization.

A quick worked example, in plain terms: a pool draws 5 questions, each worth 10 points, for a total of 50. You set the pass threshold at 80% — so a learner needs 40 of 50 (four of five questions) to pass. If partial scoring is on for a matching or sequence question, a learner can earn part of that question's points for getting part of it right, which nudges the final score up in a fair way.

✅ The One-Line Rule of Thumb

Decide the pass threshold first, based on how much the topic matters, then set points and attempts to serve it. The number isn't arbitrary — an 80% bar on a safety quiz says something different from a 60% bar on an optional refresher. Let the stakes choose the bar.

💡 We won't print a "right" pass mark. There's no universal correct threshold — it depends on your topic, your organization's policy, and any regulations you answer to. Pick a defensible number for your course, and if you're building for a workplace, ask whether a required standard already exists.

🏁 The Results Slide

The results slide is the moment of truth the learner sees when the quiz ends. Captivate can generate one for you, and it typically shows the score, the pass/fail outcome, and how it was reached. It's also the slide most tied to what gets reported, so it's worth setting up thoughtfully.

A results slide usually pulls from Captivate's built-in quiz variables — running totals the tool keeps automatically, like the score so far, the maximum possible, the percentage, and the pass/fail status. You place these as dynamic text so the numbers fill in live. Here's the idea as a slide in the all-new Captivate:

Figure 2 — All-new Captivate (a simplified mock-up, not a real screenshot): a results slide showing a live score, pass/fail, and a retake button, with the pass mark and reporting set in Visual Properties.

Small touches make a results slide humane rather than cold: a warm pass message, a genuinely helpful fail message ("Review Module 2, then try again — you've got this"), and a clear retake path. Remember your growth-mindset framing from the whole course — a failing score is feedback, and your results slide is a good place to say so.

📤 What Gets Reported (and Retakes)

Here's where this lesson connects to the next big one. When a course runs inside a Learning Management System, the LMS wants to know things like: did this person complete the course, did they pass, and what was their score? Your scoring and results settings are what produce those answers.

The reporting data, in plain terms

  • Completion — did the learner finish (or reach the results slide)?
  • Score — the points or percentage they earned.
  • Pass/fail — measured against your threshold.
  • Sometimes more — depending on the standard, individual answers or interactions can be reported too.

Captivate packages this data using an e-learning standard — most commonly SCORM or xAPI (Tin Can) — so an LMS can read it. You set up what to report here (turn on score reporting, confirm the pass mark); you actually publish the SCORM or xAPI package in Lesson 15. For now, the key idea: the number on your results slide is the number the LMS records, so get it right before you publish. All-New

🔁 Retakes done right

Retakes let a learner try again after a fail — but a retake is only meaningful if it's a genuine second test. Two habits make them fair:

  • Pair retakes with a pool. A fresh random draw each attempt means learners re-earn the pass rather than memorizing a fixed set.
  • Decide how the LMS treats multiple attempts — for example, whether it keeps the best score or the latest. Policies vary, so match your organization's rule.
💡 Test the numbers before you trust them. Preview your quiz, deliberately pass it once and fail it once, and check that the results slide and the reported outcome both say what you expect. A mis-set pass mark or a reporting toggle left off is the kind of quiet bug that only shows up when a real learner's completion doesn't record — catch it now, not in the LMS.

🎯 Try It: Build a Pool & a Results Slide

🏋️ Activity: A small pool, a pass mark, a results slide (about 20 minutes)

Objective: Turn the questions from Lesson 12 into a fair, scored, reportable assessment with a random draw and a results slide. All-New

Steps

  1. Create a question pool and add several comparable questions to it — reuse and expand your Lesson 12 questions so the pool is bigger than the number you'll draw. (⏱️ 6 min)
  2. Add random question slots to your quiz that draw from the pool (for example, draw 3 from a pool of 5–6). (⏱️ 3 min)
  3. Set points and a pass threshold — decide the pass mark first based on how much the topic matters, then confirm points per question. (⏱️ 3 min)
  4. Add a results slide and make sure it shows the score and a clear pass/fail message; add a warm pass note and a helpful fail note. (⏱️ 5 min)
  5. Preview and test: pass it once, fail it once, and confirm the results slide reads correctly and score reporting is turned on. (⏱️ 3 min)
💡 Hint

If your version of the all-new Captivate offers only limited pooling, don't stall — build the biggest pool it supports, set your pass mark and results slide, and note that Captivate Classic (Lesson 18–19 territory) offers deeper random pools if you ever need them. The pooling feature set moves between releases, so use what's in front of you and check the current version's docs.

✅ Activity Complete When…

  • You have a question pool with several comparable questions
  • Your quiz draws a random subset from that pool
  • A pass threshold is set and a results slide shows score and pass/fail
  • You've previewed both a passing and a failing run and the numbers are correct

🎯 Quick Quiz

Question 1: Why use a question pool with random draws instead of showing everyone the same fixed questions?

Question 2: A learner takes a 5-question quiz worth 10 points each (50 total) with an 80% pass mark. How many questions must they get right to pass?

📓 Learning Journal

Keep your Learning Journal going — a note in your favorite app, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt: What pass mark feels right for your course, and why? Write down the threshold, the reasoning behind it (stakes, audience, any standard you must meet), and how you'll word your fail message so a learner who missed it feels encouraged to try again rather than defeated.

📝 Lesson Summary

🎓 Key Takeaways

  • A question pool holds a bank of questions; random draws give each learner a different, fairer quiz and make retakes meaningful.
  • Scoring is a set: decide the pass threshold first (based on stakes), then set points and attempts to serve it.
  • The results slide shows the live score and pass/fail — make it clear, humane, and correct, because its number is what gets recorded.
  • A scored quiz can report completion, score, and pass/fail via SCORM or xAPI — you set that up here and publish it in Lesson 15. Deep pooling has historically been a Classic strength, so check your current version.

🎉 What You've Accomplished

Your assessment is now more than a list of questions — it's a fair, randomized, scored system with a real pass mark and a results slide that reports out. You understand what an LMS will record and why the numbers have to be right before you publish. That's the last piece of the assessment puzzle, and it's the part that turns a quiz into something an organization can actually rely on.

❓ Common Questions at This Stage

How big should my question pool be?

Comfortably bigger than the number you draw. If you draw 5, a pool of 10–15 comparable questions gives real variety; a pool of exactly 5 isn't really random. Grow the pool over time as you think of good questions on the same objective.

Does the all-new Captivate do random pools as well as Classic?

Deep, flexible random pools have historically been a Captivate Classic strength, and the all-new tool has been closing the gap release by release. Check what your current version supports — for most courses it's plenty, but for heavy-duty pooling today, Classic may still be the safer choice.

What's the right pass score?

There isn't a universal one — it depends on your topic, audience, and any policy or regulation you must meet. Pick a defensible number for your course, set it before you tune points and attempts, and test both a pass and a fail before you publish.

🔭 Looking Ahead

In Lesson 14, we make sure everyone can actually take your course: accessibility as a first-class concern — WCAG and Section 508, alt text, keyboard and focus order, color contrast, and captions — including how to keep your new quizzes and results accessible to all.

✅ Before the Next Lesson

  • Finish your pool, pass mark, and results slide, and save the project
  • Preview a passing run and a failing run and confirm both read correctly
  • Write this lesson's journal prompt — your pass mark, your reasoning, and your fail message

📚 Additional Resources

🌟 Encouragement for the Journey

Pools, scoring, results, reporting — these were probably the words that sounded most intimidating on the course outline, and you just made them ordinary. That's real progress. Your assessments are now fair, reusable, and ready to prove that your course works. Take a breath and be proud — you've earned it.