Wedding Planning Spreadsheet: What Should You Track?

What Should a Wedding Planning Spreadsheet Track?

A wedding planning spreadsheet should hold what you would otherwise have to reconstruct: what still needs doing, who is coming, who you have hired, what it costs, what has been paid, what you have settled, and when everything falls due.

In practice that is eight working areas — tasks, guests, vendors, the budget, payments, a timeline, decisions and documents — and almost every template covers the first five. The last three are where most spreadsheets quietly give way, because they hold a plan together rather than list it.

The goal is not completeness. A tracker that follows everything is a tracker nobody updates, and a stale one is worse than a short one: it looks authoritative and is wrong.

Information, Decisions and Actions

A planning tracker holds three different kinds of thing at once, and separating them is the quickest way to work out what any given column is for.

Information

Things you need to remember: a phone number, the venue address, what a contract covers, a guest's dietary requirement. It changes rarely, and its only job is to be findable.

Decisions

Things you have chosen: the photographer you booked, the menu you settled on, the table arrangement you agreed with the venue. A decision is finished rather than pending, but it still needs recording, because six weeks later somebody will ask what you decided.

Actions

Things somebody still has to do: send the final numbers, review the contract, confirm the delivery time. An action has an owner and a date, and it is the only one of the three that goes stale on its own.

Most spreadsheets carry information well, actions badly and decisions not at all, which is how a plan can look organized and still leave you unsure what is settled. It also makes a useful test for a new column: which of the three is it holding, and does that kind of thing already live somewhere?

This is a practical way to sort planning information, not an established methodology. Use it if it makes your own tracker easier to reason about, and ignore it if it does not.

Start With One Source of Truth

The commonest planning failure is not disorganization but duplication: the guest list in a spreadsheet and also in a notes app, a quote in an email and also typed into the budget, two copies of one file with slightly different names.

What follows is predictable:

• the same figure appears twice, and the two disagree
• one copy is updated and the other is not
• nobody is certain which version is current
• a change falls between the copies and lands in neither

The fix is not more discipline. It is giving every kind of information exactly one home and making everything else point at it, so that when something changes there is only one thing to change. A column belongs wherever the thing it describes already lives: a guest's meal choice sits on the guest list, and the catering area reads its total from there.

Track Tasks, Not Just Categories

What makes a task a task

Most wedding checklists are lists of categories: flowers, music, transport, stationery. They are good for making sure nothing is forgotten and no use at all for making anything happen.

"Flowers" is not a task: nobody can start it, finish it, or tell you whether it is late. "Choose a florist and confirm the package" is a task, because it has a moment at which it is unambiguously done. That is the test — if two people can read a row and disagree about whether it is finished, it is a category wearing a verb, and it wants breaking into the two or three things that actually have to happen.

Give every task a deadline and an owner

A task with no date and no name attached does not move: a list of undated, unassigned work has no way of telling you which row deserves today. A workable row carries the task written as an action, one owner, a deadline, a status, and a note where there is something the title cannot hold.

Single ownership matters more than it sounds. Shared ownership reads as fair and behaves as nobody: two of the commonest reasons a wedding task is late are that each of you thought the other had it, and that neither wanted to ask. Keep the statuses short and keep them yours, too — three words, five, or a single checkbox all work, as long as each means the same thing every time it is used.

And a deadline is more useful as the date something should be started than the date it must be finished.

Keep the Guest List in Its Own Working Area

The guest list changes most and touches most. Catering numbers, seating, stationery and several vendor quantities all read from it, which is why it should live in one place and be referenced rather than copied into each.

It wants a row per person, carrying:

• the name, as it should appear on an invitation
• the household or invitation group they belong to
• which side or circle they come from
• contact details, in whatever form you will actually use
• whether an invitation has been sent, and their reply
• a companion or plus-one, where one applies
• anything a vendor will need: a dietary requirement, an access need, a child's age

The person is the unit, because a row reading "the Nikolaou family (4)" cannot be seated, catered for or counted reliably. The invitation group is a field of its own, so you can invite by household and count by head without keeping two lists in step.

Building and grouping a list is a large subject in itself, and How to Organize a Wedding Guest List covers it in full, replies included.

Track Vendors and What You Have Agreed

A vendor list holding names and phone numbers answers the easy question. The hard one, months later, is what you agreed to, and that is rarely written down anywhere except a contract nobody has reopened since signing.

A vendor row is worth carrying:

