Accessible Feedback Report¶
Accountability artifact — instantiates Epistemic Inclusion Design
Documents what knowledge was contributed, how it was used, what changed, what remained unchanged, and how future contestation or review can occur.
Most inclusion efforts fail not at the listening but at the returning: people give their knowledge and never learn whether it mattered. Accessible Feedback Report is the artifact that closes that gap. It is a document — not a body, not a workshop — whose single job is to make the trace from contributed knowledge to what the institution did with it legible to the very people who contributed, in a form they can actually read. Its defining move is symmetry of accounting: it reports the changes a contributor's input produced and the changes it did not, with the reason, so the report cannot quietly launder a process that listened but refused to move. Everything else — participation, elicitation, revision — happens before it; this page is where the loop is written down and handed back.
Example¶
A state disability-benefits agency has just finished redesigning its functional-assessment questionnaire after a year of hearing from claimants whose conditions fluctuated day to day. The old form asked "can you walk 100 metres?" as a yes/no, and applicants with relapsing conditions kept getting denied. Rather than send the usual press-release "thank you for your input," the agency issues an Accessible Feedback Report. It lists, in plain language and in the three languages its applicants most use, each theme people raised: "You told us a single yes/no erases good days and bad days." Against each, it states what changed — the item now asks about variability and worst-day capacity — and, crucially, what did not: "You asked us to drop medical evidence requirements entirely. We did not, because appeals law requires it. Here is who to contact if you disagree, and when the form is next reviewed." The report is posted, mailed on request in large print, and read aloud in a recorded audio version. A claimant who spent an hour describing her fatigue can now see her own words traced to a specific line of the new form — or see, in writing, exactly why they were declined.
How it works¶
The report is organized as a ledger, not a narrative. Each row pairs a piece of contributed knowledge with a disposition drawn from a fixed vocabulary — adopted, partly adopted, deferred, declined — and a one-line reason for anything less than full adoption. Declined and deferred items get the same visibility as adopted ones; that is what keeps the artifact honest. The report then states its own scope: whose input it reflects, who was invited but absent, and where the account should not be read as representing everyone. Finally it names the route forward — how a reader challenges a disposition, and when the decision is next open. The whole thing is issued through the channels the contributors use and rendered at a reading level and in formats they can reach, because a feedback loop that only the fluent can decode has not closed for anyone else.
Tuning parameters¶
- Disposition granularity — one summary verdict per theme versus a line-by-line trace. Finer granularity earns more trust but costs authoring effort and can expose messy internal disagreement.
- Reading level and format spread — how far you push toward plain language, translation, audio, and large print. Wider reach includes more people but flattens nuance and multiplies production cost.
- Cadence — a single end-of-process report or a running log updated at each decision. Running logs sustain trust but risk reporting churn as if it were progress.
- Contestation window — how long, and through what route, a reader can push back on a disposition. Longer windows deepen legitimacy but delay closure.
- Attribution resolution — quoting contributors' own words versus paraphrased themes. Verbatim is more recognizable but can breach confidentiality for identifiable speakers.
When it helps, and when it misleads¶
Its strength is that it directly attacks the archetype's most common failure — a process that listens but does not change — by forcing the "what did not change, and why" column into the open where it can be argued with. Done well it is the difference between consultation theatre and an accountable decision, and it is the artifact that lets a later reviewer audit whether influence was real.
Its failure mode is that a report is easy to fake and hard to verify from the outside: it can perform the form of "you said, we did"[n1] while the "we did" column lists only cosmetic edits, or while the changes it claims were already planned. It can also over-claim representativeness — writing "the community told us" when a handful of the most available voices did. The guarding discipline is to bind each disposition to a concrete, checkable artifact (the exact form line, the meeting minute, the policy diff) and to state scope honestly rather than let the report speak for people who were never in the room. The report documents change; it does not manufacture it, and it should never read as though it did.
How it implements the components¶
accountability_feedback_loop— the report is the loop's output: a returned account of what was contributed, adopted, declined, and how to contest, handed back to contributors.accessibility_and_language_support— plain-language rendering, translation, and alternate formats (audio, large print) so the account reaches the people it is accountable to, not only fluent insiders.representativeness_scope_note— the explicit statement of whose input the report reflects and whose it does not, guarding against speaking for the absent.
It does not authorize the changes it reports: knowledge_structure_revision is exercised by Community Review Board and Inclusive Taxonomy Review, and the generative participation_channel belongs to Co-Design Workshop. This artifact records their outcomes; it does not produce them.
Related¶
- Instantiates: Epistemic Inclusion Design — this is the closing artifact that makes contributed knowledge traceable to action.
- Consumes: Community Review Board and other deciding mechanisms supply the revisions and decisions the report documents.
- Sibling mechanisms: Co-Design Workshop · Community Review Board · Credibility Audit · Hermeneutic Gap Analysis · Inclusive Taxonomy Review · Member Checking Validation · Participatory Research Process · Stakeholder Knowledge Forum
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The mechanism documents what knowledge was contributed, how it was used, what changed, what remained unchanged, and how future contestation or review can occur, so its operative form is a static or prospective information artifact.
Independent corroboration: The frozen evidence defines Accessible Feedback Report as 'Documents what knowledge was contributed, how it was used, what changed, what remained unchanged, and how future contestation or review can occur', so its operative form is Representation, Specification & Plan.
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: Point-by-point 'you said, we did' reporting, disposition of consultation input, representativeness scope, and routes for contestation are characteristic public-participation and administrative-accountability practices.
Related originating lineages:
- Communication & Media Studies — Plain-language, multilingual, multimodal communication makes the feedback trace intelligible to its audiences.
- Ethnography & Qualitative Methods — Responsible interpretation of contributed knowledge and member checking inform how participants recognize whether their input was represented faithfully.
- Human-Computer Interaction — Plain language, translation, audio, large print, and usable delivery channels make the accountability artifact accessible to its contributors.
- Law & Governance — Reasons, review routes, contestability, and equal treatment of adopted and declined input contribute procedural legitimacy.
Review resolution: Public administration is the shared primary because the report is an accountable institutional response artifact. Qualitative inquiry, HCI, communication, and rights practice each materially shape evidence collection, accessible presentation, and remedy.
Attribution caveat: The report format is an administrative consultation convention; its explicit epistemic-inclusion ledger is an Encyclopedia synthesis.
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.
Notes¶
[n1] "You said, we did" — a common public-consultation convention in which a body reports back, point by point, how the input it received was used. Its value depends entirely on the honesty of the "we did" column; used cosmetically it becomes exactly the credibility-laundering it was meant to prevent. ↩