Community Event Cancellation Decision Checklist
Assign who reviews resource shortages, who decides whether your community event or tournament proceeds, how the decision is recorded and who sends cancellation notices.
Contents
Before event day, assign a few people to a few jobs. One person reviews resource shortages. One decision-maker, with a named alternate, decides whether the event goes ahead. One person records that decision. One person sends cancellation notices. Then set fixed review times. At each review, compare confirmed resources against minimums you defined in advance and choose one of four outcomes: proceed, modify, postpone or cancel. Write down the reason and the time of authorization. If you cancel, work through a notice register so every audience gets the same approved message from a named owner.
This checklist is an internal workflow for amateur tournaments, leagues and volunteer-run community events. It does not tell you what you owe anyone if you cancel. Refunds, credits, fees and penalties depend on your venue agreement, your participant policies, any governing-body rules your event follows and the obligations that apply where you operate. Give one person the job of confirming those terms before any promise about them appears in a notice.
Assign the roles before anything goes wrong
- Resource reviewer: gathers confirmed counts for staffing, venue access, equipment and other essentials, and reports shortfalls at each scheduled review.
- Decision-maker: the person authorized to choose proceed, modify, postpone or cancel.
- Alternate decision-maker: a different person who takes over if the decision-maker can't be reached by the review time.
- Decision recorder: writes down the shortages reviewed, the alternatives considered, the outcome, the reason and the time it was authorized.
- Communications lead: owns the cancellation action register and confirms each notice was sent.
- Venue and policy owner: checks venue terms and participant policies before notices mention refunds, credits, rescheduling or fees.
In a small event, one person can hold more than one role. Write every name down anyway, and make sure the alternate is a different person from the decision-maker. Share the list with the whole organizing team so nobody has to guess who makes the call.
Set minimums before you review shortages
A shortage only means something when you compare it with a minimum. Before event week, decide what the event can't run without. That might be a number of staffed stations, the courts or rooms you need, specific equipment or anything else your format depends on. These are organizer choices, so record them as your own thresholds. Separately note any requirement that comes from the venue or a governing body.
| Event component | Organizer-defined minimum | Currently confirmed | Shortfall | Proposed alternative | Alternative owner | Confirmation deadline | Decision needed |
| Staffing (e.g., scorekeepers, check-in) | [your minimum] | [confirmed count] | [gap] | [e.g., reduced format, combined stations] | [name] | [time] | Yes / No |
| Venue availability | [spaces and hours needed] | [confirmed with venue] | [gap] | [e.g., shorter schedule, alternate space] | [name] | [time] | Yes / No |
| Equipment | [items needed] | [items confirmed] | [gap] | [e.g., borrowed or substitute items] | [name] | [time] | Yes / No |
| Other essential resource | [your minimum] | [confirmed] | [gap] | [alternative] | [name] | [time] | Yes / No |
Count only what is confirmed. A volunteer who said they might come, or a delivery that is expected but not scheduled, does not go in the confirmed column.
Run the decision on a schedule
- 1. Set review times in advance and name the decision-maker and alternate for each one.
- 2. Have the resource reviewer bring only confirmed shortages to the review.
- 3. For each shortfall, list the proposed alternative, who owns it and when it must be confirmed.
- 4. Assess each alternative against the criteria your team agreed on beforehand, such as whether the format stays fair or whether essential roles are still covered.
- 5. The decision-maker chooses proceed, modify, postpone or cancel.
- 6. The recorder logs the decision, the reason and the time it was authorized.
- 7. If no final decision is made, record the exact time of the next review. Don't leave the question open.
What each outcome means in practice
| Outcome | When it fits | What happens next |
| Proceed | All minimums are confirmed | Confirm the final setup with staff and volunteers |
| Modify | A shortfall is covered by an approved alternative, such as a reduced format | Tell affected participants, captains and volunteers what changed |
| Postpone | The event can't run as scheduled, but you intend to hold it later | Send notices saying when the next update will come, and route date and policy questions to their owners |
| Cancel | No approved alternative covers the shortfall | Start the cancellation action register |
Record the decision the same way every time
Event:
Review time:
Decision-maker (or alternate acting):
Confirmed shortages:
Alternatives considered and result:
Decision: Proceed / Modify / Postpone / Cancel
Reason:
Authorized at (time):
Next review (if no final decision):
Recorded by:
Keep this record with your other event documents. It shows volunteers, partners and future organizers what you knew, what you tried and who signed off.
Coordinate cancellation notices
Build cancellation notices on plans you already have. Use your communication plan for channels, approved message templates and contact lists. If weather is the reason, follow your weather plan so you don't create a second set of thresholds or timelines. The register below tracks who tells whom, what they say and whether it was done.
| Audience | Notice owner | Approved message | Channel | Send time | Completed | Follow-up owner |
| Participants and registrants | [name] | [message version] | [per communication plan] | [time] | Yes / No | [name] |
| Team captains | [name] | [message version] | [channel] | [time] | Yes / No | [name] |
| Volunteers | [name] | [message version] | [channel] | [time] | Yes / No | [name] |
| Venue contacts | [name] | [message version] | [channel] | [time] | Yes / No | [name] |
| Suppliers | [name] | [message version] | [channel] | [time] | Yes / No | [name] |
Include only the audiences that apply to your event. Don't let a notice mention refunds, credits, a new date or fees until the venue and policy owner has confirmed the venue terms and participant policies behind them. If those answers aren't ready, the notice can say the event is cancelled and when the next update will come.
Example: a staffing shortfall (hypothetical)
This scenario is illustrative, not drawn from a real event. An organizer decides that four staffed stations are the minimum for the planned format, but only three are confirmed. A format coordinator has until 4:00 p.m. to work out whether a reduced format could run with three stations. At 4:15 p.m., the named decision-maker reviews that option against the team's agreed criteria. If the decision is to cancel, the record names who updates the registration page, who contacts teams and who confirms supplier notifications.
Quick checklist
- Resource reviewer named
- Decision-maker and a separate alternate named
- Decision recorder named
- Communications lead named
- Venue and policy owner named
- Minimums set for staffing, venue, equipment and other essentials
- Review times scheduled
- Decision record template ready
- Cancellation action register set up and linked to the communication plan and weather plan
- Venue terms and participant policies confirmed before any notice promises refunds, credits or new dates
Related articles
Plan a Community Event Information Desk Enquiry Workflow
Build an information desk enquiry workflow for a community event or tournament: desk reference sheet, enquiry log template, referral steps and a printable desk copy.
Plan and Maintain a Community Event Attendee FAQ
Build an attendee FAQ from approved event information, with a named owner for each answer, publication approval and clear triggers for rechecking.
Prepare a Community Event Committee Handover
A practical handover template for community event and tournament committees: what to record, how to transfer each work area, and how successors confirm ownership.
Define Roles and Responsibilities for a Community Event Committee
A practical way to assign committee roles for a community event or amateur tournament: name an owner for every deliverable, set approval authority, map dependencies and agree when changes get reviewed.
Specify the Information and Presentation for an Event Ticket
Build a ticket design brief for your tournament or community event: confirm the required details, set a clear visual hierarchy and lock down print or digital output needs before design starts.
Compare Volunteer Management Software Against Event Requirements
Compare volunteer management software against your event's real needs with a requirements worksheet, scripted demo tests, like-for-like pricing and fair scoring.
Plan a Community Cleanup Event
A practical guide to planning a community cleanup: define the purpose and area, assign named owners, confirm collection arrangements and send participants a clear, final plan.
Plan Waste Collection and Cleanup for a Community Event
A step-by-step plan for community events and amateur tournaments: reduce materials, map collection points, assign volunteers and close out cleanup with confirmed collection.
Coordinate Community Event Accessibility Requests
A practical template for collecting, answering and confirming accessibility requests at community events and amateur tournaments, with restricted tracking and clear delivery owners.
Plan Accessibility Across a Community Event
An event accessibility checklist for community events and amateur tournaments: build an accessibility plan from publicity to arrival, venue, activities, vendors and emergencies.