The planning checklist, grouped by when

A twelve-month checklist assumes a twelve-month engagement. If your wedding is in five months, much of that list is overdue the day you download it, and the panic that follows is entirely manufactured. Build it the other way round: start from your date, write in the deadlines other people own, and let the order things depend on decide what comes first.

Why a downloaded checklist rots

The lead times are somebody else’s. If venues where you live get booked a year out, a checklist that tells you to secure yours before anything else is right. If they take a booking a month out, that same instruction burns the only weeks you had on a decision that could have waited. The list cannot know which of those you live in, so it guesses, and it guesses long.

The culture is wrong. Generic checklists rarely have a line for the horoscope reading, the mehendi night, the church paperwork or the elder who has to be consulted before a date can even be proposed. They do have a line for your something blue. You end up with a list that is fussy about the wrong things and silent about the ones that will stall you.

The scale is wrong. A forty-person lunch in a garden and a six-hundred-person hotel reception are not the same project with different numbers on it. One of them needs a seating plan, a transport list and three separate headcounts. The other needs a table and a good caterer.

Dependency order beats month labels

“Nine months before” is only meaningful next to a date somebody else chose. What survives translation is the order. Some tasks cannot sensibly begin until another has finished, and those are the ones whose position is not up for negotiation.

• The date fixes everything. Nothing under it can be booked, quoted or sent until it is settled.
• The venue comes before the caterer, the decorator and the band. It decides your capacity, whether outside catering is allowed at all, and what time the music has to stop.
• The guest list comes before the invitation. You cannot address what you have not written down, and the list is where the arguments happen, not the design.
• The RSVP deadline comes before the final headcount, and it has to sit well before it. A deadline is your first ask, not an answer.
• The final headcount comes before seating, the caterer’s closing invoice and the transport count. All three break if it moves.

Get that spine right and the month labels stop mattering. Booking the venue is urgent because six other things are queued behind it, not because a PDF said month three.

Work backwards from the deadlines you do not control

Some dates are not yours. The venue wants the balance on a day it picked. The kitchen closes its numbers several days out and will not reopen them, because their own supplier holds them to the same cut-off. The tailor has a last fitting after which nothing can be altered. The registrar has notice periods. If you are printing anything at all, the printer has a cut-off and a reprint window.

Write those in first. They are fixed points, and every task you own hangs off one of them. Then give the chasing its own room: leave a fortnight between your RSVP deadline and the day the kitchen closes numbers. That fortnight is a working figure, not something anyone measured - it exists because some guests will not answer until you ask a second time, and because one cousin will confirm for himself and arrive with four people. Count backwards from each fixed point after that, and give yourself an honest amount of time rather than a heroic one.

Start from a ready-made list, then cut it

The quickest route to a usable checklist is to take one somebody else wrote and delete most of it. Deleting is easier than remembering: you strike out the lines that do not apply and, on the way past, notice the two you had forgotten.

That is what the starter checklists in the planning tools are for. There are four of them - Wedding, Birthday, Corporate and Other event - and they are offered only while your checklist is still empty, so take one before you start typing tasks of your own. Picking the closest match fills your list with the usual tasks, each carrying a category, an owner label, a priority and a due date. All of it is editable and most of it should be edited. The due dates are counted from the day you add them rather than from your event date, so the first job is moving them onto your real timeline.

Then cut. Anything already done, delete. Anything that belongs entirely to somebody else, delete. Anything you are simply not going to have, delete. What is left is short, and short is the point.

Grouped by when it is due, not by month

A month-labelled checklist makes you find today. You scroll to the current month, read it, and quietly leave behind the two things from the month before.

The checklist groups tasks by when they are due instead: overdue first, then this week, then the next thirty days, then later, then anything with no date on it. An overdue task from four months ago sits at the top beside one from last Tuesday, because to you they are the same problem. Finished work drops to the bottom.

There is also a daily push notification for anything overdue or due within the next day or so. It arrives as one summary rather than one message per task, and only reaches you on a device where you have allowed notifications. A switch in the checklist header turns it off if it is not helping.

When you do not need a checklist at all

Not every wedding needs this. If yours is small, close and already booked, your list is nine items long and it belongs in the notes app on your phone. A tool with categories and priorities is overhead you will come to resent. If you have a planner, the real list lives with them, and a second copy on your side becomes something to reconcile rather than use. And if what you actually need is to send the invitation and find out who is coming, go straight to the guest list and the RSVPs and leave the checklist alone. It sits beside the invitation; it is not a condition of sending one.

Related: All features