Skip to content
Blog Roc Disruption Documentation

Disruptions

What Good ROC & Disruption Documentation Looks Like

Dispatch IntelEducational operational content only. FleetFlow does not guarantee Amazon Relay scores or platform outcomes, and Amazon controls its own platform rules and metrics.

Disruptions are not unusual. Handling them badly is what turns an incident into a performance problem.

01 Collect facts

Time, location, driver status, equipment status, facility status. Facts first, opinions later.

02 Communicate and escalate

Notify the right parties, including ROC where appropriate for the managed load, while the load is still active.

03 Document and follow through

A disruption that is documented while it is happening can be defended later. One that is reconstructed from memory usually cannot.

Want this handled for your fleet?

Talk to FleetFlow ↗