Classroom workflows

Use practical recipes for common middle-school teaching needs.

Best for

Middle-school teacher

Typical use

5-20 minutes per recipe

Chapter 13 of 24 · Verified 2026-08-16

These recipes turn common middle-school needs into short, repeatable AlloFlow workflows. They are starting points, not scripts. Keep the learning target constant while you vary access, practice, and expression.

Button names can differ slightly by deployment. If you cannot find a surface, press ? to turn on Help Mode, use Help Search, or return to the Launch Pad and choose Guided Mode, Learning Tools, or Educator Tools.

Before students use any generated material, complete the review steps in Prepare a lesson and the access checks in Accessibility and UDL.

Recipe 1: Make a complex text approachable without changing the target

Use when: Students need different entry points to the same article, passage, primary source, or teacher-created explanation.

Typical preparation: 10-20 minutes after the source is ready.

Build it

1. Open Guided Mode and add the source under Source Material.
2. State the common learning target. Identify any wording, quotation, or technical vocabulary students must encounter in the original.
3. Analyze the source, then use Text Adaptation to generate an adapted text or a smaller chunked version.
4. Add one representation support, such as a glossary, visual organizer, worked example, bilingual view, or read-aloud option.
5. Compare every version with the source. Restore missing facts, qualifiers, evidence, and discipline-specific terms.
6. Add directions that name the same thinking task for everyone.
7. Preview the student view and test the keyboard, zoom, read-aloud, and response route.

What students experience

Students can enter through a version or support that reduces a barrier, but they still work toward the same essential understanding. Give students a route back to the original text for quotation, evidence, or productive challenge.

Teacher check

Ask, “Did I reduce unnecessary language load, or did I reduce the idea?” If the central concept or evidence changed, revise before sharing.

Recipe 2: Support a multilingual learner or newcomer

Use when: A student benefits from home-language access while building English vocabulary and participation.

Typical preparation: 10-15 minutes plus fluent review when available.

Build it

1. Add a short, accurate source rather than an entire unit at once.
2. Set the output language, translations, and grade level in Universal Settings before you generate.
3. Generate a bilingual view, glossary, sentence frames, or translated directions.
4. Keep names, formulas, quotations, cognates, and essential academic terms visible in both languages.
5. Ask a fluent colleague, interpreter, family liaison, or qualified reviewer to check high-stakes wording when possible.
6. Offer more than one response mode: selected response, labeled diagram, short writing, oral response, or AAC-supported response.
7. Pair language support with a clear content model. Do not make translation the only scaffold.

What students experience

The student can use the home language to access meaning while seeing and practicing the English terms needed for class participation.

Teacher check

Do not treat machine-translated wording as proof of language proficiency or use translation quality as part of the student’s content grade. Confer when a response appears inconsistent across languages.

Recipe 3: Provide age-respectful word and sound practice

Use when: A middle-school learner needs targeted phonemic awareness, phonics, syllable, spelling, or handwriting practice without elementary-looking materials.

Typical preparation: 5-10 minutes.

Build it

1. Open Learning Tools and locate Word Sounds Studio.
2. Choose one narrow skill connected to current reading or writing, such as a sound contrast, syllable pattern, spelling pattern, or focus word set.
3. Select a short practice activity and preview every item.
4. Remove words that are culturally confusing, ambiguous, or unrelated to the learner’s instruction.
5. Turn on visual, audio, pacing, or AAC supports that the learner already uses.
6. Use a small number of trials, then finish with a word or sentence from class content.

What students experience

The learner receives focused practice with immediate interaction and a visible connection to grade-level work.

Teacher check

Use performance to plan instruction, not to diagnose a reading disorder or replace a validated assessment. Coordinate sustained intervention with the reading specialist, special educator, or other responsible team member.

Recipe 4: Move from source annotation to evidence-based writing

Use when: Students can discuss a text but need support selecting evidence, organizing a claim, or explaining reasoning.

Typical preparation: 15-25 minutes.

Build it

