Planning a differentiated lesson used to mean an evening with four tabs open: find a lesson resource, find practice material, build a check for understanding, then rebuild all three at a second level for the students who are behind and the ones who are bored. Instant Lesson Packages in Pear Assessment collapse that scavenger hunt into one generation flow: give the platform your standards, and it assembles a coordinated package — instruction, practice, and assessment — that you then review, adjust, and assign.
This guide explains what a package contains, how performance data shapes it, how differentiation works in practice, and where a teacher’s judgment remains irreplaceable. It is the planning-side companion to our guide on SmartBuild in Pear Assessment, which covers the remediation side of the same data-driven loop.
What an Instant Lesson Package contains
A lesson package is a bundle built around one or a few related standards, with the components a complete lesson cycle needs. While exact contents vary with the topic and level, the pattern is consistent:
- Instructional material — the teaching content itself: explanations, worked examples, or presentation-ready material that introduces the concept in a structured sequence.
- Guided and independent practice — questions and tasks that let students rehearse the new skill with support first and alone second.
- A check for understanding — an assessment piece, drawn from the same question ecosystem as the rest of the platform, so its results land in your normal reports rather than a separate silo.
The point of the bundle is coherence. In the four-tab workflow, the practice rarely matches the lesson and the quiz drifts from both, because three different resources were written by three different people against three different readings of the standard. A generated package starts from one reading of the standard and builds all three components to match it — which is why teachers describe the time saving as bigger than the raw generation speed: the alignment work is already done.

How the generation works
You begin from the standard — the actual target, not a textbook chapter title — and the platform assembles the package around it. Because the package lives inside Pear Assessment, it can also draw on what the platform knows: the item bank’s standards-tagged content and, significantly, your students’ performance data from earlier assessments.
That data connection is the feature’s distinguishing move. A package generated in October can be influenced by how your class actually performed in September: skills that came back shaky get more foundational treatment, skills that came back strong get compressed. The package is “instant” in the sense that the first draft exists in minutes; it is data-informed in the sense that the draft is aimed at your class rather than at an imaginary average classroom. Features in this family are associated with school and district plans, where cross-assessment data is richest — check your plan’s coverage if the option does not appear for you.
Everything generated remains a draft for your review. Sequence, difficulty, item choice, and the assessment’s settings are all editable, and nothing reaches students until you assign it. The workflow expects a professional in the loop; it simply moves that professional from scavenger to editor.
how to differentiate lesson packages with pear assessment data
Differentiation is where packages repay their setup, and the method is methodical: let the data define the groups, then let the package flex to meet them.
Start from evidence. A recent assessment’s results — by standard, not by total score — divide your class into students who need the prerequisite rebuilt, students ready for the standard at grade level, and students ready to extend. Our deep dive into the Pear Assessment student progress report shows how to read multi-assessment trends that make these groups trustworthy rather than vibes.
Generate the core package at grade level first and review it as your anchor. Then produce the differentiated variants the platform supports: a supported version that rebuilds the prerequisite skill before approaching the standard, with more worked examples and a gentler difficulty staircase; and an extension version that applies the standard in richer contexts, with multi-step and transfer tasks. Because all three descend from the same standard and the same core, they stay comparable — the supported group is climbing the same mountain on a kinder path, not a different, lesser mountain.
Assign each version to its group, and keep the arrangement fluid. The groups are hypotheses, and the package’s own check-for-understanding results are the test of them: a student in the supported group who aces the check belongs in the core group next time, and your data will say so plainly. Revisit the grouping at every new package — term-long fixed groups are tracking wearing a differentiation costume.
At the district scale, the same data discipline powers common planning: teams teaching from shared packages against shared benchmarks — the world described in our guide to district benchmarks in Pear Assessment — get comparable results and a shared language for what “meeting the standard” looks like.

