A branching lesson lets different learners take different paths through the same lesson. You can skip pages a learner already knows, send someone who misses a question back to review, let learners choose where to go, or end the lesson early with a pass or a fail.
Branching lessons are still experimental, so some features may be missing or change.
This article is about branching between the pages of a lesson. To build a role-play or decision scenario inside a single tile, see "Branching scenarios".
How a branching lesson is different
In a regular (linear) lesson, learners move through the pages in the order of your page list.
In a branching lesson, pages are joined into runs. A run is a chain of pages that learners go through in order. At the end of a run, learners go wherever you've connected it: another run, a node that makes a decision, or an ending. You see and edit those connections on the branching canvas.
What learners see in the sidebar
This is the part that surprises authors most. A learner's sidebar doesn't list every page in the lesson. It lists:
The pages they've visited on their path so far.
The pages and screens ahead on their path, up to the next decision point.
More pages ahead, when what comes next depends on a decision they haven't made yet, like a question they haven't answered.
Pages on branches the learner hasn't reached, or won't reach, stay hidden. This is expected: a learner who tests out of a section never sees its pages, and a learner sent to review only sees the review pages.
The same goes for Find in lesson. Learners can search the pages they can open. Matches on pages ahead are counted ("3 more matches in pages you have not reached yet") but not shown.
When you preview your lesson you see what a learner would see, so pages off your path won't be in the sidebar either. To check a specific path, use Preview from this node (see "Previewing a path").
Turning a lesson into a branching lesson
Open your lesson in the Editor.
In the bar at the top left, next to the lesson title, click the Branching icon (beside Storyboard and Editor).
In Switch to the branching editor?, click Switch to branching to confirm.
Things to know:
Switching can't be undone, and it clears your undo history. Your pages stay in the same order, chained into a single run, so learners see no difference until you add a branch.
A lesson also switches to branching when you add an Assessment.
In translated copies of a lesson you can't convert it or change its branching. Set up branching in the main language.
You can also ask the Mindsmith Agent to do it, for example "Let learners who get the first question right skip the review pages."
The branching canvas
Click the Branching icon to open the canvas, a map of your whole lesson.
What's on the canvas
Pages cards (green) show a run of pages as small thumbnails, with the page count in the header. Each card has a Next row for where the run goes when learners click Continue, plus a row for each button on the run's last page.
Node cards are decision and activity points (see "Node types").
Lines show where each exit leads. Lines are drawn around cards so they don't cross over them. A line that loops back to an earlier point is highlighted so you can spot loops.
The start of the lesson is marked. To change it, open a card's menu and choose Make Start Node. A logic node can't be the start.
Moving around
The toolbar in the bottom-left corner has:
Zoom In and Zoom Out: click to zoom a step, or press and hold to keep zooming. The current zoom shows between them.
Tidy layout (network icon): rearranges all the cards into neat columns flowing from the start. It only moves cards. It never changes your connections or content, and you can undo it.
Move Mode and Selection Mode change what dragging the empty canvas does. In Move Mode it moves you around the canvas. In Selection Mode it draws a box that selects several cards at once. In both modes you can drag a card to move it.
You can also pinch or Ctrl/Cmd + scroll to zoom, scroll with a trackpad to pan, or drag with the middle mouse button.
Working with pages on the canvas
Add a page to the end of a run with the New Page button on its card.
Reorder pages in a run by dragging the handle. Drag a page onto another run to move it there, or onto empty canvas to make it a run of its own.
Split a run in two with the scissors button between two pages.
Merge two runs: hover over the Next line between them and click Merge. This works when the second run has only one way in.
Edit a page: click it. The Editor opens that page with its run in the page list. (Double-clicking the card opens the run's first page.)
Adding and connecting nodes
Click the dot on the right edge of a card's exit row, or drag a line out of it and drop it on empty canvas.
In the menu, choose:
New: add a new node or Pages card, already connected.
Existing…: search for a page or node to connect to.
An ending: Complete, Fail, or Back to start.
Disconnect: remove the connection.
To connect to something already on the canvas, drag the line onto it.
To remove a line, hover over it and click the trash icon. You can also add nodes with Add Node in the Agent bar at the bottom of the screen.
When you delete a card, anything that led into it is reconnected to wherever it led. You can copy, cut, and paste cards.
Node types
Node | What learners see | Where it can lead |
|---|---|---|
Pages | Your lesson pages | Its Next route, plus a route per button on its last page |
Logic | Nothing; it decides silently | A route per condition, plus Default |
Assessment | A scored set of questions, with an optional time limit | Next, or separate Passed and Failed routes |
Choice | A screen of options to pick from | A route per option |
Modal | A pop-up with text and buttons | A route per button |
Explore | Clickable areas, points, or text | A route per area |
Video | A video | One route, when the video ends |
Code | An interactive code activity | A route when finished, plus any extra exits |
Use a logic node whenever the path should depend on how a learner answered. Use a choice node only when you want learners to pick their own path on purpose.
Assessments are covered in their own article, "Assessments".
Logic nodes
Logic nodes are the brains of a branching lesson: they hold the rules that decide which path each learner takes. A logic node checks earlier answers and sends each learner down the first path that matches. Learners never see it.
Setting one up
Connect it into the path. Add a logic node and connect the run that leads to it, for example from that run's Next. A logic node can only check what comes before it on the path: the questions and Assessment results on the pages that lead into it. It can't check pages that come after it or pages on a different branch.
Add conditions. Open the logic node. Each row is one condition, for example:
Question 3 Is Incorrect
Question 1 Is "Manager" (a specific answer option)
The safety Assessment Score at least 80%
Click Add condition for more rows. Drag rows to reorder them.
Connect each condition on the canvas to where those learners should go, and connect Default for everyone else.
How it decides
The most important thing to remember: a logic node checks its conditions in order, from top to bottom, and sends the learner down the first one that matches. It stops checking there, so a later condition never gets a say for that learner. Put the most specific conditions first.
Default catches everyone else, including learners who haven't answered a question the node checks. Always connect Default. If it isn't connected, learners who match nothing finish the lesson there. The editor warns you about this.
Correct and Incorrect need a graded question. Short Answer, Ranking, and Matching questions can only be checked for correct or incorrect.
For Assessments, conditions use the learner's best attempt, and you can check one topic's score in place of the overall score.
Routing from buttons
You can send learners somewhere straight from a button, without a separate node.
Add a Buttons tile to the last page of a run.
Open the Branching canvas. Each button shows up as its own exit row on that run's card, labeled with its text.
Drag a line from the button's dot to where it should lead, or click the dot and pick a destination from the menu.
A button you haven't connected follows the run's Next route.
Endings
Any exit can end the lesson:
Complete: ends the lesson normally. It doesn't force a pass: whether the learner passes still depends on their score and your passing settings.
Fail: ends the lesson as not passed, whatever the learner's score. You rarely need it. With LMS Reporting Mode set to Passed/Failed/Incomplete, your LMS gets "failed". With Complete/Incomplete, it gets "incomplete".
Back to start: learners go back to the start of the lesson. Their answers are kept.
If a run's Next isn't connected and none of its buttons are, learners who finish it complete the lesson.
The page list (filmstrip) in a branching lesson
In the Editor, the page list on the left works a little differently for branching lessons:
It shows one run at a time: the run that holds the page you're editing.
Rows above and below the run list its parents (what leads in) and children (where it leads). Click one to jump there.
A logic node in the list opens a summary of its conditions and where each one goes.
Use the Branching view to see the whole lesson at once.
Navigation for learners
Back retraces the learner's own path, skipping logic nodes, not the order of your page list.
With restricted navigation, pages ahead on the sidebar are locked until the learner reaches them ("Complete previous pages to unlock this page").
Navigation Freedom in lesson Settings controls whether learners can jump around. Required narration always uses restricted navigation.
Previewing a path
Preview in the top bar starts the lesson from the start, like a learner.
Preview from this node (the play button on a canvas card) starts at that page or node, so you can check one branch without clicking through the whole lesson.
In preview, clicking a locked page offers an author-only Skip that jumps straight there.
Branching lessons in courses
All routes stay inside one lesson. A Complete, Fail, or the end of a run finishes that lesson, and the course decides what comes next.
Learners get the same path-based sidebar for each lesson in the course.
The lesson score only counts questions on the learner's path.
Analytics
Filter by branch in Analytics shows results for the learners who took a particular path: an answer to a routing question, a wired button, or an Assessment's Passed or Failed. Pick several to combine them. The filter only covers identified learners and also applies to exports.
In Engagement, a page nobody has reached shows Not reached yet. Otherwise it shows the share of learners who reached it.
Examples
Test out of topics with an Assessment
A placement Assessment at the start lets learners skip the topics they already know. Tag the Assessment's questions with topics (here, Safety and Equipment), then add one logic node per topic. Each one checks that topic's score: learners who scored at least 80% skip ahead, and everyone else (Default) goes through that topic's pages first. Both paths meet at the next logic node, so each topic is decided on its own.
Review what learners got wrong
After a short knowledge check, send anyone who missed a question to a review section, and let learners who got everything right skip it. One logic node does it: add a condition per question (Is Incorrect) and connect all of them to the same review pages. Default catches the learners who got everything right and sends them straight to the wrap-up. The review pages then lead into the wrap-up too.
Different paths by role that meet again
Ask learners their role on the first page with one button per role, and wire each button on the canvas to that role's pages. Both role paths then lead to the same pages, so everyone finishes with the shared policy and the final Assessment.
Troubleshooting
"My pages disappeared from the sidebar." Learners (and previews) only see the path they're on. Check the Branching canvas to see where each page sits, and use Preview from this node to check a branch.
A page is never shown. Nothing leads to its run. Connect an exit to it on the canvas.
Learners get stuck or the lesson ends early at a logic node. Connect its Default route, and check that the questions it uses come before it on every path.
Tips
Sketch the paths first. Decide who should see what before you start wiring.
Use Tidy layout after big changes to make the map readable again.
Preview every branch with Preview from this node before you share the lesson.
Ask the Mindsmith Agent to set up common patterns, like "add a test-out question that skips the next three pages for learners who get it right."












