For implementation teams

Prepare by role. Decide from the same journey.

Australia’s amendments create legal, design and system questions that no single team can answer alone. These pathways show what legal, product and UX, compliance and engineering should contribute before 1 July 2027, and how to keep pending regulation or guidance from becoming an assumed requirement.

See the shared workflow

Choose your role

Turn the reform into work your team can own.

Legal

Unfair trading reform for legal teams

A legal-team pathway through Australia’s enacted unfair trading amendments, 1 July 2027 commencement, pending detail and customer-journey evidence.

Practical outcome
A provision-level decision record that identifies the applicable test, supporting journey facts, unresolved regulatory detail, remediation and a clear review trigger.
Open the role pathway →
Product & UX

Unfair trading reform for product and UX teams

A product and UX pathway for improving Australian pricing, subscription and cancellation journeys before the 1 July 2027 commencement.

Practical outcome
A coherent journey in which material choices and consequences are understandable, usable and reviewable from the first offer through confirmation and exit.
Open the role pathway →
Compliance & Engineering

Unfair trading reform for compliance and engineering teams

An operational pathway for turning Australia’s unfair trading amendments into reproducible journey evidence, release controls and review triggers.

Practical outcome
A traceable readiness control showing which journeys were reviewed, what the system did, which legal assumptions were used, what changed and when the assessment must run again.
Open the role pathway →

Evidence workflow

How the teams build one implementation record

The handoff is strongest when the legal premise, customer experience and system outcome can be reviewed together and updated without rewriting history.

  1. Legal

    Classify the provision and operative date

    Separate section 28B, transaction charges and subscription provisions, then mark enacted, commencing, pending and current-law layers.

    Evidence to retain
    Provision, scope, commencement, prescribed detail and statutory threshold.

  2. Product & UX

    Explain the customer decision environment

    Map price, recurrence, choices, notifications, account controls and exit with a neutral alternative for consequential states.

    Evidence to retain
    Journey map, interface comparison, research and design rationale.

  3. Engineering

    Prove the transaction or account outcome

    Reproduce variants and confirm amounts, notifications, subscription state, cancellation effectiveness and confirmation.

    Evidence to retain
    Configuration, interface, business events, persisted state and release.

  4. Compliance

    Maintain readiness through change

    Join the source, evidence and approvals, then reopen the review for material releases, regulation, guidance or enforcement.

    Evidence to retain
    Owner, conclusion, remediation, pending detail and review trigger.
This workflow is a practical review model, not a statement of legal duty.Provenance: Original Flowlane workflow diagram synthesised from this portal’s enacted-law status model, journey evidence and role guidance; reviewed 10 August 2026.