Home What we do Event library Industries Why Automation Blueprints About Book a session
Event repository

A public library of business events and the workflows that should fire.

Every entry answers the same four questions. Grounded in real operational contexts across six industries and four event source types.

The framework

Every event entry answers the same four questions.

01
What is the event?
Precise description of the operational moment. Source, context, conditions, and timestamp.
02
Why does it matter?
The operational and business cost of missing this event. Specific to industry and context.
03
What should happen?
The workflow. Who is notified, what systems update, what escalates, what the outcome should be.
04
What does the outcome look like?
The measurable difference between an organisation that responds and one that does not.
Event source types

Business events come from every corner of your organisation.

Real-time
Sensor, stream, API. Fires continuously, demands immediate response. Minutes between event and consequence.
Batch
Scheduled jobs, reports, period-end calculations. Drives planning and optimisation cycles across the business.
User-triggered
Approvals, overrides, manual decisions. Human decisions are operational events and belong in the workflow record.
Customer-triggered
Transactions, behaviour data, service interactions. Customers generate business events continuously.
Repository entries
Real-time · Asset operations
Bearing temperature threshold exceeded
Energy and Utilities
What happened and why it matters

Asset A7 bearing temperature sensor crosses 95 degrees Celsius at 14:32. Pattern consistent with early-stage bearing failure in 94 percent of historical matches. Predicted unplanned downtime in 18 days if no intervention. Current state: no workflow fires. Maintenance team will find out when the asset fails.

Workflow that should fire
  • Classify event severity and asset criticality tier automatically
  • AI analysis: match against historical failure patterns at 94 percent confidence
  • Auto-generate maintenance work order in EAM or ERP system
  • Dispatch nearest qualified technician with parts inventory pre-check
  • Record event, action, outcome and cost in your operations log
Real-time · Supply chain
SLA breach risk detected six hours before breach
Logistics
What happened and why it matters

Shipment tracking deviation detected. Projected delivery is six hours outside the contracted SLA window. The breach has not occurred yet. Current state: no workflow fires at this detection point. The organisation will respond reactively after the breach triggers a customer complaint.

Workflow that should fire
  • Calculate SLA breach probability and time window available for intervention
  • Identify alternative carrier or route options from pre-approved list automatically
  • Trigger re-routing approval workflow to operations team with recommended option
  • Proactively notify customer with updated ETA before they notice the delay
  • Log event, action, outcome and cost impact to carrier performance scorecard
Customer-triggered · Customer operations
High-value inquiry unanswered for fifteen minutes
Hospitality and Travel
What happened and why it matters

High-value group booking inquiry received outside business hours. No response after fifteen minutes. Historical data shows 62 percent of similar inquiries are abandoned after 30 minutes without any contact. Current state: inquiry sits in a shared inbox. Nobody is notified. The booking window closes.

Workflow that should fire
  • Classify inquiry value and urgency tier at point of receipt before any delay occurs
  • Auto-send personalised acknowledgement with availability snapshot within two minutes
  • Escalate to on-call sales manager if no human response in fifteen minutes
  • Trigger rate intelligence check against competitor availability and current pricing
  • Record the outcome booked, abandoned, or converted in your revenue management system
Batch · Financial operations
Customer payment pattern shift detected
Financial Services
What happened and why it matters

End of period analysis flags a payment behaviour change correlating with 78 percent default probability within 45 days. The model runs monthly. By the time the relationship manager sees it, the data is already three weeks stale and the intervention window has narrowed significantly.

Workflow that should fire
  • Detect payment pattern shift and run AI risk classification in real time
  • Cross-reference with portfolio exposure, covenant terms and credit limits
  • Alert relationship manager with recommended intervention brief and available options
  • Trigger compliance review workflow if regulatory thresholds are crossed
  • Record the decision, intervention and outcome in your risk management system
Real-time · Asset operations
Fleet battery health below route threshold
EV and Mobility
What happened and why it matters

Fleet vehicle battery health score drops below the minimum required for a scheduled long-distance route six days before the departure date. Current state: no workflow fires. The fleet manager will discover the issue during pre-departure checks, triggering a reactive scramble for a replacement vehicle.

Workflow that should fire
  • Detect battery health threshold breach against the route schedule calendar
  • Cross-reference fleet dispatch schedule for impact window and severity assessment
  • Auto-schedule service appointment before departure date without manual intervention
  • Notify driver and fleet manager simultaneously with the recommended action
  • Update fleet availability in dispatch system and trigger route re-assignment if needed
Real-time · Quality operations
Production line drift detected before first defect
Manufacturing
What happened and why it matters

Statistical process control chart detects production line drift at two standard deviations from baseline. The first defective unit has not yet been produced. Current state: supervisor check is scheduled for end of shift. By then dozens of units will have passed through and the quality hold applies retrospectively.

Workflow that should fire
  • Detect SPC drift reading and classify against process control parameters immediately
  • AI root cause analysis against historical failure patterns and current material batches
  • Alert line supervisor immediately with a specific process adjustment recommendation
  • Trigger quality hold workflow automatically if confidence threshold is exceeded
  • Notify supply chain if incoming material input is identified as a contributing root cause
Missing an event

We add new entries continuously.

Every consulting engagement Blueprints completes adds new event patterns to the repository. The goal is a reference library comprehensive enough that any operations leader immediately recognises what they are missing.

Suggest an event
Work with Blueprints

Is your organisation missing one of these events?

We run focused sprints to design the event logic and workflow for one critical operational gap. Fixed fee. Two to three weeks. Executable output your team can implement or we build alongside you.