How to Use Exit Tickets in a Self-Paced Online Course: Turn Responses Into Next Steps

In a self-paced course, plan what happens after an exit ticket before writing the questions. A learner finishing on Tuesday evening needs usable instructions then—not simply a submission receipt while the teacher waits for everyone else.

NWEA’s October 8, 2026 explainer describes exit tickets as brief formative checks that inform the next instructional move. The workflow below is SubSchool’s editorial adaptation for asynchronous teaching, not an asynchronous method validated by that article. Its organizing principle is simple: connect each response pattern to a learner action and, where needed, a teacher-review deadline.

1. Put the check at a learning boundary

For this workflow, an asynchronous exit ticket is a short learning check completed after a defined lesson segment. Place it after instruction and initial practice, but before the ticket’s answer explanation. Learners should attempt the question before seeing its solution.

Keep three records separate: lesson completion, ticket submission, and evidence of understanding. Watching a video records an activity; submitting a ticket records participation; the answer and reasoning provide evidence about the selected objective. Do not label all three as mastery.

Tell learners what to use, what to submit, and what happens afterward. For example: “Use the lesson notes, but attempt the question before opening the answer explanation. Submit an answer and a short explanation. Then follow the comparison guide. If your response needs review, your teacher will reply within the stated review window.”

2. Choose one objective and define the evidence

Replace a broad goal such as “understand equations” with something observable: “Solve a two-step linear equation and explain how inverse operations preserve equality.” Then write the evidence you expect before drafting the ticket.

For this objective, sufficient evidence might include a correct solution, valid operations on both sides, and an explanation of why the first operation removes the added constant. A correct number without reasoning leaves part of the objective unchecked.

Decide what counts as an acceptable alternative, too. A learner might use a valid method different from your worked example. Route unfamiliar but plausible reasoning to teacher review rather than treating a mismatch with the model wording as an error.

3. Write a compact ticket

Use two required components and one optional component:

1. Application: Ask learners to apply the selected idea to a new example.
2. Reasoning: Ask why a step, choice, or conclusion is justified.
3. Uncertainty: Invite learners to name anything they would like checked.

Use uncertainty to invite support, not to override the academic evidence. A confident response still needs checking; an uncertain learner may have a sound explanation. Likewise, avoid replacing the application question with “Did you understand?” That does not supply the evidence specified in the decision sheet.

Keep the ticket focused enough that you can name a useful next step for each likely response. If it checks several unrelated objectives, split it into smaller checks at appropriate lesson boundaries.

4. Prepare immediate feedback without implying automatic branching

Write a post-submission feedback panel before release. It should contain an answer explanation, comparison criteria, and a small menu of next steps. Where your course setup supports it, show this after submission. Otherwise, provide clearly labeled instructions for opening it after the attempt.

A submission receipt should say only that the response was received. Reserve judgments about understanding for the evidence check. For open responses, give learners comparison criteria without presenting self-comparison as a final teacher judgment.

Use wording such as: “Compare your answer and explanation with the criteria below. Choose the matching next step. If you cannot tell which applies, request review.” Explain which activities learners may complete while waiting and which prerequisite-dependent work should wait for feedback.

The routing table below is a manual planning tool. A teacher can assign routes, or learners can use a teacher-approved comparison guide. It does not assume that SubSchool automatically branches lessons or classifies responses.

Manual response-routing table

5. Copy and edit this exit-ticket decision sheet

Copy this table into a document or spreadsheet and replace the placeholders. The worked column is an original example for a lesson on two-step equations. Set the review deadline to match your actual teaching capacity; the example window is not a recommended universal standard.

How the example becomes an action

A response showing x = 5 and explaining equal subtraction matches the stated evidence. The feedback can direct that learner to the next lesson without making a broader claim about lasting mastery.

A response showing x = 5 but no explanation receives a specific request: “Explain why subtracting 4 from both sides keeps the equation balanced.” Do not assign an entire remedial lesson when the missing evidence is one explanation.

A response showing 3x = 23 suggests that the learner added 4 rather than removed it. Direct the learner to the inverse-operations explanation, then offer the new practice item, 2x + 5 = 17. Its solution is x = 6. Ask for the steps as well as the answer.

If the same error appears again, route the response to teacher review. If the learner uses a different valid method, review its logic rather than insisting on the example’s sequence.

6. Give teacher review a queue and a deadline

Use a review queue with a learner identifier, lesson, submission time, reason for review, next step already offered, deadline, and status. Keep it in your approved teaching workspace. For external drafting tools, use fictional or anonymized lesson examples rather than identifiable learner responses.

Prioritize responses blocking prerequisite-dependent work, explicit requests for help, and corrections that still do not meet the criteria. Publish a response window you can maintain. If review is delayed, tell learners when to expect feedback and what they can do meanwhile.

Close the loop with an instructional decision: proceed, clarify, practice, or discuss. Preserve the original response alongside the revision so that the review records what changed. If several learners produce the same misunderstanding, inspect the explanation and prompt as well as their answers.

7. Check the workflow before release

• Does the ticket check one stated objective rather than completion?
• Are the expected evidence and acceptable alternatives written down?
• Can learners attempt it before seeing its answer explanation?
• Does every route name a concrete action or lesson section?
• Are ambiguous answers and repeated errors sent to human review?
• Are the review window and waiting activities visible?
• Have you tested the instructions with correct, incomplete, and incorrect sample responses?

Start with one lesson and review how the routes work before applying the sheet across a course. Adjust unclear prompts and unhelpful next steps rather than adding more questions by default.

For the targeted-practice step, SubSchool’s AI homework generator creates editable practice from lesson context or source material, with answer expectations. Explore the AI homework generator feature to support preparation, then check every task against your objective. Teachers retain authorship and the final decision about feedback, review, and progression.