A wedding is a logistics problem wearing nice clothes. Underneath the florals it's an event for 75 to 300 people with a fixed date, a fixed budget, a dozen vendors on separate contracts, and a schedule that has to survive contact with an open bar. Treat it that way — as an operations project with feelings attached, not the other way around — and most of the stress evaporates.
This is the system. Everything else on this site is a deep dive into one piece of it; this page is the map.
The three phases nobody tells you about
Wedding planning gets sold as one long romantic montage. Operationally, it's three distinct jobs.
Inspiration (engagement to ~12 months out). Pinterest, venue tours, arguments about whether "garden party" is a theme or a personality. This phase is genuinely fun and requires no software. Enjoy it.
Planning (roughly 12 to 3 months out). Decisions get made and money gets committed: venue, vendors, guest list, attire. The failure mode here is scattered information — the caterer's quote in email, the guest list in a spreadsheet, the payment schedule in someone's head.
Execution (the last 90 days). RSVPs land, the seating chart gets built and rebuilt, the day-of timeline has to work for six vendors at once, and the drink order needs an actual number. This is the phase where couples without a coordinator break — not because the work is hard, but because it's all cross-referenced, and the references live in different apps.
The whole trick of wedding logistics is this: decisions made sloppily in phase two become emergencies in phase three. The system below is designed to prevent exactly that.
Build in order of irreversibility
Not all decisions are equal. Sequence them by how hard they are to undo.
- The date and the venue. Everything else keys off these two. The venue sets your maximum headcount, your rain plan, and often your caterer. Book it first; it's the least reversible thing you'll do besides the marriage.
- The guest list, draft one. Before you can budget, you need a number. You don't need names finalized — you need a count within twenty. Guest list mechanics have their own guide.
- The budget. With a headcount and a venue, you can allocate the rest honestly. Per-guest costs (catering, bar, rentals) scale with the list; fixed costs (photographer, DJ, attire) don't. The full breakdown is here.
- The big vendors. Photographer, caterer, music, officiant — the ones who get booked out a year ahead. Each one adds a contract, a deposit, and a payment schedule to track.
- Everything else, by the checklist. Invitations, attire, flowers, favors, transport — real deadlines, but forgiving ones. The 12-month checklist orders all of it.
One source of truth, or several sources of trouble
The average couple plans a wedding across three spreadsheets, a shared note, two vendor portals, a group text, and a folder of PDFs. Every one of those is a place where the truth can fork.
Here's the test: when one guest RSVPs "no," how many things do you have to update by hand? In the spreadsheet system, at least four — the list itself, the seating chart, the catering count, and the bar math — and you have to remember all four. Multiply by every RSVP change from now until the final count, and you understand why the last month feels like a part-time job.
The alternative is one database where the guest list feeds everything downstream. One update, four corrections, zero remembering. That is the entire architectural idea behind ringbearer, and honestly, you could build a crude version of it yourself in a single well-disciplined spreadsheet — the tool matters less than the principle. The principle is non-negotiable: every fact lives in exactly one place.
The five documents every wedding runs on
Strip away the software and every wedding needs the same five artifacts. Whether they're pages in an app or tabs in a spreadsheet, make sure they exist:
| Document | What it answers | Breaks without it |
|---|---|---|
| Guest list | Who's coming, what they eat | Catering, seating, bar, stationery |
| Budget ledger | Planned vs. spent vs. owed | Your buffer, your sleep |
| Vendor roster | Who's hired, what's signed, what's due | Payment deadlines, day-of contacts |
| Seating chart | Who sits where | The last 2 weeks of your life |
| Run of show | What happens when, minute by minute | The entire wedding day |
The last two deserve their own reading: the seating chart method and the day-of timeline, hour by hour.
The math you can't skip
There's a category of wedding arithmetic that everyone postpones because it feels fiddly, and then does badly at midnight: drinks per guest per hour, dietary counts, ceremony duration, table capacity. None of it is hard. All of it is tedious, and errors surface at the worst possible moment — usually as an empty bar at 9 pm or a missing vegan plate at table nine.
Food and drink math covers the formulas. The ceremony script guide covers timing the one part of the day with an audience seated and watching. The general rule: any number a vendor will ask for, compute it from the live guest list, not from memory.
The last 90 days, compressed
If the system is set up, the execution phase is a sequence, not a scramble:
- 90 days: invitations out. RSVPs need six weeks to come back, and your caterer's final count is due two to three weeks before the date. Work backward; the margin is thinner than it looks.
- 60 days: vendor confirmations begin. Every vendor gets the same question — arrival time, needs, contact on the day — and the answers go into the run of show.
- 30 days: seating chart, draft one. Not sooner (RSVPs still moving), not later (you'll want revision time).
- 14 days: final counts to caterer and bar. Dietary summary attached.
- 7 days: run of show to every vendor. One document, one version.
- The day: someone who is not you holds the timeline. Delegate.
How this works in ringbearer
This whole handbook describes the manual version of the system. ringbearer is that system with the manual labor removed: the guest list feeds the seating chart, the dietary counts, and the drink math automatically; the budget tracks planned, actual, and paid per vendor; the run of show goes to vendors as a live link instead of a PDF with a version number. The product tour shows each piece. It's free to start, and the whole thing exists because we planned our own wedding on three spreadsheets and would not wish it on you.
Where to go next
Start with whichever fire is closest: the budget if you're early, the guest list if invitations loom, the seating chart if RSVPs are landing, and the day-of timeline if the date is close enough to make your stomach drop. The wedding is a project. You've finished harder ones.
See how this works in the app: the product tour.