The calendar looks reasonable because each wedding occupies one square. The team works far beyond that square.
The team handles final confirmations, supplier chasing, stationery checks, packing, rehearsals, travel, returns, invoice queries, and the next couple’s messages during the days around an event. Two weddings can appear neatly on separate weekends while their delivery work competes for the same planner in the middle.
A capacity audit makes that overlap visible before the planner accepts another booking. It tests five parts of the season: event complexity, founder-only work, team coverage, response coverage, and recovery time. A failed test needs a capacity decision, rather than another promise to become more organized once the season starts.
Wedding-business adviser Becca Pountney recommends blocking personal time early so later opportunities require an active decision about what to give up. That principle works for delivery capacity too. Put the unavailable time in first, then check each new booking against the work and life already promised.
Audit delivery periods instead of event dates
Start with every booked event, then mark the period in which the team will deliver it. Include the preparation peak, travel, on-site work, returns, and the client follow-up that belongs to delivery. Add the founder’s protected time and any team absence.
The unit you are testing is the delivery period. Its exact length will vary by service, event, and studio. A coordination booking at a familiar venue creates a different shape from a multi-day celebration with custom production across several locations.
Look for overlaps where two events need the same person, decision, or response promise. An empty Saturday reveals very little if the week around it already contains a rehearsal, a long travel day, and final confirmations for another couple.
Test one season five ways
Use the audit below on each delivery period. Mark a test red as soon as its failure condition appears.
| Test | Mark it red when | Capacity decision |
|---|---|---|
| Event complexity | Two demanding events overlap in preparation or delivery, and both require close senior control. | Reduce scope, add experienced delivery support, move a milestone, or decline the new booking. |
| Founder-only work | The founder’s required work exceeds her available working time after events, travel, and protected time are removed. | Delegate a defined task, change the service, or keep the booking out. |
| Team coverage | A critical function has one owner and no qualified cover during an event, absence, or travel period. | Train cover before the season, bring in a known freelancer, or reduce concurrent work. |
| Response coverage | The client response promise cannot be met while the team is on-site or recovering. | Assign an inbox owner, reset the promise before booking, or create a closed period. |
| Recovery | Rest days repeatedly become the only buffer for unfinished delivery work. | Restore the buffer by moving work, adding help, or removing a booking. |
Change the plan whenever you mark a test red. If the planner keeps every booking by giving up the same day off, that repeated loss reveals the capacity limit.
Define complexity before the diary gets crowded
“Large wedding” is a poor proxy for difficult delivery. Guest count matters. Complexity can also come from split venues, travel, custom builds, unusual access, a large vendor team, a compressed setup, or a couple who has bought a high-contact service.
Write the studio’s complexity markers from past work. Then identify which combinations require senior attention. A familiar venue with a trusted vendor team may accommodate more guests with less delivery risk than a smaller event in an untested location with difficult access.
The threshold is operational: mark the period red when the event needs close control at the same time another event needs the same control. That tells the planner what has collided.
Count the work only the founder can do
Founders often estimate capacity using all working hours, then fill those hours with tasks only they can perform. The founder may need to handle creative direction, sensitive client calls, final commercial decisions, and leadership on the event day. She may still be packing boxes, updating schedules, confirming routine details, and formatting documents through habit.
Separate the two.
First, list the decisions and moments where the founder’s judgment or relationship is essential. Estimate that work for each event using the studio’s own records. Then remove event days, travel, protected time, and fixed commitments from the founder’s available hours.
If the required founder-only work no longer fits, the period fails. Moving routine admin helps only after that arithmetic is honest. General support still leaves two simultaneous founder conversations with one owner.
Two simultaneous founder calls require two qualified owners.
Check who covers the ordinary work
During busy season, single-owner functions become obvious. Someone needs to monitor the shared inbox while the lead planner is at a venue. Someone needs authority to answer a routine supplier question. Someone needs to know how a document is assembled before the person who usually does it becomes unavailable.
For every critical function, write a primary owner and qualified cover. Use a person’s name rather than “the team.” Cover also needs access, context, and a boundary for decisions. A name in a spreadsheet will not help if that person has never seen the process.
Test the cover before the season. Let the second person run the inbox, prepare the event pack, or lead the routine confirmation while the primary owner is still available to correct gaps.
Make response capacity part of the service
A planner can deliver an excellent wedding and still damage the next client relationship by disappearing during it. Review every promise made about email, calls, approvals, and emergencies. Then compare those promises with event days, travel, and team coverage.
Choose a realistic operating rule for busy periods. That may mean a named inbox owner, narrower response windows during event weekends, or a planned closure after a demanding event. Tell clients before the season so they know when and how the team will answer. If nobody explains the temporary rule, clients have to guess.
Planner Jaclyn Watson’s account of wedding-business economics describes the hidden load around staffing, administration, postponements, and owner pay. Pricing has to account for that work. A season audit asks the next question: can the particular people in this studio deliver the work when it clusters?
Treat recovery as booked time
A tired planner makes worse decisions. After a complex event, she still has to answer the next couple, make commercial calls, and notice the small discrepancy in a supplier update.
Put recovery into the audit before testing new work. The studio decides what adequate recovery means for its team and event mix. The useful threshold is simple: if unfinished delivery work repeatedly takes the protected recovery period, the schedule is over capacity.
Do not solve that failure by renaming recovery as flexible time. Change the workload.
Make a capacity decision for every red test
Suppose a new inquiry arrives for an open date. The audit shows that its final-confirmation period overlaps a complex event already booked. The founder is required for both, the inbox has cover, and the wider team has room.
The studio lacks a second person qualified to provide senior control.
The planner can reshape the service so a trusted associate leads defined parts of delivery, move an internal milestone with the couple’s agreement, or refer the inquiry. Hiring general admin support would leave the failed test untouched. Accepting the booking and hoping the weeks separate themselves would do the same.
Record the decision: For every red test, write the collision and the change that resolves it. Add the owner and due date. Keep the booking unapproved until every red test has a resolution.
Run the audit while there is still room to make a good decision. The final calendar may show fewer bookings. It will also show who covers the inbox, where the founder’s judgment is required, and which days remain protected when the last supplier leaves.
