How to Design Preschool Thematic Units That Actually Teach Something

A “Dinosaurs” week looks wonderful from the doorway. Children are painting fossils, roaring at each other during free play, sorting plastic dinosaurs by size. By Friday, every child can name a stegosaurus. Far fewer of them have counted anything, sequenced anything, or practised a new sound during the week the theme filled the room, but it didn’t carry the curriculum through it.

This is the gap how to design preschool thematic units actually has to close: a theme that generates excitement isn’t automatically a unit that generates learning. The two get confused constantly, and the confusion is expensive a term full of memorable weeks that don’t add up to measurable progress.

What Makes a Theme Into a Designed Unit

A theme is a subject children find engaging dinosaurs, weather, community helpers, the ocean. A designed unit is that theme deliberately attached to specific objectives across language, math, science, social-emotional learning, creative arts and physical development, with a way to see whether each objective landed. The theme is the container. The unit is what’s actually inside it.

That distinction matters because a container can be full of the wrong thing. A “Dinosaurs” unit can spend four days on vocabulary and craft and never touch counting, sorting, or a science question a four-year-old could actually investigate sizing dinosaurs, comparing footprints, predicting what a “big” one eats. The theme was strong. The unit design wasn’t.

Decorative Theme vs Designed Unit

A decorative theme starts with an exciting topic dinosaurs, the ocean, community helpers and builds activities around whatever fits naturally, which usually means language and art absorb the week while the rest gets whatever time is left. A designed unit starts the same way on the surface, with a topic, but it’s chosen alongside the domain objectives it needs to carry, so every activity earns its place because it teaches something specific through that topic rather than just decorating it.

The difference shows up most clearly in domain coverage and in evidence. A decorative theme touches whichever domains happen to suit it usually language and creative arts, sometimes only glancingly. A designed unit deliberately represents language, math, science, social-emotional learning, creative arts and physical development, even if not equally, because each one was accounted for when the unit was planned rather than left to chance. Evidence follows the same pattern: a decorative theme tends to leave a finished craft and a happy week as its only proof that anything happened, while a designed unit ties its evidence to a stated objective in at least two or three domains, so there’s something more specific to point to than enthusiasm.

By the end of the week, that gap is what children actually carry forward. A decorative theme leaves them remembering the topic. A designed unit leaves them remembering the topic and able to do something they couldn’t do the week before.

Start From the Objectives, Not the Topic

The most reliable fix is to reverse the usual order. Instead of picking a topic and then hunting for activities to fill it, start with the objectives the week needs to carry a counting skill, a phonics focus, an SEL goal, a scientific observation and then choose the theme that gives those objectives the most natural home. “Seasons and Weather” isn’t just a nice topic; it’s chosen because it can genuinely carry sorting, cause-and-effect reasoning, and vocabulary growth without forcing any of it.

This only works if a unit is designed with the theme already chosen through the process covered in [Blog 32 ] how to choose themes for an early years curriculum a theme picked well gives the objectives somewhere to sit naturally; a theme picked purely for novelty makes every objective feel bolted on.

Keep Every Domain Present, Not Just Decorated

The easiest domains to lose inside a theme are the ones that don’t photograph well early numeracy, in particular, tends to shrink into “count the dinosaurs” and stop there, while language and art absorb most of the week. A designed unit checks this deliberately: does the theme carry a real math objective this week, not just a counting prop?

Does it carry a science question a child can actually investigate, not just a fact to memorise?

If a curriculum keeps producing units that are heavy in some domains and thin in others, [Blog 31] balancing learning domains in preschool curriculum is worth checking against a single unit can look balanced on its own and still be part of a term that consistently shortchanges the same domain every time.

If a theme can’t carry a genuine objective in a domain without being forced, is that a sign the domain needs a different theme this term, or a sign the domain needs its own dedicated time outside any theme at all?

Sequence the Unit, Don’t Just Fill It

A designed unit also has a shape across its days, not just a list of activities. A workable sequence usually moves through introduction (a visual, a story, a question to notice), exploration (hands-on activity tied to an objective), application (using the new skill somewhere slightly different a game, a role-play, a real object), and reflection (a simple way for children to show what changed). Activities dropped in randomly across the week tend to repeat the same skill in different costumes rather than building anything.

This sequencing question connects directly to how units stack across a whole programme. A single well-designed week means little if the unit after it doesn’t build on it which is the territory covered in [Blog 33] how to structure a three-year preschool programme.

Decide What Counts as Evidence Before the Unit Starts

If a unit is genuinely carrying objectives, it should be possible to say before the week even begins what evidence would show each objective was met. Waiting until Friday to figure out what to look for usually means falling back on the craft table as the only proof of learning, which mostly proves a child can use scissors.

Two upstream pieces make this easier to plan for: [Blog 5.1] aligning preschool assessment with learning objectives for tying each domain objective to something observable, and [Blog 6.1] collecting evidence of learning through play for capturing it without turning the unit into a test.

Where KODEIT Pre-K Fits

Every KODEIT Pre-K level runs on six themed Student Books, and each one carries a named significance before a single activity is planned “Seasons and Weather” is built to develop environmental awareness, “Numbers and Shapes” to develop early math skills, and so on, so the theme is never the whole plan, just the entry point into it. The accompanying Practice Books are deliberately designed per unit rather than per lesson, so English, Mathematics and Science practice reflects the same theme without repeating the same single activity all week a structural way of making sure a theme doesn’t quietly crowd out the domains that need more than one afternoon to land.

FAQs

What’s the difference between a preschool theme and a thematic unit?
A theme is the topic children find engaging dinosaurs, weather, the ocean. A thematic unit is that topic deliberately connected to specific objectives across language, math, science, SEL, creative arts and physical development, with evidence planned in advance to show whether each objective was met.

How many domains should one thematic unit actually cover?
There’s no fixed number, but a unit that only ever touches language and art leaving numeracy, science or SEL as an afterthought usually signals the theme was chosen for novelty rather than designed around a full week’s objectives.

Should the theme or the objectives come first when designing a unit?
The objectives should come first, even though the theme usually gets chosen and announced first. A theme selected because it can naturally carry that week’s objectives holds up far better than objectives forced to fit a theme picked purely for its appeal.