Running five, eight, twelve weddings at once without dropping anything

One wedding is easy to hold in your head. Two is fine. From the third or fourth simultaneous booking, something shifts: you open an email and it takes thirty seconds to remember where this couple stands, whether the caterer's quote is signed, whether the follow-up went out.

Those thirty seconds, multiplied by a hundred prompts a week, become your day. And the real risk is not lost time. It is the cross-file error: the quote sent to the wrong couple, one wedding's deadline applied to another, a vendor you believe is booked who was booked for someone else.

What a full caseload actually costs

The difficulty is almost never inside a file. Taken alone, every task is simple: call a florist, chase a couple, compare two quotes.

The difficulty sits between files. Every switch forces you to reload an entire context: who these people are, which tier they bought, where their budget stands, which decisions are stuck, which tensions need handling. That reload has a cost that appears on no invoice, and it grows with the number of active files rather than the number of hours worked.

Which is why adding a fifth wedding to a system built for four does not add 25 percent of load. It adds more.

One system per wedding, one view across all of them

The answer has two levels, and the common mistake is having only one.

The file level holds everything about one wedding and nothing else: the couple, their vendors, their budget, their tasks, their deadlines, their documents. When you open it, you should recover the full picture in seconds, without reconstructing anything from memory.

The studio level answers one question: what needs me today, across every wedding? Not a list of everything that exists, but everything out of the ordinary: overdue items, approaching payment deadlines, weddings closing in on their date, decisions waiting on you.

Most planners who feel overwhelmed have the first level in some form and lack the second. They open files one by one to check nothing is burning, which amounts to a full inventory every week instead of handling exceptions.

Work by exception, not by exhaustive review

This is the method change that matters most.

An exhaustive review of eight files takes half a day and rarely leaves you better informed, because in most of them nothing moved. A review by exception takes twenty minutes: you look only at what changed state or passed a deadline.

In practice that requires your system to surface three things on its own: overdue tasks per wedding, upcoming payment deadlines, and files whose date is approaching. If those three require manual checking, you do not have a system. You have a filing cabinet.

What should surface is not what exists. It is what falls outside the ordinary.

The weekly ritual

One hour, the same day each week, in three passes.

Exceptions first: what is overdue, what awaits a decision, what threatens a deadline. This is the only genuinely urgent pass.

The coming week next: meetings, deliveries, site visits, payment dates. You are checking that nothing collides between files, which happens more often than expected when two weddings sit close together.

Silent files last: the ones you have not heard from in two or three weeks. A couple's silence is rarely a good sign in itself. Usually it means a decision is stuck and nobody told you.

This ritual replaces the constant anxious checking that is the real source of burnout in this profession.

Let the couple do their own data entry

A meaningful share of the typing has no reason to be yours.

The guest list, the replies, dietary requirements, family contact details: the couple holds all of it, and you frequently spend time transcribing it. Every transcription is lost time and a chance to introduce an error.

The right split gives the couple access to what concerns them, with appropriate permissions, while you keep control of what belongs to your craft: the overall budget, vendor coordination, the run sheet. You supervise instead of typing, and the couple moves forward without waiting for you to be free.

The benefit shows most in high season: the weeks when you are least available are exactly the weeks couples have the most to update.

The three alerts worth automating

Three signals cover nearly every avoidable incident.

Overdue tasks by wedding. A dated task left undone should surface on its own, carrying the name of the file it belongs to.

Payment deadlines. Deposits owed to vendors, balances due from couples: these are the costliest oversights and the easiest to prevent.

Proximity to the date. Past a certain threshold, a file changes regime: decisions must close, numbers go to the caterer, the run sheet gets shared. That switch deserves to be flagged rather than noticed.

Everything else can wait for your weekly review.

Questions from the field

How many weddings can one person handle?

It depends mostly on the tiers you sell. Eight to twelve full engagements is a demanding pace for one person, with a heavily compressed season. Day-of coordination lets you take considerably more, since it consumes fewer hours in advance but concentrates everything on the date itself. Be careful about accepting two weddings on the same weekend without checking travel and timings first.

Is a dedicated tool necessary, or will a spreadsheet do?

A spreadsheet handles the file level well. It handles the studio level badly, because it surfaces nothing on its own: you have to go and look. That is precisely the difference between filing and being alerted.

How do you avoid cross-file mistakes?

By never working two files in the same window at the same time, and by checking the couple's name before sending anything. It sounds trivial. It is the most frequent and most embarrassing error in the profession.

What changes

A system that surfaces exceptions gives you back two things. Time, obviously. But more importantly, permission to stop thinking about your files constantly, because you know that whatever should alert you will alert you.

That is what turns eight weddings endured into twelve weddings held, and it is also what decides whether each one is actually profitable. We cover that last point in our article on per-wedding P&L.

Run your studio with ÆTHERNA. 60-day trial, no card required. aetherna.fr/en/planners