SUMMARY: A burden ledger records the time, proof, coordination, monitoring, expense, privacy exposure, and risk a process assigns to participants and operators. It makes externalized work visible beside ordinary cost and performance metrics.
Begin with one consequential workflow and a defined start and end state. Include successful, abandoned, delayed, disputed, and corrected cases. Use synthetic tests where collection would expose sensitive participant information.
1. Map Every Required Action
List forms, documents, accounts, visits, calls, uploads, signatures, status checks, handoffs, and deadlines for both participant and institution. Include actions performed outside the primary interface.
2. Record Time in Context
Separate active effort, waiting, travel, unavailable-service time, and deadline pressure. Record whether the person can safely pause and resume without losing work or queue position.
3. Inventory Evidence Demands
For each requested item, identify who already holds it, why it is needed, acceptable formats, freshness rules, repetition, privacy sensitivity, and the cost of obtaining it.
4. Count Coordination Work
Log channels contacted, transfers, identifiers carried between systems, context repeated, contradictory instructions, and dependencies the participant must discover.
5. Measure Monitoring Load
Count status checks, missed notifications, unanswered contacts, uncertain deadlines, and correction verification. A silent process turns attention into a continuing fee.
6. Capture Expense and Exposure
Record direct cost, lost work, transportation, connectivity, assistance, document fees, data disclosure, security risk, and harm sustained while the case remains unresolved.
7. Segment Without Stereotyping
Compare routes by language, accessibility need, device, geography, entry channel, case complexity, and evidence type. Use observed process differences rather than assumptions about capability.
8. Attach Burden to State History
Link ledger entries to the participant status ledger and decision receipt. Preserve the event that created each burden and the owner able to remove it.
9. Test Burden-Reducing Alternatives
Compare data reuse, prefilled fields, proactive status, longer windows, accessible formats, unified ownership, temporary protection, and institution-led correction. Check for new privacy or exclusion risks.
10. Publish a Burden Budget
Set maximum acceptable actions, elapsed time, repeated proofs, handoffs, and participant expense. Require review when the route exceeds the budget, and revalidate it after policy or topology change.
Pair this work with the default-route audit. Default cases often reveal the highest volume of quietly externalized effort.
Operator rule: count every task required to reach, understand, maintain, challenge, and correct an outcome, regardless of who performs it.
Continue the discussion in the Clandestinia forum.
Follow the Digital Systems Accountability guide to connect evidence, explanations, challenge routes, and the work of correction.