1. Add the source and create a focused question rather than a broad “write about” prompt.
2. Use the Annotation tools to model one purposeful highlight or note. Give each annotation color a meaning only if that convention helps students.
3. Generate a visual organizer, DBQ scaffold, or writing scaffold aligned to claim, evidence, and reasoning.
4. Add sentence starters as optional supports, not required prose that every student must copy.
5. Provide a brief model and a non-example. Ask students what makes the evidence relevant.
6. Let students draft in an approved space. Use AI feedback, if enabled, as a suggestion source rather than an automatic grade.
7. Require a final source check: every quotation, paraphrase, and citation must match the source.

What students experience

Students move from selecting evidence to explaining why it matters. They may type, dictate, record, draw and label, or use another approved expression route when that route measures the target.

Teacher check

Read the final work. Generated feedback can miss nuance, reward formulaic writing, or invent a source detail. Students should be able to explain their own claim and revision.

Recipe 5: Run a low-stakes formative check

Use when: You need one clear decision before moving on.

Typical preparation: 5-10 minutes.

Build it

1. Write the decision first: “If many students confuse mass and weight, I will model one comparison.”
2. Create one to three questions through Quiz, Exit Ticket, Polling, Concept Sort, or another short activity.
3. Make the distractors plausible and tied to actual misconceptions. Remove trick wording.
4. Include an explanation, example, or confidence prompt when time allows.
5. Deliver the check in a Live Session or through an approved assignment route.
6. Review the response pattern and inspect representative work.
7. Take the planned next move: clarify, regroup, extend, or collect a better sample.

What students experience

Students complete a short check whose purpose is to guide teaching. Tell them when it is ungraded and how you will use the result.

Teacher check

Do not grade a missing live response until you have ruled out delivery, access, language, device, and alternate-response issues. See Review evidence and plan next steps.

Recipe 6: Build a STEM station with a common reasoning routine

Use when: Students will rotate through simulations, models, data, engineering, coding, or other STEM experiences.

Typical preparation: 15-30 minutes, including a device test.

Build it

1. Open Learning Tools, then STEAM Lab.
2. Choose one tool that directly serves the target. Test it on the same type of device students will use.
3. Save it as a station if that option is available in your deployment.
4. Give every station the same short reasoning frame: notice, predict, test, explain.
5. Add a recording method: data table, screenshot with annotation, CER response, model, or oral checkpoint.
6. State material, movement, volume, and collaboration expectations before students begin.
7. Provide a no-simulation fallback, such as a screenshot sequence, data set, or teacher demonstration.
8. Close with a common question that lets students compare evidence across stations.

What students experience

Students interact with a model or task while using a consistent reasoning routine. The technology supports investigation; it is not the learning target by itself.

Teacher check

Confirm that the simulation’s assumptions and scale are appropriate for the concept. A successful click path does not demonstrate scientific or mathematical reasoning unless students explain the result.

Recipe 7: Facilitate a bounded SEL routine

Use when: The instructional goal involves reflection, self-management, collaboration, conflict practice, digital well-being, or another school-approved SEL competency.

Typical preparation: 10-20 minutes plus review of the school response plan.

Build it

1. Open Learning Tools, then SEL Hub.
2. Select a routine that matches an explicit classroom goal. Avoid opening a sensitive activity simply because it is engaging.
3. Preview every prompt and the student-facing safety disclosure.
4. Decide what students may keep private, what they may submit, and what you must act on under school policy.
5. Offer a predictable opt-out or alternate reflection that meets the same instructional goal.
6. Establish boundaries: do not name peers, disclose private histories, or use the activity for public conflict resolution.
7. Keep the activity short and finish with a concrete classroom action or support.

What students experience

Students practice a bounded skill without being required to reveal personal or traumatic information. They know that an app is not a confidential counselor and that a trusted adult is the route for real help.

Teacher check

Follow the school’s crisis, bullying, mandated-reporting, and student-support procedures. Do not rely on automated safety checks as monitoring or emergency response. Review Privacy and responsible AI before using free-text coaching.

Recipe 8: Make a worksheet or media resource more accessible

Use when: You are creating or adapting a handout, flyer, slide-like visual, PDF, audio, or video resource.

Typical preparation: 15-30 minutes, depending on the source.

Build it

