Analytics · Exception reporting
Name the night's
exceptions.
A summary tells a manager that 94 percent of retrievals met a target. It says almost nothing about the remaining six percent, even though that is where the operating work begins.
The report
An exception is a record with enough context to take a next action.
The list should connect a threshold or rule to a named session, timeline, location, assignment, and current resolution state. It should make investigation easier without declaring blame.
Not every slow or unusual session represents staff failure. Vehicle problems, guest timing, garage access, weather, payment, and bad source data can all create legitimate exceptions.
From summary to action
Percentages orient. Incidents operate.
Keep both layers
Summary reporting
ORIENTATION- Shows direction and scale
- Supports comparison across periods
- Does not identify what to investigate
Exception reporting
ACTION- Names the affected session and moment
- Carries context and ownership
- Records resolution and recurrence
Design the exception record
Trigger
Why it appeared
State the threshold, missing event, conflicting value, or unusual sequence that raised the record.
Context
What surrounded it
Include stand, demand window, parking zone, role assignment, and neighboring queue state where relevant.
Evidence
The event timeline
Show the requests, acknowledgments, handoffs, photos, messages, and corrections that actually exist.
Owner
Who reviews next
Assign the investigation without presuming the assigned person caused the issue.
Resolution
What changed
Close as explained, corrected, process change, data issue, guest issue, or unresolved, with a short note.
Avoid alert theater
If every deviation becomes urgent, managers learn to clear the list instead of learn from it.
Review the exceptions the system cannot detect
Missing
No record was created
A refusal, no-show, manual handoff, or abandoned guest can vanish before analytics sees it.
Wrong
The event was recorded incorrectly
Premature completion and copied values can make a bad journey appear normal.
Silent
The rule has no signal
Guest confusion and awkward recovery may require staff capture until a reliable event exists.
The weekly question
Which named exceptions deserve a process change?
A manager can act on twelve reviewable incidents: change a schedule, repair an integration, coach a handoff, adjust a threshold, or identify a data gap. A percentage alone cannot tell them which.
The takeaway: 'what went wrong' should open the work, not summarize it away.