• the business, and the person you actually deal with
• their contact details
• what they are providing
• where the conversation has got to: enquiry, quote, booked, agreement signed
• whether a contract exists, and where the signed copy lives
• the agreed total
• the dates that matter: arrival, setup, delivery, how long they stay
• what you are waiting on from them

The status is the column that earns its keep. Two vendors quoting the same figure are in entirely different positions if one has countersigned and the other has not answered an email in three weeks.

Holding a vendor, their agreement and their payment schedule together is a subject of its own: How to Keep Track of Wedding Vendors and Payments covers the whole record.

Track Payments Separately From the Budget

These two get merged into one tab constantly, and the merge is what makes the numbers untrustworthy. A budget is a plan; payments are events.

It is worth keeping five figures apart:

• estimated, meaning what you currently think something may cost
• quoted, meaning what a vendor has actually said it will cost
• committed, meaning what you have agreed to, paid or not
• paid, meaning what has genuinely left your account
• remaining, meaning committed minus paid, which is money you already owe

The trap is subtracting paid from the budget and reading the result as what is left to spend. It is not: that treats everything you have committed to and not yet paid as money still available.

In tracker terms this is two areas rather than one. A budget line per category or item, carrying the estimated, quoted and committed figures; and a row per payment, carrying the vendor, a label, the amount, the due date and whether it has cleared.

The money side has a guide of its own: How to Create a Wedding Budget covers setting the total, allocating it and reading what genuinely remains.

Track Decisions and Open Questions

This is the area almost no template includes. A wedding is a long sequence of choices, and a plan recording only tasks and costs loses both halves of it: what was decided, and what has not been decided yet.

Each causes its own trouble. An open question quietly blocks work: you cannot brief a florist until the colours are settled, and nobody notices the dependency until the florist asks. A settled question, unrecorded, gets reopened three months later, when one of you remembers agreeing to a buffet and the other remembers agreeing to think about it.

A decision row is short:

• the question, written as a question
• whether it is open or settled
• the answer, once there is one
• the date it has to be answered by, where something is waiting on it
• a line on why, because the reasoning is what disappears fastest

That last one earns its column. Most reopened decisions are reopened not because the answer was wrong but because nobody remembers what it was weighed against, and one line — plated rather than buffet, because the room does not work for a queue — usually ends the conversation before it restarts.

Read from top to bottom, it also gives you something no task list can: an honest view of how much of the wedding is genuinely settled.

Keep Documents and Supporting Information Findable

A spreadsheet makes a good index and a poor filing cabinet, and the distinction is worth holding on to: a surprising amount of planning time goes on looking for a document that certainly exists.

Things worth being able to find quickly:

• signed contracts, and any revised version
• quotes, invoices and receipts
• written confirmation of anything agreed by email or message
• links: a floor plan, a shared folder, a supplier's portal
• notes and photographs from meetings and site visits

Rather than pasting a contract's contents into a cell, keep the files somewhere durable that you control and point the tracker at them: what the document is, who it belongs to, where it lives. The tracker tells you the agreement exists and is signed; the file is the agreement. And choose one location, because documents spread across two inboxes, a phone and a shared drive are, in practice, documents you do not have.

Build a Planning Timeline

Tasks tell you what needs doing. A timeline tells you when the plan itself falls due, which is a different question and the one that tends to get answered late.

It is a short list of dated milestones rather than a second copy of the task list:

• the bookings that have to be in place before anything else can proceed
• the date invitations go out, and the reply deadline
• the dates each vendor needs final numbers by
• final payment dates
• the last week: confirmations, final counts, deliveries, anything to collect
• the day itself, once its running order exists

Most of these are not yours to choose. A vendor's cut-off for final numbers and a contract's final payment date are handed to you, and the useful work is getting them into one dated view early enough to plan backwards from. Two large payments landing in the same fortnight is something to discover in March.

The wedding-day running order belongs here too, though it arrives late and is a document in its own right. For the order the rest of the work happens in, Wedding Planning Checklist: What to Organize and When walks the whole plan phase by phase.

What a Simple Wedding Planning Spreadsheet Looks Like

Put together, a tracker that holds a plan without becoming one is roughly eight areas, each with a handful of fields:

• Tasks, holding actions: the task, an owner, a deadline, a status, a note
• Guests, holding people: the person, their household, contact details, their reply
• Vendors, holding relationships: the business and contact, what they provide, where the conversation stands, whether an agreement is signed, the agreed total
• Budget, holding the plan for the money: the category or item, estimated, quoted, committed
• Payments, holding transactions: the vendor, a label, the amount, the due date, paid or not
• Timeline, holding dated milestones: the date, what falls due, who is seeing to it
• Decisions, holding choices: the question, open or settled, the answer, why
• Documents, holding references: what it is, who it belongs to, where it lives

