A wedding planning mind map that starts with budget

Set the budget before the guest list

A wedding spends money in the order you are tempted to spend it, and the venue comes first every time. A budget set after the guest list is always a larger number, because the guest list pushes the venue up and the venue sets the ceiling on everything else. Put the total in the root node as a number, with the date beside it.

Then add one branch per spending category: venue and catering, outfits, flowers, photography, music, travel, stationery, and a contingency. Each branch carries one number and a note recording what that number assumes, such as "80 guests, Saturday, service for six hours". A number with its assumption beside it is a decision you can revisit later, while a number on its own is only a hope.

• The total sits in the root node with the date
• One branch per category, one number per branch
• Every number has its assumption in the note
• Contingency is a branch, not the leftover

Split the day into its moving parts

A wedding is not a list of tasks, it is a set of workstreams running in parallel: getting ready, ceremony, reception, travel between sites, flowers and decor, food and drink, photographs, and the guests themselves. Give each workstream a branch, and under it the tasks in the order they happen, so the map shows the shape of the day instead of the size of the to-do list.

Move related workstreams onto their own layers as the map grows. Layer tabs scope the map to a single layer, so you can work on flowers for an hour with the timeline out of the way, and one map can carry the budget, the vendors, the schedule and the guests separately. The 3D layer stack goes further and places each layer on its own depth plane, with up to eight layers in one map. The layers guide covers both views.

• One branch per workstream, not per vendor
• Keep related workstreams on separate layer tabs
• Order the tasks inside each branch
• Aim for a map you can hold in your head

Assign an owner to every branch

Put the contact details in the rich note of the branch: the name, the phone number, what they have agreed to own, and what they need from you. The note supports bold, italic, underline, bulleted and numbered lists and a button for links, so a list of decisions and dates fits neatly inside it.

Name a second person for the branches that cannot fail, because on the day the person holding the plan for the cake may be the one stuck in traffic. A second name in the note costs five seconds and removes the most common cause of a wedding-day scramble.

• One person named per branch, never a pair
• Contact details and agreed scope go in the rich note
• Name a backup for every branch that cannot fail
• A branch with no name is a branch nobody is doing

Track vendors and deposits

Give each vendor a node holding the name, the price agreed, the deposit and the date it was paid, the balance and the date it falls due, and the date you signed. The deposit dates are the ones that cause the panic, because they arrive whether or not you are ready for them. Write them as dates rather than as "paid" so the map can be read in date order.

Use color for the state of each vendor node: one color for paid, one for deposit due, one for awaiting a reply. The palette is eight Coggle-style colors with a row of recent colors underneath, so the colors you use most stay one click away, and the first child of a branch inherits the parent color while siblings cycle through the palette. Checking the map for a color is faster than reading every note.

• One node per vendor with price, deposit and dates
• Color marks paid, due and awaiting a reply
• The note records the file name of the contract
• A node image holds a photo of a receipt

Watch the countdown to the day

Add a countdown branch where each child is a dated task, from three months out to the week before. The order is what makes it work: a task with a date can be late, while a task on a list of intentions never fails. Put a note on each date node for the two or three things that have to be true before the next milestone, so a slipped booking is visible early rather than on the day.

Review the countdown at a fixed rhythm, once a week, and make each review a pass over the map. Use Ctrl/Cmd+F to search for a vendor name, a place or a month, and the results are ranked so you jump straight to the node. Search only runs while a mind map is the active tab, so switch to the map before you search rather than wondering why the shortcut does nothing.

• One dated node per task, in a countdown branch
• A task with a date can be late, an intention cannot
• Search for a vendor before each weekly review
• One current map instead of a message thread

Keep a day-of timeline on the same map

The last branch is the day itself, written as times: 08:00 hair and makeup, 13:00 first look, 14:30 ceremony, 15:30 drinks, 18:00 dinner, 23:00 last dance. Give every time a child holding the location and the owner, because a time without a place is only half an instruction. A day planned as times rather than tasks is the same idea as the travel itinerary map, where each branch is a day.

Put this branch on its own layer so the budget layer stays clean, and it works where the signal does not: the document autosaves locally, so the timeline is on the device in your pocket at a venue with no reception. The offline guide explains how to check that behavior before you travel, which is a five-minute job with a long payoff.

For the day itself, collapse everything except the timeline. The chevron on a node collapses a branch, and Collapse All reduces the map to the root and its branch labels, so you can collapse the budget branches and leave one clean column of times on screen. The collapsing guide covers the controls, and exporting the timeline as a PNG gives anyone who wants a paper copy something to print.

• One node per time, with the location and owner
• The timeline lives on its own layer
• Collapse the budget branches, keep the times
• Export the timeline as a PNG for a paper copy

Note: The map records what you write and nothing more. It has no reminders and no payment tracking, so a deposit date is a date you read, not a notification you receive.

A checklist you can reuse

• The root node holds the total budget and the date
• Every category branch holds one number and the assumption behind it
• The contingency is a branch with a fixed percentage
• Each workstream is a branch, and the big ones sit on their own layers
• Every branch has a named owner, and the critical ones have a second
• Each vendor node records deposit paid, balance due and both dates
• The day-of timeline is written as times with a location and an owner

Common mistakes to avoid

• Setting the budget after the guest list. The guest list pushes the venue up and the venue caps everything else. Fix the number first, then let the list fit inside it.
• Leaving branches without an owner. A branch with no name is a branch nobody is doing, and nobody is what it looks like on the week of the wedding. Name one person per branch.
• Marking deposits as paid. "Paid" cannot be read in date order and does not survive a question. Write the amount and the date, and color the node for status.
• One map with everything on it. Budget, vendors, guests and the timeline in a single flat map becomes unreadable by month three. Move the workstreams onto layer tabs.
• The day-of plan in a separate document. A plan that lives somewhere else is a plan nobody has on the day. Keep the timeline on the same map, on its own layer, where it stays with everything else.

Frequently asked questions

How many layers does a wedding map need?

Three or four is usually right: budget, vendors, guests and the day-of timeline. A map can hold up to eight layers, and the 3D layer stack places them on separate depth planes, but adding layers past the point where you can describe each one in a sentence creates work rather than order.

Can I share the map with my partner?

There is no share link in Canvasola and no live editing for two people in one map, so your partner cannot open it in the app from your browser. Export it as a PNG, an SVG or a Markdown outline and send the file, or save a .canv project file for anyone who has Canvasola. Cloud sync is opt-in and holds five projects of 2 MB each.

Will the map remind me when a deposit is due?

No. Canvasola has no reminders and no notifications of any kind, so a due date is a date you read when you open the map, which is why the weekly review pass matters. The version history keeps 20 snapshots, so you can look back at how the numbers changed, but the map will not chase you.

How do I keep the day-of plan readable on the day?

Collapse the branches you do not need. The chevron on a node collapses a branch, and Collapse All reduces the whole map to the root and its branch labels, which leaves a single column of times on screen. Export that as a PNG as well, in case the phone battery dies.

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.