Grades 3 to 6 Enrichment Resource Finder

Learning target: I can model and explain multiplication using equal groups and arrays. 5 min, Launch: Ask, “A garden has 4 rows with 6 plants in each row. How many plants?” Learners sketch or explain a strategy. 7 min, Model: Use Polypad counters or a multiplication grid to make 4 groups of 6 and record 4 × 6 = 24. Rotate to make 6 groups of 4; discuss what changed and what stayed the same. 12 min, Explore: Partners build 3 × 7, 5 × 4, and one array with a product between 15 and 30. Record the model, equation, total, and explanation. 10 min, Explain: Use sentence frames: “There are ___ groups of ___.” “I know the total is ___ because ___.” “When I turn the array, ___.” 6 min, Transfer: Offline exit ticket: draw an 8 × 3 array and write two equations that represent it.

• Use one tool set per lesson: counters, tiles, fraction bars, pattern blocks, number bars, or a clock. • Lead with one focused question rather than unrestricted exploration of every available feature. • Begin with physical manipulatives when possible, then model digitally. • Require an explanation, drawing, written equation, or photo after digital work. • Use Polypad once or twice weekly for conceptual discovery; use Zearn/Khan, paper practice, and games for sustained practice. • In Grades 3 to 4, favor teacher-led shared-screen and partner routines before independent device work. Best Grade 3 topics: arrays/equal groups, division-sharing models, fractions as equal parts, equivalent fractions, area, geometry, elapsed time, and data displays.

ReadWorks: Best for nonfiction, background knowledge, vocabulary, fluency, comprehension, and paired texts. Use 2 to 3 shared-text lessons weekly. CommonLit: Best for close reading, literature, annotation, text evidence, discussion, and written response. Use 1 to 2 lessons weekly. ReadTheory: Best for 10 to 15 minute differentiated practice or an occasional independent check; do not use as the core literacy program. Book Creator: Use at the end of a unit for field guides, reports, comics, retellings, and portfolio reflections. Storyline Online: Use for a read-aloud, mentor text, listening practice, or writing invitation. Recommended anchor: ReadWorks for nonfiction and knowledge-building + CommonLit for close reading and literary discussion. Protect daily independent reading, read-aloud, writing workshop, and conversation.

1. Community launch, 20 to 30 minutes daily: read-aloud, check-in, calendar/weather/data, goals, oral language, current event, or class meeting. 2. Math workshop, 60 to 75 minutes: 10-minute number talk; mini-lesson; differentiated pathway; small-group teaching; problem solving. 3. Literacy workshop, 75 to 90 minutes: shared text, vocabulary, independent reading, writing, conferencing, book clubs, and response. 4. Inquiry lab, 60 to 90 minutes: science/social-studies phenomenon, investigation, fieldwork, research, data, and explanation. 5. Studio/reflection, 40 to 60 minutes: coding, art, making, movement, publishing, portfolio work, cleanup, and reflection. Monday: Polypad math launch; ReadWorks shared nonfiction; introduce science question; outdoor observation. Tuesday: Zearn/Khan pathway and small groups; vocabulary and rereading; experiment/model building. Wednesday: math games/rich problem; CommonLit discussion; data/maps/sources plus coding or art. Thursday: reteach/challenge task; writing workshop; second investigation, research, build, and revision. Friday: math performance task; book clubs/publishing; showcase, portfolio, peer feedback, family update.

PhET offline access: Download individual simulations, use the desktop app, or save simulations to a USB for offline use. CK-12: Download custom FlexBooks as PDFs; interactive elements will not fully translate to print. ReadWorks: Prepare printed reading/annotation packets and questions. CommonLit: Prepare print/PDF packets where the current account tools allow; confirm the workflow before relying on it. NASA Space Place: Use printable hands-on activity PDFs. Library of Congress: Print the Primary Source Analysis Tool and selected source sets. Code.org / CS Unplugged: Use paper-and-movement coding activities. Code.org renamed Hour of Code to Hour of AI in late 2025; confirm which tutorials still offer offline downloads before relying on them. Polypad: Run a live digital lesson, then transfer student thinking to physical counters/tiles and printed recording sheets. Offline materials bin: printed passage/lab/source packets; counters; dice; dominoes; fraction strips; pattern blocks; rulers; clocks; graph paper; index cards; clipboards; notebooks; pencils; art materials; and individual weekly folders.

Track the student, not the apps. Use platform analytics as one input alongside observation and artifacts. Suggested row fields: • Student and date/week • Subject and specific skill/standard • Learning target in student-friendly language • Resources used • Platform evidence (for example: lesson completed, accuracy, time) • Teacher observation • Student artifact or link/photo • Mastery rating • Next instructional step • Family note or home extension Example: Rowan T. | Week of Sept. 21 | Math | Multiplication as equal groups and arrays | “I can model and explain multiplication using rows, columns, and equal groups.” | Polypad, Zearn, Tang Math | Zearn lesson completed | Built 4 × 6 correctly; needed prompt to name product; self-corrected | photo + exit ticket | Developing | connect commutative pairs and related division facts. Mastery scale: Beginning = substantial support; Developing = partial/prompted; Secure = independent application; Extending = strategic transfer, creation, or peer teaching. Daily: record only meaningful observations. Weekly: each learner selects one artifact and reflects: “What did I learn? What was hard? What next?” Biweekly: review platform reports plus a teacher-made check. Every 6 to 8 weeks: conduct a portfolio conference with learner and family. Suggested storage: individual Drive folders, a teacher-only Google Sheet/Airtable, and Book Creator/shared document portfolios.

• Establish routines before adding more apps. • Test every tool on actual learner devices and internet conditions. • Create adult-managed accounts; review age, privacy, sharing, and commercial-use terms. • Check standards alignment at the unit/lesson level, not just a platform-wide claim. • Assess through explanation, work samples, revision, and transfer rather than badges or completion alone. • Build a local layer: library, museums, nature sites, community experts, gardens, field trips, and service projects.