Three decisions come first,
and the rest follows from them.

Before a venue, before a date, before anyone looks at a dress, three decisions set the boundaries of the whole event: how many people will be there, how much you are prepared to spend, and what kind of day you want. A long lunch for thirty, a ceremony and a marquee for a hundred and forty, a weekend abroad with twenty people. These are not the same project, and they do not share suppliers, timelines or costs.

The three constrain each other, and the guest count is the strongest of them. Almost every large cost is charged per head: food, drink, chairs, place settings, stationery, transport, sometimes the room itself. One extra table of ten is not the price of ten dinners. It is ten dinners, ten glasses of wine, ten of everything else, and sometimes the difference between a room that fits and one that does not. Cutting the list is the only lever that moves every line at once.

The kind of day you want pushes back on both numbers. A seated dinner needs a room that seats everyone at once; a standing reception does not. A barn with no kitchen means bringing one, a real cost that never appears on the hire price. An outdoor ceremony needs a plan for rain whether it rains or not. Decide the shape first and you learn what it demands; book the space first and you learn afterwards.

This is an afternoon's work, not a research project. Write the names rather than a number, household by household, so the count is honest. Agree the total you will spend, and where it comes from, before anyone quotes you anything. Then write two or three sentences describing the day and keep them: they are what you check every later decision against. The wedding budget guide takes a total apart by category, which is where a number becomes usable.

Almost everyone books the venue first, and the instinct is sound: good places run out, and a date with no room is not a date. But a venue is not a decision, it is a container. It arrives with a capacity, a catering rule, a curfew, a minimum spend and a diary. Sign for one before the three decisions are settled and you have not chosen a wedding, you have inherited one.

It goes wrong in three familiar ways. The capacity quietly becomes the guest list, so you cut people you meant to invite or pay for an overflow room. The venue's own caterer or minimum spend sets the budget, rather than the budget choosing the venue. And the one date they had available becomes your date, which is fine until it collides with a notice period at the register office, a peak-season price, or the two people whose absence would make the day pointless.

There is one honest exception. If a particular place is the reason for the wedding, the family farm or the town you met in, then it is your answer to what kind of day you want, and it comes first legitimately. Build the count and the budget around it deliberately. The mistake is never booking a venue early. It is booking one instead of deciding.

Once the three decisions and the space are settled, five bookings deserve attention ahead of everything else, because each can only serve one wedding a day or has to be made to order. In rough order: whoever conducts the ceremony, the caterer if the venue does not provide one, the photographer, the music, and anything made to measure. The first four compete for a date; the fifth competes for a production queue, which is why a dress ordered late is a different problem from a florist booked late.

The list of things that can genuinely wait is longer than people expect: flowers, cake, hair and make-up outside high season, transport, decor hire, favours, and the invitations themselves. If a supplier can serve several weddings in one weekend, or you are buying a product rather than booking a person, it can wait. If they can only be in one place on your date and you want that particular one, book them and pay the deposit.

Approach all five with the same brief on the same day and the quotes come back comparable: date, venue, number of guests, the hours you need them, two lines on what you want. A message that says ninety guests, seated, three in the afternoon until midnight, gets a number back. Asking what they charge for a wedding gets a range and a meeting. Vowly's vendor search keeps the briefs and replies next to the event rather than in an inbox.

Getting married is two things on one day: a wedding, which you design, and a legal act, which you apply for. The second runs on a calendar you do not control. In most countries you must give formal notice to a civil authority some period before the ceremony, and that period is set by law. It does not shorten because the venue only had one Saturday left, and it differs between countries and sometimes between regions.

So in the first month, find the office that will actually register your marriage, not a blog and not a supplier, and ask it four questions. What documents are required, and in what form: originals, certified translations, an apostille? How far in advance must notice be given? How long does the resulting authorisation stay valid, since a notice that expires before your date is an avoidable disaster. And what changes if one of you is a foreign national, or has been married before?

