This playbook is for people who already operate. Goal: a 45-minute weekly ritual that turns the tower into a decision instrument.
Monday ritual (15 min)
Open only three slices:
- % of inconclusive captures in the prior week
- Top 5 reasons for score drops (EPI, framing, unreadable asset…)
- Providers / branches with the most work order reopenings
If slice 1 is high, the problem is template or training. If 3 is concentrated, the problem is provider management.
Wednesday ritual (15 min)
Pick three work orders with a low score. Not thirty. Walk through:
- Is the field rubric clear?
- Did the technician know the expected framing?
- Was there a gate block, or did someone “work around” it?
Document one fix in the template or onboarding. One per week is enough.
Friday ritual (15 min)
Close the scorecard:
| Signal | Suggested target | Action if it blows |
|---|---|---|
| Inconclusive | < 12% | Rewrite prompts |
| Reopen for evidence | fall month over month | Mandatory gate |
| Time to human release | < 4 business hours | Dedicated tower queue |
| Pending sync > 24h | near zero | Review offline / device |
How to use it with Aria
- Build an exception dashboard by template
- Save Wednesday’s three work orders as training material
- Share the scorecard with the provider (transparency reduces friction)
Expansion (loyalty)
When the ritual stabilizes, add a fourth signal: estimated second-visit cost. That is where evidence becomes explicit ROI for the board.
Want the scorecard in the panel?
In enablement, we design the exception widgets with your operations team.