Transparent Decision Record¶
Document — instantiates Procedural Fairness Design
A record of decision standard, evidence considered, rationale, participation, and review status.
A Transparent Decision Record is the durable internal file a decision leaves behind: the standard that governed it, the evidence actually weighed, the reasoning that connected the two, who took part, and where the decision now sits in any review. Its defining property is accountability after the fact — it exists so that a later reviewer, an auditor, or the next decision-maker facing a similar case can reconstruct not just what was decided but whether it was decided on stated grounds, consistently with comparable cases, and within a defensible boundary of disclosure. It is the file, not the envelope: it does not deliver anything to the affected party in the moment, and it does not itself reopen the case. A record that omits the reasoning, or that cannot say how this case relates to like ones, is a folder of paperwork, not a fairness record.
Example¶
A hospital committee decides whether to add a patient to the kidney transplant waiting list. Whatever it concludes, it writes a Transparent Decision Record. It states the listing standard applied (medical suitability plus the program's published psychosocial criteria), lists the evidence considered (lab values, the transplant surgeon's assessment, the social-work evaluation), and sets out the rationale linking them — why, for this patient, the criteria were met or not. It records who sat on the committee and any recusals, and it notes the review status: pending appeal, or final. Because it also references how comparable borderline cases were handled, a later reviewer can see whether this patient was treated like similar patients or differently for stated reasons. And it draws a transparency boundary: the clinical rationale is preserved in full for review, while the patient-facing summary omits third-party details protected by privacy law. Two years on, an audit of the program's equity can actually be run — because the reasoning was written down, not just the verdict.
How it works¶
- Capture the governing standard verbatim — the rule, rubric, or criteria the decision was measured against.
- Record the evidence actually weighed and, briefly, what was set aside and why.
- Write the rationale — the chain from standard to evidence to outcome, including the close judgment calls.
- Log participation and review status — who decided, who recused, and where the case sits in any review.
- Set the disclosure boundary — what is preserved for accountability versus redacted for privacy or safety, noting each redaction rather than hiding it.
Tuning parameters¶
- Reasoning depth — a full deliberative rationale or a summary conclusion. Depth aids review and consistency; brevity saves time but can hollow the record.
- Consistency linkage — whether the record actively cites comparable prior cases or stands alone. Linkage enforces like-treated-alike but demands a retrievable case history.
- Retention and access — how long the record is kept and who may read which layer. Longer retention and wider access aid accountability but raise privacy exposure.
- Redaction granularity — line-item redaction with the reason noted, or wholesale withholding. Fine redaction preserves as much as possible; coarse withholding is faster but corrodes trust.
- Machine-readability — free text or structured fields. Structure enables audits and pattern-finding across cases at the cost of authoring effort.
When it helps, and when it misleads¶
Its strength is that it makes a decision reviewable and comparable across cases — the principle that like cases be treated alike[1] has no teeth unless someone wrote down the standard and reasoning so unlike treatment can be spotted. It also surfaces systemic defects: a run of records reveals an unclear or inconsistently applied standard that no single decision would.
Its failure mode is boilerplate reasoning — a record that recites the outcome and cites a policy label without ever showing how the evidence produced the result, so it looks accountable while explaining nothing. The companion misuse is over-redaction, using the privacy boundary to withhold the actual basis until the record is unfalsifiable. The guarding discipline is to test the record by reconstruction — could an independent reviewer, seeing only this file, tell why this case came out as it did and whether comparable cases match — and to note every redaction so the boundary is visible rather than a black hole.
How it implements the components¶
Transparent Decision Record fills the durable-accountability slice — documenting the decision for later scrutiny, not delivering or reopening it:
reason_giving— it is the on-file rationale linking standard, evidence, and outcome.consistency_standard— it fixes the governing standard and links comparable cases so like treatment is checkable.precedent_reference— it cites prior decisions relied on and becomes itself a reference point for later ones.transparency_boundary— it sets and marks what is preserved for review versus redacted for privacy or safety.
It does NOT implement notice_requirement, affected_party, or decision_timeline — delivering the decision to the party in time to act is Decision Notice.
Related¶
- Instantiates: Procedural Fairness Design — the record is the archetype's accountability memory, preserving reasons and consistency for review.
- Sibling mechanisms: Decision Notice · Appeals Process · Review Panel · Grievance Process · Moderation Appeal · Hearing Procedure · Ombuds Channel
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Transparent Decision Record operates as a persistent ledger, log, register, or case record that preserves history and traceability because it a record of decision standard, evidence considered, rationale, participation, and review status.
Independent corroboration: The frozen evidence defines Transparent Decision Record as 'A record of decision standard, evidence considered, rationale, participation, and review status', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: 5 U.S.C. § 557, Initial decisions; conclusiveness; review requires administrative decisions to state findings, conclusions, reasons, and the record basis, while preserving participation and review status. This directly supports law governance as the best-evidenced historical home of the operation—A record of decision standard, evidence considered, rationale, participation, and review status.—while the alternates record adjacent lineages rather than mere domains of later use.
Related originating lineages:
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: a record of decision standard, evidence considered, rationale, participation, and review status.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: a record of decision standard, evidence considered, rationale, participation, and review status.
- Systems Thinking & Cybernetics — Feedback, system boundaries, stocks, flows, and regulation supplies a distinct formative lineage for the mechanism's transparent decision record logic.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus law_governance). The defining operation is: A record of decision standard, evidence considered, rationale, participation, and review status. The researched 5 U.S.C. § 557, Initial decisions; conclusiveness; review requires administrative decisions to state findings, conclusions, reasons, and the record basis, while preserving participation and review status. That is mechanism-specific evidence for law governance as the historical origin. Organizational management remains represented among the uncapped alternates where it contributes a genuine formative practice, but broad deployment or governance of the operation is not by itself evidence that the mechanism originated there. origin_mode=single_lineage records lineage; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Lyons, D. "On Formal Justice". In Moral Aspects of Legal Theory: Essays on Law, Justice, and Political Responsibility, 13–40. Cambridge University Press (1993). Examines the formal-justice principle that like cases should be treated alike. registry ↩