Planning kids' snacks so they stop being an afterthought

Snacks are the meal nobody plans

Every household with children eats three meals a day and buys for four. Snacks are the ones nobody writes down: they are not on the plan, so they are not on the shopping list, so the shopping is wrong, so the 4pm decision is made by whoever is hungriest, standing in front of an open cupboard. That is the whole problem, and it is a planning problem rather than a cooking one.

A weekly snack plan for kids fixes it in four steps. Decide how many snacks a day your household actually has. Build a short after-school snack rotation of assembled snacks rather than recipes — crackers, cheese and apple slices is a snack, not a dish with instructions. Put the rotation on the plan so the shopping list buys for it. Then adjust the single days that are different, because there is a party on Wednesday and a late pick-up on Friday.

The rest of this guide is that method, and how each step works in Our Table Tonight. The advice about what children eat is deliberately general: this is about planning, not nutrition.

Step one: decide how many snacks a day you actually have

Count honestly rather than aspirationally. Most families with school-age children have one after school and something small after tea; younger children often have one mid-morning as well. The number matters because it is what turns snacks from an invisible category into a countable one. Two snacks a day for two children is twenty-eight snacks a week, and twenty-eight of anything is worth buying deliberately.

In the app, that number is a setting rather than a habit. Your profile has a default number of snack slots per day, and if you plan in a household, the household's own setting takes precedence over your personal one. Whatever the number, the planner draws that many snack slots on every day of the week, next to breakfast, lunch and dinner.

The slots are the point. An empty snack slot on Tuesday is a visible gap in the same way an empty dinner is, and the week's progress counter — “X of Y slots filled” — counts them. If you have never planned snacks before, the first thing you will notice is that the week you thought was fully planned is about two-thirds planned.

Step two: build a rotation, not a recipe book

The mistake is treating snacks like small dinners. A snack is usually assembled, not cooked: it has components and no method, and writing it out as a recipe with steps means inventing instructions nobody will ever read. What you want is a short list — five or six — that you cycle through, so the decision each afternoon is which one of six rather than what on earth.

Aim for a rotation you can actually shop for. A few rules that hold up in practice:

• Keep it short. Six options is enough for a fortnight without repeating twice in a week, and short enough that the ingredients overlap and nothing rots.
• Prefer components that appear in more than one option. Cheese that is in three snacks gets bought once and used up.
• Include at least one that survives a bad day — the option that needs no fridge, no slicing and no adult.
• Let the children pick two of the six. A rotation nobody agreed to is a rotation you argue about every afternoon.

Packs: the natural shape of a snack

The app has a form for exactly this. A pack is a title and a list of items with no instructions: “After-school plate” — crackers, cheese, apple, a handful of grapes. Quantities and units are optional on each item, because “yoghurt” needs no number and “2 oatcakes” does. You can tag a pack with the meals it suits, so a snack pack is tagged snack and turns up when you are filling a snack slot.

Build them from the packs page, or without leaving the planner: the slot assignment window has a Build Pack tab, so an option you improvised on Tuesday becomes a saved pack in about thirty seconds. The packs page lists your own packs and any shared into a household you belong to, which matters when the person making the snack is not the person who thought of it.

Snacks that really are cooked — flapjacks, a batch of muffins — stay ordinary recipes with prep and cook times. The recipe form also has a “Kid friendly” tag, which is worth setting as you go: it is a fact about the dish that is easy to record once and impossible to reconstruct later from memory.

Step three: put the rotation on the plan

Now assign them. Filling a week of snack slots from a rotation of six takes a couple of minutes, and it is the step that makes the shopping right. Snack slots are ordinary slots: they take a recipe or a pack, they take a servings override if three children are eating rather than one, and they can be marked as eat-out or leftovers when the snack is a bag of crisps at the swimming pool.

Two things follow automatically once they are on the plan.

The shopping list buys for them. Generate the list for the range you are shopping for and the app collects the ingredients from every assigned slot in that range — snacks included — scales them by any servings overrides, merges duplicates so the cheese in three snacks becomes one line, and groups everything by category. That single merged line is the difference between buying enough cheese and buying cheese three times.

The allergen check runs on them. When you assign something to a slot in a household plan, the app compares the allergen tags recorded on that item against the allergens each member of the household has recorded, and flags a match with an amber badge naming the person. A snack slot is checked exactly like a dinner slot. One caveat worth knowing: the check reads recorded tags, and a pack built in the pack builder records its items but not allergen tags, so it will produce no warning. Silence means no information rather than a clear result — the same rule as anywhere else in the app.

Step four: adjust the days that are different

No week has the same shape every day, and this is where a rigid plan usually dies. The planner handles it per day rather than per week: each day has an “Add snack” button and a way to remove a snack slot, and doing either affects that day only. Wednesday with a party gets no after-school snack; Friday with a late pick-up from football gets two; the rest of the week keeps the default.

That is worth doing rather than leaving a slot empty and mentally noting it. An adjusted day reads correctly to everyone else in the household, and the progress counter stops nagging about a slot that was never going to be filled.

After a fortnight

Mark the meals at the end of each week — Made, Didn't Make, and optionally a rating out of five. Snack slots are in that list with everything else, and only Made writes to your cook history, so after a fortnight each recipe shows how many times you have actually prepared it.

Read that before you rebuild the rotation. It will tell you which two of your six options are doing all the work and which one you have planned four times and made once. Drop the one nobody eats, keep the rest, and the rotation gets better without anyone having to remember what happened three weeks ago.

1. Set the number of snack slots a day in your profile or household settings.
2. Build five or six packs with overlapping components; tag them snack.
3. Assign them across the week's snack slots.
4. Generate the shopping list for the range you are shopping for.
5. Add or remove a snack on the days that are different.
6. Mark the week made, and drop whichever option nobody ate.