Field Note 072: Burden Shifting

SUMMARY: Burden shifting occurs when a system transfers the work of proving, reconciling, monitoring, and correcting institutional state onto the person affected by it. The organization keeps authority while the participant becomes the unpaid integration layer.

Digital administration often appears efficient because the institution counts only its own handling time. Work performed outside the queue disappears: finding documents, repeating context, checking status, coordinating departments, correcting vendor records, and proving that a prior correction failed.

Evidence Burden

The participant may be required to reproduce information the institution already collected or can retrieve more reliably. Every request introduces cost, delay, privacy exposure, and another opportunity for mismatch.

Coordination Burden

When systems disagree, the person is told to contact each owner separately. They carry identifiers between channels, explain the same sequence repeatedly, and discover dependencies that should have been visible inside the institution.

Legibility asymmetry makes this transfer possible: the institution sees the participant across records while the participant must reconstruct the institution from fragments.

Monitoring Burden

Silent queues and uncertain deadlines force repeated checking. The participant must notice missed responses, stale status, reverted changes, and downstream errors. The cost grows with every channel that lacks durable acknowledgment.

Risk Burden

The institution controls the process, but the participant absorbs late fees, lost access, disclosure, delay, or reputational damage while review continues. A formally available remedy does not rebalance this exposure.

Defaults Hide the Transfer

The default path often assigns unresolved work to the party with the least system access. A case can be closed internally while remaining operationally open for the person living with its effects.

Count the Externalized Work

Measure documents requested twice, channels contacted, handoffs, status checks, elapsed days, identity re-verifications, contradictory instructions, correction retries, money spent, and harm sustained. Segment by language, accessibility, device, geography, and case complexity.

Attach those measures to the participant status ledger so institutional closure cannot erase participant effort.

Field assessment: a process is not efficient when it reduces institutional work by exporting the same work, with less authority and worse tools, to the affected person.

Continue the discussion in the Clandestinia forum.