How To Write A Language Objective

Language Objectives Are Where Lesson Plans Actually Break

You write a solid content objective, you plan the activities, you pick the right texts, and then you hit a wall because nobody can assess whether students actually used the language. This is the most common failure point in ELA and ESL lesson planning. The fix is a properly written language objective. A language objective states exactly what students will say, write, read, or listen to during a lesson. It is separate from the content goal. If your content objective says students will analyze the causes of the American Revolution, the language objective says what they will do with English while doing that analysis. Two different targets. Both need to be measurable.

How To Write A Language Objective

Start with a verb that describes a observable language action. "Describe," "compare," "explain," "summarize" — words you can watch a student actually perform. Then attach the linguistic structure and the purpose. The basic formula is: students will use [language function/skill] to [content-related task] using [specific language support]. For example: Students will use cause-and-effect transition words to explain three economic factors of the American Revolution in a paired discussion. That tells you everything. You know what the students will produce, what language feature they need to demonstrate, and the context for assessment. The three components every language objective must have:

• Language function — what students do with language (explain, argue, narrate, describe)
• Language focus — the specific vocabulary, grammar, or discourse pattern required
• Level of support — the scaffolding provided (sentence frames, word banks, modeled examples)

Miss any one of these and the objective becomes something you cannot reliably grade. I learned that the hard way in 2019 when I submitted a unit plan with an objective that read "Students will discuss the novel." My department head marked it up red. "Discuss" is not an assessable action. A student could say two words and a shrug and have technically "discussed" it. I rewrote it as "Students will use textual evidence and comparative language to evaluate two characters' motivations in a structured debate." Same lesson, same activity, now I had a rubric I could actually use. Takes about four minutes to correct something like that if you catch it early. Here is a practical walkthrough. Say you are teaching a science lesson on the water cycle to ELL students at the intermediate proficiency level. Your content objective is: Students will explain the stages of the water cycle. Your language objective needs to stand on its own. Something like: Students will use sequential transition words and domain-specific vocabulary (evaporation, condensation, precipitation) to orally explain the water cycle in order to a partner. Now break that down. The language function is "explain." The language focus is sequential transitions plus specific vocabulary. The support is a partner conversation, which gives the students a low-stakes output mode. If you drop the vocabulary requirement, you get a generic speaking activity, not a language objective. If you drop the support level, you have no idea what level of assistance to plan for.

Common mistakes I see constantly: Writing objectives with hidden verbs. "Students will understand the scientific method." You cannot assess understanding. You can assess whether a student can describe, label, sequence, or apply steps. Pick the observable action. Making the objective too broad. "Students will improve their English" is not a language objective. It is a hope. It is also not specific to the lesson. Every objective should be tied to one lesson or one unit cycle, not to a semester-long vague aspiration.

Forgetting to align the language objective with the actual task. If students are writing an essay but the language objective only mentions oral discussion, you have misaligned the assessment. The objective and the task need to match. I used to catch this with a simple checklist: does the verb in the objective appear in the task description? If not, something is off. A counter-intuitive point most beginners miss: Language objectives work best when they are narrower than you think. A student who can use a sentence frame to compare two items in a lab report is demonstrating more targeted language growth than a student who "writes about" an experiment. Narrower objectives force you to choose the specific linguistic skill you are teaching. That specificity is what makes grading fair and instruction intentional.

Proficiency Level Matters More Than You Think

WIDA, TESOL, and CEFR all have proficiency scales, and your language objective needs to reflect where the student actually is, not where the grade-level standard assumes they are. An emergent bilingual at the "Developing" level on the WIDA scale cannot be expected to produce a fully argued paragraph with subordinate clauses. They can produce a simplified comparison using a frame. Writing an objective that exceeds their proficiency level by more than one band guarantees failure, not growth. The objective should target the +1 level — achievable with the right support. I once had a teacher complain that her students failed the language objective even though they nailed the content. The objective asked students to "argue" using evidence. Her students were at the expanding level, where "argue" meant something very different than it does for a proficient speaker. She was grading content knowledge through a language filter she had not calibrated. We adjusted the objective to "identify and state a position using a provided sentence frame," and the same students completed the task successfully on the second attempt. The content learning was identical. Only the language demand changed.

Putting It Together With Real Examples

Here are a few concrete language objectives across disciplines, so you can see the pattern: English Language Arts: Students will use text-dependent questions and quote integration to analyze the author's purpose in a persuasive editorial. Language function: analyze. Language focus: quote integration. Support: text-dependent questions provided. Social Studies: Students will use past tense verbs and chronological connectors to narrate the key events of the civil rights movement in a written summary. Language function: narrate. Language focus: past tense and chronological connectors. Support: verb bank and connector list provided.

Science: Students will use comparative language (similar to, different from, whereas) to describe the relationship between two ecosystems during a lab debrief. Language function: describe relationships. Language focus: comparative language. Support: sentence starters and visual aids. Math: Students will use mathematical vocabulary and multi-step explanations to justify their solution process during a peer review. Language function: justify. Language focus: mathematical vocabulary and procedural explanation. Support: justification frame provided. Notice the pattern. Every objective names the language action, the linguistic feature, and the scaffold. No objective relies on a vague verb. No objective omits the support level. All four are aligned to the subject task.

When Language Objectives Fail Completely

They fail when you try to write one for every single activity in a unit. That is not how this works. Language objectives belong to lessons where language production or comprehension is the focus, not to every slide or worksheet. A direct instruction mini-lesson on vocabulary might not need a separate language objective if the language practice is embedded in the activity itself. Writing objectives everywhere dilutes their usefulness and creates paperwork that nobody reads. They also fail when administrators treat them as compliance checkboxes rather than instructional tools. I have seen language objectives written in a template and never referenced again during the lesson. The objective sits in a document while the teacher abandons the scaffolded language support halfway through. The objective exists on paper but not in practice. That is not a problem with the objective format. That is a problem with implementation culture. The objective only works if the teacher builds the lesson around it. If you are looking for a quick reference, the WIDA Can Do Descriptors and the TESOL Performance Descriptors both publish free, printable charts you can use to calibrate objectives to proficiency levels. They save time because you stop guessing at what "explain" or "compare" means at each level. Instead of spending twenty minutes drafting an objective from scratch, you pull the relevant descriptor, swap in your content topic, and adjust the support level. That cuts the writing time significantly.

The real test of a language objective is simple: can you look at a student output after the lesson and tell, without ambiguity, whether the student met the objective? If the answer is yes, you wrote it correctly. If you need to interpret or guess, rewrite it.