“The published sensory hour did not operate at the listed time.”
Correction + accountability model
Report what changed without turning one experience into a public verdict.
Community observations help keep access information current. Facts, personal experience, access incidents and verified policy issues remain distinct.
REPORTING RULEOBSERVE → CLASSIFY → CHECK → RESPOND → CORRECT
READ THIS PAGE
Start here. Read straight down.
Use this page to report changed conditions, incorrect information, access problems, and successful corrections without collapsing facts and experiences together.
Important information is visible on the page. Nothing essential is hidden in accordions or pop-ups.
THE SIMPLE PATH
- Choose the correct report type.
- Preserve the organization’s right to respond without allowing valid history to disappear.
- Route verified service failures into the broader issue-resolution system when needed.
Four record types
Do not collapse them.
“The lobby was very crowded at 3:15 p.m.”
“I became overwhelmed while waiting.”
“My requested written communication method was refused.”
Issue states
Procedural fairness without erasing valid history.
Organizations can correct factual information, submit evidence and describe corrective action. They should not be able to delete a verified issue simply because it is unfavorable.
Reported
Awaiting review
Organization contacted
Information requested
Corrected / resolved
Unresolved / recurring barrier
Referred when another authority or service is the correct route
Build status: the public correction form and REP/field-failure integration are defined here as the operating model but are not connected to a live backend in this static package. The page does not pretend to submit a government record.