Event planning guides
RVA event run sheets with practical handoffs
An RVA event run sheet should tell the organizing team what happens next and who owns it. Include access and cleanup, not just the guest program.
What you'll learn
- Write actions instead of vague milestones
- Write the run sheet for someone covering your role
- Decisions to resolve before you commit
A useful run sheet should let another organizer identify the next action without calling you. Include access, delivery, setup, program, and closing. Pair each action with a person and any dependency that could delay it.
Write actions instead of vague milestones
Download the blank event run sheet to fill in your own times, owners, locations, dependencies, and handoffs. It opens in a spreadsheet and contains no automatic scheduling formulas. The planning templates collection includes the brief, budget, packing list, and role cards that support it.
Pair each time with a task, owner, and dependency. Add the contact needed if the task is delayed. Keep the sheet short enough to scan during the event and distinguish fixed commitments from flexible program moments.
Write the run sheet for someone covering your role
Instead of writing catering at five, specify who receives food, where it goes, and when service begins. Those are different actions and may involve different people.
Use columns for time, action, owner, location, and dependency. Replace “catering at five” with separate receiving, setup, and service tasks. Mark flexible moments distinctly from supplier deadlines. Before the event, ask each lead to read their rows and identify any handoff they do not understand.
Decisions to resolve before you commit
| Decision | What a usable answer includes |
|---|---|
| Action | Describe what must happen rather than a vague milestone |
| Owner | Name the person responsible and their contact |
| Dependency | Identify the prerequisite and fallback contact |
Avoid the mistake that creates extra work
Avoid issuing several run sheets with different times. Keep one current version and communicate material changes to the affected people.
Show the dependency as well as the time
Suppose refreshments are delivered at 12:30 and the group break begins at 12:45. Those two lines leave a gap: someone must receive the delivery, resolve any discrepancy, and prepare the agreed service arrangement. Put those tasks and their owners in the run sheet rather than assuming the break starts successfully because the delivery arrived.
| Example row | Owner | Dependency | Completion signal |
|---|---|---|---|
| Receive delivery | Receiving lead | Confirmed access and current order | Items checked or issue assigned |
| Prepare service | Named helper | Delivery and agreed setup instructions | Host told the arrangement is ready |
| Announce break | Facilitator | Readiness signal | Guests receive clear instructions |
Mark the times as estimates or confirmed commitments as appropriate. If a dependency slips, tell the decision owner; do not silently move only your own line and leave the next person working from the old time.
Use the setup timeline for work before arrival and the delay plan for agreed program adjustments. Keep one current version and communicate material changes to each affected lead.
Further planning resources
For the surrounding logistics, use the RVA gathering guides. Research local options with Richmond Region Tourism regional overview. Confirm specific property arrangements directly.
A little more clarity
Common questions
Should every conversation appear on a run sheet?
No. Include operational actions and important program transitions rather than scripting informal social time.
