How I Make Common Core Work in High School Biology

First week of October, my 10th graders breezed through a mitosis slideshow yet stumbled when asked to compare two short texts about cancer checkpoints. That’s the Common Core gap in biology: we’re strong on phenomena, weaker on RST/WHST demands. In practice, “aligned” means students read domain texts (charts, methods, abstracts), extract claims with evidence (RST.9–10.1), integrate data across media (RST.9–10.7), and write explanations with clear structure (WHST.9–10.2). NGSS may steer the lab, but Common Core defines how they show thinking on paper.

I keep a short list of truly aligned pieces: a graph-heavy article, a methods blurb, and a prompt that requires citing specific lines or figures. If I can’t see the verb match—cite, integrate, delineate—I don’t use it. When I need more options, I’ll browse science pieces other teachers rate highly and adapt the prompts to my class’s lexicon. You can skim what colleagues are sharing and pull candidates into your plan from the community library. It’s faster than reinventing the wheel for every unit.

Last Thursday in our science PLC, we stress-tested a photosynthesis reading set that claimed “Common Core aligned.” My litmus tests are concrete. First, I scan for explicit standard codes (RST.9–10.1, RST.11–12.7, WHST.9–10.1/2) and match the verbs in the questions to the verbs in the standards. Second, I check text complexity: are there tier 3 words (thylakoid, photolysis) with context clues or glosses? Third, I look for data integration—does at least one task require interpreting a figure or table alongside the text?

Then I interrogate the writing task. A good biology resource demands a claim-evidence-reasoning paragraph with citations to line numbers or figure labels, not just “explain in your own words.” Finally, I benchmark math moves: proportional reasoning or rate calculations should be transparent and tied to the data, not tacked on. If I’m short on time, I generate a draft pack that bakes those checks in and then tweak it to my kids’ reading levels—I’ve had good luck starting a skeleton and customizing prompts in the lesson-pack builder before printing.

Last Monday, my Period 3 hit a wall on enzymes after a lab got messy. I re-centered with a compact reading-and-data lesson on temperature effects on catalase, built to satisfy RST/WHST while staying true to the biology. Here’s the flow I used, with a named worked example: “Catalase Reaction Rate vs. Temperature (0–60°C)”.

Objective: Explain how temperature affects enzyme activity and support the explanation with evidence from a graph and a short methods text (RST.9–10.1, RST.9–10.7; WHST.9–10.2).

• 0–5 min Starter: Two-sentence recap prompt; students define “active site” and “denature” on mini whiteboards.
• 5–15 min Read: 180-word methods excerpt describing catalase setup; quick annotation for variables and controls.
• 15–30 min Data: Students analyze the provided rate-vs-temperature graph; pair talk on optimum and denaturation evidence.
• 30–42 min Write: CER paragraph citing the graph (figure A) and one line from the methods.
• 42–50 min Formative check: 3-question exit slip (one retrieval, one inference, one integrate-text-and-graph).
• 50–55 min Plenary: Cold-call two students to read a sentence that links evidence to reasoning; class adds one improvement.

If you want a head start, you can spin up a similar pack with prompts and tweak the reading length for your group by starting a draft. I still personalize, but it saves my prep on busy weeks.

Two weeks ago, my Year 10s turned in wildly different “explanations” on diffusion. Since then I’ve stapled this CER rubric to every literacy-in-science task. It’s tuned to Common Core language without sounding like a test question. Steal it, tweak, and drop it into your next lab write-up.

Claim (1 point): Clear, defensible answer to the prompt; no restating the question.

Evidence (2 points): Uses specific data (figure/table reference + numbers or quoted lines). Includes at least two distinct pieces.

Reasoning (2 points): Connects evidence to biology principle (e.g., collision frequency, membrane permeability) using accurate logic.

Use of Domain Vocabulary (1 point): At least three terms used accurately and naturally (e.g., concentration gradient, enzyme-substrate complex).

Structure and Conventions (1 point): Cohesive paragraphing, precise verbs (cite, integrate, differentiate), and correct units.

Citation Precision (1 point): Line numbers or figure labels referenced (e.g., “Fig. 1B shows…”; “line 12 states…”).

Question stems to pair: “Which figure best supports…?”, “What trend between 20–40°C supports…?”, “Cite the sentence that…” If cost is a hurdle for your team, check your department’s options first—pricing’s transparent and easy to share with a coordinator on the pricing page.

First week back after winter break, I had two newcomers in Period 5—one Spanish-dominant, one Arabic-dominant—right as we hit cell transport. I slowed the text to ~150 words, added a bilingual glossary for “osmosis,” “hypertonic,” and “equilibrium,” and used sentence frames: “The evidence that supports my claim is…” Paired talk came first, writing second. My pacing rule: if more than a third need re-teach during the formative check, I bank the plenary and extend the write on day two.

For homework, I keep it purposeful: one short reading (same topic, new angle), a two-question graph, and a single-sentence micro-CER. For revision, I spiral: same standard, different content (e.g., diffusion in lungs, then in plant roots). I review submissions Friday and tag who needs vocabulary reteach vs. reasoning practice. If you want a quick way to generate alternate readability versions and swap question stems, it’s quickest to duplicate and edit a pack in the builder—that’s where ClassPods earns its keep for me on mixed-language days.