The same applies to a religious ceremony if you are having one. In some places these carry their own requirements - meetings with the officiant, a preparation course, documents from another parish - and they run on months rather than weeks. Ask early, and treat those dates as fixed points the rest of the plan works around.

The guest list is not something you settle in February and file. It is a document you keep for a year, because people move, couples form and separate, a new partner needs a seat, a colleague becomes a friend. Give it columns from the first day - household, contact details, which parts of the day they are invited to, whether they have replied and for how many people, meal choice, dietary needs, notes - and it is still the working document in the final month, when the caterer wants a number by Thursday.

The A-list and B-list question deserves an honest answer. The practice works in one narrow case: the first wave goes out early, with an early deadline, so the second wave still arrives at a normal time. If a second invitation lands three weeks before the day, everyone who gets it knows what it is, and guests talk to each other. If your timings cannot support that, you do not have an A-list. You have one list, and it may need to be shorter.

Count people, not replies. One yes can mean one person or a family of four, and the figure the caterer needs is heads. Vowly's RSVP collects party size, companion names, meal choice, dietary notes and allergens in one reply, and where the day has separate parts, guests answer for the ceremony, the dinner and the after-party separately. A list that begins in a spreadsheet can be imported with its columns mapped and duplicates flagged, and the guest list guide has the tests for the awkward middle.

Delegation at a wedding fails on vagueness, not on willingness. Mum is doing the flowers can mean five jobs: choosing them, paying for them, ringing the florist when the florist goes quiet, collecting them on the Friday, and getting them into a car with room. The useful question for every handover is who chases this when it stops moving. If the honest answer is you, it has not been handed over.

Keep whatever costs money or has to stay consistent: contracts, deposits, final numbers, timings, addresses, and the guest list itself. Hand over bounded jobs with an ending, such as collecting the cake, building the playlist for the drinks reception, or bringing an aunt from the station. One owner, one deadline, one phone number, written down where you can both see it rather than agreed across a kitchen and remembered differently.

Name one person who is neither of you to run the day itself, a paid coordinator or a calm friend. On the morning the questions arrive continuously - where do these go, who is paying this driver, when does the cake come out - and the couple are the worst-placed people in the building to answer them. Give that person the running order, the supplier numbers, and permission to make small decisions without asking.

What makes planning miserable is not the volume of work, it is that the work has no edges. It arrives by message at nine at night, it takes over dinner, and after a few months the wedding is the only subject the two of you have. The fix is unglamorous: one standing conversation a week, same day, same time, fifteen minutes, with a written list in front of you.

Fifteen minutes is enough because the meeting is only for decisions. Tasks belong on the checklist and numbers in the budget. Each of you brings two things: what is due before the next meeting, and what is stuck. If something genuinely needs an hour, book the hour separately. The value of the short meeting is that it stays short, and the rest of the week is allowed to be about something other than seating.

Agree who decides what. There will be categories one of you cares about and the other does not, and pretending otherwise turns a preference into a negotiation. When you get stuck on something small, check what it is standing in for, because most wedding arguments are about money or family rather than napkins. Who is contributing, and what that entitles them to expect, is better handled in week two than month ten; the guide on who pays for what is a reasonable way to open it.

Expect the job to change character about six weeks out. For most of the year, planning is choosing: which venue, which photographer, which colour, which song. In the final stretch the choosing stops and the work turns into arithmetic and logistics - final numbers to the caterer, meal choices and allergens collated, seating built, timings agreed with each supplier, deliveries scheduled, balances paid, someone briefed to hold the rings.

Plan for that shift rather than being surprised by it. Set the RSVP deadline a week or two before the date the caterer needs numbers, because people will still be replying after it. Build the seating plan when the count is close to final, and expect to rebuild it twice. Write one running order and give everybody the same version; if the details live as a link rather than a printed page, guests read the version you last corrected. The wedding checklist has the month-by-month sequence, and its last-minute section covers this final stretch week by week.