Skip to main content
OchroniLoginStart free trial
ProcessPricingQuestionsLoginBook a demoStart free trial
Home/Supply chain incident guide

Manage a confirmed supply chain disruption.

Declare one incident. Record facts, impact, severity, tasks, customer messages, and closure. Ochroni also receives events from connected source systems.

Start free trialBook a demo

Published August 3, 2026 · Last reviewed August 3, 2026 · After detection · Ochroni recommendation

Category guideBuyer guide

Synthetic example — not a customer case study.

A vehicle stops before a time-critical pickup

We invented the facts, times, roles, and events in this example. They show a response method. They do not show a customer result.

Summary

Recommendation: start one shared response when a known disruption needs work from more than one person. Limit: Ochroni coordinates the response. Responders and source systems provide facts and estimates.

Reviewed August 3, 2026. Scope: supply chain incidents, tasks, and closure.

Incident response guide

Six steps for one incident response

Use this checklist after a disruption. Adjust the steps for the risk.

Incident roomDispatch · warehouse · customer
DeclareIncident declaration

Fact

Vehicle stopped near A2 at 07:14 CET

Impact

Two pickup commitments at risk

Incident lead

Dispatch lead
AssessImpact assessment

Safety

Driver safe

Service risk

Review two pickup commitments

Severity

High until the carrier responds
CoordinateOwned tasks

Recovery

Dispatch lead · replacement vehicle · due 07:35

Site

Warehouse contact · revised slot · due 07:40

Customer

Customer lead · next checkpoint · due 07:45
CommunicateCustomer message

Known

Pickup window at risk after a vehicle breakdown

Action

Replacement capacity and site slot under review

Next message

07:45 CET or after a material change
RecoverRecovery check

Decision

Use replacement vehicle · approved 07:42

Estimate

Arrival 08:05–08:20 · carrier source

Closure

Vehicle at site and revised slot accepted
CloseClosure record

Resolved

Replacement vehicle accepted at site · 08:20

Risk

Review revised departure

Follow-up

Carrier contingency task · named owner

Keep one incident record

Keep one incident record for facts and decisions. Assign each task an owner. Store each estimate with its source and time.

Step 1

Declare one incident.

Record known and unknown facts, impact, severity, and incident lead.

  • Record the movement or site at risk.
  • Separate facts from assumptions.
  • Set the next decision time.
Step 2

Assess the impact.

Check safety, service, orders, and time pressure. Record evidence for the current severity.

  • Check safety exposure.
  • Check service commitments.
  • Record the evidence.
Step 3

Assign the work.

Give each task one owner and one time. Keep decisions in the incident record.

  • Assign the recovery task.
  • Assign the site task.
  • Assign the customer task.
Step 4

Write a customer message.

State the fact. State the impact. State the active work. State the next time. Mark each estimate as an estimate.

  • State the known impact.
  • State the active work.
  • Set the next checkpoint time.
Step 5

Review the recovery.

Check the closure condition. Close the incident after the closure decision. Store each estimate with its source and time.

  • Record the recovery decision.
  • Update the task owner.
  • Check the closure condition.
Step 6

Close the incident.

Record the closure fact and active risk. Give each follow-up task an owner.

  • State the closure condition.
  • Record the active risk.
  • Assign each follow-up owner.
Review the incident room guideRoles and cadenceWrite a customer messageThree message templatesReview the incident recordEvidence-led templateCompare visibility and responseCategory comparisonReview access and hostingSecurity overview

Worked incident record

A synthetic vehicle breakdown

Synthetic example — not a customer case study. It illustrates a recommendation, not a measured response time or customer outcome.

Initial facts and owners

KnownVehicle stopped. Driver safe.
ImpactTwo pickup slots at risk
Incident leadDispatch lead
Cadence15 minutes or material change
07:14

Fact: the driver reports a breakdown on the A2 corridor. The driver is safe.

07:16

Decision: declare one incident because the disruption affects two pickup commitments.

07:18

Ownership: the dispatch lead becomes incident lead. Warehouse and customer tasks get owners.

07:20

Cadence: update every 15 minutes or after a material change.

07:25

Unknown: no source has confirmed replacement capacity or the revised site slot.

Tasks, messages, and closure

RecoveryReplacement vehicle
EstimateCarrier source and time
Customer messageRecorded
ClosureCondition met. Follow-up owned.
07:32

Task: dispatch asks a carrier contact to confirm replacement capacity by 07:40.

07:42

Decision: use the replacement vehicle. The carrier gives an 08:05–08:20 estimate.

07:45

Customer message: the record lists impact, action, uncertainty, and the next checkpoint.

08:05

Fact: the replacement vehicle reaches the site. The warehouse accepts the revised slot.

08:20

Closure: the team meets the condition. One contingency task remains with a named owner.

Choose a response scope

What this guide covers

Use this guide after responders confirm a disruption. It covers shared work, facts, tasks, customer messages, and closure.

