Institutional Barrier Review¶
Procedure — instantiates Structural Harm Mapping
Inventories the barriers an institution's own design throws up — its hours, forms, staffing, eligibility rules, and accountability gaps — and pins each to the point where a rule could change.
An Institutional Barrier Review works the far side of the counter from an access map: it inventories the obstacles the institution's own design creates — office hours and locations, form and language requirements, staffing ratios, eligibility criteria, identity-verification demands, service fragmentation, and the accountability gaps between units — and pins each barrier to the specific rule, schedule, contract, or budget line that produces it. Its defining feature is that it treats barriers as institutional artifacts with owners, not as facts of nature or applicant failings: for every barrier it asks which constraint creates it and where a different choice could dissolve it. It is a supply-side audit of friction, cataloguing what the institution does to people rather than what people fail to do.
Example¶
A state unemployment-insurance agency is buried in backlog and complaints. A barrier review starts not with claimants but with the agency's own rulebook and org chart. It catalogues the institution-made barriers: a claims line staffed only 8-to-4 on weekdays, when many claimants are still working; an identity-verification vendor that fails for anyone without a credit history; a weekly certification form that erases itself if the browser times out; and a rule that auto-denies any claim whose eligibility questionnaire goes unanswered. For each barrier the review records the constraint behind it (a staffing budget, a vendor contract, a legacy IT system, a fraud-control policy) and the decision point where it could change — who could extend the hours, renegotiate the vendor, or flip the auto-deny default. Illustratively, a large share of denials trace to that auto-deny default rather than to actual ineligibility: a barrier no single caseworker can override, which is exactly why it needs an owner.
How it works¶
What distinguishes it is that it reasons from the institution outward:
- Start from the rulebook and org chart, not the applicant's journey; enumerate barriers the institution's design imposes.
- Classify each barrier by constraint type — policy, contract, staffing, tooling, or metric — because the type dictates who can change it.
- Attach an owner and a decision point to every barrier, so each obstacle names the authority that could remove it.
- Split hard from soft. Separate statutory constraints (fixed here) from discretionary ones (changeable locally), and sort the changeable ones first.
Tuning parameters¶
- Barrier taxonomy — the categories you scan for (hours, documentation, eligibility, staffing, tech, accountability). Miss a category and its barriers stay invisible.
- Constraint depth — stop at the surface rule or dig to the budget, contract, or statute beneath it. Deeper is truer but slower and touches harder-to-move levers.
- Owner resolution — how precisely you name who could change each barrier. Vague ownership yields a critique no one must answer.
- Hard/soft split — how carefully you flag legally fixed versus locally discretionary barriers, which decides what is actionable now.
- Scope — one service line or the whole agency. Wider catches fragmentation between units; narrower ships faster.
When it helps, and when it misleads¶
Its strength is that it moves blame off the frontline and onto the design, then names who can change it — a corrective to the reflex of holding street-level staff responsible for constraints they do not control.[1] Its failure mode is producing a handsome catalogue of barriers with no owners attached, so the review reads as institutional self-criticism with no lever to pull. A common misuse is to fill the list with statutory barriers the agency already knows it cannot touch — a display of helplessness — while quietly skipping the discretionary ones it could fix tomorrow. The discipline is to give every barrier an owner and a decision point and to rank by "changeable here" first, so the review ends in commitments rather than lament.
How it implements the components¶
institutional_constraint— its core output: the formal and informal limits (policy, staffing, contract, tooling, metrics) that create each barrier and bound what actors can practically do.decision_point_map— every barrier is pinned to a place where a rule, schedule, default, or allocation could change, turning the inventory into a set of levers.
It does not walk the applicant's own route — access_and_resource_map is the Access Pathway Map's — nor trace a single written provision downstream to the burden it produces — structural_pathway is Policy Pathway Analysis's.
Related¶
- Instantiates: Structural Harm Mapping — it supplies the institution-side inventory of barriers and the owners who could remove them.
- Sibling mechanisms: Access Pathway Map · Policy Pathway Analysis · Structural Audit · Systems Harm Analysis · Social Determinants Mapping · Equity Impact Assessment · Harm Reduction Dashboard · Remedy Co-Design Workshop · Affected-Party Review Panel
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Institutional Barrier Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it inventories the barriers an institution's own design throws up — its hours, forms, staffing, eligibility rules, and accountability gaps — and pins each to the point where a rule could change
Independent corroboration: The frozen evidence defines Institutional Barrier Review as 'Inventories the barriers an institution's own design throws up — its hours, forms, staffing, eligibility rules, and accountability gaps — and pins each to the point where a rule could change', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Auditing how public-service rules, hours, forms, and frontline discretion obstruct access is primarily a public-administration and implementation practice.
Related originating lineages:
- Gender Studies & Queer Theory — Intersectional power analysis materially sharpens attention to uneven burdens and excluded claimant populations.
- Sociology & Anthropology — Institutional and street-level analysis materially locates apparently personal burdens in upstream structure.
Review resolution: Both independent reviews place the primary lineage in public_administration_policy. The queued differences (alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement) concern secondary metadata rather than primary provenance. The final retains gender_studies, sociology_anthropology only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=cross_disciplinary_synthesis because the entry's present form deliberately composes methods from the documented lineages. domain_reach=multi_domain records application breadth separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Street-level bureaucracy — Michael Lipsky's term (1980) for how frontline public workers, squeezed by caseloads, ambiguous rules, and scarce resources, effectively make policy through their discretion. It grounds the review's central move: barriers a claimant meets at the window usually originate in constraints set far above the clerk, so accountability belongs upstream. registry ↩