For teams · Compliance & Engineering

Unfair trading reform for compliance and engineering teams

Compliance and engineering teams should translate the enacted requirements and open implementation questions into observable journey states, configuration and release controls. Deterministic system facts can be tested automatically, while statutory interpretation, legitimate purpose and detriment remain bounded human review questions.

Who this is for
Compliance owners, engineers, QA teams, design-system maintainers, data teams and governance leads responsible for Australian consumer journeys.
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.
Boundary
Implementation evidence and release assurance for 1 July 2027 and current law. Automation supports review; it does not certify compliance.

Evidence workflow

Compliance & Engineering: from question to reviewable decision

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. Specify

    Define the factual control

    Separate observable system behaviour from the legal question and document what remains pending in regulation or guidance.

    Evidence to retain
    Control statement, provision, commencement, scope, exclusions and human-review boundary.

  2. Capture

    Follow the complete journey

    Collect the relevant states from offer or entry through charge, renewal, account change, cancellation and confirmation.

    Evidence to retain
    Screens, structure, inputs, configuration, prices, timestamps and backend outcomes.

  3. Review

    Join automation with judgment

    Use automated checks for reproducible facts and route the statutory test, consumer effect and legitimate-purpose questions to qualified reviewers.

    Evidence to retain
    Control result, reviewer analysis, counter-evidence, approved exception and remediation.

  4. Re-run

    Monitor meaningful change

    Repeat the journey after product releases and authoritative legal developments, retaining the prior state for comparison.

    Evidence to retain
    Change set, before-and-after journey, new source, regression result and reopened decision.
This workflow is a practical review model, not a statement of legal duty.Provenance: Original Flowlane workflow diagram authored for the Compliance & Engineering pathway from the portal’s current legislative and journey methodology; source context checked 2026-09-14.

Role ownership

What this team should make explicit

Model legal states as system facts

Identify charge type, contract classification, notification event, cancellation request, effective date and confirmation state without encoding unresolved legal interpretation as fact.

Reproduce customer variants

Define locale, account, product, device, feature flag, experiment and data conditions that can change the price or decision environment.

Test the completed outcome

Do not treat a click as success. Confirm price composition, subscription state, cancellation effectiveness, notification dispatch and customer-visible confirmation.

Operate review triggers

Reopen controls for material releases, pricing or contract changes, regulations, guidance and enforcement, not merely because a calendar reminder elapsed.

Evidence checklist

The records needed for a defensible handoff

Reproduction record
Environment, consumer state, contract or charge type, locale, viewport, experiment allocation and steps to reach the interface.
System outcome
Rendered interface, accessible structure, price components, notifications, business events and persisted subscription or cancellation state.
Legal configuration
Provision, commencement date, prescribed detail status, approved interpretation and the source version used by the control.
Review trail
Signal, human conclusion, severity, fix, verification, exception, release and the event that next reopens the decision.

Use in review

Questions that expose missing context

  1. Can a second reviewer reproduce the same journey and system outcome from the retained context?
  2. Which controls test observable facts, and which decisions still require legal, product, UX or accessibility judgment?
  3. Does the evidence prove the transaction, notification or cancellation outcome rather than only a user interaction?
  4. Are price, contract, locale, device, account and experiment variants represented where they affect the decision environment?
  5. How will pending regulation or guidance be added without silently changing historic decisions?
  6. What product release, legal source or enforcement development automatically reopens the control?

Cross-functional handoffs

What the next team needs from you

From product and UX

Request the intended customer outcome, fair-design principle, state model and acceptance criteria, not only final-screen artwork.

From legal and compliance

Request the provision, operative date, factual threshold, pending detail and clear boundary for human interpretation.

Back to reviewers

Return reproducible journey evidence, actual backend outcome, variant coverage and known blind spots so the decision can be defended and revisited.