Incident room

Use an incident room for named roles, owned tasks, one incident record, an update cadence, and a closure condition.

Use the incident room guide

Transport visibility

Use a source system for tracking, detection, or ETA estimates. Ochroni records facts after a person or connected system provides them.

Compare visibility and response

Closing checklist

Before you close one incident

Answer each item from the incident record.

  • Separate known facts, assumptions, impact, and current severity.
  • Name the incident lead and each active task owner.
  • Record the next checkpoint time.
  • Record each decision, reason, time, and person.
  • State uncertainty and the next checkpoint in the customer message.
  • Record the source and time for each estimate.
  • Record the fact at closure.
  • Name each residual risk task owner.

Severity guide

Four checks for current severity

Check each factor against current evidence. Raise severity when risk or coordination needs grow. This is an Ochroni recommendation, not an industry standard.

Safety and compliance

Low: no credible safety or regulatory risk. High: a credible risk needs specialist or leadership attention.

  • Record the source.
  • Escalate material uncertainty.

Operational scope

Low: one contained movement or task. High: several commitments, sites, partners, or operations face risk.

  • Count confirmed scope.
  • Update as facts change.

Decision urgency

Low: the next decision can wait for the normal cadence. High: delay may reduce recovery options or increase impact.

  • Name the decision time.
  • Shorten the cadence when needed.

Coordination scope

Low: one owner can resolve the issue. High: several tasks need separate owners and shared facts.

  • Add needed participants.
  • Review each scope change.

Facts, recommendations, and limits

What the method and product cover

The method is an Ochroni recommendation. Source systems, contracts, safety procedures, and customer commitments remain authoritative.

Fact boundary

Ochroni records responder entries and events from connected source systems. Check each material fact at its source.

Recommendation boundary

One incident lead, named task owners, one incident record, and a set cadence define the method. Adjust them for the incident.

Capability boundary

Responders declare incidents. Ochroni receives events from connected source systems. It does not detect logistics conditions. It does not calculate ETAs.

Hosting boundary

Ochroni stores customer content in the EU. Review security, privacy, and legal information before a trial.

Pricing

EUR 299 each month for the response team.

Use a synthetic incident in the trial. Contact Ochroni about security and rollout.

The public price does not include VAT. EU B2B reverse charge may apply.
EUR 299 each monthPay EUR 2,990 each year. Save two months.
  • Include all team members under fair-use terms
  • Use the incident room, tasks, incident record, and guest links
  • Use the product free for 14 days
  • Start without a payment card
  • Cancel renewal at any time

Fair-use terms apply to all team members and participants. The Terms of Service describe them.

Start free trialBook a demo

One plan

The price applies to the response team.

  • Include the response team in one plan
  • Start the trial
  • Use tasks and incident records
  • Publish customer messages

Review note

Incident management sources

Reviewed

August 3, 2026

What we compared

This page applies Ochroni incident, incident room, incident record, task, and participant features to logistics coordination. Government sources add general incident guidance.

Check these facts

The government sources give general coordination guidance. They do not specify logistics software or endorse Ochroni. Apply your safety, legal, contract, and operating requirements.

Spot a factual problem? Contact us.
  1. 01
    Ochroni home

    Ochroni · checked August 1, 2026

    Public price and trial for Ochroni.

  2. 02
    Ochroni security

    Ochroni · checked August 1, 2026

    Public security and guest access.

  3. 03
    Emergency response and recovery guidance

    UK Cabinet Office · checked July 17, 2026

    General guidance on clear objectives, roles, information management, coordination, and communication during an incident.

  4. 04
    National Incident Management System overview

    U.S. Fire Administration · checked July 17, 2026

    General incident-management context for shared terminology, roles, coordination, and information management.

FAQ

Review these questions.

When should a supply chain disruption become an incident?

Declare an incident when several people or workstreams must share tasks, decisions, communication, or escalation. Do not wait for every fact.

Does Ochroni detect a disruption or calculate an ETA?

No. Ochroni receives events from connected source systems. It does not detect logistics conditions. It does not calculate ETAs.

What belongs in the incident record?

Record material facts, decisions, task and ownership changes, estimates, customer message status, severity changes, closure, and follow-up tasks.

Can teams keep Slack or Microsoft Teams?

Yes. Use Ochroni for incidents. Use Slack, Microsoft Teams, or email for other work.

Can guests join an incident?

Yes. Guests use guest links from a phone browser.

Where does Ochroni store customer content?

Ochroni stores customer content in the EU. Review the Privacy Policy and DPA.

Can we review security before a trial?

Yes. Book a demo for security questions before a trial.

OCHRONI

Test this process with a synthetic incident.

Run a synthetic incident in the trial. Contact Ochroni to review declaration, ownership, customer messages, and closure.

Start free trialBook a demo

Use a synthetic incident. Check the source and time for every estimate.