An invisible line in the budget
Money spent on food that is later thrown away never appears as a category. The bank statement shows the purchase, and the bin hides the outcome. Nothing in the records connects the two. A two-week audit makes the missing line visible, and the result tends to surprise even careful households.
The audit is a measurement, not a punishment. It needs only a pen, a note on the phone or a space in the app.
How to run the audit
For fourteen days, every time edible food is discarded, write down what it was, roughly how much, and why. Reasons are as useful as quantities. Typical reasons include:
- Cooked too much.
- Forgot it was in the fridge.
- Spoiled before use.
- Bought for a recipe that did not happen.
- Plate leftovers nobody wanted.
Do not count peels, bones or items that were never edible. The audit is about food that could have been eaten.
Putting a price on it
Estimate each item’s value from what it cost to buy. Half a bunch of greens might be 15 units, two rotis 6, a bowl of rice 20, half a loaf 25. Add the figures at the end of the fortnight. Say the total is 410 units. Over a month, that suggests roughly 880, and over a year around 10,700 units, with the usual caveat that two weeks may not represent the whole year.
| Reason | Share of total waste |
|---|---|
| Cooked too much | about 35% |
| Forgotten in the fridge | about 30% |
| Spoiled before use | about 25% |
| Other | about 10% |
An analysis like this tells where to focus. If most waste is from cooking too much, portion sizes are the target. If it is from forgetting, a fridge shelf for “eat first” items may fix half of it.
Matching fixes to causes
Each cause has a cheap fix:
- Cooking too much: measure rice, dal and similar items with a cup for a week and note the amount that is eaten.
- Forgetting: keep a small box at eye level for items that need to be used soon.
- Spoiling: buy smaller amounts of fast-perishing items, or freeze a portion at the time of purchase.
- Unused recipe ingredients: check the pantry before adding anything to the list.
Pick one fix to try for the next two weeks, not all of them. A single change, tested properly, is more informative than a general resolution.
Recording it in the app
The waste estimate does not belong in the transaction list, because no money moved. A better home is the notes on the monthly review or a recurring reminder that asks, once a month, “How much food was wasted this month?” Writing the figure in the same place each time builds a trend. If the number falls, so does the effective cost of every grocery trip.
The payoff
Reducing waste by even a modest share reduces grocery needs without anyone eating less. It is among the few savings that require no sacrifice at the table, only attention at the edges of the day, and it is possible to measure the effect with the same audit repeated a few months later.
Involving the people who cook
Waste figures are most useful when the people cooking and serving see them. A short conversation, sharing the fortnight’s total and the main causes, usually produces practical suggestions that no spreadsheet would: smaller serving bowls, a standing day for leftovers, a shared view of what is in the fridge. The numbers are the starting point for a conversation, and the conversation is where change actually happens.
Repeat the audit after a few months to check progress. A second measurement is the only real proof that a change worked.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

