Why this matters
Badge scan failure rates usually spike during peak arrival waves. Without an explicit error budget, teams either overreact and cause queue delays or ignore losses that corrupt downstream attribution.
Error budget policy design
- SLO definition: successful scan-and-save rate target per hour (e.g., 99.2%).
- Error budget: maximum tolerated failed scan events before escalation.
- Burn alerts: trigger at 50%, 75%, and 100% budget consumption.
- Fallback modes: offline capture, manual check-in, and deferred sync queue.
KPI thresholds
- Median scan latency under 2.5 seconds.
- Data-loss rate below 0.8% per day.
- Retry success above 85% within 10 minutes.
- Duplicate record rate below 1.5%.
Escalation runbook
- Route failures by root cause: device, network, app, badge print quality.
- Shift affected lanes to fallback workflow in under 5 minutes.
- Notify sponsor lead-capture stakeholders when error budget burn exceeds 75%.
- Reconcile deferred sync files before end-of-day closeout.
Internal links
- /guides/en/expo-attendee-badge-scan-data-quality-playbook
- /guides/en/expo-attendee-badge-scan-retry-sla-template-2026
Sources
Next step CTA
Set your scan reliability SLO now, then run a peak-hour simulation before your next show opens.