Incident Documentation Log

Create a factual incident record with time, location, observable events, actions, evidence, and follow-up ownership.

Entries stay in this browser. Data-use details

How to document an incident factually

Method: Safety and medical care come first. Complete the log when it is safe. Write what was seen, heard, received, or recorded, and label uncertainty instead of filling gaps with assumptions.

Create a factual incident record and assign follow-up

Start with the facts another person would need

Complete this after urgent safety and medical needs have been handled.

Date Time or time range Exact location How you learned about it

Immediate safety status Urgent needs were handled No urgent need was identified Status is not yet clear

Build the event sequence

Before

During

After

Account for records without changing originals

List what exists and where the original is stored. Do not upload it here.

Photos Video Messages or email Receipts or transaction record Access or system log Damaged property or scene record

Evidence location and handling notes

Assign follow-up instead of leaving a loose note

ActionOwnerDue or review date

Convert the incident record into follow-up

Record needs core facts

A good record lets another person reconstruct what happened and what remains open without relying on memory. It should be factual, limited, securely stored, and shared only with people who need it.

Missing before handoff

Date
Time
Location
Observable event sequence

Handoff or case reference

What the incident log is not

This log supports factual handoff and review. It does not replace emergency action, medical care, mandatory reporting, legal advice, or an official evidence process. Protect privacy, retain originals as required, and share the record only with people who need it.