Prepare a Factual Community Event Incident Record

A factual community event incident record is a short, structured note about what happened. It does not guess why it happened. The core rule is to give four kinds of information their own fields: what the recorder directly observed, what other people reported, what actions have already been taken (by whom and when), and who is authorized to follow up. The same field list works in Word, a fillable PDF or a spreadsheet. This guide covers the record itself, not how to respond to an emergency. Your event's safety plan, venue rules and any applicable reporting requirements still govern the response.

Fields to include in the record

Use the same fields every time so that records from different volunteers and different events can be compared. The order below moves from identification to facts to follow-up.

Field	What to record	Notes
Incident ID	A unique reference, such as an event code plus a number	Assign it when the record is opened
Recorder	Name or role of the person writing the record	Collect only the identity details your organizer has approved
Event	Event name, division or session	Useful when several events share one log
Occurrence date and time	When the incident happened	Mark it as approximate if the exact time is not known
Recording date and time	When the record was written	Keep it separate from the occurrence time
Location	Court, field, table, room or area	Use the names on your site map or schedule
Direct observations	Only what the recorder personally saw or heard	No causes, diagnoses or fault
Attributed accounts	What others reported, credited to their name or role	One entry per person
Actions already taken	What was done, by whom and at what time	Facts only, no recommendations
Related record references	IDs of linked forms, photos or venue reports	Store references, not copies
Follow-up owner and status	The authorized person responsible and the current status	For example: open, handed off or closed

Keep observations, accounts and actions apart

Most weak incident records blend these categories. A recorder writes down a bystander's statement as if they saw it themselves, or turns an observation into a conclusion. Each field answers a different question:

Direct observation: What did the recorder see or hear firsthand?
Attributed account: What did someone else say, and who said it?
Action already taken: What was done, by whom and when?
Authorized follow-up: Who owns the next step, and what is its status?

Illustrative example (hypothetical): During a tabletop tournament, a volunteer finds a chair on the floor and fills in the record like this:

Direct observation: At approximately 14:10, I saw a chair lying on its side beside table B.
Attributed account: The table steward reported that it had fallen before I arrived.
Action already taken: At 14:12, the event coordinator moved the chair.
Follow-up: Assigned to the event coordinator; status open.

Notice what the example leaves out. The steward's statement stays in the account field and is not presented as the recorder's observation. The record does not say why the chair fell or whether anyone was at fault. It does not mention injuries unless someone directly observed one or reported one. If a detail matters but nobody knows it, write "unknown" instead of filling the gap.

Copy-ready template text

You can paste the block below into a Word document, use it as the layout for a fillable PDF, or turn its labels into spreadsheet column headers. It is a starting structure, not an official form. Adjust it to match any requirements from your venue or governing body.

COMMUNITY EVENT INCIDENT RECORD
Template revision: ________

Incident ID:
Recorder (name or role):
Event / session:
Occurrence date and time:        [ ] exact   [ ] approximate
Recording date and time:
Location:

DIRECT OBSERVATIONS (seen or heard by the recorder only)


ATTRIBUTED ACCOUNTS (one per person: name or role, then what they reported)
1.
2.

ACTIONS ALREADY TAKEN (action | by whom | time)
1.
2.

RELATED RECORD REFERENCES


FOLLOW-UP
Authorized owner:
Status:   [ ] open   [ ] handed off   [ ] closed

CORRECTIONS (what changed | by whom | date)
1.

If a fact is not known, write "unknown". Do not leave it blank or guess.

Word, PDF or Excel: build every version from one field list

Each format suits a different job. A Word document is easy to edit and to print for clipboards. A PDF keeps a fixed layout and can be made fillable. A spreadsheet makes it easier to log and sort many incidents across a season. Whichever formats you use, keep them consistent:

1. Write a field dictionary that gives each field's name, what belongs in it and a sample entry. Every version uses the same names in the same order.
2. Choose one format as the master record and decide where the official copy lives. Give the template a revision reference, such as a version number and date, and print it on every version.
3. In a spreadsheet, use one row per incident and one column per field. If several people give accounts, number them within a single cell, or keep a separate accounts tab linked by incident ID.
4. Test conversions before event day. Fill in a sample record, convert it between formats, and confirm that no field was dropped, cut short or merged with another.
5. Withdraw old versions so volunteers are not filling in mismatched forms.

How to record an incident on event day

Recording does not replace the response your safety plan requires; it happens alongside it. Once the people responsible have handled the immediate situation, a recorder can work through these steps:

1. Open a new record and assign the incident ID.
2. Note the occurrence time, marked approximate if needed, and the current time as the recording time.
3. Describe the location using the names on your site map or schedule.
4. Write direct observations in plain, specific language: what, where and when.
5. Add each person's account separately, credited to their name or role, and keep it as close to their own words as practical.
6. List the actions already taken, with who took each one and when.
7. Add references to any related records.
8. Hand the record to the authorized follow-up owner and set the status.

Corrections and unknown facts

Records change as new information arrives. Do not overwrite an earlier entry. Instead, add a correction that shows what changed, who made the change and when. In a spreadsheet this can be a corrections column or a change-log tab. In Word or PDF, a dated corrections section at the end works. Mark any fact that has not been established as unknown, and if it becomes known later, update it through a tracked correction.

Decisions to settle before you use the template

The template organizes what gets written down. It does not decide who may see the record or where it must be sent. Before the event, the responsible organizer should settle the points below. Requirements from the venue, insurer, governing body and applicable law vary by event and location, so check the current ones for your situation.

Which identity details are collected, and about whom
Who can view and edit records
Where records are stored, and which copy is the master
How long records are kept
When and how records are passed to the venue
Which incidents, if any, must be reported to an outside body, and who reports them

Wording to avoid

Causes: write "the chair leg was detached" if you saw it, not "the chair broke because the leg was loose."
Diagnoses: describe what you observed, such as "held their wrist," rather than naming an injury.
Fault: leave blame and responsibility to the authorized follow-up process.
Unattributed statements: replace "someone said" with an account credited to a name or role wherever possible.
Vague times: replace "earlier" with an approximate clock time.