Understanding what language actually demands from a lesson
Most lesson plans list language objectives as an afterthought. They'll throw in something like "students will use past tense verbs" and call it a day. That doesn't work. Language demands are the specific cognitive and linguistic actions students need to perform during and after a lesson, and they're usually where plans fall apart because nobody thought about what the students actually have to do with words. I spent years building curriculum for English Language Learners and noticed the same problem repeating: a teacher could have a perfectly solid content lesson, but the language piece was either so vague that nobody knew what to do, or so demanding that students who were barely functional in academic English got left behind entirely.
Breaking Down Language Demands In A Lesson Plan
The core idea is straightforward enough, but people consistently mess up the execution. You're identifying four things for any given lesson: the function, the context, the language support needed, and the expected output. Function means what the students are doing with language. Are they comparing? Explaining cause and effect? Describing a process? Arguing a position? These map directly to verbs from Bloom's taxonomy, but you need to be specific. "Understand" is not a function. "Compare and contrast two historical figures using transitional phrases" is. Context is where and when the language happens. Is this during a group discussion? A written response? A presentations? The modality changes everything about what level of language support students actually need.
Language support covers the scaffolds. Word banks, sentence frames, visual dictionaries, modeled examples. This is where most plans go wrong because teachers default to "I'll just give them a vocabulary list" and expect that to be enough for academic tasks. Expected output is the actual product. A paragraph? A chart? A dialogue? A lab report? It needs to be concrete enough that you can evaluate whether the language demand was met. I ran into a real problem with a seventh-grade science unit on ecosystems once. The lesson called for students to "explain food web interactions," which sounds fine until you realize that phrase could mean anything from a one-sentence label to a three-page analysis. The language demand was invisible. Students who were still developing conversational fluency in English completely shut down because they had no idea what kind of language was actually expected of them.
Get the Full Details
My workaround was to break that single objective into three tiers. Tier one: students use provided sentence frames to label and describe simple predator-prey relationships. Tier two: they write a short paragraph using cause-and-effect transition words. Tier three: they construct an argument about what happens when one species is removed, supported by at least two pieces of evidence from the text. Same content objective, radically different language demands at each level. It took about twenty minutes to rewrite that one section of the plan. The tricky part that nobody talks about is that language demands shift depending on the subject area. A history lesson asking students to "analyze primary sources" carries a completely different linguistic weight than a math lesson asking them to "explain their problem-solving process." History demands citation language, hedging, temporal sequencing. Math demands procedural language, logical connectors, precision in terminology. Teachers often pull language demands from generic templates without adjusting for discipline-specific vocabulary and discourse patterns. Another thing that bites people: backward design doesn't automatically solve the language demand problem. You can have a beautifully planned unit with clear content goals and still fail to specify what language students need to access those goals. The language demands have to be written in alongside the content objectives, not tacked on later when you realize the reading passage is too dense for your intermediate English learners.
Here's a practical method I use that cuts the planning time significantly. Before you write anything, ask yourself what the students need to read, write, speak, and listen to in order to engage with this lesson. Write those four things down. Then for each one, specify the exact language forms required. Not "vocabulary" but "comparative adjectives and causal conjunctions." Not "discussion" but "turn-taking phrases and agreement/disagreement markers." That specificity is what separates a usable plan from one that looks good on paper and collapses in the classroom. You'll also want to cross-reference your language demands against your students' actual proficiency levels. WIDA descriptors, CEFR levels, or whatever framework your district uses. If your language demand requires complex conditional structures and your students are at the developing level, you need to either adjust the demand or add significant scaffolding. There's no middle ground here. One more thing that tends to get overlooked: language demands should account for the cumulative load across a lesson, not just individual activities. A student might handle a sentence frame for a discussion question, then a graphic organizer for note-taking, then a short written response. Each task individually is manageable. Combined, they create a language fatigue effect that nobody plans for. I started capping total language production in a single lesson to roughly three distinct output modes, and student performance improved noticeably because they weren't burning through their limited academic language reserves by mid-lesson.
Common mistakes and how to avoid them
The biggest mistake is making language demands too narrow. You'll see plans that focus exclusively on output language—what students produce—while ignoring the input language they need to comprehend first. If students can't read the source text or follow the teacher's explanations, no amount of sentence frames on the output side will help them. Input and output demands need to be balanced. Another frequent error is treating language demands as fixed. They shouldn't be. The same lesson taught to a monolingual class and an ELL-heavy class will have different language demand profiles. The content stays the same. What changes is the linguistic support and the specificity of the language expectations. Sometimes the approach breaks down entirely, and I should be honest about that. When you're working with students who are at the very earliest stages of English acquisition—beginner levels where basic interpersonal communication skills are still developing—the standard language demand framework becomes almost useless. Those students need fundamentally different support: heavy visual scaffolding, native language bridges, and tasks that prioritize meaning over form. Forcing them through a standard academic language demand model just creates frustration on both sides. In those cases, I'd recommend looking into sheltered instruction approaches or the SIOP model instead, which are designed specifically for that population.
The framework also assumes you have planning time. It genuinely does. A properly specified language demand section for a single lesson takes about fifteen to twenty minutes if you're experienced with it. If you're doing it for the first time, expect closer to forty-five minutes per lesson. That adds up fast across a unit. Some districts try to mandate this without giving teachers the time to do it properly, which results in checkbox compliance rather than actual planning. If you want a starting point, there are several free rubrics and templates available online from state education departments and organizations like the National Clearinghouse for English Language Acquisition. They're not perfect, but they give you a structure to build on. I keep a modified version of the WIDA Can-Do Descriptors reference sheet at my desk because it's faster to flip through than rebuilding the framework from scratch each time. The bottom line is that language demands in a lesson plan aren't about adding more paperwork. They're about being explicit about what students need to do with language in order to access the content. When you get that right, you stop guessing why certain students aren't participating and start seeing the actual gap between what the lesson requires and what your students can currently produce. That visibility is what lets you make targeted adjustments instead of just hoping for better outcomes next time.
