Wedding planning checklist: what to do and when

Planning a wedding is really a few hundred small tasks looking for a place to live: some in your head, some in your partner's, and the rest scattered across chats, phone notes and a notebook bought enthusiastically in week one. The problem is almost never not knowing what to do — it is that nobody is sure what is already done, what is urgent now, and who owns what. So here is the checklist, organized by phase — plus a few words on how to run it, because a good list is measured not only by what is on it but by how it behaves.

Why one shared list instead of two phones and a notebook?

Because a task that lives in one head does not exist for the other. When the notes are scattered — he closes with the DJ in a chat, she keeps the photographer meeting in her phone notes — every planning conversation opens with "wait, did you book the...?". One shared list fixes this with two simple moves: every task goes to one place, and every task carries a name — who owns it. Not "we'll handle it", but "Daniel books the shuttles by the end of the month". The moment tasks have owners, the ones you were both sure the other was doing disappear.

What do you book first?

Three things everything else leans on: a date, a budget and a venue. They are linked — the season and the day of the week move the price, the venue caps the guest count — so the custom is to close them together, before any other vendor:

• A date, or a date range: a few weeks of flexibility opens venues and prices that locking onto a single day shuts out.
• A budget frame: not a detailed spreadsheet yet — one total number you are at peace with. The real wedding math runs per guest, but at this stage a frame is enough.
• A rough guest count: no names yet — 150? 300? 500? This is the number that decides which venues are even relevant.
• The venue: the first vendor you sign, because its date becomes your date. From the moment you sign — every other task has a deadline.

What happens in the middle months?

The months between signing the venue and sending the invitations belong to the vendors and the list. There is no sacred order here — just one rule: good vendors get booked early, so start with whoever matters most to you:

• Vendors: photographer, DJ or band, decor, dress and suit. Each one is a small chain of meetings, a quote and a deposit — and each chain is several checklist lines, not one.
• The full guest list: this time with names and phone numbers. It is the foundation for the invitations, the RSVPs and the seating — and every delay here pushes everything behind it.
• The invitation: design and wording. Good wording answers four questions — who, when, where and what you are asking — and asks the guest for one action.
• Marriage registration: opening a file at the Rabbinate, or whichever route you chose — bureaucracy with queues of its own, so it starts earlier than it seems it should.
• The rings: bought mid-journey, calmly. How they make it to the chuppah — more on that in a moment.

Why can't seating and meals close early, even for organized couples?

Because they don't depend on your diligence — they depend on other people's answers. This is the point that most surprises organized couples: almost every task on the list can be moved earlier, except the two most stressful ones. A seating map is built on who is actually coming — arranging tables by the invitation list means arranging them twice. And the meal commitment to the venue closes on a real confirmation count, because every extra plate is money. These two checklist lines simply wait for the RSVPs, which is why the final month is less "doing things" and more "closing answers" — and that is perfectly fine, when the list is built around it from the start.

What happens in the final month?

You send the invitations, collect the confirmations — and only then close what was waiting for them. The custom is to send invitations four to six weeks ahead, and from here the list becomes answer-driven:

• Sending invitations and reminders: a personal link for every guest, and reminders only to those who haven't answered — the full message calendar is a guide of its own.
• Tracking RSVPs: the standing task of the month — knowing at any moment how many confirmed, how many declined and how many are still in the air.
• Closing meal counts with the venue: after the last reminder, on the actual number of confirmations — including vegetarian, vegan and gluten-free.
• The seating map: start once most answers are in, close finally a few days before — with a few flexible seats for last-minute changes.
• A confirmation round with the vendors: arrival times, the evening's schedule, contact people — so every vendor knows when they come in and who picks up their call.

What is left for the final week?

If the list was run well, the final week is operational — not creative. No new decisions get made; old decisions get made to happen:

• The final headcount: a closed number with the venue, after the last reminder has done its work.
• The day-of message: arrival time, navigation and table number — prepared in advance, going out on the wedding morning only to guests who confirmed.
• Payments and envelopes: who pays which vendor, when and how — settled in advance, not improvised on the dance floor.
• Roles for the day itself: everything that happens on the wedding day has an owner's name on it — and that owner is not one of you.

Which tasks do couples always forget?

The ones no vendor is responsible for — so by default, nobody is responsible for them. They deserve a checklist line right now, with a name beside each:

• The rings on the wedding morning: bought two months ago, safely stored in a drawer — which is exactly the story. One person owns getting them out of the house and to the chuppah.
• Who takes the gifts home: at the end of the night you are the least available people in the hall. Agree in advance who collects the envelopes and gifts, and in whose car they travel.
• Vendor meals: the photographer, the DJ and the crew eat too — they are counted into the meal order with the venue in advance, not discovered when food runs short.
• A transport backup: the number of a driver or an alternative company, saved ahead of time. When the shuttle is late at eight in the evening — you don't start searching.

Why should a finished task disappear?

Because a list that only grows stops being read. A checklist is a working tool, not an archive: when forty lines face you and thirty are already done, the eye stops scanning and the list turns into background noise. A finished task gets checked and vanishes; a task that is no longer relevant gets deleted without guilt; and what remains on screen is always the answer to one question — what do we do now. The sign of a healthy list is that it gets shorter as the wedding gets closer. If it only swells, it has turned from a roadmap into a storage room.

And where does this list live day to day?

Most conveniently — in the same place where the guests, the RSVPs and the budget already live. Weddigo ships with a built-in wedding checklist: ready-made tasks, organized into categories you can edit — delete what isn't relevant to you, add what only you know. And it sits in the same dashboard as the guest list, the RSVPs, the seating, the budget and the live stats — so when a task like "close meal counts with the venue" comes up, the number it needs is one screen away.

A good checklist doesn't test how much you remember — it tests how much you are allowed to forget. A task with an owner and a due date is a task you don't have to think about until its turn comes.