For teams · Legal

Digital fairness for legal teams

Legal teams can prepare now without pretending that the Digital Fairness Act already contains final duties. The useful work is to identify the decision environment, map current rules and their factual thresholds, record what remains under consideration, and connect each conclusion to the interface states customers actually encounter.

Who this is for
Consumer, product, privacy, platform and commercial counsel advising consumer-facing digital services in the EU.
Practical outcome
A review record that explains the current legal basis, the material facts, the unresolved questions and the product change or monitoring decision.
Boundary
Current-law analysis and preparation for an announced initiative. This pathway is not a prediction of the Commission proposal and is not legal advice.

Evidence workflow

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

  1. Frame

    Write the legal question narrowly

    Start with one choice or journey and the current rule that may be relevant. List unknown facts before reaching a conclusion.

    Evidence to retain
    Question, jurisdiction, customer context and candidate legal provisions.

  2. Observe

    Review the full customer path

    Examine entry, choice, confirmation, persistence and exit states. Check whether the same outcome changes by device, account or locale.

    Evidence to retain
    Ordered interface states, copy, controls, prices, timestamps and state transitions.

  3. Map

    Apply the legal threshold

    Connect each material fact to the elements of current law and keep policy proposals or research findings in their own evidence layer.

    Evidence to retain
    Provision-level map, scope assumptions, threshold analysis and counter-evidence.

  4. Decide

    Give the team an actionable boundary

    State what should change, what may remain, which safeguards matter and when the assessment must be repeated.

    Evidence to retain
    Decision note, owner, remediation, residual uncertainty and review 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 source and journey methodology; source context checked 2026-09-14.

Role ownership

What this team should make explicit

Separate the legal layers

Keep current law, official announcements, subjects under consideration, stakeholder proposals and editorial analysis visibly distinct. A topic appearing in the policy debate is not a final prohibition.

Frame the complete test

Identify the relevant actor, customer, transaction, interface and threshold. Avoid treating a taxonomy label such as “false hierarchy” as a legal conclusion by itself.

Define the evidence question

Translate broad concerns into questions that can be answered from a journey: what was shown, when, to whom, with which default, price, consequence and realistic alternative?

Record uncertainty and change

State which conclusions depend on unavailable facts or future EU text, and set a review trigger for a proposal, guidance, enforcement decision or product release.

Evidence checklist

The records needed for a defensible handoff

Source record
The instrument, provision, official document, publication date and stable source URL behind each material proposition.
Journey sequence
The screens, copy, controls, defaults and state changes before and after the consequential choice, not a screenshot selected in isolation.
Decision context
Audience, device, locale, account state, price conditions, consent state and other facts that determine whether a rule or risk is relevant.
Version and approval
The build, capture date, reviewer, conclusion, approved remediation and the facts that would require the decision to be reopened.

Use in review

Questions that expose missing context

  1. What current legal provision is being applied, and which factual element of that provision does each captured state support?
  2. Is the concern based on present law, an official DFA milestone, a matter under consideration, guidance or editorial research?
  3. What would a neutral or legitimate implementation look like in the same commercial context?
  4. Could a user understand the price, recurrence, audience or consequence before taking the consequential action?
  5. What evidence would disprove the initial concern, and has that state been captured?
  6. Which product release or regulatory event should reopen this review?

Cross-functional handoffs

What the next team needs from you

To product and UX

Provide the decision point, material information, acceptable alternatives and the reason a particular state or sequence creates legal concern.

From engineering

Request reproducible states, configuration, targeting logic, price calculations and confirmation that the proposed fix persists across variants.

To governance owners

Record the conclusion, unresolved issue, monitoring trigger and who is accountable for revisiting the evidence.