Operational fingerprint
Define a per-journey burden scorecard (minutes, retries, documents requested) and publish it monthly so searchers can compare programs over time.
What is a Burden Index?
A burden index quantifies the time and effort a system imposes on people.
Glossary anchor
Burden Index
Connect the explainer to the canonical definition for citations and shared language.
A burden index quantifies the time and effort a system imposes on people to comply, appeal, or recover. It translates friction into a measurable metric so teams can reduce the time tax they create.
Publishing the burden index keeps the human cost visible and accountable over time.
A benefits portal tracks total minutes spent per appeal, publishes a monthly burden index, and commits to reducing the index quarter over quarter.
Implementation
Distinct implementation signals
Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.
Common failure pattern
Burden indices fail when teams average away outliers; include p90 and p99 burden to expose who experiences the longest administrative drag.
Evidence to ship
Attach raw journey timing logs, abandonment points, and remediation commits that explain quarter-over-quarter burden reductions.
Standard
STD-01 — The Temporal Bill of Rights
Tie burden metrics to the transparent burden and bounded duration clauses.
Binding
Binding vectors
Bake burden reporting into procurement clauses and operational gates.
Evidence pack
STD-01 evidence pack
Document burden measurements and remediation actions.
What inputs should the burden index include?
Include time-to-complete tasks, number of steps, waiting time, and any support escalations required to resolve issues.
How often should it be reported?
Report at least monthly for high-impact systems, with interim checks during peak volume or incident windows.