Short answer: Build the budget so every number shows its working. Split income into fixed and variable, give each category an amount, record in the notes what that amount assumes, then compare the plan with one real month and change the assumptions that did not survive contact with your spending.
Set the ceiling and the take-home
Start with the two numbers that frame everything. The take-home is what lands in your account after tax, pension and deductions, and it is a fact you can find on a payslip. The ceiling is the most you will spend in the month, and it is a decision.
Do the ceiling after the take-home, never before. A ceiling set from a feeling about the month rather than from the money that arrives is how budgets end up aspirational. Leave a little back before you plan anything: that leftover is the buffer, and it is what keeps a bad month from becoming a crisis.
Write the buffer as its own node rather than folding it into savings. It changes how you read every other number on the map: a category that fits only if the buffer is spent is a category that does not fit. The complete Canvasola guide covers how to keep the map tidy as you build it.
- Take-home is a fact, ceiling is a decision
- The root names the month being budgeted
- The buffer is its own node, not folded into savings
- Nothing is spent until the take-home is written down
Note: A budget with no buffer is a budget that fails in the first month something goes wrong. If the buffer feels unaffordable, the ceiling is usually the number that needs lowering, not the buffer.
Split income into fixed and variable
Start with two branches on the map: fixed and variable. Fixed costs are the ones you have already agreed to, such as rent, loan repayments, insurance, subscriptions and a transport pass. Variable costs are the ones you decide week to week.
Check the fixed branch against the take-home before you plan anything else. If the fixed total takes seventy percent or more of what arrives, the variable plan is not a matter of taste, and the lever is the fixed side. Subscriptions are the usual surprise here: list them all at once, including the ones you forgot you had.
Add an irregular branch for the costs that land once a year, such as a car service, a dentist bill or a birthday. They are not fixed and not variable, they are annual, and treating them as either is how a month that looked comfortable turns out to be short.
- Fixed, variable and irregular are three separate branches
- Fixed costs are checked against the take-home first
- Subscriptions are listed as a group, not one at a time
- Annual costs get their own branch, never an average
Note: Utilities sit on the line between fixed and variable. Decide once where you put them and keep the rule, because moving them between branches every month hides the trend.
Give every category a number
Put the amount in the label so the map can be scanned: Groceries 450, Transport 120, Phone 35. One node per category, no nesting of categories inside categories, because a category with children stops reading as a number. If a category has sub-items, they belong in the note.
Work from the take-home down rather than from the categories up. Subtract the fixed total, then the buffer, then decide what is left to distribute across the variable categories. This order tells you immediately whether the plan is realistic.
Give each category a cap as well as a plan. The plan is what you expect to spend and the cap is the line you try not to cross, and the difference between the two is the small amount of control most budgets actually need. Press A to auto-arrange once the branches are in, so the layout stays readable as it grows.
- The amount is in the label, not only in the note
- One category per node, no category trees
- Work down from the take-home, not up from the categories
- Every variable category has a plan and a cap
- Auto-arrange with A after adding the branches
Note: Round the numbers. A plan built from round numbers is a plan you can change, and a budget with three significant figures per category spends its time on precision it does not need.
Record what each number assumes
This is the part a spreadsheet does not do for you. Open the rich note on the category node and write what the number assumes, using the bulleted list: 450 assumes 60 a week for a household of four. The notes guide explains the editor.
Cross-link the categories that share a cost. One payment for a car can cover fuel, parking and the school run, and a single subscription can cover two people or two services. Linking those nodes makes the double counting visible, and links work between any two nodes on the map.
Add the reason for the number as well as the working. A category that went up because of a medical bill is different from one that went up because a price changed, and the two need different responses next month. The assumption is the first thing you will want to challenge when you review the budget.
- Each note lists what the number assumes, one bullet per assumption
- Shared costs are cross-linked so double counting shows
- The reason for a change is recorded next to the number
- Notes are searchable, so an assumption is easy to find later
Note: An assumption written in August may be wrong by November. Put the date next to it, so a stale number is obvious before you rely on it.
See where the months run short
Add a totals branch under the root and give it a child for the planned spend, a child for the take-home and a child for the difference. The difference node is the one that matters: when it is negative, the plan does not work, and you see that before the month starts.
Convert the irregular costs to a monthly figure by dividing the annual amount by twelve, and put that number on the branch with the original amount in the note. Then look for the shortfall by category: which variable categories would have to shrink, and by how much. Doing the arithmetic on one node makes the trade-off concrete.
Re-run the layout after you adjust anything. Pressing A clears manual positions and re-runs the layout, so the totals branch stays where you put it and the categories stay in a sensible order. A map you can scan in five seconds is what makes the monthly check worth doing.
- A totals branch holds planned spend, take-home and the difference
- Annual costs are shown as a monthly equivalent
- The shortfall is traced to specific categories
- Auto-arrange keeps the totals branch visible after edits
Note: A negative difference is information, not a verdict. Sometimes the right answer is to move money between categories, and sometimes it is that the buffer was too small.
Review the budget after one real month
Give each category an actuals child next to the plan, and add a difference child where the two disagree. Do this once, a few days after the month ends, while the spending is still familiar. The pattern across every category tells you far more than any single category does, and it takes about twenty minutes.
Use search to work through it quickly. Ctrl/Cmd+F while the map is active looks through labels and notes, so you can find one category without hunting for it, and the ranked results let you move between matches. Review the categories you did not expect to be wrong first, because those are the ones that change the plan.
Change the plan, not just the numbers. Decide for each variance whether to cut the category, raise the cap, or accept it and adjust elsewhere, and write that decision in the note. The guide to keeping a map current covers the habit, and the fitness goal map applies the same review to a habit.
- Every category has an actuals child and a difference child
- The review happens once the month has ended, not during
- Search finds a category without hunting for it
- Each variance ends in a decision written in the note
Note: One month is not enough to judge a category. Two or three months show whether a variance was a one-off or the new normal, and the version history keeps 20 snapshots so you can see how the plan moved.
A checklist you can reuse
- The month being budgeted is named on the root
- Take-home, ceiling and buffer are all on the map
- Fixed, variable and irregular costs are on separate branches
- The fixed total is checked against the take-home
- Every category has a number in the label and a cap
- Every number has its assumptions listed in the note
- Shared costs are cross-linked between categories
- A totals branch shows planned spend, take-home and the difference
Common mistakes to avoid
- Budgeting from a wish. A ceiling set from how the month feels will be missed by the second week. Set it from the money that actually arrives, then plan inside it.
- Averaging annual costs away. Spreading a yearly bill across twelve months hides the month it lands. Keep irregular costs on their own branch and convert them deliberately.
- Numbers without assumptions. A bare amount cannot be challenged, so it just gets inherited month after month. Write what the number assumes in the note beside it.
- Double counting shared costs. A single payment often covers two categories and quietly inflates the total. Cross-link the categories that share a cost so it is visible.
- Rebuilding the map every month. Copying last month's budget and editing it loses the record of what you learned. Extend the map instead, so the variances stay on it.
Frequently asked questions
Should irregular costs go in the variable branch?
Keep them separate. An annual bill averaged over twelve months reads as affordable until the month it lands, and then it is a surprise. Put those costs on their own branch, show the original amount in the note, and use a monthly equivalent for the totals.
What if the difference is negative every month?
The plan is not realistic at the current take-home, and the fix is a structural one: cut a fixed cost, raise the take-home with more hours or more pay, or accept a smaller buffer. Trimming variable categories by a few dollars each month does not close a gap of a few hundred.
How do I keep track of a cost shared between two people?
Give the shared cost one node and cross-link it from each category that uses it, so nobody assumes the other person has counted it. The note on the node should say who pays what and when, which is the part that causes arguments.
Is a mind map better than a spreadsheet for this?
For the arithmetic, a spreadsheet is better and Canvasola does not replace one. For seeing which number rests on which assumption, and for keeping the reasoning next to the figure, a map with notes and cross-links is a better fit. Many people use both.
Give every number its working.
Open a map, set the take-home and the ceiling at the root, and give each category a number with its assumptions.
This guide is part of the mind map use cases collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.