The wedding day run sheet ai use case is narrow, unglamorous, and the highest-stakes document in the whole planning process. It is what runs on the day, in the hands of people who are not you, when the timings have slipped by twenty minutes and someone asks whether the ceremony can still start. Most prompt collections stop at budget and vendor selection. Almost nobody writes the plan for the version of the day where it rains.
Two documents fix that. The run sheet is the timed sequence everyone works from. The wet weather plan is the alternative sequence, written in advance, with the trigger that activates it named before anyone is standing in a wet field arguing.
What a run sheet actually has to do
A run sheet is not a schedule for guests. It is an operational document for the small number of people doing the work, and it has three jobs. It tells each person what happens next, it tells them what must be ready beforehand, and it tells them who to call when it does not happen as written.
Keep it to one or two pages. A twelve-page run sheet is a document nobody updates, and an out-of-date document is worse than none because everyone trusts it.
The copy-ready run sheet prompt
Build a wedding day run sheet for [date] at [venue name, full address, and room names]. The confirmed schedule is: [paste ceremony, drinks, dinner, speeches, first dance, and transport times]. The people are: [paste name, role, and phone for each supplier and each helper]. Venue constraints: [room release time, curfew, kitchen cut-off, power limits, sound limits, parking, loading access]. There are [number] guests, including [number] who need step-free access, [number] children, and [number] wheelchair users. Produce four tables. FIRST, the master timeline with columns for time, duration, what happens, who leads it, who else is needed, and what must be ready beforehand. SECOND, supplier arrival and departure times with name, role, contact, and access notes. THIRD, guest movement between locations with who moves and when. FOURTH, a contact card for each supplier. Then output a FLAGGED section listing every overlap, every task with no named owner, every supplier arrival that falls outside the venue access window, and every timing that depends on a factor nobody has confirmed. Leave each as a question rather than resolving it. Do not invent names, phone numbers, times, or venues. Where a supplier has not confirmed, write [AWAITING CONFIRMATION]. Do not add buffer by making tasks faster. Build in the time an activity change actually takes, including reset time between ceremony and photographs.
Fill in these details
- Room names, not descriptions. "The main room" is ambiguous on the day. Use the names printed on the venue signage.
- Access notes: Loading entrance, lift, parking limits, and where a supplier may park. This is the information that prevents a van blocking a lane.
- Guest numbers that change the plan: Children, wheelchair users, and anyone needing step-free access affect timings, seating, and the ceremony layout.
- Supplier contacts: Real names and real numbers. Replace anything the model produces with a verified contact.
- Venue constraints: Curfew and kitchen cut-off are non-negotiable and must be in the document itself, not in someone's head.
Write the wet weather plan before the forecast exists
A wet weather plan written on the morning of the wedding is a panic document. A wet weather plan written in advance is a set of instructions. The difference is entirely in the trigger: someone must be authorised to activate it, at a stated time, against a stated condition, without needing a phone call chain.
Build a wet weather contingency plan for a wedding at [venue] on [date]. The plan covers these outdoor elements: [ceremony lawn, drinks on the terrace, photographs in the garden, arrivals under the marquee edge]. The indoor or covered fallback for each is [name the actual spaces, with their capacities]. The decision will be made by [name and role] at [time] on the day, based on [the forecast source you will actually check and any ground condition you can see]. For each outdoor element give me: the trigger that moves it indoors, the exact alternative layout, who physically moves what and in what order, how long the move takes, and what it costs in time. Then write the two changes this plan forces on the printed timeline, as a revised sequence rather than a note. If a fallback space does not exist for an element, say NO FALLBACK AVAILABLE and describe the cheapest option to create one. Do not assume marquees, heaters, umbrellas, or covered walkways exist. Do not invent weather probabilities. Do not write anything that requires a supplier to act without confirming with them first, and mark those lines [CONFIRM WITH SUPPLIER].
The wedding-morning decision prompt
This is the prompt that runs at the decision time, not at the decision itself. It exists so that the person activating the plan is reading a checklist rather than improvising.
It is [time] on the wedding morning. The forecast is [paste the forecast]. The observed conditions are [what you can see outside, such as standing water on the lawn or steady rain]. Our stated trigger was [the trigger you agreed in advance]. Walk me through the decision in order: which elements move, which stay, who tells which supplier, and in what sequence. Give me a short message I can read aloud to each supplier. Then print the revised timeline with the changes marked, and list anything I must check by phone before confirming, such as an indoor space that has not been formally released for our use.
Keep the activation decision with one named person. A committee making this call adds delay to the exact situation built for delay.
Worked example: a ceremony that moves indoors
A venue with an outdoor ceremony lawn, a drinks terrace, and a marquee has the following written plan.
| Element | Trigger | Fallback | Move time | Cost in the timeline |
|---|---|---|---|---|
| Ceremony | Rain at decision time, or standing water on the lawn | Main room, rows reset to 80 seats | 40 minutes | Ceremony starts 40 minutes later |
| Drinks | Any rain | Marquee side wall closed | 10 minutes | None |
| Photographs | Rain continuing past the ceremony | Main room, window light | 5 minutes | Group photos shorten to 20 minutes |
The entry that matters is the one saying NO FALLBACK AVAILABLE. The garden portraits have no covered alternative in this budget, so the plan records that plainly and the couple decides in advance that portraits are dropped rather than improvised on the day.
Test the day plan before it prints
1. Walk the timeline backwards from the curfew
Start at the venue's hard stop and work backwards. This is how you find the ceremony time that cannot move and the speeches that will be cut, rather than discovering both when the band is loading out.
2. Check every named person is a real person
Read the owner and contact columns end to end. Placeholder names, missing numbers, and roles without a phone are the defects that appear only at 09:15 on the day. Replace them with verified contacts.
3. Confirm the fallback spaces in writing
Ask the venue to confirm that each fallback room is genuinely held for your use and available at the required time. A covered space that is technically booked by someone else in the afternoon is not a fallback, and discovering this during rain is the worst version of the discovery.
4. Hand it over and stop carrying it
Give the printed run sheet to one named coordinator and let them run the day. If you are also carrying a copy, you will both change it, and the version in the supplier's hand is the one nobody reads.
Common run sheet mistakes
- Writing it months early. Times move, and an out-of-date run sheet is confidently wrong. Rewrite it once times are confirmed, then re-check it in the final week.
- No named owner per line. A task without an owner is a task that gets done twice or not at all.
- Buffer created by hurrying. Adding two minutes to everything is not contingency. Adding reset time between activities is.
- Wet weather planned only as a note. A note without a trigger, an authorised person, and a revised timeline is not a plan.
- Assuming marquees and heaters. Cover is a cost and a supplier contract. If it is not booked, it does not exist in the fallback.
Frequently asked questions
When should I write the wedding run sheet?
Write the first version once the venue, ceremony time, and catering are confirmed, then rewrite it in the final week when supplier arrival times and the final guest count are known. Mark the printed version with the date it was generated, since it is the only live document.
Who should hold the run sheet on the day?
One named person, usually the coordinator or a trusted helper who is not a principal in the wedding. Give them the printed sheet, the supplier contacts, and the authority to activate the wet weather plan. They should not be looking for the document while also managing guests.
Can I use these prompts with Gemini or other assistants?
Yes. These prompts depend on structured output and explicit refusal instructions, not on any vendor-specific feature. Models differ in how reliably they fill long tables, so check the finished document against your venue constraints yourself rather than assuming the shape was respected.
Print it, then rehearse the moving parts
Generate the run sheet, fill every [AWAITING CONFIRMATION] with a real answer, and confirm the wet weather fallbacks with the venue in writing. Then read the activation time out loud to the person who will call it. For more prompts covering the operational side of the day, browse the wedding planner prompt collection.