Institutional debris is the record of what people did to keep a formal system functioning: workarounds, overrides, tickets, grievances, and exception codes.
Institutional debris is the record that builds up around a formal process as people make up for what it cannot handle: workaround logs, manual overrides, support tickets, grievance files, exception codes, shadow spreadsheets, repeated data corrections, escalation paths, staff notes, informal procedures, repair records, and patterns of people giving up.
Formal documentation describes the intended process. The debris describes the second process that grew around it to keep it working. Where the two differ is where the formal process stops working. An audit needs that most, and no policy records it.
A hypothetical case. A benefits workflow documents one intake form and one review step. The debris around it shows something else. Caseworkers keep an unofficial spreadsheet of cases the system gets wrong. One employee is known for fixing impossible cases. Applicants have learned that writing the true reason for a job loss produces a denial. The exception code for 'manual review' fires forty times a week. Each of these is evidence about the formal system that no policy document contains.
In the glossary: Exception absorption.
In practice
Workaround logs, override records with their reasons and consequences, how often each exception code fires, grievance and appeal files, shadow spreadsheets, support-ticket categories, repeated data corrections, staff notes, and systems that were quietly abandoned.
On the question it speaks to, debris outweighs formal documentation, because it records what the system does, not what it says it does. A policy that says people may appeal is weak evidence. The history of actual appeals is stronger.
A recurring workaround is presumed to mean the design upstream has failed. The institution can rebut that by showing the workaround is a preference, not a fix. Organizations read workarounds as resilience. The debris supports the opposite reading: a rigid system kept running by people's flexibility.
Draw the system's boundary around its consequences, not around who owns it. A consequential system includes whoever carries what it cannot handle, and that is rarely the operator. The customer's repair work, the nurse's overrides, and the hidden moderation queue are all inside the system.
Where the standards use it:
No. It ends documentation's monopoly. The intended process is one source and the debris around it is the other. An audit that reads only the intended process grades the institution on its own description.
Sometimes, and the institution can show that. The burden is on the institution. Repeated workarounds around the same defect measure the gap between the formal system and the world. Reading them as resilience is how the extra work becomes invisible.