Core Concepts

Scene Progression

6 min readUpdated

Control what happens automatically when a student gets a scene right — stay put, advance to the next scene, or jump to a scene you choose.

Every scene can do something on its own when the student gets it right. That is what Progression controls.

You find Progression in a scene's settings panel, in the Progression section. A closing scene is the one exception: nothing follows an ending, so there is no progression to set on it.

The Lesson Graph draws the same setting as an arrow between two scene cards, and clicking that arrow opens these exact controls — it is one setting shown in two places, not two independent ones.

The progression you have configured is also summarized at the top of the canvas in the Scene info strip — Manual Scene Flow, Automatically flows to <scene>, or Flow decided by a router. The destination name in the strip is clickable, so you can jump to a scene's flow target without leaving the canvas.

When a scene is set to flow to the next scene but there is no next scene yet, the strip shows a + Add next scene button instead of a destination — click it to create the next scene. The new scene is added to your scene list but the canvas stays on the scene you are working on, so a quick click to wire up your flow never pulls you away from what you are building. Open the new scene from the scene panel whenever you are ready to work on it. If your lesson has a layout, Berdee first asks which layout the new scene should use. Choosing Create new layout there is the one exception to staying put: it opens the new layout so you can design it.

The modes

Stay

The scene's widgets handle navigation themselves. A Submit button or a regular button you place on the scene is what moves the student forward. That includes widgets on the scene's applied layout: a "Next" button on a layout navigates from whichever scene the student is currently viewing, so one shared button serves every scene that uses the layout.

Use Stay when you want the student to control the pace — for example, a scene that shows feedback after submission and has a "Next" button the student clicks when they are ready.

Next (auto)

When the student gets the scene correct, Berdee automatically moves them to the next scene in your scene list. This is the default for new scenes — you do not have to pick a destination by hand, and reordering scenes "just works" because the destination is resolved at runtime.

Use this for a clean checkpoint flow: the student answers, submits, sees brief feedback, and is carried to the next step without needing to click a separate navigation button.

"Correct" needs something to answer. A scene whose only scoring comes from a scored button never auto-advances — pressing it earns points but doesn't move the student on. Give that scene a Continue button with a navigate action.

The same goes for a scene whose only questions have Scoring turned off, like a practice warm-up. Those questions still know the right answer, but they don't make the scene "correct", so a right answer never moves the student on. Give the scene a Next button. _Example: Make some questions count more, and one not at all builds a warm-up like this._

_Example: A five-question vocabulary check where each scene advances automatically on a correct answer, so students feel momentum through the activity._

If there is no next scene to advance to, that is fine — Berdee simply keeps the student on the scene, and your Lesson-submit button ends the attempt. It never blocks publishing or assigning. You will see a non-blocking flow warning, Last Scene Has Nowhere To Advance, in the validation pill so you can tell a deliberate ending from a link you forgot to set; switch the scene to Stay if you want the warning to go away.

**The last scene of the lesson flows into the closing scene.** There is no next scene to advance to, so Berdee carries the student to the lesson's ending instead — which finishes the lesson and locks their answers. A straight-through lesson therefore needs nothing wired by hand to reach its ending; the scene info strip shows the ending's name as that scene's destination. If your lesson has several endings, this default flow goes to the first one in the scene list.

Specific scene

When the student gets the scene correct, Berdee moves them to the exact scene you pick. Use this when the next step is not the next scene in the list — for example, jumping to a feedback scene, an extension activity, or a recap scene at the end of a section.

A closing scene is a destination like any other, so this is also how you send a branch to a specific ending. _Example: a challenge round whose Progression points at your Mastered ending, while the rest of the lesson flows into the default one._

Random scene (existing lessons only)

Some older lessons send the student to a randomly chosen scene on a correct answer. You can't choose this mode for a scene that doesn't already use it, but a scene that does keeps working for students, and you can still edit it:

  • Pool — which scenes are eligible: any of them (repeats are possible), Only unvisited scenes (never repeats a scene the student has already seen), or Unvisited or previously incorrect (also lets a scene the student got wrong come back around).
  • Fallback scene — where to send the student if the pool ever runs empty (for example, "only unvisited" once every scene has been seen). If you leave this unset, Berdee simply does not navigate when the pool is empty, so set a fallback whenever running dry is a real possibility.

Router

Instead of a fixed destination, a router decides where the student goes — by score, by variables, or by how many times they've been through. The Router mode appears once your lesson has at least one router (create them from the Lesson Graph — click the orange dot on a scene's right edge and choose A router, or use Add router in the + Add scene menu above the graph).

_Example: After a quiz, passing students continue forward while struggling students are routed to a review scene._

How "correct" is decided

When a scene has one scorable widget (a multiple-choice question, a fill-in-the-blank, etc.), that widget's correctness is all that matters.

When a scene has two or more scorable widgets, you choose the rule:

  • All correct — every answer on the scene must be right.
  • Cumulative — the student's combined score reaches the Passing % you set. The Passing % field appears right under the rule when you choose Cumulative. A Lesson Graph They answer wrong path from that scene then means "below the Passing %". _Example: Move on when students get four of five right._
  • Specific — only the widgets you select need to be correct. Useful when some widgets are practice and only the main question should count.

When the check happens

  • Continuously _(default for non-Stay scenes)_ — Berdee checks as soon as the student's answer becomes correct, without waiting for Submit. This is the right choice for most auto-advance flows because the scene moves on the moment the student succeeds.
  • Submit — Berdee checks correctness only when the student clicks a Submit button. Use this for quiz-style scenes where the student should review answers and confirm before advancing. Required when you use the Cumulative correctness rule.

The celebration delay

After Berdee decides the student is correct, there is a short pause (600 ms by default) before navigation. This gives the student a moment to see their success — the correct-answer celebration plays during this window.

You can adjust the delay in scene settings. Students who have enabled reduced motion in their device or browser settings will experience a shorter pause automatically.

Accessibility

Screen readers announce _"Correct! Moving on."_ before the page changes. The celebration delay gives assistive technology enough time to read this message before the new scene loads.

Learn by doing

Was this article helpful?