A global petrochemical company spent millions on a supply chain control tower. The screens lit up with alerts the moment anything moved. When the first major disruption hit, the technology fired notifications within minutes. Then everything went quiet. Not because the problem had been solved, but because no one had ever established who owned the response or how decisions should be escalated.
The company had visibility into the disruption almost immediately. Deciding what to do about it took much longer.
Seeing is not the same as acting
Investments in AI, analytics, and visibility platforms have dramatically improved how quickly companies learn about disruptions. But recognizing a disruption is only the beginning. Understanding its impact, deciding how to respond, and executing that response can take weeks.
We call this elapsed time supply chain response latency. It is the gap between knowing a problem exists and doing something about it. And it is the most under-measured number in modern supply chains.
The gap is measured in weeks
A recent survey of 2,500 global manufacturers found that 47% take about a week just to identify which materials, suppliers, sites, or products are affected by a disruption. Another 23% take a month or longer to understand what the disruption means for their supply chain.
Once the critical risk information is finally available, it takes an average of 16.4 additional days before that information influences a decision. The best performers close that gap in 10 days. The worst need 20.
Every additional day before a decision translates into lost production, higher expediting costs, missed customer commitments, or fewer recovery options. The organizations that close the gap fastest are not the ones with the most sensors. They are the ones with the clearest response processes.
Add those stages together and the picture is sobering: response latency is measured in weeks, not hours. A real-time alert has little value if it lands in a multi-week decision and execution delay.
The formula is simple: response latency equals the time to understand the impact, plus the time to decide on an action, plus the time to execute that action. Organizations routinely measure inventory, cost, service, and lead times. Almost none measure how long it takes to move from a disruption notification to an informed action.
Why the week disappears
Part of the answer is how decisions are actually made. In the same survey, 46% of organizations described their decision-making as primarily analyzing past actions and consequences. Only 17% reported proactive decision-making supported by AI or machine learning.
Historical analysis explains what already happened. Disruption response requires teams to weigh trade-offs and choose a course of action while the situation is still unfolding. The longer it takes to fold new information into decisions, the longer the latency.
Picture the planner who receives a port closure alert at 9 a.m. The impact assessment meeting is scheduled for Thursday. The reroute proposal needs three signatures. By the time the last signature lands, the backup port is congested too. The alert was perfect. The response was the problem.
Four ways to close the gap
1. Decide who decides. Create a decision-rights matrix that names the owner, approver, contributors, and escalation threshold for the most common disruption scenarios. Teams should know which decisions can be made locally and when an issue must be escalated.
2. Cut the approvals. Every additional approval introduces delay. Review your three most recent disruptions and identify every approval that added time without materially improving the decision. Then remove it.
3. Write the playbook before the crisis. Response playbooks for the highest-probability, highest-impact disruption types mean teams do not have to invent a response under pressure. The time between recognizing a problem and acting on it shrinks dramatically.
4. Measure response latency. For the next disruption, record four timestamps: disruption notification, impact confirmation, decision, and execution. Do this for a few real events and you will find exactly where the week goes. Use those findings to refine playbooks, clarify decision rights, and streamline approvals before the next disruption occurs.
Your next bottleneck is a timestamp away
If you measured response latency today, where would the biggest delay appear: understanding the impact, making the decision, or executing it?
Start with the last disruption you lived through. Write down the four timestamps, then ask who decided, who approved, and which step added the most time. The answer will tell you exactly where your next improvement should go.
That question matters more than which visibility platform you buy next. Because a supply chain that can see every problem but cannot act on any of them is not resilient. It is just well informed.