Skip to content

Accommodation Process

Case review workflow — instantiates Equity Adjustment

Provides a structured way to request, assess, approve, implement, and review individualized adjustments without treating the request itself as a favor.

Version
v1 · 2026-08-24 · History
Mechanism #
64
Type
Case Review Workflow
Form family
Protocol, Workflow & Routine
Solution family
Governance & Accountability
Problem family
Exclusion, Inequality & Distributional Harm
Problem subfamily
Distributive Allocation & Equal-Treatment Harm
Origin domain
Law & Governance
Also from
Organizational & Management Science, Public Administration & Policy
Instantiates
Equity Adjustment

An Accommodation Process is the standing workflow through which one participant asks for an individualized adjustment and the system responds with a disciplined, repeatable exchange — request, assess, approve, implement, review — rather than a case-by-case act of goodwill. Its defining idea is that the right to ask and be answered is built into the system: there is a known door to knock on, a good-faith dialogue behind it, and a record that the answer followed a reason. It handles individualized cases, so it does not by itself change any rule for everyone; what it changes is whether a person can reliably surface a barrier and get a bounded, reviewed response without over-advocating or over-disclosing.

Example

A logistics company employs a warehouse associate managing a chronic autoimmune condition whose medication makes early-morning starts unsafe. Rather than negotiate quietly with a sympathetic shift lead, the associate uses the company's accommodation process: an intake form routes the request to a designated coordinator, who opens a good-faith dialogue — the ADA calls this the interactive process[n1] — to understand the barrier and the options. Together they land on a shifted start time and a seated task rotation; the coordinator records the relevant difference, the barrier, the adjustment agreed, and the standard it preserves (the associate still meets the same pick-rate and safety expectations), and schedules a check-in at ninety days. Crucially, the medical detail stays with the coordinator, not the shift lead, and the outcome review at ninety days confirms the pick rate held. The associate never had to plead a case to their own manager or expose a diagnosis to the team.

How it works

What distinguishes this from an ordinary approval queue is that it is engineered so the request itself is legitimate and reviewable:

  • A named, visible door. A standing intake channel that participants know exists and can reach without insider knowledge — the antidote to hidden gatekeeping, where only the confident or well-connected think to ask.
  • A good-faith dialogue, not a verdict. Assessment is a two-way exchange to find a workable adjustment, not a one-shot approve/deny on the first form.
  • A rationale on the record. Each case is documented — difference, barrier, adjustment, preserved standard — so the decision is explainable and consistent across cases without broadcasting sensitive detail.
  • A scheduled look-back. Every adjustment carries a review point that checks whether it actually worked and whether the standard held.

Tuning parameters

  • Intake threshold — how much a participant must supply to open a case. A low threshold catches quiet need but raises volume; a high one filters noise while recreating the very barrier for people short on documentation or confidence.
  • Interactivity depth — a single decision vs. an iterated dialogue toward a fit. More iteration lands better adjustments but costs coordinator time and slows the response.
  • Decision latency — how fast the loop closes. Speed serves the urgent case; deliberation serves consistency and defensibility.
  • Review cadence — how soon and how often the look-back runs. Frequent review catches adjustments that stopped working, at the cost of process overhead.

When it helps, and when it misleads

Its strength is turning informal favors into disciplined discretion: a person with a real barrier can reach a fair response through a known channel, and the record plus the look-back keep the outcome honest. It is the mechanism that most directly attacks hidden gatekeeping — the failure where help exists but only insiders know how to claim it.

Its failure mode is process as gauntlet. When intake demands heavy proof, the workflow can recreate the original barrier at the door and quietly select for the already-advantaged; run as pure paperwork, the "interactive" step collapses into a rubber-stamp denial. A classic misuse is letting the record become a surveillance file rather than a rationale — documentation that exposes more than the decision required. The guarding discipline is to minimize what the intake demands, keep the dialogue genuinely two-way, and audit who never files — because silence is often the loudest sign the door is not really open.

How it implements the components

Accommodation Process fills the intake-and-review slice of the archetype — the workflow that receives, records, and re-checks an individualized case:

  • participation_channel — the standing, visible route by which a participant requests an adjustment and is guaranteed a good-faith response, so asking does not depend on being well-connected.
  • adjustment_rationale_record — the per-case record of difference, barrier, adjustment, and preserved standard that makes differentiated treatment explainable and consistent without unnecessary disclosure.
  • fairness_outcome_monitor — the scheduled look-back that checks whether the adjustment worked and the standard held for that case.

It does not itself change the governing rule or define what the standard protects (rule_adjustment, core_standard) — that is its nearest twin, Hardship Exception Review, which decides whether a rule should bend for unusual hardship. It also does not deliver the environmental fix (support_adjustmentAccessibility Change) or score the severity of need (relevant_difference, barrier_mapNeeds Assessment Rubric).

Editorial Notes

Form Classification

Form family: Protocol, Workflow & Routine

Rationale: The mechanism provides a structured way to request, assess, approve, implement, and review individualized adjustments without treating the request itself as a favor, so its operative form is an ordered repeatable procedure or workflow.

Independent corroboration: The frozen evidence defines Accommodation Process as 'Provides a structured way to request, assess, approve, implement, and review individualized adjustments without treating the request itself as a favor', so its operative form is Protocol, Workflow & Routine.

Review outcome: Independent reviewer agreement; medium confidence.

Origin Attribution

Primary origin: Law & Governance

Origin pattern: Single lineage

Present-day reach: Multi-domain

Rationale: A known request channel, good-faith interactive process, reasonable individualized adjustment, confidentiality, and reasoned decision record arise characteristically from disability and employment law.

Related originating lineages:

Review resolution: Both reviewers identify the legally structured accommodation process as primary. Organizational management and public administration are the materially formative delivery lineages; HCI informs particular options but not the process's origin.

Review outcome: Reconciled after independent review; high confidence.

Notes

A long queue of near-identical requests through this process is a signal, not a workload: when many people ask for the same adjustment, the barrier is probably in the default design, and the right response shifts from processing more cases to handing the pattern to Barrier Removal Workflow or Accessibility Change.

[n1] Under the Americans with Disabilities Act, the "interactive process" is the good-faith dialogue an employer and employee are expected to undertake to identify a reasonable accommodation — a structured, two-way exchange rather than a favor unilaterally granted. Referenced as an illustration of the dialogue this workflow formalizes.