King of Freight · Concept prototype

The TMS remains the system of record for loads, contracts, customer master data, and accounting. This fictional demonstration shows how FreightFlow could surface what needs attention, who should act, and whether it was resolved.

Synthetic data · fixed Sep 8 scenario · saved in this tab

Settings / controlled automation

Automation rules

Explicit operating logic that teams can inspect, explain, and audit.

12 active rules

Rules in catalog

versioned domain definitions

Rule catalog

Rules are read-only in this demo. The typed catalog is structured for later versioning and editing.

Stale tracking warning

STALE_TRACKING_WARNING

tracking

Trigger

Status is in_transit AND last tracking update is over 60 minutes old

Severity

warning

Action

Verify driver location

Escalation

Escalate at 120 minutes

Stale tracking critical

STALE_TRACKING_CRITICAL

tracking

Trigger

Status is in_transit AND last tracking update is over 120 minutes old

Severity

critical

Action

Contact carrier immediately

Escalation

Assign to carrier relations if no response

Delivery appointment at risk

DELIVERY_RISK_LATE

appointments

Trigger

ETA is later than delivery appointment

Severity

critical

Action

Request revised ETA and notify customer

Escalation

Broker and operations manager review

Low ETA buffer

DELIVERY_RISK_LOW_CONFIDENCE

appointments

Trigger

ETA is within 30 minutes of appointment AND tracking is stale

Severity

warning

Action

Confirm location before the next customer update

Escalation

Escalate if carrier does not respond

Customer update overdue

CUSTOMER_UPDATE_OVERDUE

customer

Trigger

Current time is past customer notification due time

Severity

warning

Action

Create customer-update exception

Escalation

Broker approval required for service-risk drafts

Customer update window

CUSTOMER_UPDATE_DUE_SOON

customer

Trigger

Customer notification is due within 30 minutes

Severity

info

Action

Prepare routine update preview

Escalation

No escalation unless shipment is at risk

POD follow-up

POD_FOLLOW_UP

documents

Trigger

Shipment is delivered AND POD is missing for over 12 hours

Severity

warning

Action

Send POD reminder to carrier

Escalation

Escalate at 24 hours

POD escalation

POD_ESCALATION

documents

Trigger

Shipment is delivered AND POD is missing for over 24 hours

Severity

critical

Action

Escalate missing POD

Escalation

Route to carrier relations queue

Signed BOL missing

BOL_MISSING

documents

Trigger

Shipment is delivered AND signed BOL is missing

Severity

warning

Action

Request signed BOL from origin or carrier

Escalation

Place billing hold until received

Carrier non-response

CARRIER_NON_RESPONSE

carrier

Trigger

Carrier has not responded after 2 contact attempts

Severity

critical

Action

Escalate to carrier relations

Escalation

Notify dispatcher and operations manager

Pickup appointment risk

PICKUP_APPOINTMENT_RISK

appointments

Trigger

Pickup appointment is within 2 hours and ETA has no operating buffer

Severity

warning

Action

Confirm appointment and carrier ETA

Escalation

Notify customer if projected late

Billing document hold

BILLING_DOCUMENT_HOLD

documents

Trigger

Delivered shipment has missing POD or BOL

Severity

warning

Action

Keep invoice in document readiness queue

Escalation

Billing ops follow-up after 48 hours

Controlled by operations

The engine uses explicit thresholds and domain fields. It does not infer intent, hide a confidence score, or make an unreviewable decision.

Architecture note

Each rule has a stable ID, typed severity, trigger, action, escalation, category, and enabled state. A future editor can add versions and approvals without moving logic into UI components.