Open standards & artifacts for accountable systems.

Standard

Permanent link /standards/minimum-viable-contestability

Minimum viable contestability standard

A short, non-jargony baseline for standing, reasons, records, timelines, remedies, and non-retaliation.

Contestability

Minimum viable contestability

Use this one-page standard to confirm that a system can be contested with real authority, timelines, and remedies.

Read STD-02

One-screen summary

Minimum viable contestability standard

Six baseline commitments that make contestability real and safe to use.

  • Standing: Anyone affected can trigger review without permission gates or retaliation.
  • Reasons: Decisions come with plain-language reasons and what could change the outcome.
  • Records: A decision record exists with timestamps, owners, and a shareable receipt.
  • Timelines: Published review clocks force a final response and escalation path.
  • Remedies: Reversal, correction, or compensation is reachable and trackable.
  • Non-retaliation: Contestants cannot be punished for using the review process.

Minimum viable contestability standard

Six baseline commitments that make contestability real and safe to use.

  • Standing: Anyone affected can trigger review without permission gates or retaliation.
  • Reasons: Decisions come with plain-language reasons and what could change the outcome.
  • Records: A decision record exists with timestamps, owners, and a shareable receipt.
  • Timelines: Published review clocks force a final response and escalation path.
  • Remedies: Reversal, correction, or compensation is reachable and trackable.
  • Non-retaliation: Contestants cannot be punished for using the review process.

Source: /standards/minimum-viable-contestability

Baseline requirements

Minimum viable contestability standard

Each requirement is written to be direct, auditable, and safe for affected people.

Standing (who can contest)

People affected by a decision can open review without gatekeeping.

  • Allow the affected person to file a contest without extra approvals.
  • Allow trusted representatives to file with consent.
  • No paywalls, hidden prerequisites, or behavior tests before filing.

Minimum evidence

  • Visible contest entry point.
  • Receipt confirming submission.
  • Policy stating who can file and how.

Reasons (what happened and why)

People receive clear reasons they can act on and verify.

  • Provide a plain-language reason for the decision.
  • Name the policy, data, or rule that drove the outcome.
  • State what evidence or changes could reverse the decision.

Minimum evidence

  • Reason statement attached to the decision record.
  • Accountable owner name and contact path.
  • Versioned policy reference or rule ID.

Records (receipts and logs)

Every contestable decision leaves a traceable, shareable record.

  • Issue a decision record with a unique ID and timestamp.
  • Keep the record accessible to the affected person.
  • Log updates, evidence, and outcomes in a repair log.

Minimum evidence

  • Decision record or receipt with unique ID.
  • Accessible record history for the affected person.
  • Repair log or decision ledger entry.

Timelines (review clocks)

Review timelines are published and enforced with escalation rules.

  • Publish the review deadline and expected response time.
  • Provide status updates and escalation triggers.
  • If deadlines are missed, default to human review or pause.

Minimum evidence

  • Published SLA or review clock.
  • Status tracker or timeline receipt.
  • Escalation rule documentation.

Remedies (reversal and repair)

Reversal, correction, or compensation is real and reachable.

  • Offer a clear path to reversal or correction.
  • List any compensation or remedy options.
  • Show proof that remedy was delivered once complete.

Minimum evidence

  • Remedy options published with the decision record.
  • Completion receipt for remedy actions.
  • Audit trail showing reversal or correction.

Non-retaliation (safe to contest)

People are protected from penalties for contesting decisions.

  • State a no-retaliation guarantee in the contest flow.
  • Prohibit increased friction, fees, or access loss after filing.
  • Track any adverse impacts and remediate immediately.

Minimum evidence

  • Non-retaliation policy statement.
  • Monitoring note for adverse impacts.
  • Contact path for reporting retaliation.

Text-only version

Text-only version for quoting

Copy this version into briefs, audits, or escalation notes without formatting.

Minimum viable contestability standard
Permalink: /standards/minimum-viable-contestability

One-screen summary
- Standing: Anyone affected can trigger review without permission gates or retaliation.
- Reasons: Decisions come with plain-language reasons and what could change the outcome.
- Records: A decision record exists with timestamps, owners, and a shareable receipt.
- Timelines: Published review clocks force a final response and escalation path.
- Remedies: Reversal, correction, or compensation is reachable and trackable.
- Non-retaliation: Contestants cannot be punished for using the review process.

Baseline requirements
Standing (who can contest)
- Allow the affected person to file a contest without extra approvals.
- Allow trusted representatives to file with consent.
- No paywalls, hidden prerequisites, or behavior tests before filing.

Reasons (what happened and why)
- Provide a plain-language reason for the decision.
- Name the policy, data, or rule that drove the outcome.
- State what evidence or changes could reverse the decision.

Records (receipts and logs)
- Issue a decision record with a unique ID and timestamp.
- Keep the record accessible to the affected person.
- Log updates, evidence, and outcomes in a repair log.

Timelines (review clocks)
- Publish the review deadline and expected response time.
- Provide status updates and escalation triggers.
- If deadlines are missed, default to human review or pause.

Remedies (reversal and repair)
- Offer a clear path to reversal or correction.
- List any compensation or remedy options.
- Show proof that remedy was delivered once complete.

Non-retaliation (safe to contest)
- State a no-retaliation guarantee in the contest flow.
- Prohibit increased friction, fees, or access loss after filing.
- Track any adverse impacts and remediate immediately.

See also: Standards · Mechanisms

Copy citation (APA/BibTeX)

Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS

Version

Draft

Last updated

Jun 1, 2025

DOI

Pending Zenodo deposit

APA

Ethotechnics Standards Working Group. (2025). Minimum viable contestability standard. Ethotechnics Institute. https://ethotechnics.org/standards/minimum-viable-contestability

MLA

Ethotechnics Standards Working Group. "Minimum viable contestability standard." Ethotechnics Institute, 2025, https://ethotechnics.org/standards/minimum-viable-contestability.

Chicago

Ethotechnics Standards Working Group. "Minimum viable contestability standard." Ethotechnics Institute. Jun 1, 2025. https://ethotechnics.org/standards/minimum-viable-contestability.

BibTeX

@misc{ethotechnics_standards_minimum_viable_contestability,
  title={Minimum viable contestability standard},
  author={Ethotechnics Standards Working Group},
  year={2025},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/standards/minimum-viable-contestability},
  version={Draft}
}

RIS

TY  - WEB
TI  - Minimum viable contestability standard
AU  - Ethotechnics Standards Working Group
PY  - 2025
UR  - https://ethotechnics.org/standards/minimum-viable-contestability
ER  -