Skip to content
Mise
← Back to Mise

Mise

How we work this out

Last reviewed 19 September 2026

Mise turns your plan into a shopping list and a rough read on nutrition. This page says how: what we count, what we leave out, and where the numbers can be wrong. It describes the app as it works today.

What this is

Mise plans meals. From the plan, it estimates what the food adds up to for each person and sets that against published daily reference intakes — protein, fibre, iron, calcium, B12 and the rest.

Targets come from one table per age band: toddler, two child bands, teen and adult. Sex, if you give it, changes only the calorie target. For an adult you can also choose pregnant, breastfeeding or weight loss, which moves calories and a few nutrients up or down.

  • It isn’t a food diary. Nobody logs anything, so Mise doesn’t know what anyone actually ate — only what was planned for them. We read the plan, not the plate.
  • It isn’t dietary or medical advice. The figures are directional: useful for noticing a pattern in the plan, not for judging how anyone is doing.
  • A clinician’s plan wins. If someone has a plan from a doctor, dietitian or allergist, it comes before anything here.

Who we think is eating

Each person has a home-meal schedule: which meals they eat at home on weekdays and at weekends, out of breakfast, a morning snack, lunch, an afternoon snack and dinner. New people start with every meal ticked. It’s on their card in Household, under Diet, allergies & meals.

Turn on Vacation for a week and everyone counts as home for every meal that week, whatever their usual schedule.

For a one-off — a night out, a meal everyone fends for themselves — mark the meal instead of leaving it empty: We’re eating out or Fend for yourselves in that meal’s add menu, or for a whole day from the day’s ⋯. We don’t shop or count a marked meal, and Plan my week leaves it alone. If just one person is out, untick them under Home for this meal (once a dish is on the meal, tap its people count); the dishes stay for everyone else.

A packed lunch you make counts

If you pack someone’s lunch from what you cook, leave their lunch ticked: it’s on the shopping list and counted toward their day. Untick a meal only when someone else feeds them — a school or work canteen, a nursery lunch, or a meal they regularly eat out.

Each meal stands for a share of someone’s day, and carries that share of their daily target:

Breakfast
25%
Lunch
35%
Dinner
30%
Each snack
5%

Who ate what

Nobody logs anything. For every planned dish, Mise works out who eats it from what you’ve already told it: who’s home for the meal, what they can eat, and what kind of dish it is. Each person eats their own portion size, set on their card.

  • Only lunch and dinner have mains. Each person is counted on the main their diet and allergies allow. A meat main and a tofu main at one dinner, with three meat-eaters and one vegan at the table: the vegan is counted on the tofu, the other three on the meat.
  • When two mains suit exactly the same people, nothing tells us who’d take which. So both are cooked for everyone and counted for everyone, rather than a guessed split — a little extra food beats a short dinner.
  • Sides, breakfasts and snacks go to everyone at the meal who can eat them.
  • Someone who’s home but can eat nothing at a meal isn’t counted for it. That meal leaves their numbers rather than reading as a gap.
  • Nobody is counted on a cooked dish whose required ingredients carry one of their allergens, or that their diet rules out. An allergen only in an optional line is left out of their portion instead (see Optional extras).
  • A store-bought item counts for whoever it’s added for: the one person you added it for, or everyone at that meal. The exceptions are an allergen Mise counts every version of it as having, or a diet none of its common versions fit — nuts in almond milk for a nut allergy, string cheese for a vegan. Either rules it out for that person, as a recipe would (see Store-bought items).

If the answer is wrong for a meal, tap the people count on it to see who’s eating what and set who eats a dish yourself — or put it back to automatic. Someone you put on one main is taken off the others at that meal. You can’t put anyone on a dish their allergy or diet rules out, or that needs something they never eat: it says why instead.

The shopping list, the nutrition figures and Plan my week all read this same answer, so they never disagree about who ate what.

What we compare it to

Only the meals you planned. Every meal planned for someone adds that meal’s share of their day to their target, and what the food carried to their total — so both sides of the comparison always come from the same meals.

  • A night out, or a day you haven’t planned yet, is left out. It isn’t counted as a gap.
  • A person is judged only once they’ve been given at least a day’s worth of meals. Until then you’ll see how many meals are planned for them, not a percentage.
  • Calories are shown per day’s worth of the meals planned, not per calendar day.
  • A weekly side adds to a meal someone was given; it never makes a meal count on its own.

A nutrient reads low when the planned meals carried less than 70% of what those same meals should. Sodium and saturated fat are limits rather than goals, so they’re flagged when they go over.

Watching a nutrient, and supplements

On someone’s card in Household, under Diet, allergies & meals, you can ask us to watch a nutrient for them or tell us they take a supplement for one. Both are optional, and we store which nutrient and nothing else.

  • A watch pins that nutrient to their rows on the Nutrition page, this week’s and the four-week view’s, marked “watched”. It never changes a target, or the point where something reads low or over.
  • A supplement stops that person’s low flag for that nutrient and marks it “supplemented”. Their row still shows what the food alone carried: we add nothing to their intake, because we don’t know the dose.
  • It’s that person’s flag only. The household figure stays everyone’s food, and if the meals planned for anyone else ran low on it, that’s still flagged.

What we can’t score

