NTD Safety and Security Major Event Report

Use this template for reportable major safety and security events that meet your agency's NTD filing rules, such as fatalities, serious injuries, major property damage, or other qualifying incidents. It is designed to capture the facts needed to classify the event and document why it is reportable. If the incident is minor, routine, or outside your reporting threshold, this template is usually not the right fit. When in doubt, route the event through your compliance or safety lead before submitting.

This template is built for time-sensitive filing workflows, so it should be completed as soon as the incident is stabilized and the core facts are known. The form includes a reporting_deadline_met field to help track whether the filing window was satisfied. If the event is still unfolding, submit the known facts first and update the record when investigation details are confirmed. Do not wait for a full root-cause analysis if the reporting deadline is approaching.

A safety, security, operations, or compliance representative should complete the form, depending on your agency's incident workflow. The reporter should be someone who can verify the event details, coordinate with responders, and preserve the audit trail. In many agencies, the initial draft is entered by dispatch or operations and then reviewed by a compliance owner before submission. The reporter_name, reporter_title, and reporter_email fields make ownership clear.

The event_summary should describe what happened in plain language, including the type of incident, where it occurred, and the immediate outcome. Keep it factual and avoid speculation about cause unless it has been confirmed. Use the event_category field to classify the incident, and use injury_or_damage_details to add supporting context. A good summary is short enough for review but specific enough for audit and follow-up.

Use the numeric fields for fatalities_count, serious_injuries_count, and property_damage_estimate so the report can be reviewed consistently. Enter only confirmed counts and estimates, and update them if the investigation changes the record. If there was no injury or no damage, record zero rather than leaving the field blank when your workflow requires a value. This helps avoid ambiguity during NTD review and internal audit.

Yes, the multiple_agencies_involved field and other_agencies section are meant for joint incidents, shared facilities, and coordinated response events. List the other agencies only when they were directly involved in the incident, response, or reporting chain. If the event was entirely internal, leave those fields blank or set the branching logic to hide them. This keeps the form aligned with data minimization and reduces unnecessary PII collection.

Attach only the documents that support the report and are actually needed for review, such as photos, incident logs, dispatch notes, or a short timeline. Avoid uploading unrelated records or sensitive files that are not necessary for the filing. If your process uses an audit trail, make sure the attachments are time-stamped and tied to the incident record. Use progressive disclosure so attachment prompts appear only after the core event fields are completed.

This template standardizes the fields needed for NTD reporting, which makes it easier to compare incidents, review deadlines, and preserve an audit trail. Ad-hoc emails often miss key details like event classification, asset identifiers, or confirmation that the deadline was met. A structured form also supports validation, required-vs-optional clarity, and cleaner handoff to compliance reviewers. That reduces rework when the report is prepared for submission.