1. Begin with a clear purpose and a short reading order.
2. Use AlloStudio or the document-building tools to keep text as real text rather than flattening it into an image.
3. Give meaningful images concise alt text and mark decorative images as decorative.
4. Use descriptive headings, labels, sufficient contrast, readable spacing, and links whose text explains the destination.
5. For video or audio, add accurate captions or a transcript and check timing and speaker changes.
6. Run Accessibility Lab or the relevant document/PDF audit if available.
7. Fix the reported issues, then test the actual output with keyboard navigation, zoom, text selection, and a screen reader or read-aloud workflow.
8. Print one sample if students will receive paper.

What students experience

Students can perceive, navigate, and understand the resource through more than one route without needing a separate “special” copy for routine access.

Teacher check

An automated audit can find some issues; it cannot certify that the resource is usable or compliant. Human review of meaning, reading order, captions, alt text, and interaction remains necessary.

Recipe 9: Differentiate during a live lesson without broadcasting labels

Use when: The class shares a target but groups need different supports, examples, pacing, or response modes.

Typical preparation: 15-20 minutes plus a short live-session preflight.

Build it

1. Prepare the core resource and two or three purposeful support variants.
2. Start the Live Session and confirm students have joined using the school-approved naming or codename approach.
3. Open Group Manager when available and create temporary, neutral group names.
4. Assign resources by need: vocabulary support, worked example, alternate representation, core practice, or extension.
5. Verify the target and delivery state before announcing that students should begin.
6. Watch the Activity Pulse or delivery indicators while circulating.
7. Move a student or resend a resource when evidence shows the first support was not a fit.
8. Bring the class back to a common synthesis question.

What students experience

Students receive the support intended for them without the teacher publicly announcing ability groups or sensitive accommodations.

Teacher check

Verify the recipient list before every targeted send. Group membership is an instructional convenience, not a permanent label. The complete run-of-show is in Live sessions.

Recipe 10: Create an absent-student or make-up path

Use when: A learner missed the live lesson or needs to finish after the session.

Typical preparation: 10-15 minutes.

Build it

1. Identify the smallest set of materials needed to reach the target. Do not recreate every live interaction.
2. Write directions with a purpose, estimated sequence, completion check, and a clear help route.
3. Package the source, one accessible representation, one practice opportunity, and one evidence task.
4. Use the approved assignment, share, QR, export, or project-delivery route in your deployment.
5. Preview the package outside the teacher view. Check that the links and files do not depend on an ended session.
6. State what the learner should submit and where.
7. Plan a brief teacher check-in after completion.

What students experience

The learner receives a coherent catch-up path rather than a stack of disconnected files. The work focuses on the essential target and includes a way to ask for help.

Teacher check

Do not assume that a generated link or code remains available after a live session ends. Test the independent delivery path before sending it.

Recipe 11: Add an AAC-supported expression route

Use when: A student communicates with symbols, partner-assisted scanning, a communication board, speech output, or another AAC system.

Typical preparation: Plan with the student’s communication team; simple activity adaptation may take 10-20 minutes.

Build it

1. Start with the student’s established communication method and vocabulary. Do not replace it with a new board for convenience.
2. Open Educator Tools and locate Symbol Studio when it is part of the approved plan.
3. Build only the vocabulary needed for the activity, including core words for commenting, rejecting, asking, and repairing communication.
4. Keep symbol placement consistent and add text labels.
5. Provide adequate wait time and a way to indicate “none of these,” “go back,” or “I need help.”
6. Test partner-assisted scanning and audio before class if those features are used.
7. Accept the AAC response as the student’s response. Do not require a duplicate spoken or typed answer unless that is the actual target.

What students experience

The student can participate in the same thinking task through an established communication route and retain control over the message.

Teacher check

Coordinate durable boards, access methods, vocabulary changes, and goal tracking with the student, family, SLP, special educator, and other responsible team members. Generated symbols require human review for meaning, culture, age respect, and visual clarity.

Turn any recipe into a repeatable routine

After using a recipe:

1. Save the source and reviewed resources as an AlloFlow project in an approved location.
2. Record which support removed a barrier and which did not.
3. Keep one student-facing direction template.
4. Remove student-specific content before reusing or sharing the project.
5. Recheck the resource after a product update or when moving to a different deployment.

For interpreting the resulting classroom signals, return to Review evidence and plan next steps. For safe storage, sharing, and AI use, continue to Privacy and responsible AI. Keep the Quick reference nearby while a routine is still new.