For teams · Legal

Unfair trading reform for legal teams

Legal teams should treat the enacted text, future commencement, pending regulations or guidance, current ACL and current enforcement as separate layers. The most useful preparation is to connect the complete statutory test to the pricing, subscription or cancellation states customers actually encounter and to record which conclusions still depend on prescribed detail.

Who this is for
Consumer, commercial, product and regulatory counsel advising consumer-facing businesses in Australia.
Practical outcome
A provision-level decision record that identifies the applicable test, supporting journey facts, unresolved regulatory detail, remediation and a clear review trigger.
Boundary
Implementation preparation for enacted legislation that commences on 1 July 2027, alongside current ACL and enforcement. This pathway is not legal advice.

Evidence workflow

Each stage produces evidence for the next team. Keep the sequence together so a later reviewer can see what was enacted, observed, assumed and decided.

  1. Classify

    Choose the correct statutory path

    Identify whether the question concerns the general unfair-trading test, transaction charges, subscriptions or current law.

    Evidence to retain
    Provision, commencement state, business role, consumer context and open prescribed detail.

  2. Observe

    Review the complete decision environment

    Follow the experience from entry to commitment and through renewal, change, exit or confirmation as relevant.

    Evidence to retain
    Ordered interfaces, prices, claims, controls, timestamps and state transitions.

  3. Apply

    Test every legal element

    Map the observed facts to the statutory language and actively seek facts that weaken the initial concern or support a legitimate implementation.

    Evidence to retain
    Element-by-element analysis, scope assumptions, counter-evidence and current-law overlay.

  4. Decide

    Set remediation and review triggers

    Give product teams a clear boundary and state which future regulation, guidance, enforcement action or release requires reassessment.

    Evidence to retain
    Decision note, owner, fix, residual uncertainty, commencement plan and trigger.
This workflow is a practical review model, not a statement of legal duty.Provenance: Original Flowlane workflow diagram authored for the Legal pathway from the portal’s current legislative and journey methodology; source context checked 2026-09-14.

Role ownership

What this team should make explicit

Classify the legal pathway

Distinguish the section 28B general prohibition, section 48A transaction-charge disclosure and sections 48B to 48H subscription rules before applying their different scope and elements.

Keep commencement and current law separate

State when the new provision commences and identify current ACL, privacy or sector obligations that may already matter. Do not describe a future rule as presently operative.

Track prescribed detail honestly

Mark contract classes, information, timing and limited circumstances that still depend on regulations or guidance. Avoid filling those gaps with assumed policy intent.

Apply the test to the journey

Connect conduct, decision environment, consumer effect, detriment and other statutory elements to observed screens and state transitions, not only a pattern name.

Evidence checklist

The records needed for a defensible handoff

Authoritative legal record
Registered Act, provision, commencement information, regulations, guidance and current enforcement source behind every material statement.
Consumer path
The offer, price, options, notifications, account controls, cancellation and confirmation states in their actual sequence.
Scope facts
Consumer connection, contract or charge type, business role, timing, targeting, detriment and any prescribed category on which the analysis depends.
Decision lifecycle
Reviewer, assumptions, approved change, unresolved issue and the regulatory or product event that should reopen the assessment.

Use in review

Questions that expose missing context

  1. Which provision is being applied, when does it operate and what consumer or transaction scope must be established?
  2. Which elements are supported by observed journey facts, and which remain assumptions or require future prescribed detail?
  3. Is the statement about enacted law, pending regulation or guidance, current enforcement, implementation advice or editorial research?
  4. Where does the customer first learn the total price, recurrence, notification, change or cancellation consequence?
  5. What legitimate purpose or necessary safeguard could explain the implementation, and is a less harmful path available?
  6. Which authoritative or product event will cause this decision to be reviewed again?

Cross-functional handoffs

What the next team needs from you

To product and UX

Explain the material consequence, statutory element and acceptable design boundary in language tied to the journey rather than only a section number.

From engineering

Request reproducible state, price logic, contract classification, notification timing and proof that the approved outcome persists across variants.

To governance owners

Record commencement dependencies, pending regulatory detail, residual risk and the owner of each review trigger.