A line of text is not a story
In a list of transactions, each entry occupies one row: a date, a merchant, an amount. It is easy to glance down the column and decide that something was wasteful. But a row hides everything that explains it. Was it planned? For whom was it? What did it replace? Without context, judgement is guesswork.
A short list of questions fills in the context. Use them on the transactions that stand out, not on everything.
Think of this as the difference between reading a headline and reading the article. The headline is quick but easily misleading, and a couple of minutes of context usually turns a vague suspicion into either a clear fix or a clear all-clear.
The ten questions
- **Was this planned?** A planned purchase and a surprise are different problems.
- **Who was it for?** Spending on others reads differently from spending on yourself.
- **Is it a one-off or a pattern?** Look for the same merchant earlier in the month.
- **Did it replace something else?** A takeaway may have replaced a larger grocery run.
- **Is the category right?** Misfiled items make the picture misleading.
- **Was the price normal?** Compare with the last time you bought something similar.
- **Was it used or enjoyed?** Some purchases pay back, others do not.
- **Was it needed at that time?** Timing sometimes explains a high cost.
- **Would it be chosen again?** An honest answer shows whether it was worth it.
- **What would change next time?** The practical outcome of the review.
Not every question applies to every transaction. Pick three or four that fit.
A worked case
Take a 2,600 charge at a home goods store. At first glance, it looks like an indulgence. Run the questions. It was planned, since a kitchen item had broken. It was for the household, not for personal treats. It was a one-off. It replaced a repair that would have cost nearly as much. The category was filed as “shopping”, but it fits “home upkeep” better. Would it be chosen again? Yes. The charge has gone from suspicious to sensible, with one fix: the category.
Where the questions help most
- On large single payments that dominate a category.
- On small payments that repeat frequently.
- On items you do not remember buying.
- On transactions that provoke a flash of regret.
In each case the aim is understanding. Sometimes the answers show a real leak; sometimes they show a perfectly good decision wearing a misleading label.
| Question result | What it suggests | Action |
|---|---|---|
| Planned, useful, normal price | A sound purchase | Leave as is |
| Unplanned, not used | A possible leak | Add a rule or a pause |
| Wrong category | Data problem, not spending problem | Correct and teach the app |
| Price much higher than last time | Possible overpayment | Compare options next time |
Keep notes
When a question leads somewhere useful, write a note on the transaction. “Replaced repair, good call” or “Check price next time” will make your future reviews quicker and richer. Over a few months, the notes form a personal record of what you learned.
Avoid interrogating everything
It is not necessary, or kind, to question every row. Doing so would turn a review into an ordeal. Focus on the few lines that matter. Everything else can be left alone.
Fix what the answers reveal
Often the result of the questions is a small administrative correction. Fix categories, merge duplicates, and clear up merchant names. Better data makes the next review easier, and the improvement compounds.
A last thought
Judgement is the end of a process, not the beginning. By asking first, you give each transaction a fair hearing, and you give yourself a better basis for changing what truly deserves changing.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


