Plan the source text, station labels, evidence slip, and teacher ledger together. A classroom escape room can finish with a teacher check rather than a lock. The useful result is a set of answers students can trace to the source.
Choose a modest reading goal
This original demonstration asks students to locate three stated quantities and cite the matching detail. It uses fictional club supplies, not a real inventory or a claim of curriculum mastery.
Use this exact authored source sheet:
The practice club has 2 paintbrushes. It has 4 drawing pads. It has 6 paperclips.
Number its sentences 1, 2, and 3. That gives teams a simple reference method. For actual teaching, replace the practice text with teacher-vetted material that fits the intended reading goal and learners. Recheck every station and answer after replacing it.
Sadlier's original activity planning post starts with lesson goals, describes independent tasks with different starting points, and offers a teacher or gatekeeper as an alternative finish. We adopt those planning ideas, not its downloadable puzzles, seven-task packet, or summed lock code. Sadlier's classroom escape room planning post
This packet needs no locked door, closed classroom, or countdown pressure. Offer a seated packet or paper rotation instead of requiring movement. The classroom activity and later discussion should work without an online display.
Make three independent task cards
Give every station the same instruction pattern: locate, record, and cite.
| Station | Student task |
|---|---|
| A | How many paintbrushes does the practice club have? Record the quantity and cite the sentence that supports it. |
| B | How many drawing pads does the practice club have? Record the quantity and cite the sentence that supports it. |
| C | How many paperclips does the practice club have? Record the quantity and cite the sentence that supports it. |
No station needs an answer from another station. A team can visit C, then A, then B. Its evidence slip still has fixed labeled rows A, B, and C.
Keep a separate visit-order field if it helps you manage the room. Visit order is a logistics record, not the final-code rule.
For a small practice group, roles might include reader, recorder, and evidence explainer, with an opportunity to switch. These are proposed participation options, not assigned student roles or proof that every learner contributed. Leave actual observations blank.
Give students an evidence slip, not just code boxes
The student packet should contain the source sheet, three task cards, directions, and blank slip:
| Station | Quantity as written | Source sentence/detail | Clue requested or used |
|---|---|---|---|
| A | Blank | Blank | Blank |
| B | Blank | Blank | Blank |
| C | Blank | Blank | Blank |
Add the direction: “Write the final code using A, then B, then C. Join the quantity strings; do not add them.”
Keep the teacher key out of this packet. The teacher's separate ledger records A as “2” with sentence 1, B as “4” with sentence 2, and C as “6” with sentence 3. Its expected final code is “246.”
Those filled values are teacher preparation, not completed student work. The article's worked example can show them for the adult reader; the student-print version must omit the worked answers, teacher ledger, and demonstration results.
Assemble strings in label order
A correct demonstration has A = “2,” B = “4,” and C = “6.” Concatenating those strings in A/B/C order produces “246.”
A team visiting C/A/B still produces “246.” A visit-order assembly would produce “624,” which is not the specified code. Point the team back to the labeled rows rather than asking it to repeat all three tasks.
Do not sum the answers to 12. That is an arithmetic result from the quantities, not this activity's code.
Keep code components as strings. If a future teacher-approved packet intentionally uses a component such as “02,” retain that leading zero and specify the component length in the revised key. Do not silently convert “02” to the number 2. The current fixture uses three one-digit components and has no leading-zero task.
The final-code field should remain incomplete until all labeled components are present and valid for the selected packet. A and B alone yield only a partial “24,” not a successful code.
Locate the station that needs another look
For the current fixture, stage A = “2,” B = “3,” and C = “6.” Its proposed code is “236.” The quantity comparison can identify B for recheck; it should retain the entered answer and point to station B.
A practical teacher clue is “Find the sentence about drawing pads.” Record that a clue was requested or used in B's slip row. Do not invent a score penalty or promise that a hint has no consequence under a school's assessment policy.
If all quantities are correct but an evidence field is empty, report the missing evidence. If evidence text is present, an online checker can detect its presence, but that alone does not show that the explanation is accurate.
Use separate outcomes: quantity mismatch, incomplete response, code matches, and teacher evidence review pending. A correct “246” with three nonempty explanations can be “Code matches; teacher evidence review pending.” The teacher still decides whether the cited details support the answers.
Do not describe a hidden browser answer panel as secure assessment storage. A client-side reading example is inspectable. Keep the authoritative teacher key separate from student distribution, and make the teacher's evidence check explicit.
Finish with a short explanation
Ask the team to explain which source detail supports B and why C/A/B visits still use an A/B/C code. This makes the activity's reading and ordering rules visible.
Then offer a revision question: “If the drawing-pad quantity changed, which station answer and code position would change?” The answer concerns B and the middle component, provided the new packet is reviewed and the other details stay the same.
Record actual explanations, clue use, and teacher acceptance only when observed. Completing the practice code does not establish a reading gain, assessment grade, or transfer to a different passage.
Before using the packet, proof the student and teacher outputs separately. Keep labels, source sentences, and blank evidence rows readable at the actual article width and on paper. At 360 pixels, stack the station records with repeated labels. The companion provides local quantity and completeness checks; paper output still needs a separate print check.
Copy this complete prompt
Create one complete, self-contained US-English HTML companion for “Practice Club · Evidence Escape”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Check quantities & completeness; Reset to blank; Load worked demonstration; Request station B clue; Select student text; Select teacher text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Prepare an original no-lock classroom escape room reading packet and optional local demonstration checker for “Escape Room Classroom Activity: Check the Evidence Before the Final Code.”
The primary artifacts are a teacher-vetted paper packet, blank team evidence slip, and separately distributed teacher answer ledger. This is a modest practice demonstration, not a claim of curriculum mastery, secure assessment, or learning improvement.
Use this exact original source text, with numbered sentences:
1. The practice club has 2 paintbrushes.
2. It has 4 drawing pads.
3. It has 6 paperclips.
Create independent task cards:
A asks the paintbrush quantity. B asks the drawing-pad quantity. C asks the paperclip quantity. Each asks students to record the quantity and cite the supporting sentence/detail. Any visit order is allowed. A team visiting C/A/B still fills labeled A/B/C rows.
The student packet includes source text, directions, task cards, and a blank slip with station, quantity string, supporting sentence/detail, and clue-request/use fields. It must exclude the teacher answer key, worked answers, and demonstration results.
The separate teacher ledger has A="2"/sentence1, B="4"/sentence2, C="6"/sentence3 and expected code "246". Include blank fields for actual teacher evidence review, observed clue use, and acceptance. Do not prefill real student responses or approvals.
Final code concatenates quantity STRINGS in A/B/C label order, not visit order and not a sum. For the current fixture require one ASCII digit per component after trimming outer whitespace; blanks, letters, decimals, or multiple digits are incomplete/invalid. Do not convert components to numbers. A future revised key can intentionally specify longer components such as "02"; preserve leading zeros and the reviewed component-length contract.
Demonstrate:
- A2/B4/C6 yields "246", including visits C/A/B.
- Visit-order "624" is not the specified final code.
- A2/B3/C6 yields "236" and identifies B for recheck.
- A2/B4 with C missing has partial "24" and cannot validate as complete.
- Correct quantities with blank evidence identify the missing evidence.
- Correct quantities and nonempty evidence report “Code matches; teacher evidence review pending,” not automatic educational success.
In the HTML demonstration, check station quantity/completeness separately and retain entries when a check fails. Evidence presence is not evidence quality; the actual teacher reviews supporting details. Changing a component or evidence clears stale check/review outcomes. Label demonstration state clearly and do not fabricate teacher acceptance.
Provide a proposed clue “Find the sentence about drawing pads” for B, with clue-use recording separate from answer correctness. Impose no invented penalty policy. A Reset clears demonstration entries, partial code, local clue-use/check states, and returns to the original source revision; it does not erase actual teacher paper records or imply saved online progress.
Keep student and teacher print outputs separate. A hidden client-side panel is not a secure answer key. No locked classroom, countdown, purchase, downloaded puzzle, saved student record, automated grade, network submission, or required room movement is part of this design. Provide seated and paper options plus an evidence/order debrief.
At the actual article width show three independent tasks, source text, A/B/C final-code rule, and the labeled adult worked example together. At 360 pixels and the actual narrow article container use stacked labeled records without page-level horizontal overflow. Any optional checker/clue/reset controls need keyboard access, focus, selected/status messages, and real local effects.
Before completion, proof source/key alignment, independence, visit-order invariance, string concatenation, incomplete/wrong/invalid states, evidence presence versus teacher review, clue records, reset, and separate student/teacher print content. Actual printing, implementation, rendered reference comparison, and classroom use remain pending until performed.
The teacher packet and private teacher key stay authoritative. Do not promise secure hidden answers, stored team progress, grading, or participant collection.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Escape Room Classroom Activity: Check the Evidence Before the Final Code
A team hands you the right code, but nobody can explain where one digit came from. Another team solved the tasks correctly and assembled its code in the order it visited the stations. Both problems begin in the instructions.
Plan the source text, station labels, evidence slip, and teacher ledger together. A classroom escape room can finish with a teacher check rather than a lock. The useful result is a set of answers students can trace to the source.
## Choose a modest reading goal
This original demonstration asks students to locate three stated quantities and cite the matching detail. It uses fictional club supplies, not a real inventory or a claim of curriculum mastery.
Use this exact authored source sheet:
> The practice club has 2 paintbrushes. It has 4 drawing pads. It has 6 paperclips.
Number its sentences 1, 2, and 3. That gives teams a simple reference method. For actual teaching, replace the practice text with teacher-vetted material that fits the intended reading goal and learners. Recheck every station and answer after replacing it.
Sadlier's original activity planning post starts with lesson goals, describes independent tasks with different starting points, and offers a teacher or gatekeeper as an alternative finish. We adopt those planning ideas, not its downloadable puzzles, seven-task packet, or summed lock code. [Sadlier's classroom escape room planning post](https://www.sadlier.com/school/ela-blog/classroom-escape-room-printables-for-escape-room-classroom-activity)
This packet needs no locked door, closed classroom, or countdown pressure. Offer a seated packet or paper rotation instead of requiring movement. The classroom activity and later discussion should work without an online display.
## Make three independent task cards
Give every station the same instruction pattern: locate, record, and cite.
| Station | Student task |
| --- | --- |
| A | How many paintbrushes does the practice club have? Record the quantity and cite the sentence that supports it. |
| B | How many drawing pads does the practice club have? Record the quantity and cite the sentence that supports it. |
| C | How many paperclips does the practice club have? Record the quantity and cite the sentence that supports it. |
No station needs an answer from another station. A team can visit C, then A, then B. Its evidence slip still has fixed labeled rows A, B, and C.
Keep a separate visit-order field if it helps you manage the room. Visit order is a logistics record, not the final-code rule.
For a small practice group, roles might include reader, recorder, and evidence explainer, with an opportunity to switch. These are proposed participation options, not assigned student roles or proof that every learner contributed. Leave actual observations blank.
## Give students an evidence slip, not just code boxes
The student packet should contain the source sheet, three task cards, directions, and blank slip:
| Station | Quantity as written | Source sentence/detail | Clue requested or used |
| --- | --- | --- | --- |
| A | Blank | Blank | Blank |
| B | Blank | Blank | Blank |
| C | Blank | Blank | Blank |
Add the direction: “Write the final code using A, then B, then C. Join the quantity strings; do not add them.”
Keep the teacher key out of this packet. The teacher's separate ledger records A as “2” with sentence 1, B as “4” with sentence 2, and C as “6” with sentence 3. Its expected final code is “246.”
Those filled values are teacher preparation, not completed student work. The article's worked example can show them for the adult reader; the student-print version must omit the worked answers, teacher ledger, and demonstration results.
## Assemble strings in label order
A correct demonstration has A = “2,” B = “4,” and C = “6.” Concatenating those strings in A/B/C order produces “246.”
A team visiting C/A/B still produces “246.” A visit-order assembly would produce “624,” which is not the specified code. Point the team back to the labeled rows rather than asking it to repeat all three tasks.
Do not sum the answers to 12. That is an arithmetic result from the quantities, not this activity's code.
Keep code components as strings. If a future teacher-approved packet intentionally uses a component such as “02,” retain that leading zero and specify the component length in the revised key. Do not silently convert “02” to the number 2. The current fixture uses three one-digit components and has no leading-zero task.
The final-code field should remain incomplete until all labeled components are present and valid for the selected packet. A and B alone yield only a partial “24,” not a successful code.
## Locate the station that needs another look
For the current fixture, stage A = “2,” B = “3,” and C = “6.” Its proposed code is “236.” The quantity comparison can identify B for recheck; it should retain the entered answer and point to station B.
A practical teacher clue is “Find the sentence about drawing pads.” Record that a clue was requested or used in B's slip row. Do not invent a score penalty or promise that a hint has no consequence under a school's assessment policy.
If all quantities are correct but an evidence field is empty, report the missing evidence. If evidence text is present, an online checker can detect its presence, but that alone does not show that the explanation is accurate.
Use separate outcomes: quantity mismatch, incomplete response, code matches, and teacher evidence review pending. A correct “246” with three nonempty explanations can be “Code matches; teacher evidence review pending.” The teacher still decides whether the cited details support the answers.
Do not describe a hidden browser answer panel as secure assessment storage. A client-side reading example is inspectable. Keep the authoritative teacher key separate from student distribution, and make the teacher's evidence check explicit.
## Finish with a short explanation
Ask the team to explain which source detail supports B and why C/A/B visits still use an A/B/C code. This makes the activity's reading and ordering rules visible.
Then offer a revision question: “If the drawing-pad quantity changed, which station answer and code position would change?” The answer concerns B and the middle component, provided the new packet is reviewed and the other details stay the same.
Record actual explanations, clue use, and teacher acceptance only when observed. Completing the practice code does not establish a reading gain, assessment grade, or transfer to a different passage.
Before using the packet, proof the student and teacher outputs separately. Keep labels, source sentences, and blank evidence rows readable at the actual article width and on paper. At 360 pixels, stack the station records with repeated labels. The companion provides local quantity and completeness checks; paper output still needs a separate print check.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Keep the prepared instructions with the source
Use the companion’s instruction copy for the preparation review. Keep the source revision, station labels, and final-code directions together, and review what belongs in the student copy before distributing it. Maintain the teacher key separately.