Urgency · Australia
High-demand claim
High-demand claim is a working label for this design mechanism: A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. This is editorial implementation guidance for Australian journeys, not a finding of unlawfulness. From 1 July 2027, a similar interface is relevant to ACL section 28B only if the complete consumer-connection, manipulation or unreasonable-distortion and actual-or-likely-detriment test is met. Current ACL rules require a separate assessment.
- Family
- Urgency
- Also known as
- Journey stages
Definition
What is this pattern?
A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. This is a design and research taxonomy for learning and evidence review, not a statutory offence label or an automatic finding that an interface is unlawful.
How it works
A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. A demand message suggests competition from other buyers without a current, relevant measure connecting that activity to the user’s available offer.
Warning signs
- The claim refers to demand, viewers, purchases or bookings rather than remaining stock.
- It is temporally framed and connected to a transaction.
- Truth and representativeness require provenance or controlled replay.
Potential harms
- The unsupported demand cue can create pressure to book before comparing alternatives.
- Historical popularity is framed as immediate demand and may rush a decision.
Learn by comparison
What does this look like?
These fictional examples make the design mechanism easier to recognise. They do not depict a real company and do not establish that an individual interface is unlawful.
Illustrative example 1 · Fabricated live-viewer count
A fictional travel site displays “42 people are viewing this” from a fixed script that runs for every result and visitor.
Potential consumer harm: The unsupported demand cue can create pressure to book before comparing alternatives.
Illustrative example 2 · Old booking spike presented as current demand
A fictional seller says “Selling fast today” using sales from the launch week three months earlier.
Potential consumer harm: Historical popularity is framed as immediate demand and may rush a decision.
Fabricated live-viewer count
A fictional travel site displays “42 people are viewing this” from a fixed script that runs for every result and visitor.
42 people viewing now. The number is fixed and unrelated to current viewers.. Book before demand rises. Claim basis, collapsed
Current availability. The page uses verifiable inventory rather than invented audience pressure.. Rooms available for these dates. Claim basis, expanded: The relevant population, period, inventory or offer state is presented with the message.. View the source and period for “Rooms available for these dates”
Why the first version can mislead: The message applies immediate pressure at the pricing decision. The cue “Book before demand rises” should correspond to a defined operating state and a real consequence. The example instead states: “The number is fixed and unrelated to current viewers.” The unsupported demand cue can create pressure to book before comparing alternatives.
What a fairer design does: Use a clearly defined live metric only when supported, including the relevant listing and measurement window.
Show annotated differences (4)
- The number is fixed and unrelated to current viewers.Why this state matters: The message applies immediate pressure at the pricing decision. The cue “Book before demand rises” should correspond to a defined operating state and a real consequence. The example instead states: “The number is fixed and unrelated to current viewers.” The unsupported demand cue can create pressure to book before comparing alternatives.
- Claim basis, collapsedReview prompt: Which timestamped inventory, reservation, demand or offer event substantiates “Book before demand rises”, and what changes when its limit is reached?
- The page uses verifiable inventory rather than invented audience pressure.Fairer design: Use a clearly defined live metric only when supported, including the relevant listing and measurement window.
- View the source and period for “Rooms available for these dates”Review prompt: Record the claim, timestamp, data source and post-claim state; which evidence supports “The claim refers to demand, viewers, purchases or bookings rather than remaining stock”?
Review questions (3)
- Which timestamped inventory, reservation, demand or offer event substantiates “Book before demand rises”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “The claim refers to demand, viewers, purchases or bookings rather than remaining stock”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “Remaining-stock claim”?
Old booking spike presented as current demand
A fictional seller says “Selling fast today” using sales from the launch week three months earlier.
Selling fast today. The supporting sales period ended three months ago.. Tickets moving quickly. Claim basis, collapsed
Ticket availability. Remaining allocation and refresh time are shown without a stale demand claim.. 312 tickets at 14:05. Claim basis, expanded: The relevant population, period, inventory or offer state is presented with the message.. View the source and period for “312 tickets at 14:05”
Why the first version can mislead: The message applies immediate pressure at the pricing decision. The cue “Tickets moving quickly” should correspond to a defined operating state and a real consequence. The example instead states: “The supporting sales period ended three months ago.” Historical popularity is framed as immediate demand and may rush a decision.
What a fairer design does: State the actual period behind a demand claim or remove the claim when it is no longer current.
Show annotated differences (4)
- The supporting sales period ended three months ago.Why this state matters: The message applies immediate pressure at the pricing decision. The cue “Tickets moving quickly” should correspond to a defined operating state and a real consequence. The example instead states: “The supporting sales period ended three months ago.” Historical popularity is framed as immediate demand and may rush a decision.
- Claim basis, collapsedReview prompt: Which timestamped inventory, reservation, demand or offer event substantiates “Tickets moving quickly”, and what changes when its limit is reached?
- Remaining allocation and refresh time are shown without a stale demand claim.Fairer design: State the actual period behind a demand claim or remove the claim when it is no longer current.
- View the source and period for “312 tickets at 14:05”Review prompt: Record the claim, timestamp, data source and post-claim state; which evidence supports “It is temporally framed and connected to a transaction”?
Review questions (3)
- Which timestamped inventory, reservation, demand or offer event substantiates “Tickets moving quickly”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “It is temporally framed and connected to a transaction”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “static aggregate popularity claim”?
What is a fairer alternative?
Base demand messages on current auditable data and state the metric and period without exaggeration.
Legal and information status
How Australian law may apply
A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. A demand message suggests competition from other buyers without a current, relevant measure connecting that activity to the user’s available offer. These harms describe a review risk, not an automatic legal conclusion. Australian section 28B commences on 1 July 2027 and requires its complete, context-specific test. Existing ACL provisions remain a separate current-law assessment.
ACL section 28B, inserted by the 2026 Act
Possible risk indicator
In pricing journeys, the high-demand claim mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The urgency label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support this working pattern within the urgency family. It is editorial implementation guidance, not an Australian statutory category, regulator finding or legal safe harbour.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Final Act mappingEditorial implementation guidance
This editorial practice label is not itself an express statutory prohibition. Apply the complete provision and its scope to the facts.
Possible general-test applicationCommences 1 July 2027
ACL section 28B, inserted by the 2026 Act: In pricing journeys, the high-demand claim mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The urgency label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Existing ACLCurrent enforcement
Existing ACL provisions continue to apply on their own elements before and after commencement. The 2027 provisions must not be applied early.
Verified enforcement contextCurrent enforcement
No named pattern-specific enforcement example is asserted on this page. Existing ACL analysis remains fact-specific and separate from the 2027 provisions.
RegulationsRegulation pending
Later regulations may affect specified exclusions, matters or exceptions. That uncertainty does not postpone a core enacted rule unless the provision itself depends on prescription.
Regulator implementation materialGuidance pending
Government funding and parliamentary material anticipate regulator education and guidance. No dedicated final ACCC implementation guide is treated here as published.
Journey and evidence recommendationsEditorial implementation guidance
Base demand messages on current auditable data and state the metric and period without exaggeration. This is editorial portal guidance, not a statutory duty, regulator safe harbour or compliance certificate.
Context matters
Context and boundary cases
- The claim refers to demand, viewers, purchases or bookings rather than remaining stock.
- It is temporally framed and connected to a transaction.
- Truth and representativeness require provenance or controlled replay.
- Boundary to test: Remaining-stock claim
- Boundary to test: static aggregate popularity claim
- Boundary to test: auditable live demand metric with clear definition
When a similar design can serve a legitimate purpose
- Remaining-stock claim
- static aggregate popularity claim
- auditable live demand metric with clear definition
Operational review
What teams should review
- Teams
- Which timestamped inventory, reservation, demand or offer event substantiates “Book before demand rises”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “The claim refers to demand, viewers, purchases or bookings rather than remaining stock”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “Remaining-stock claim”?
- Which timestamped inventory, reservation, demand or offer event substantiates “Tickets moving quickly”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “It is temporally framed and connected to a transaction”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “static aggregate popularity claim”?
Evidence to retain
- Annotated pricing screenshots at each responsive breakpoint
- The complete state sequence before, during and after the consumer decision
- Design-system component, content, default and configuration records for the reviewed release
- Operational records substantiating price, availability, timing and eligibility claims
- Usability, accessibility, reversal, complaint and support evidence relevant to consumer impact
- A dated product and legal review record identifying evidence, uncertainties and release decisions
Legal map and implementation tools
Evidence base
Sources
- Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
- Competition and Consumer Amendment (Unfair Trading Practices) Act 2026Federal Register of Legislation · Primary · checked 2026-09-14 · C2026A00064
- Competition and Consumer Act 2010, including Schedule 2: Australian Consumer LawFederal Register of Legislation · Primary · checked 2026-09-14 · C2004A00109
- Unfair trading tricks and traps to be bannedTreasury Ministers · Primary · checked 2026-09-14
- Inquiry into the Competition and Consumer Amendment (Unfair Trading Practices) Bill 2026Senate Economics Legislation Committee · Primary · checked 2026-08-09