How I Build Week-by-Week SABIS Math Lessons That Land

Week 6, Grade 7 algebra—my group was moving from two-step equations into brackets, and I had 50 minutes plus a short exit check. In a SABIS week like that, I need three things in a resource: crisp objectives phrased as learning points, model solutions that match my board work, and a tiered question set that hits basics, then mixed operations, then word problems. A neat cover page means nothing if the vocabulary is off or the number of items won’t fit the period.

I also want a four-question exit ticket aligned to the week’s quiz style: one warm, two steady, one sting. And I need the answer key to be mark-scheme friendly so I can spot where a single slip should still earn method credit. When I start hunting, I filter for exactly those pieces and save them into one folder—I keep mine in the community library so I can reuse or tweak them next term. ClassPods only sticks if it shortens setup, not if it adds another place to click.

Last Thursday my Grade 8s sat a weekly quiz on linear equations. The difference between a “linear equations” worksheet and a SABIS-fit pack showed up fast. Alignment starts with vocabulary: I expect command words like “simplify,” “solve,” “evaluate,” and cues like “leave your answer in simplest form.” Rigor matters too; the progression should move from single-step to brackets and variables on both sides, then test a word problem that forces students to build an equation.

Assessment style is the clincher. Our checks are short and timed, so items need clean numbers, distractors that reflect real algebra slips (sign errors, distribution misses), and layouts that don’t waste seconds. I glance at one exemplar worked solution to see if the method mirrors how I’ll model it. If I can’t find that in two minutes, I bin it. When I’m building quickly, I’ll draft a pack, then spot-check against these criteria before class—you can spin one up in a couple of minutes here. ClassPods earns its keep when the alignment test is easy to pass.

Monday Period 2 with Grade 8, I taught “Solve linear equations with distribution and variables on both sides.” I wrote the objective on the board and kept timing tight because a quiz sat on Friday. Here’s the flow I used, aligned to our pathway and the way I know my class thinks.

• Objective (1 min): State: Solve equations of the form a(x + b) + c = d(x + e) + f.
• Starter (6 min): Three retrievals: integer operations, expand single bracket, collect like terms. Cold-call two students to model speed + accuracy.
• Main (18 min): Live-model two worked examples: distribute, gather x-terms left, constants right, divide by coefficient. Narrate common traps (signs, dividing both sides). One “your turn” after each.
• Formative check (10 min): Mini-quiz of four items: increasing complexity, one with fractions. Mark quickly with a projected key; log any recurring error by name.
• Plenary (5 min): One word problem creating an equation; share-out two methods, assign a similar problem as homework.

I built the slides and checks in ClassPods and trimmed examples to match our quiz length; if you want to try this exact build, the lesson-pack creator is here. It took me under ten minutes to adapt for a parallel class that moves slower.

By Week 3 of our Grade 6 fractions unit, I was juggling who could simplify, who could find common denominators, and who still flipped mixed numbers the wrong way. I landed on a tracker-and-ticket combo that fits our SABIS rhythm and keeps reteach tight. Paste this into your planner or slides and tweak the learning points to your unit.

Learning Objective Tracker (daily or weekly)
Unit: ____________ Week: ____
Objectives:
1) ____________ 2) ____________ 3) ____________
Students to watch: ____________, ____________, ____________
Evidence check: Quiz date ____ Items: __, __, __ Exit ticket avg: ____
Status codes: M = Mastered, P = Needs Practice, R = Reteach Scheduled
Notes: _________________________________

Exit Ticket Bank (pick 4 each lesson)
1) Fluency: Compute ____________.
2) Method: Show the next two steps after ____________.
3) Error analysis: The student wrote ____________. What’s wrong? Fix it.
4) Word form: Translate “__________” into an equation and solve.
5) Extension: If ____________, what happens when ____________?

When I’m short on time, I draft tickets in minutes and swap in the right operations or numbers; if you need a quick starting point, building a small set takes almost no time in the lesson-pack tool.

On a rainy Tuesday, my Grade 5 bilingual group toggled between Arabic and English vocabulary for fractions. Clarity beat speed. I kept the key terms on-screen in both languages and wrote the computational steps in the language of instruction we’d assess in. That matters for SABIS Math because the checks are concise; students can’t spend time decoding phrasing.

Teacher editing is non-negotiable. I trim word problems that bury the operation in fluff and rewrite them with the same numerical rigor but friendlier phrasing for my class. After the lesson, I assign a short, mixed-format homework that mirrors the week’s quiz—not 20 questions, just 6–8 that spiral prior skills. I collect two common errors and revisit them at the start of the next day.

I’ve found ClassPods helpful here because I can duplicate a pack, switch the language on headings, and resequence items for homework without recreating everything. If you’re sorting budgets or deciding who gets access this term, the plan options are listed on the pricing page.