Dark-pattern family · 4 patterns

Urgency

Applies temporal or quantitative pressure through real, exaggerated or fabricated scarcity claims.

This family groups related interface mechanisms for learning and journey review. It is not a legal category and does not make every matching interface unlawful. Start with the mechanism, then examine the complete decision, audience, effect and EU rule actually within scope.

Explore the 4 patternsBrowse the 8 individual examples

Recognition framework

How to review urgency.

Treat every countdown, stock warning, demand message and deadline as a claim about an operational state. Define its subject, denominator, location, time window and consequence, then replay expiry and return visits. Pressure should disappear when the underlying constraint does not exist.

Recognition signals

  • A timer, stock statement, demand cue or deadline presses for immediate action.
  • The claim is not tied to a defined inventory, audience, reservation or offer event.
  • The message resets, renews or has no stated consequence when its limit is reached.

Decision points

  • The inventory, reservation, audience or offer event behind the message
  • The refresh interval and timestamp visible to the user
  • What changes when the stated limit is reached
  • Whether the same message persists across users, variants and returns

Fair-design principles

  • Connect every pressure claim to a verifiable operating state and timestamp.
  • Explain what is limited and what actually changes at expiry.
  • Remove urgency cues where the evidence cannot support their wording and scope.

Evidence to retain

  • Inventory, reservation or promotion system record
  • Rendered message with timestamp and selected variant
  • Expiry and repeat-visit replay
  • Approval and monitoring for pressure claims

Boundary to keep visible

Real stock limits, reservations and fixed promotions can be useful. Accuracy depends on scope and persistence: a genuine local constraint should not be worded as universal scarcity, and a deadline should not renew silently.

EU legal and policy context

Keep taxonomy, current law and the announced DFA process separate.

A family name helps teams compare interface mechanisms. It is not an EU legal category, and similarity to an example does not establish that a current rule has been infringed or that a future Digital Fairness Act will use the same label.

Current-law context

The UCPD and any relevant sector instrument require their own scope, conduct, information and likely-effect assessment. The complete journey and evidence matter; a taxonomy match is only a prompt to investigate.

Officially announced

The Commission is preparing a legislative DFA initiative and currently places a proposal in Q4 2026. That planning date is indicative, and no published proposal yet creates a family-specific duty.

Under consideration

The call for evidence discusses possible policy responses to digital fairness concerns. Options, consultation questions and stakeholder submissions are not Commission proposals or present obligations.

Still unknown

Final instrument form, scope, definitions, thresholds, enforcement, transition and application remain unknown until primary legislative text is published and validated.

Open the current-law mapCheck the verified timeline

Journey coverage

Where urgency can become visible.

Review the state before the decision, the controls and information available at that moment, the immediate result and any later account or billing consequence. Journey links below show where this family appears in the published taxonomy; they do not imply that every product or every stage contains the mechanism.

4 related patterns

Pricing

Pricing review starts before checkout. Search cards, campaign landing pages, recommendation logic, comparison tables and membership offers can each shape the price a person understands. Teams should reconstruct the comparable payable amount, the basis of every saving or popularity claim and the information available when a product first becomes a realistic option.

Open the journey guide →

3 related patterns

Checkout

Checkout concentrates price, add-ons, urgency, identity and the final payment action. Review should begin with the state carried into the basket and finish only when the order, receipt and account state agree. A control that appears clear in isolation can still be misleading when a fee arrives late, a removed item returns or the final button does more than its label predicts.

Open the journey guide →

Pattern directory

Explore every urgency pattern.

Each detail page contains two fictional interface comparisons, practical recognition and exclusion criteria, a fairer alternative, review questions and a legal-status map that keeps editorial taxonomy separate from current law and the announced DFA process.

Editorial analysisUrgency

Countdown timer

A visible countdown applies time pressure, particularly where it resets, is personalised without disclosure or has no corresponding consequence at zero. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.

  • Pricing
  • Checkout

2 visual examples

See visual examples
Editorial analysisUrgency

High-demand claim

A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.

  • Pricing

2 visual examples

See visual examples
Editorial analysisUrgency

Limited-time or reservation claim

A textual deadline or temporary-reservation claim pressures action, particularly where the deadline renews or its stated consequence does not occur. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.

  • Pricing
  • Checkout

2 visual examples

See visual examples
Editorial analysisUrgency

Low-stock claim

A claim that few units remain applies purchase pressure, especially where inventory basis or persistence is unsupported. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.

  • Pricing
  • Checkout

2 visual examples

See visual examples

Evidence-led workflow

Turn a visual signal into a reviewable record.

  1. Reproduce the complete decision path and preserve each material state, option, disclosure, default and price before and after the action.
  2. Check the pattern’s inclusion criteria and legitimate-use boundaries instead of classifying from appearance alone.
  3. Verify the operating facts behind timing, stock, ranking, price, consent and account state, and record what evidence would falsify the initial concern.
  4. Apply current law, announced preparation, matters under consideration and unknown future details as separate layers with dated sources.

Evidence base

Sources

  1. Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
  2. Unfair Commercial Practices DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2005/29/EC; CELEX 02005L0029-20220528
  3. Review of EU consumer lawEuropean Commission, Directorate-General for Justice and Consumers · Primary · checked 2026-09-14
  4. Commission work programme 2026: Europe's Independence MomentEuropean Commission · Primary · checked 2026-09-14 · COM(2025) 870 final; CELEX 52025DC0870; Annex I item 30
  5. Digital Fairness Act: call for evidence for an impact assessmentEuropean Commission · Primary · checked 2026-08-09 · Initiative 14622; Ares(2025)6275573