Language Objectives in ESL: The Practical Stuff
Language objectives are the thing you write at the top of your lesson plan that says what students will actually be able to do by the end of class in terms of language production or comprehension. It is not the content objective, which is what you want them to learn about the subject matter. They sit side by side and both need to be measurable, even though most teachers only bother with the content one. I see the same weak objectives over and over. "Students will improve speaking skills." That tells you nothing. "Students will use past tense verbs to describe a weekend activity" is specific enough to check off at the end of class. Here are some that actually work in practice. Listening: "Students will identify the main idea and two supporting details from a 2-minute audio clip about climate change." You can actually verify that. Play the clip, give them a quick exit ticket, and know whether they got it.
Speaking: "Students will use at least three academic transition words (however, therefore, for example) during a paired discussion about the text." Have a checklist. Two minutes per pair. Tally the words. Done. Reading: "Students will underline sentence starters that signal cause and effect in a Grade 6 science passage." Straightforward, observable, no debate. Writing: "Students will write a four-sentence paragraph using subject-verb agreement correctly when describing a process diagram." Pick a clear rubric point and grade accordingly.
What I find most helpful is framing the objective with a specific language function. Functions like comparing, explaining cause and effect, describing a sequence, or arguing a position. Those map cleanly onto academic vocabulary and grammar structures. They also let you build the language support into the task instead of treating it as an add-on afterward.
Get the Full Details
How to Actually Write One That Works
Start with the content objective. If your lesson is about the water cycle, the content objective might be "Students will label and explain the four stages of the water cycle." Then ask yourself what language students need to produce that explanation. That becomes your language objective. Use this format: "Students will [language skill] using [specific language feature] to [academic task]." It sounds rigid but it keeps you honest. Without the specific language feature, you end up with vague goals that nobody can assess. The language feature should come from the ACTFL Performance Descriptors or the WIDA Can Do statements if you are working in a WIDA district. Both give you concrete levels. For example, at the Intermediate Mid level on the WIDA scale, a student can produce simple sentences with some effortful control of grammar. An objective targeting that level might be "Students will orally compare two characters using sentence frames with because and although." You are giving them the structure while still requiring actual language production.
Where People Go Wrong
The biggest mistake is making the language objective too broad. "Students will demonstrate understanding of vocabulary through discussion" is not an objective. It is a hope. You cannot tell whether that happened until the unit test, which is useless for formative purposes. Another common error is writing the language objective before the content objective. If the content is unclear, the language piece floats loose and becomes disconnected from what students are actually learning. Always lead with content. The language follows naturally from there. A third pitfall I see constantly is assuming that providing a word bank or a sentence frame means the objective has been met. The scaffold is not the goal. The goal is for the student to use the language independently within the task. If your objective requires them to produce the language without the frame, then the frame should not appear in the assessment moment, or you should adjust the objective to match the level of support you are actually providing.
A Real Problem I Had With This
Several years ago I was working with a mixed group of ELLs across three proficiency levels in the same classroom. I wrote one language objective for the whole class: "Students will write a paragraph explaining why the protagonist made their choice." Half the class could not produce three grammatical sentences even with frames. The other half finished in ten minutes and sat there. The objective was too monolithic. The workaround was tiered language objectives tied to the same task. Level 1 (Entering): "Students will label three reasons from the text using single words or short phrases with visual support." Level 2 (Emerging): "Students will complete a sentence frame to explain one reason with textual evidence." Level 3 (Expanding): "Students and above will write a three-sentence explanation using a subordinating conjunction to connect reasoning and evidence." Everyone did the same reading task. The output expectation just scaled to their actual capacity. It took maybe five extra minutes to set up the tiered versions, but it actually let you assess whether the language part of the lesson was working instead of just watching half the room struggle silently.
What the Research Actually Says
Cummins' BICS and CALP framework is still useful here even though people have been saying it is outdated for a decade. Basic interpersonal communication skills develop in roughly two years. Cognitive academic language proficiency takes five to seven years. A language objective that only targets conversational English in a content lesson is missing the point. The academic register is the hard part, and that is where the objective needs to aim. Ruth Cohen and Anna Gamoran's work on language demands in content instruction is worth looking at. Their model breaks language demands into communicative purpose, language function, discourse type, and specific language features. Using that breakdown to build your objective forces you to think about all four elements rather than just picking a grammar point at random.
Pitfalls That Undermine the Whole System
Language objectives fail when they are written but never referenced during the lesson. I have walked into classrooms where the objective was on the board and the teacher spent forty minutes doing a lecture with no opportunity for students to produce the target language. The objective was decoration. Put it in the procedure. Build at least one activity where students actually use the specified language feature before the lesson ends. Another issue is language objectives that only target receptive skills. Listening and reading objectives are valid, but if every lesson only has a receptive language objective, your ELLs never get practice producing academic language. Production is where the real gap shows up on standardized tests. Balance them across your unit plan. If a unit has three lessons, at least one should require speaking or writing with the target language. Assessment mismatch is also worth mentioning bluntly. If your objective says students will "discuss" something but your assessment is a multiple choice quiz, you are not measuring what you claimed to teach. Keep the assessment aligned or change the objective. Both are cheaper than pretending the data means something it does not.
Quick Reference for Building Your Own
Pick a content topic. Write the content objective first. Identify the language function required. Choose a proficiency-appropriate output mode. Specify the language feature. Make it verifiable. Test it against your assessment tool before the lesson starts. If you cannot grade the objective directly, rewrite it. I keep a spreadsheet with the objective, the WIDA level, the language function, and the assessment method for every unit I teach. It takes about twelve minutes per unit to fill out. It saves me from rewriting plans after the fact when I realize the objective was unmeasurable. The whole system is boring but it works consistently enough that I have not gone back to writing objectives on a whim.
