Incident Documentation and Waiver Records

Incident documentation and waiver records answer different questions. The signed waiver records what was presented and submitted during consent. The incident report records what staff observed and did after something happened.

Do not force both jobs into one document. Preserve the original waiver, create the incident report in the system your organization has approved, and use a consistent retrieval process to bring the records together when authorized people need them.

Define the record set before an incident

Counsel and your insurer should specify which records your business needs and how they should be handled. Operationally, the set may include:

Record	What it establishes
Signed waiver submission	Responses, signature data, submission time, and associated waiver version
Incident report	Observations, sequence, staff actions, and people involved
Medical or emergency response record	Care or escalation documented by the responsible team
Photo, video, or equipment record	Evidence preserved under an approved collection and access process
Follow-up log	Later communication and decisions, separated from the first report

FlexWaiver stores the signed submission and its waiver version. It is not an incident-reporting or evidence-attachment system. Narratives, photos, medical details, and follow-up should remain in the authorized system your business uses for those records.

Preserve the waiver as it was submitted

After an incident, staff should be able to retrieve the relevant submission without changing the original answers. Capture or note the details needed to locate it again:

Participant name as entered
Submission date and time
Waiver name and version
Location or activity context available in the workflow
Signer and guardian information when applicable
An internal incident identifier in the separate report

Do not paste sensitive incident notes into unrelated waiver fields or overwrite a mismatch. A discrepancy may be important to the review. Preserve it and let the approved follow-up process address it.

Record facts before interpretation

An incident report is easier to review when it distinguishes direct observations from conclusions. Train staff to capture:

What happened

Describe the observable sequence in plain language. Note what the participant was doing, where it occurred, and which equipment or area was involved. Avoid guessing at causes or medical diagnoses.

When and where

Use a specific date, time, and location. If times are estimates, label them as estimates rather than presenting false precision.

Who was present

Record the participant, responding staff, and witnesses under the organization’s policy. Do not collect extra personal details merely because a field is available.

What staff did

Document immediate actions, escalation, equipment isolation, emergency contact, and transfer of responsibility. Keep later follow-up in a dated log rather than rewriting the first account.

Use consistent identifiers across systems

The waiver platform and incident system may not have a direct connection. A documented naming convention can still make retrieval reliable.

For example, the incident report can reference the participant name, activity date, waiver name, submission time, and a submission identifier visible to authorized staff. The incident system owns the incident identifier; the waiver record remains unchanged.

Test this convention using realistic cases:

A guardian signed for a minor
Several participants share a family email address
A participant used a nickname in one system
The incident is reported days after the activity
More than one waiver was active for the venue
Staff from another location must assist with retrieval

The test succeeds when an authorized employee can locate the correct records without relying on the memory of the person who was on shift.

Control exports and duplicate copies

Incident response can prompt people to download, email, print, and screenshot records quickly. Each copy expands the number of places containing participant information.

Define in advance:

Which roles may inspect the waiver and incident report
Who may export or share a record
Where an approved export may be stored
How requests from counsel, insurers, participants, or authorities are routed
When temporary working copies must be removed
Who starts a preservation hold when counsel requires one

The FTC’s data-security guidance emphasizes knowing what personal information the business keeps, limiting what it retains, protecting access, securely disposing of records, and planning for security incidents. Apply those principles to original systems and every exported copy.

Build a first-hour checklist

The exact response depends on the activity and severity, but an operator checklist can separate immediate care from later administration.

Care for people first: follow the venue’s emergency and safety procedures.
Stabilize the area: preserve safety and prevent additional harm under the operating plan.
Notify the right role: involve the manager or incident lead defined by policy.
Create the incident report: capture timely observations in the approved system.
Identify the waiver record: note the submission and version without modifying either.
Preserve approved evidence: follow policy for photos, video, equipment, and access logs.
Route communication: use approved contacts and avoid informal commentary in public or group channels.
Start required follow-up: let counsel, the insurer, and internal policy determine notices, preservation, and next steps.

This checklist is a framework, not an emergency-response plan. Adapt it to the activity, jurisdiction, staffing, and professional guidance your organization relies on.

Run a quarterly retrieval drill

Choose a test participant and ask an authorized staff member who did not create the record to:

Find the signed submission
Confirm the associated waiver version
Locate the separate incident record from the documented references
Explain who may export each record
Identify the retention and preservation status
Record how long retrieval took and where the process was unclear

Fix naming, permissions, and written instructions before an actual request exposes the gap.

Incident documentation FAQ

Can FlexWaiver store incident photos and narratives? FlexWaiver stores waiver submissions and associated versions. Use your organization’s approved incident system for narratives, photos, medical details, and evidence handling.

Should staff add incident details to the signed waiver? No. Preserve the original submission. Record incident details separately and reference the waiver using consistent identifiers.

Who should have access? Access should follow a documented need-to-know policy approved by leadership, counsel, and your insurer. Avoid broad exports and informal sharing.

How long should incident and waiver records be retained? Requirements vary. Counsel and your insurer should define the periods, relationship between record types, and any preservation holds.

Keep researching

Preserve the signed record

Make waiver retrieval part of the incident drill.

Create a reviewed waiver, test the signing record, and document how authorized staff will retrieve the exact submission and version.

Start free

No credit card required.