O4.13.4Response deadlines for redressdesign

Redress without response deadlines exists on paper only

Aliases: redress deadlines · appeal SLA · response time commitments

What it is

A redress right without deadlines is a paper right: an appeal promised "as soon as possible" can queue forever while the user gives up waiting — a redress that nominally exists and one that actually exists are the same thing in user experience and in compliance assessment. The deadline is the unit of enforcement: an appeal right without one is a posture of revocability.

Why it happens

Without deadlines the failure path is attrition, not refusal: no stage ever says "no," it simply stays "processing" — the user's time cost is uncapped, and the eventual abandonment gets booked as "the user chose not to pursue." Deadlines carry three functions: expectation for the user (how long until an outcome), load discipline for the platform (backlog becomes visible and must be scaled or simplified), and obligation for compliance (some rules mandate redress timeframes, with timeout triggering escalation). The working design has three layers: the committed deadline (the published handling time), the escalation deadline (timeout auto-escalates to a senior reviewer or suspends enforcement — a penalty appeal timing out pausing the penalty is the strong form), and the redress deadline (an unresolved case's default outcome favouring the user). Honesty of commitment is the floor: promising seventy-two hours and delivering seven days wounds trust more than promising nothing — deadline data must enter transparency statistics for external checking.

Where it stops holding

Deadlines must be tiered to be real: complex cases (legal disputes, deepfake forensics) and simple categories (spam) sharing one deadline is either inflated or distorted — set per case type and publish the tiers. Deadlines trade against quality: rushing to meet them sacrifices accuracy (hasty wrongful removals), so on-time rate must be read beside overturn rate — a single on-time metric rewards carelessness. And extreme scale needs contingency: election weeks and breaking events bring report floods where temporary extensions are legitimate, but they must be announced, never allowed to fail silently.

Applying it

  • Publish tiered deadlines: per case type (simple categories seventy-two hours, complex ones fourteen days), with the current on-time rate displayed live.
  • Hard timeout consequences: penalty appeals unresolved at timeout auto-suspend enforcement; service requests auto-escalate and compensate (membership days and the like).
  • Verification: read on-time rate and overturn rate together monthly — high on-time with anomalously rising overturns means corners are being cut; both healthy counts as passing, and the results go into the transparency report.

Related

  • Same group: O4.13.1 External redress beyond the platform · O4.13.3 Reporting abuse and brigading
  • Nearby: O4.08.3 Appeals as the companion of automated decisions · O4.13.2 Transparency statistics as accountability
  • Search terms: redress deadline · appeal SLA · DSA response time

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/O4.13.4