Structure a Factual Community Event Summary Report

The format at a glance

A factual event summary report starts by naming who it is for and what period it covers. It then covers the event's identity and objectives, the activities actually delivered, documented participation, recorded outcomes, and the records behind each figure. The same order works for a weekend tournament reported to a league board, a neighborhood festival reported to a sponsor, or a volunteer clean-up reported to a grant funder. This kind of report states what happened and what your records establish. It is not a promotional recap or an impact evaluation. Every number in it should trace back to a named record and the person responsible for that record.

• 1. Report details: recipient, purpose, reporting period, preparer and approval date
• 2. Event identity and objectives: name, dates, location, organizing group and what the event set out to do
• 3. Activities delivered: what was planned compared with what actually took place
• 4. Participation: documented counts, each with its definition and source
• 5. Outcomes: results a record supports, kept separate from forecasts and impressions
• 6. Issues and follow-up: an authorized summary only, with a pointer to where the full records are held
• 7. Evidence references: a table linking each claim to its source record and owner

Pin down the brief before drafting

Four inputs shape the rest of the report, so confirm them first.

• Recipient: a league committee, sponsor, funder, venue or your own volunteer team will each need a different level of detail.
• Purpose: the report might account for funds, record the event for next year's planning, announce results or meet a required filing.
• Reporting period: give the exact dates covered, especially if registration, setup or follow-up activity fell outside the event days.
• Required format: if the recipient supplies a template, word limit or set of required fields, follow it. Fit your sections into their structure rather than imposing your own.

Some content is required and some is your choice, so keep the two apart. A funder's reporting template, a governing body's results submission or a venue agreement may dictate content and deadlines, so read the actual document rather than assuming what it asks for. Everything else is an organizer decision, including section order, level of detail and whether to include photos.

What goes in each section

Event identity and objectives

State the event name, dates, location and organizing group. Then give the objectives as they were written before the event. Reproduce the original objectives rather than rewording them afterward, so readers can compare intent with delivery.

Activities delivered

Set what was scheduled beside what happened, and note cancellations, substitutions and format changes. For a tournament, this section covers the format used, the number of divisions, matches scheduled and completed, and any rescheduled or forfeited games. Support it with the approved program or schedule and the session or match logs.

Participation

Every count needs a definition. 'Registered', 'checked in', 'attended at least one session' and 'unique individuals across both days' are four different numbers. Mixing them is the most common source of contradictory figures. Name whose count you are using, such as the registration lead, the gate team or the scorekeepers. Use one owner's defined figure for each measure.

Outcomes

Report an outcome only when a record supports it. Examples include final standings from the official scoresheets, funds raised from the treasurer's reconciled total, or items collected from a counted or weighed log. Keep projected figures and actual figures in separate, clearly labeled places so a forecast never reads as a result. If you include an estimate, label it as an estimate and say how it was made.

Issues and follow-up

Incident details, injury reports and disputes belong in restricted records held by a designated owner. The summary report carries only an authorized summary suited to its audience, plus a note on who holds the full record. Treat improvement commitments the same way: list them briefly and point to the debrief tracker where they are managed, rather than reproducing the debrief.

Match each statement to what the record actually shows

A record supports a specific claim, not everything near it. Take a hypothetical case. 'Four workshops were scheduled and three were delivered' can be supported by the approved program and the session logs. 'Thirty people attended a workshop' needs the participation owner's defined count. Neither statement shows that participants learned a skill. Include a learning outcome only when an appropriate documented assessment supports it.

Tournaments work the same way, as this illustrative example shows. A check-in sheet can show how many teams arrived. Scoresheets can show how many matches were completed and who won. Neither shows that players enjoyed the event or plan to return. That kind of claim needs its own record, such as a post-event survey with a stated number of responses. Otherwise leave it out.

Build an evidence table

Fill in the evidence table before you write any prose. Keep it as a working document behind the report or attach it as an appendix, with one row per claim. The rows below are hypothetical and show the detail each column needs.

Claim	Value or description	Unit and definition	Reporting period	Source record	Responsible owner	Verification status
Teams competing	14	Teams that checked in and played at least one match	Event days	Check-in sheet	Registration lead	Confirmed with owner
Matches completed	41 of 44 scheduled	Matches with a signed final score; 3 forfeits	Event days	Official scoresheets	Results lead	Confirmed with owner
Volunteers	22	Individuals who signed in for at least one shift	Setup through teardown	Volunteer sign-in log	Volunteer coordinator	Draft
Funds raised	Net total	Reconciled income minus event expenses	Registration open through final payment	Treasurer's reconciliation	Treasurer	Disputed

Verification status can be as simple as draft, confirmed with owner or disputed. At sign-off, any row still marked disputed should either be resolved or removed from the report body.

Assemble the report step by step

• 1. Confirm the recipient, purpose, reporting period and required format.
• 2. Gather the source records: program and schedule, registration and check-in data, scoresheets or results, financial reconciliation, volunteer sign-ins, and any quotations or images you might use.
• 3. Fill in the evidence table before drafting prose.
• 4. Reconcile figures with the attendance and metrics owners. Where two versions of a number exist, agree which record governs, and note its definition.
• 5. Draft each section using only figures that appear in the table.
• 6. Check that forecasts and actuals are labeled and kept apart.
• 7. Obtain permission for every quotation and identifiable image you plan to include.
• 8. Replace incident and debrief detail with authorized summaries and references to the record owners.
• 9. Review the draft against the table. Every number in the text should match a confirmed row.
• 10. Get approval from whoever signs off, and date the approved version.

Who confirms what before release

Group the final checks by responsibility. Each check is complete when its stated condition is met. Adjust the roles to match how your team is organized; on a small event one person may hold several.

Responsibility	Check	Done when
Report preparer	Recipient's required fields are covered	Each required field maps to a section or is marked not applicable
Registration or attendance lead	Participation counts and definitions	The lead has confirmed each figure and its definition in the evidence table
Scorekeeper or results lead	Standings, match counts and forfeits	Figures match the official scoresheets or results system
Treasurer	Income, expenses and funds raised	Totals match reconciled records, with forecasts labeled separately
Volunteer coordinator	Volunteer numbers and shifts	Figures match the sign-in records under a stated definition
Communications or media lead	Quotations and images	Permission is on file for each one used
Incident record owner	Incident summary wording	The owner has approved the summary as written
Approver	Final version	Approved, dated and saved as the record copy

A fill-in outline

EVENT SUMMARY REPORT

Prepared for:        [recipient]
Purpose:             [why this report exists]
Reporting period:    [start date] to [end date]
Prepared by:         [name, role]
Approved by / date:  [name, role, date]

1. Event identity and objectives
   Name, dates, location, organizing group
   Objectives as written before the event

2. Activities delivered
   Planned:    [items from approved program or schedule]
   Delivered:  [items confirmed by session or match logs]
   Changes:    [cancellations, substitutions, format changes]

3. Participation
   [Measure]: [value] - [definition] - [source record]

4. Outcomes
   Actuals:    [recorded results with sources]
   Forecasts:  [labeled estimates and how they were made]

5. Issues and follow-up
   [Authorized summary] - full record held by [owner]
   Improvements tracked in [debrief tracker]

6. Evidence references
   Claim | Value | Unit and definition | Period | Source | Owner | Status