That is a starting point rather than a specification, and not a set of tabs to create on the first afternoon: an empty tab is not neutral, it reads as work you have failed to do. A section earns its place when it solves a planning problem you actually have, and seating is the clearest example — for most of the planning it is not a real area at all, because you cannot seat people who have not replied. Begin with tasks, guests and money, and let the rest arrive when something forces it.

Keeping It Simple, and Keeping It Current

Fewer columns than a template gives you

A theoretically complete spreadsheet nobody has opened since April is worse than a plain one that is current. Everything a tracker holds costs something to keep true, and that cost falls due every week.

Most of what makes one unmaintainable is avoidable:

• columns added because they looked thorough, and never filled in
• the same fact typed into two places
• tabs created in advance for work that has not started
• status words detailed enough that you deliberate before picking one
• formulas and formatting elaborate enough that changing a row feels risky
• a structure only one of you understands

Treat every empty column as a question: if it has been blank for a month, either it is not information you need or it lives somewhere else. And if recording a reply means editing three cells and re-checking a total, it will not happen on a Tuesday evening.

How often should you update it?

There is no correct interval, and a schedule is less useful than a short list of moments:

• after a decision is made, while you still remember the reasoning
• after a vendor is booked, or an agreement is signed or changed
• after a payment leaves your account
• when a reply arrives, or a guest's details change
• after any conversation in which something was agreed

Between them, a short repeated pass keeps the numbers honest. Many couples find a weekly one comfortable once vendors start being booked, and monthly adequate before that; the right rhythm is the one you keep.

Spreadsheet or Wedding Planning Tool?

When a spreadsheet starts getting in the way

A spreadsheet is an excellent planning tool, and there is one shape of problem it cannot solve. The symptoms are recognizable:

• the same guest, vendor or figure appears in more than one place
• there are two versions of the file and neither is clearly current
• changing one number means changing three others by hand
• a payment date was missed because it sat in a tab nobody opens
• statuses have drifted, and half the rows say something that stopped being true

Every one of those is the same underlying thing: a spreadsheet stores values and does not know what they mean to one another. Twenty guests declining does not move the catering number, the seating area or the per-head figure in the budget. Doing that arithmetic by hand is entirely reasonable for a straightforward wedding, and stops being reasonable at about the point where you are copying one change into three places and are no longer sure you have caught them all.

A spreadsheet works well when

• you want to design the structure yourself, and change it freely
• you are comfortable maintaining it, and will
• the wedding is relatively straightforward
• most of the work is arithmetic, which is what spreadsheets are best at

A connected planning system helps more when

• several areas have to stay in step with each other
• guest changes ripple into catering, seating and cost
• more than one person is keeping information current
• you find yourself copying the same fact between lists
• tasks, vendors, costs and replies all need to be right at the same time

Plenty of couples end up with both, which is a legitimate answer rather than a failure to choose: a spreadsheet for the modelling, a planning tool for the parts that have to stay connected. What does not work is the same information living in each.

Keeping the Whole Plan in One Place

Agapaé's Planning Hub and Éros are part of the Heirloom plan.

Agapaé's Planning Hub is the system described above, already assembled.

Planning is divided into the parts a wedding is made of, all editable, and each part holds its own vendors, tasks, costs, documents and open decisions. A vendor card carries the person you deal with, their details and your notes, with a status that follows the real conversation from researching through to booked. A task carries a due date, a priority, a checklist and your own labels, and is flagged once it is past its date. A cost carries a label, an amount, a due date and the vendor it belongs to, is due or paid, and rolls up into four totals: estimated cost, paid, outstanding, and what is left of your budget.

The two areas most spreadsheets leave out are here as well. Open questions are recorded as decisions, with the options under consideration, and keep their answer once settled. Contracts, quotes and receipts can be filed as PDFs or photographs against the vendor or task they belong to. Dated tasks, unpaid payments and meetings share a calendar, and the plan's milestones sit on a timeline.

Éros is the planning assistant inside that space. It reads what is there and answers from it, and when you ask it makes the change itself: add the task, record the payment, update the vendor. It suggests and you decide.

What it does not do is worth saying plainly. Agapaé does not import an existing spreadsheet and does not synchronize with Excel or Google Sheets. It is not a vendor directory, nobody is contacted, booked or paid through it, and it sends no reminders about vendor payments. It is not accounting software, and it is no substitute for your signed agreements.

The planning side is described in full on Wedding Planning.