Widget Library

Check Answers

5 min readUpdated

Add a Check Answers button to grade and lock a scene's answers, or turn any button into one. The lesson itself finishes when students reach its ending.

A Check Answers button is how a student says "I'm done with this scene, check my work." When they press it, Berdee grades every question on the scene, locks their answers so they can't change them, and saves the results.

It isn't a special widget. It's an ordinary Button that already has the Check their answers behavior on it, so it has every setting a button has: label, colors, outline, size, and any other behaviors you add.

Add one

Open Basic in the toolbox and choose Check Answers. Berdee drops a button labeled "Check answers" onto the scene, already wired to check this scene's answers. Rename the label to whatever fits: "I'm done", "Check my work", "Did I get it?".

Turn any button into one

Any button can check answers. Select it, open ⚡ Behaviors (see Guided Behaviors), and choose Check their answers. The button now grades the scene when pressed, alongside anything else it already does.

_Example: a "Next" button that should also grade the scene: add Check their answers to it, and one press checks the answers and moves the student on._

Berdee only offers Check their answers on a scene that has a question on it. If the scene has nothing to grade, it tells you to add a question first.

What it checks

A Check Answers button always checks this scene's answers:

  1. Every question on the scene is graded against the correct answer you set. A question the student skipped counts as 0 and locks with the rest; one hidden from them at that moment isn't counted.
  2. The answers lock. If the student comes back to the scene later, they see the answers they gave, read-only.
  3. The scene is checked against its correctness rule. All correct by default, Cumulative (the combined score reaches the scene's Passing %), or Specific (only the questions you picked). See How "correct" is decided.
  4. A checkpoint is saved. The attempt stays open; the gradebook shows a score once the student reaches the ending. The attempt page's Answers so far shows what reached the server in the meantime.

You can put more than one Check Answers button on a scene; each one checks the same answers.

A Check Answers button is never worth points itself. It's the control that grades, not a question.

The lesson finishes at the ending, not on a button

A Check Answers button never finishes the lesson. A lesson is finished when the student reaches its ending, the Closing Scene. That's when the final score goes to the gradebook and every answer locks.

So the one thing every lesson needs is a way to get there: the last scene should lead to the ending, with a Next or Done button that goes to the ending, or a graded scene that moves on by itself once it's answered. If nothing leads to the ending, publishing stops with Students Can't Reach the Ending and names the scenes where students get stuck.

When to use one

A Check Answers button is optional. Reaching the ending grades everything the student visited, so a scene with scoring turned on doesn't need one. Add one when you want to:

  • Show feedback before the student moves on. Some widgets show their right and wrong styling only after the scene is checked.
  • Move the student on only after they check. Set the scene's Progression to a destination and its Evaluate on to Submit. New scenes start on Continuous, which moves the student on the moment their answers are right, without waiting for the button. See Progression waits for the button only when you ask it to.
  • Branch on the result. Send students who didn't pass the scene to a review (see below).
  • Save a checkpoint mid-lesson. If a student leaves partway through, a checked scene's answers have already reached the server.
  • Drive a random-scene pick that replays missed scenes (Scene Progression). The picker knows a scene was missed only after it's checked.

Wrong-answer and score paths

In the Lesson Graph, the paths They answer wrong ("If this scene is not passed…") and the score paths hang on the scene's Check Answers button: any button that checks this scene's answers. When the student presses it, Berdee grades the scene and sends them down the path that matches the result.

Lead a wrong-answer path forward, to a review scene that then continues, rather than back to the question: the student's answers locked when they pressed the button, so a student sent back can't change them. Step-by-step: Show an explanation when a student gets it wrong.

Progression waits for the button only when you ask it to

A scene's Evaluate on setting decides when Berdee checks whether the scene is correct:

  • Continuous _(the default for new scenes)_: checked every time an answer changes. The student moves on the moment their answers are right, whether or not they press Check Answers. The button still grades and locks the answers, but it isn't what moves the student.
  • Submit: checked only when the student presses a Check Answers button. Choose this when the button should be the moment the student moves on.

Common mistakes

  • Expecting the button to finish the lesson. It checks the scene. The lesson finishes at the ending, so make sure the last scene leads there.
  • Expecting it to control when the scene moves on while Evaluate on is Continuous. Set it to Submit.
  • Adding Try Again to a checked scene. Reset never clears a checked answer. For practice students can redo, skip Check Answers: a button that shows a message based on whether each question Is correct, plus a "Start over" button wired to reset answers. Let students check their work and start over builds one.
  • Putting it on the ending. The ending can't grade anything, because the lesson is already graded by the time the student arrives. Berdee warns about it.

Coming from the old Submit Button?

The Submit Button widget is retired, and Check Answers takes its place in the toolbox. You don't need to rebuild anything:

  • Your Submit buttons were converted automatically the next time the lesson opened. A Submit button that checked the current scene is now a Check Answers button.
  • A Submit button that finished the whole lesson ("Submit Lesson") now checks its scene and then goes to the ending, so pressing it still ends the lesson the way students expect.
  • Publishing no longer asks for a Submit button. A lesson with nothing to grade can be published and assigned as long as students can reach the ending. See Publishing an activity with nothing to grade.
  • Lessons already assigned to students keep working exactly as before, Submit buttons included. The change reaches students when you next open, save and push or publish the lesson.

Learn by doing

Was this article helpful?