[{"data":1,"prerenderedAt":164},["ShallowReactive",2],{"guide-\u002Fguides\u002Fday-of-operations\u002Fhow-to-run-multiple-parties-in-one-day":3,"guide-siblings-\u002Fguides\u002Fday-of-operations\u002Fhow-to-run-multiple-parties-in-one-day":154},{"id":4,"title":5,"author":6,"body":7,"description":129,"disclaimer":130,"draft":131,"extension":132,"faq":133,"lastReviewed":146,"meta":147,"navigation":148,"path":149,"publishedAt":146,"seo":150,"sitemap":151,"stem":152,"__hash__":153},"guides\u002Fguides\u002Fday-of-operations\u002Fhow-to-run-multiple-parties-in-one-day.md","How to run multiple parties in one day without losing your mind","Rally",{"type":8,"value":9,"toc":120},"minimark",[10,14,19,22,51,55,58,61,68,72,98,102,105,113,117],[11,12,13],"p",{},"The operators who run three or four parties on a Saturday don't work faster than you, they decide everything before Saturday. The formula is windows plus buffers plus one sheet of truth: every party in a fixed window, a full honest buffer between each, and a single source everyone reads instead of a group text everyone scrolls. The day runs itself or it runs you, and the difference is entirely in the prep.",[15,16,18],"h2",{"id":17},"the-day-is-built-on-tuesday","The day is built on Tuesday",[11,20,21],{},"By midweek, a multi-party Saturday should already have:",[23,24,25,33,39,45],"ul",{},[26,27,28,32],"li",{},[29,30,31],"strong",{},"The route decided."," Parties sequenced by geography and window, drive times checked for Saturday traffic, not Tuesday-at-midnight traffic. The 2pm party across the county from the noon party is a Tuesday discovery, when it can still be moved, staffed separately, or regretfully declined.",[26,34,35,38],{},[29,36,37],{},"The buffers verified per leg."," Real teardown, the actual drive, real setup, plus the cushion. The buffer math has its own guide, and on a multi-party day it stops being advice and becomes physics: three parties means two buffers, and the day's feasibility is just arithmetic.",[26,40,41,44],{},[29,42,43],{},"Every booking green."," Paid, crewed, prepped, checked midweek. Saturday morning is for loading, never for chasing a balance or finding a third crew member. A booking that's still yellow on Thursday is Thursday's problem, on purpose.",[26,46,47,50],{},[29,48,49],{},"Fluid and fuel counted for the whole day",", plus reserve, loaded as one total. Multi-party days are where \"enough for each party\" quietly becomes \"short for the last one.\"",[15,52,54],{"id":53},"one-sheet-of-truth","One sheet of truth",[11,56,57],{},"The failure mode of a big Saturday is information scattered across the operator's head, a group text, and three screenshots. The fix is one source, the run sheet, that every crew member reads on their phone:",[11,59,60],{},"Each stop gets: address and gate code, window and target arrival, on-site contact and cell, site notes from the booking (spigot location, the dog, the narrow gate), package and add-ons, and payment status. Sequenced, timestamped, done.",[11,62,63,64,67],{},"The rule that makes it work: ",[29,65,66],{},"if it's not on the sheet, it doesn't exist."," A change day-of, a moved window, a new gate code, goes on the sheet, not into a text that two of three people saw. One writer, everyone readers.",[15,69,71],{"id":70},"running-the-day-itself","Running the day itself",[23,73,74,80,86,92],{},[26,75,76,79],{},[29,77,78],{},"Status beats chatter."," Each crew taps where they are: on the way, arrived, setup done, party running, wrapped. The operator watches statuses flip instead of texting \"where are you\" into the void. Silence plus green statuses is a great Saturday.",[26,81,82,85],{},[29,83,84],{},"The lead owns the site, the operator owns the day."," On-site decisions, cannon placement, wind, a delayed start, belong to the crew lead. Cross-party decisions, cascading a delay, resequencing, calling a client, belong to whoever's running the day. Blur the two and every problem escalates to a phone call.",[26,87,88,91],{},[29,89,90],{},"A delay at party one triggers the cascade protocol, not panic."," The lead reports the slip, the operator recalculates the next arrival, and the next client gets a proactive text: \"Crew's running about 20 minutes behind, foam still flies for the full hour.\" A client warned at 1:30 is calm, and the same client discovering it at 2:10 writes reviews. The cushion absorbs most slips, and the protocol absorbs the rest.",[26,93,94,97],{},[29,95,96],{},"The last party gets the same crew energy as the first."," That's a staffing and pacing decision made on Tuesday: enough hands, real breaks, water in the truck. The fourth family paid the same price as the first one.",[15,99,101],{"id":100},"when-the-math-says-no","When the math says no",[11,103,104],{},"Some Saturdays don't fit: the windows overlap, the geography is hostile, the buffer math fails. The three honest moves are the same as ever: shift a window and sell the client the honest slot, split the day across a second rig or crew if the revenue carries it, or decline the booking that breaks the day and offer the next date. A blown triple costs three reputations, and a declined fourth party costs one booking. Operators consistently regret the former and forget the latter.",[106,107,110],"rally-aside",{"label":108,"to":109},"See dispatch in Rally","\u002Ffeatures",[11,111,112],{},"Rally's dispatch day view is the run sheet: every stop with its times, crew, site notes, and readiness dots in sequence. Crew tap statuses from their phones, the operator watches the day flip green from anywhere, and setup and teardown times per service keep the buffers honest when the bookings are made, not just when the day arrives.",[15,114,116],{"id":115},"the-line-to-remember","The line to remember",[11,118,119],{},"A four-party Saturday is a Tuesday project with a Saturday performance. If the day feels like improvisation, the prep was missing, not the talent.",{"title":121,"searchDepth":122,"depth":122,"links":123},"",2,[124,125,126,127,128],{"id":17,"depth":122,"text":18},{"id":53,"depth":122,"text":54},{"id":70,"depth":122,"text":71},{"id":100,"depth":122,"text":101},{"id":115,"depth":122,"text":116},"Three windows, two full buffers, one sheet of truth. The operators who run big Saturdays don't work faster, they decide everything before Saturday.","none",false,"md",[134,137,140,143],{"q":135,"a":136},"How many parties can one crew do in a day?","Whatever the windows, buffers, and daylight arithmetic allows, which for most operations is two comfortably and three ambitiously. Past three, the answer is almost always a second crew or rig, because the failure cost of a packed single-crew day compounds with every stop.",{"q":138,"a":139},"Should the crew go back to the shop between parties?","Only if the route or a resupply demands it. The day is designed so the truck leaves with everything: all the fluid, all the fuel, the reserve. Shop stops are the buffer-killers.",{"q":141,"a":142},"What if one client wants extra time mid-party and the day is stacked?","The lead's answer is warm and fixed: \"We'd love to, and we've got another family waiting on us today. Next time we can book the longer package up front.\" Extra time gets sold on stacked days at booking, never granted at the curb.",{"q":144,"a":145},"Do I need to be at every party?","The whole point of the sheet, the statuses, and the lead's authority is that you don't. The operator running the day from one site, or from home, watching statuses is the model that scales past the weekend where you personally can be everywhere.","2026-07-13",{},true,"\u002Fguides\u002Fday-of-operations\u002Fhow-to-run-multiple-parties-in-one-day",{"title":5,"description":129},{"loc":149},"guides\u002Fday-of-operations\u002Fhow-to-run-multiple-parties-in-one-day","xPgwtVyjRmFpBS2hOZLXdc0aofOpH5FbsGPJeO3HppY",[155,158,161],{"path":156,"title":157},"\u002Fguides\u002Fday-of-operations\u002Ffoam-party-setup-checklist","Foam party setup checklist (what to bring and what can go wrong)",{"path":159,"title":160},"\u002Fguides\u002Fday-of-operations\u002Fhow-to-do-a-site-check-without-visiting-the-site","How to do a site check without visiting the site",{"path":162,"title":163},"\u002Fguides\u002Fday-of-operations\u002Fwhat-your-crew-needs-to-know-before-every-event","What your crew needs to know before every event",1783921368482]