Published November 4, 2026

A protocol for checking whether an accessibility request reaches a named owner with the customer's preferred channel, context, and next action. The notes below keep the customer request, the approved source, and the next owner in one reviewable place. They are written for a support team that may hand the case to another shift. Use the routine to review one ordinary case and one exception before changing the workflow.

Question and scope

This audit asks whether an accessibility request is recorded with the customer's stated need and routed to a named decision owner. It examines the request record and the handoff, not the legal sufficiency of the accommodation. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Set the scope to one support queue and a fixed period. Record the request categories, the approved channels, and the owner roles in force. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Population and unit

The unit is one customer request for an accessibility accommodation. A request that applies to several interactions remains one unit with linked events. Record the request key, the customer's preferred channel, the owner, and the decision time. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Include requests that were declined, requests still open, and requests that required a backup owner. Exclude general questions about available formats that did not ask for an accommodation. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Definitions and measures

Define completeness as the record showing the customer's words, the affected interaction, the preferred channel, the owner, and the next action. A generic label without context is incomplete. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Separate a missing field from a late decision and from a customer who did not respond. These outcomes have different remedies and should not be combined. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Evidence standard

Collect the case record, the handoff note, the customer communication, and the owner decision. Mask health and personal details in the analysis table. Use the approved restricted record for the raw evidence. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If the request was made by phone, record the call note and the time. A transcript is not required if the approved process uses a structured summary. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Sampling and collection

Sample requests rather than contacts, then review every handoff within the selected case. Stratify by request type and service period. Use a random or systematic start. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Include a request that crossed a shift and a request that required a backup owner. Those cases test whether the context and authority traveled. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Analysis and reporting

Report the number of requests, the share with a named owner, the share with the preferred channel recorded, and the share with a customer update. Show the decision time separately. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Inspect the incomplete cases. Was the form unclear, the owner unavailable, or the channel preference omitted? The pattern should lead to one process change. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Limitations

The record may not capture a private conversation or an accommodation arranged outside the support queue. State the unobserved evidence and avoid treating a blank field as a failure of care. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

The study does not determine whether an accommodation is legally required or whether the customer's need was fully met. It measures the documented handoff. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Review and next action

Choose one change: a required channel field, a clearer request category, a backup owner, or a customer-update target. Assign the owner and the next review date. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Repeat the audit after the change and compare the same measures. Close the review when the owner accepts the result. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Sources