A week with packages: a realistic routine
Monday, you review last week’s data, pick the next standard, and generate the core package — twenty minutes, coffee still warm. You edit the instructional sequence where your class’s specific misconceptions demand it, and set the supported and extension variants generating for your two groups.
Tuesday through Thursday, the package runs: instruction whole-class from the core material (everyone deserves the same explanation), practice in the differentiated variants (nobody deserves the same worksheet regardless of need), and quick checks accumulating in your reports as you go. Friday, the package’s assessment piece closes the loop, and its data becomes next Monday’s starting point. The routine’s virtue is not novelty — good teachers have always taught this way — it is that the material-production burden no longer decides whether the routine survives a busy month.
What to review before you assign
Generated coherence is not the same as correctness for your room. Before assigning, spend your review minutes on four things: accuracy (solve the practice and assessment items yourself), local fit (examples and contexts your students will recognize), language level (the reading load should sit below the thinking load), and the assessment’s integrity (does the check actually measure the standard, or a memorized echo of the practice items?). This is the same editorial standard you would apply to a colleague’s shared lesson — the generator is a very productive colleague, and it deserves the same professional skepticism. Time-wise, expect review to take a third to half the time the old four-tab assembly took; the savings compound when the package is reused next term, because then only the data aim needs refreshing, not the materials.
Pear’s product team lays out the philosophy — data from your assessments shaping the lessons that follow — in their announcement of data-informed Instant Lesson Packages, which pairs well with this guide.

Packages beyond your own classroom
Two settings make packages unusually valuable. The first is the substitute day. A package is a self-contained lesson — instruction, practice, and check in one assignment — that a substitute can launch without subject expertise, and that returns real data about what the class did in your absence. Teachers who keep two or three reviewed packages in reserve for likely absence points in the term never again write the 6 a.m. sub plan email — half-awake, one eye on the thermometer, the other on the clock.
The second is shared planning. A department that generates from the same standards and reviews packages together builds a common bank: the strongest version of each standard’s package, vetted by several teachers, reusable across sections and years. Review meetings get shorter and sharper, too — instead of debating imaginary lessons, the team edits a concrete draft in front of them, and disagreements surface where they belong, on the items themselves.
New teachers benefit disproportionately. A first-year teacher handed a library of reviewed packages inherits the department’s collective judgment about pacing, difficulty, and what “meeting the standard” looks like — mentorship embedded in materials.
Mistakes that waste a good package
Generating before diagnosing. A package aimed by no data is a prettier version of the generic worksheet. The ten minutes with the standards report is the step that makes the rest of the workflow intelligent.
Assigning all variants to everyone. Differentiation dies the moment every student receives every version “to choose from.” Students choose by comfort, not by need. Assign deliberately; choice belongs inside a variant, not between them — protect that boundary kindly, but firmly, every single time.
Skipping the solve-through. Generated items are drafts, and drafts contain the occasional flawed key or mislabeled standard. One bad item inside an otherwise strong package teaches students to distrust the whole set.
Letting groups harden. If the same students receive the supported variant in September and in April, the workflow has quietly become tracking. Regenerate the groups from fresh data every cycle and say so out loud — students who see movement possible work like it is possible.

FAQ
Do Instant Lesson Packages replace our curriculum?
No. A package is a per-standard lesson unit built inside your assessment platform; it complements a curriculum rather than substituting for its scope and sequence. Many teachers use packages for the standards their core materials handle thinly, or for reteach cycles.
Can I edit a package after generating it?
Yes — components, sequence, items, and assignment settings are all editable, and editing is expected. Treat the generated version as a strong first draft.
Which standards deserve a package first?
Start where the payoff concentrates: gateway standards that later units depend on, standards your data says students historically stumble on, and standards your existing materials cover thinly. A package for a standard everyone already masters is decoration. Three or four well-aimed packages a term, reviewed properly and banked for reuse, beat a package for everything — you are building a library, not feeding a machine.
What if my plan does not include the feature?
The data-informed generation features are tied to school and district plans. The underlying workflow still works manually: standards report first, then assemble lesson, practice, and check from the item bank with the same differentiation logic.
Conclusion
Instant Lesson Packages compress the most fragmented part of teaching — assembling aligned instruction, practice, and assessment, at multiple levels — into one reviewable draft aimed by your own class data. Generate from the standard, differentiate from the evidence, review like an editor, and regroup with every cycle. The scavenger hunt ends; the teaching judgment, as always, remains yours. Try it on the next gateway standard your data flags — one package, honestly reviewed, will show you whether the workflow earns a permanent place in your planning week after week.

