Choose and Define Community Event Performance Measures

Choose a performance measure only when it answers a question tied to one of your event objectives and informs a decision someone will actually make. Then define each measure completely before the event: what it is called, its unit, how it is calculated (numerator and denominator), what is excluded, where the records come from, when they are collected, who owns them and which decision the result feeds. A measure that is missing any of these pieces tends to produce numbers nobody trusts or uses. This guide applies to amateur tournaments, community festivals, workshops, fundraisers and volunteer-run events of any size.

Start with objectives written as questions

Many organizers start with a list of popular event metrics and try to fit them to their event. It works better in the other direction. Rewrite each objective as a question, decide what you would do differently depending on the answer, and only then pick a measure capable of answering it.

Write each objective as a question. For example, "Run the bracket on schedule" becomes "Did matches start when the published schedule said they would?"
Name the decision the answer will inform. For example, whether to add a court, shorten match length or change check-in times next season.
Choose a measure that can actually answer the question. A headcount cannot tell you whether matches started on time; a log of scheduled versus actual start times can.
Check that you can collect the data with the volunteers and tools you have. A measure you cannot staff is a measure you will not get.
Remove any measure with no identified use. If nobody can say what decision it informs, drop it before event day.

Define every measure in one planning table

Put all measures in a single table that the whole organizing team can see. Each row is one measure, and every column must be filled in before the event. These are the columns to use and what each one settles.

Column	What it settles
Objective	The event goal this measure serves, written as a question
Measure	The short name everyone will use for it
Unit and definition	What is being counted and in what unit, such as percent, people, matches or dollars
Numerator	What goes on top of the calculation
Denominator	What it is divided by, so that percentages mean the same thing to everyone
Exclusions	What is deliberately left out, such as walkovers, staff badges or canceled sessions
Record source	Where the raw data comes from, such as the registration export, a scorer's log, a gate clicker or a feedback form
Collection time	When the data is captured: before, during or after the event, and at which point
Owner	The one person responsible for collecting and handing over the figure
Intended decision	What the result will be used to decide

The numerator, denominator and exclusions columns do the most work. Two volunteers can both report an "attendance rate" and mean entirely different things if one divides by registrations and the other by tickets sold, or if one counts no-shows who were refunded and the other does not. Agree on these definitions before anyone collects data, not after the results disappoint someone.

Worked example: a workshop delivery rate

This is a hypothetical example to show how a fully defined measure looks. Suppose one objective is to deliver the planned workshops at a community skills day.

Objective as a question: Did we deliver the workshops on the approved program?
Measure: Delivery rate.
Calculation: completed scheduled workshops divided by workshops on the approved program, multiplied by 100.
Result: if 9 of 12 scheduled workshops were completed, the delivery rate is 9 ÷ 12 × 100 = 75%.
Exclusions and special cases: decide in advance how to treat canceled, substituted and partially delivered sessions, and list each one by name in the report.
Record source: the program lead's session log.
Owner: the program lead.
Intended decision: whether to change presenter confirmation steps or reduce the number of sessions next time.

Note what this measure does not tell you. A 75% delivery rate says nothing about whether attendees learned anything or enjoyed the sessions. If those questions matter, they need their own measures, sources and owners, such as a feedback form summarized by a separate feedback owner.

Illustrative measures for tournaments and community events

The pairings below are illustrations of how objectives map to measures, not a required list. Use only the ones that answer your own questions, and define each one fully in your planning table.

Objective as a question	Possible measure	Numerator ÷ denominator
Did matches run on schedule?	On-time start rate	Matches starting within your agreed tolerance ÷ matches played, excluding walkovers and forfeits
Did registered teams show up?	Check-in rate	Teams checked in by the deadline ÷ teams with confirmed registration
Were volunteer shifts covered?	Shift fill rate	Shifts staffed for their full length ÷ shifts on the volunteer schedule
Did we reach new participants?	First-time participant share	Registrants who report this as their first event ÷ registrants who answered the question
Did people leave satisfied?	Satisfied respondent share	Respondents choosing your agreed top ratings ÷ respondents who answered the question
Did the event cover its costs?	Cost recovery	Event income ÷ event costs, using the same agreed list of income and cost categories

Notice that survey-based measures divide by people who answered, not by everyone who attended. Say so in the definition, because a high satisfaction figure from a small share of respondents should be read differently from the same figure across most attendees. Reporting the number of respondents alongside the percentage keeps that visible.

Assign owners and plan the handoff

Each measure needs one named owner who collects the data and passes it on with its definition intact. Shared ownership usually means nobody counts. For a small event, one person may own several measures; that is fine as long as the table says so.

Get attendance or check-in figures from the counting owner, together with the definition and denominator they used.
Get feedback summaries from the feedback owner, including how many people responded.
Keep each figure's definition attached to it when it moves into a report or slide, so nobody silently changes the denominator.
Send interpretation and follow-up decisions to the debrief owner, who decides what changes for next time.

Separate your targets from outside benchmarks

If you set a target, such as aiming for most matches to start on time, label it as an organizer-set target. Do not present it as an industry standard or compare it with another event's figure unless that figure was calculated with the same definitions. A target you chose is a planning decision; it is not evidence of what is typical.

Check the numbers before you share them

Recheck the arithmetic for every calculated figure.
Confirm that the numerator and denominator match the definition in the planning table.
Note any missing records, such as a lost scoresheet or a clicker that was reset, and state how they affect the figure.
List the exclusions you applied, by name where practical.
Confirm you are allowed to use and share the data. Participant contact details, ages and survey responses may be limited by what you told people at registration, by venue, sponsor or league rules, or by applicable law, so check the requirements that apply to your event before releasing anything that identifies individuals.