Service Interruption and Detour Report

This template is used to record a specific transit service interruption or detour event, including when it happened, what caused it, which stops or trips were affected, and how riders were notified. It gives operations teams a consistent record for review, follow-up, and on-time performance analysis. It is especially useful when you need a single report that ties service impact to response actions.

Complete the report as soon as practical after the disruption is identified and again if new details become available during recovery. The best practice is to capture the initial facts while the event is fresh, then update the record once the service is restored and follow-up actions are known. If your agency uses incident escalation, this form can also serve as the post-event summary.

Dispatchers, supervisors, operations managers, or field staff who observed the event can complete it, depending on your workflow. The key is that the reporter should have direct knowledge of the disruption or access to verified operational details. If multiple people contribute, assign one owner so the report stays consistent and complete.

Use it for detours, missed stops, short turns, service suspensions, vehicle breakdowns, weather-related interruptions, traffic incidents, and other route-level service impacts. It also works for accessibility-related disruptions when a stop, lift, or boarding path is temporarily unavailable. If the event does not affect rider service or route performance, a lighter internal note may be enough.

The template captures the notification method, notification time, alternate service provided, and recovery actions in one record. That makes it easier to confirm whether riders were informed in time and whether the response matched the disruption. It also helps teams compare what was planned versus what actually happened during restoration.

Include the operational reason for the interruption in plain language, such as road closure, collision, weather, mechanical issue, staffing shortage, or emergency response. Add enough detail to explain the event without collecting unnecessary personal data or speculation. If the cause is still under review, note that clearly and update the record later.

Yes. You can add route-specific fields, service zones, dispatch codes, or internal escalation steps without changing the core structure. Many teams also add conditional logic for accessibility impact, alternate service details, or follow-up requirements so the form stays short when those sections do not apply.

An ad-hoc message is easy to miss, hard to compare, and usually lacks a consistent audit trail. This template standardizes the fields that matter for analysis, including duration, rider impact, notification timing, and recovery actions. That makes it easier to review patterns across events and reduce gaps in reporting.