Store-bought, packaged food counts for calories, protein, carbs, fat, saturated fat, fibre and salt only — what a label reliably lists. The rest of its label is unknown to us, which isn’t the same as zero.

  • A meal of only packaged food doesn’t count toward vitamins or minerals at all. It adds no iron target and no iron, so it can’t make iron look low or high.
  • Beside a cooked dish, a packaged item adds its calories and macros but nothing to vitamins or minerals, so that meal can read a little low on them.
  • A dish with no nutrition data counts for nothing either way.
  • When nothing planned carries a nutrient, it reads “not measured” — never low, never 0%.
  • Vitamin D barely occurs in food, so it reads low in almost any week. That says more about food than about your plan.

Why a month, not a week

Nutrients even out over weeks, and one busy week shouldn’t turn into a warning. So the Nutrition page also has a four-week view for each person: one ratio across this week, up to today, and the three weeks before — everything their planned meals carried, against everything those same meals should carry.

  • It gives a verdict once 12 of a person’s meals have carried that nutrient — about 3 a week. Snacks add to the ratio but don’t count toward the 12. Until then it says “not enough information yet”.
  • Only days up to today count. Meals planned for later this week join on their day.
  • Calories aren’t in it: they belong to the week view. Nor are vitamin D (it would read low for everyone, always) or saturated fat, unless you’ve asked us to watch them for someone — or told us they take a vitamin D supplement.
  • Each week also gets a small cell. A hatched one means that week had fewer than 3 meals carrying the nutrient — too few to say anything about it.
  • on track
  • low
  • over
  • too few meals that week
  • supplemented, not flagged

Allergies

Mise tracks 11 allergens:

  • dairy
  • egg
  • gluten
  • soy
  • nuts
  • peanuts
  • sesame
  • fish
  • shellfish
  • celery
  • mustard

Lupin and sulphites, both regulated allergens in the UK and EU, aren’t among them.

Labels only ever widen

A recipe’s allergen label combines what its author declared with what its ingredients imply, sub-recipes and optional garnishes included. A line we don’t recognise adds nothing to it. Your household’s version of a library recipe can add to its label but never take anything off.

When it depends on the brand

Some ingredients come in versions with different allergens: plant milk, stock, vegan butter, bread, kimchi and others — 45 in all. For these:

  • If a product we know of suits everyone’s allergies, we name it on the recipe and put it on the list: plant milk becomes soy milk when someone has a nut allergy.
  • If none does, the recipe and the list say what to look for (“get a nut-free one”), and the person with that allergy sees “Check label” instead of a clean “Can eat”.
  • Either way the recipe stays plannable. We can’t see the brand you buy, so read the label.

What we buy

Under What we buy in Household, you can tell us which version you actually buy. That changes the shopping list. It never changes who Mise treats as able to eat a dish, and if the product you pick has an allergen someone in the household can’t have, we stop using it until it’s changed. Only the household owner can set these.

Optional extras

If someone’s allergen is only in an optional line — pine nuts to garnish — the dish can still be planned for them, and the recipe says to leave it out. We only do this when no required ingredient could carry that allergen, including ones whose allergens depend on the brand; otherwise the dish is off for them. The label still lists the allergen, and your own saved version of a recipe is never relaxed this way.

Store-bought items

The common ready-made items (bread, oat milk, peanut butter…) carry the allergens and the diet a typical product has. An allergen Mise counts every version as having — nuts in almond milk, sesame in bread (most loaves have it or may) — rules the item out for that person, like a recipe. So does a diet none of its common versions fit: string cheese for a vegan. Something that depends on the brand — egg or dairy in some breads — says check the label, and the shopping list says what to pick (“get a nut-free one”). Branded items you search for carry what Open Food Facts lists: an allergen it lists rules the item out, and everything else still says check the label, because a crowd-sourced list can miss things.

Read every label, every time

For a branded item we pass on what Open Food Facts lists as “may contain”; beyond that we don’t model cross-contact, in a factory or in your kitchen. A common item carries what a typical product has, not what’s in the one you buy, and a crowd-sourced list can be incomplete. And a product can change its recipe without us knowing.

Branded product data comes from Open Food Facts and is used under the Open Database License. The product data we've cached from it is available under the same licence — ask through the contact page.

Dislikes and “never”

  • A dislike warns you. It never takes a dish off anyone’s meals, and they’re still counted as eating it.
  • “Never” is firmer. Plan my week and suggestions won’t put a dish that needs that ingredient on a meal that person is at. You can still add one yourself, and if you do, they aren’t counted as eating it.
  • If the ingredient is only an optional line, the dish is fine — the recipe says to leave it out for them.
  • You can set a “never” for one person or for everyone in the household.
  • “Never” matches the ingredient as the recipe writes it, not what one of your swaps replaces it with.

How wrong can these be

By a fair amount. The figures are good for spotting a direction in the plan, not for measuring anyone.

  • Recipe amounts are written by hand. Where a recipe says “1 onion” rather than grams, we estimate the grams.
  • Cooking losses are modelled, but roughly — boiling costs more vitamin C than steaming, for example.
  • Food databases disagree with each other, sometimes by a lot, and no two onions are the same.
  • Vitamin and mineral targets follow age, not portion size. Setting someone’s portion to 1.5× raises their calorie target but not their iron target, so a big eater reads a little high on vitamins and minerals and a small eater a little low.
  • The four-week view is worked out fresh from today’s household settings. Change someone’s age band, schedule, diet or allergies and the last month is re-read as if that had always been true.

So read every figure as a direction, not a measurement. If one worries you, a doctor or dietitian can tell you far more than this page can.

Something here doesn’t match what you see in the app? Tell us.

Back to Mise