Open any textbook and you will see chapters. Open a good teacher's planner and you will see units. The difference matters: a chapter is a chunk of content, written by an author who never met your students. A unit is a teaching plan built around what your students need to learn, in what order, with what practice, checked how. Unit planning is the step that turns a chapter into learning — and teachers who plan by unit find that their lessons hang together, their assessments make sense, and their students retain far more.
This guide walks through unit planning step by step, using backward design: decide the destination first, then the evidence, then the route. It ends with a worked example from a Class 8 Islamiat unit and the mistakes that most often derail a good unit.
What a Unit Is — and Why Chapters Need Planning
A unit is a coherent block of teaching, usually two to four weeks long, built around one theme, skill set, or question. It may match a textbook chapter exactly, or it may combine parts of two chapters, or split one long chapter into two units. The unit, not the chapter, is the right planning grain: it is long enough to build real understanding and short enough to plan in detail and assess properly.
Chapters need planning because textbooks are written for coverage, not for your class. A chapter may open with the hardest idea, bury the key skill on page twelve, or include material your board's syllabus does not require. A unit plan re-sequences the content for learning: it puts the foundation first, adds practice where students typically struggle, drops or shortens what is peripheral, and adds what the textbook leaves out — local examples, vocabulary work, or a skill the syllabus demands but the chapter under-serves.
A unit plan also gives students something a chapter-by-chapter march never does: a sense of where they are going. When students know the unit's goal — "by the end of these three weeks you will be able to..." — they can judge their own progress, and the teacher can keep the class oriented. A unit that opens with its goal and closes with a check on that goal feels purposeful; a unit that just starts on the next page feels endless.
Backward Design: Start at the End
Most teachers plan forward: read the chapter, decide what to teach each day, then write a test at the end. Backward design reverses the order: decide what students should be able to do at the end, design the assessment that will prove it, then plan the teaching that gets them there. The difference is like the difference between driving with a destination and driving until you run out of road. Forward planning produces lessons that cover content; backward planning produces lessons that build competence.
Backward design is especially valuable in Pakistani classrooms because it forces the hard question early: what does the board actually assess for this unit? If the board exam asks students to solve problems, the unit must be full of problem-solving practice, not note-copying. If the exam asks for explanation in Urdu or English, students must practise explaining in that language during the unit. A unit planned backward from the assessment never surprises students with a test on skills they never practised.
The process has three steps, and they must be done in order: objectives, assessment, activities. Teachers who skip ahead to activities — the fun part — usually end up with lively lessons that do not add up to the goal. Discipline about the order is the whole method.
Step 1: Objectives — What Students Will Be Able to Do
Write three to six objectives for the unit, each a skill a student can demonstrate. Use observable verbs: solve, explain, identify, compare, write, recite, translate, construct. One objective should be the "spine" — the central skill the unit exists to teach — and the others should support it. For a unit on fractions, the spine might be "solve word problems involving addition and subtraction of fractions"; supporting objectives cover finding common denominators, simplifying, and converting between mixed numbers and improper fractions.
Check the objectives against three sources: the board syllabus and textbook (what is required), the previous unit (what students already know), and the next unit (what this unit must prepare them for). An objective that fails any of these checks is suspect — either it is not required, or it assumes knowledge students do not have, or it leads nowhere. Also write the objectives in language students can understand, and share them on day one. A unit whose goals are secret from the students is a unit the students cannot aim at.
For classes with wide ability ranges, note a core and an extension level for the spine objective: what every student must reach, and what the strongest students will reach beyond it. This one note makes differentiation later almost automatic.
Step 2: Assessment — How You Will Know
Before planning a single activity, design the end-of-unit assessment. What task will prove the objectives are met? It need not be a formal test: it can be a set of problems, a written paragraph, a recitation, a presentation, a practical demonstration, or a combination. The key is that every objective has at least one assessment item, and every assessment item matches an objective. An assessment that tests something never taught is unfair; an objective never assessed is decoration.
Also plan the checkpoints during the unit: a short quiz after the first week, a homework task that samples the spine skill, a quick oral check in each lesson's closing minutes. Checkpoints catch misunderstanding early, when it is cheap to fix. A unit with no checkpoints discovers failure only at the end, when it is too late.
Write the marking expectations now, not after the test. For a written task, decide what a good answer looks like — two or three bullet points of what it must contain. For a problem set, decide which errors matter most. This takes ten minutes and makes marking faster, fairer, and consistent across sections. When assessments are agreed in advance, teachers in parallel sections can share them, and the exam schedule stays free of last-minute surprises.
Step 3: Activities — Sequenced Week by Week
Only now, with objectives and assessment fixed, do you plan the teaching. Sequence the unit in three phases. Week one — foundation: introduce the core ideas in small steps, with heavy teacher guidance, worked examples, and short practice. Students should leave week one able to do the basics with support. Week two — practice and extension: guided practice gives way to independent and pair work, harder examples, and the tricky cases where students typically stumble. This is where misconceptions get found and fixed. Week three — application and review: students apply the skill to new problems, mixed practice, past-paper-style questions, or a small project — then revise and sit the end-of-unit assessment.
For each lesson in the sequence, note the textbook pages, the activity, the materials, and the homework — a line or two each is enough, since the daily lesson plan carries the detail. Build in two specific things teachers often forget: a vocabulary list for the unit (terms students must know, in the language of instruction), and a "common errors" note — the three mistakes students always make in this unit, with the correction planned in advance. Both come from experience, and writing them down means next year's teacher inherits them.
Also plan the resources honestly. If the unit needs lab equipment, charts, printed worksheets, or a guest period, book them when the unit is planned, not the day before. Booking shared resources is easier when the unit plan sits alongside the school's timetable. A unit plan that assumes resources that are never booked is a plan that collapses in week two.
The Backward Design Check
A Worked Example: Class 8 Islamiat Unit
Consider a three-week Class 8 Islamiat unit on the Seerah — the life of the Prophet (peace be upon him) in the Makki period. Objectives: students will be able to (1) sequence the key events of the Makki period in order, (2) explain two challenges faced by the early Muslims and how they were met, (3) extract one moral lesson from each event and express it in their own words. Assessment: a written task — a timeline with five events in order, plus two short paragraphs explaining one challenge and one lesson — and an oral question in class for students who express themselves better aloud.
Week one (foundation): storytelling lessons with a wall timeline built lesson by lesson; students copy and complete the timeline; key vocabulary (terms such as Hijrat, boycott, revelation) explained and written in notebooks. Week two (practice): pair work — each pair prepares a two-minute retelling of one event; teacher-led discussion of the challenges and responses; short written answers practised with a model paragraph. Week three (application): students connect events to lessons for daily life, revise from the timeline, and sit the written task. The unit's assessment matches its objectives exactly, and every lesson visibly builds toward it.
Notice the shape: the unit does not just "cover" the chapter. It chooses what students will be able to do, checks it, and sequences the teaching to get there. The same shape works for a Science unit on simple machines, a Maths unit on fractions, or an English unit on letter writing.
Common Unit Planning Mistakes
Too many objectives. Eight objectives for a two-week unit means none gets taught properly. Three to six, with one spine. Assessment as an afterthought. A test written the night before rarely matches the objectives; write it when the unit is planned. No checkpoints. A unit with no mid-unit quiz discovers failure at the end. Planning activities before objectives. The fun activity that teaches nothing is the most expensive mistake in unit planning — it spends a period and returns nothing. Ignoring the textbook's gaps. If the chapter under-serves a syllabus skill, the unit must add material; see our companion thinking on curriculum gaps in the wider school planning picture, and keep a note in the unit plan of what was added so next year's teacher does the same.
Start with one unit. Pick the unit your students struggle with most, plan it backward, teach it, and compare the results with last year's. When the assessment shows stronger learning — and it usually does — the method sells itself to the rest of the staff. One good unit is the beginning of a planning culture.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you break a textbook chapter into a three-week unit — a spine objective, supporting objectives, a draft end-of-unit assessment, and a week-by-week activity sequence — that you can adapt for your class.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.