Legal sources and digital issue spotting · Lesson 3

An issue register with evidence and conclusion limits

7 min read

Lesson objectives

  • Convert an ambiguous digital-law question into a register of facts, assumptions, sources, provisional decisions, and escalation.
Reading tools

A review fails when a team begins with ‘there is no legal issue’ and then looks for support. Start with the decision to be made, its deadline, and the people who may be affected. For a registration platform, ‘May we release the identity-document field in Sunday's pilot?’ is testable; ‘Is our platform compliant?’ mixes too many processes and legal systems. An issue register is more than a task list. It names a fact, its source, confidence, a possible rule within a defined scope, the cost of error, and the owner or qualified specialist needed for referral. Record the screen or contract version relied upon. If the interface changes tomorrow, reviewers can see which conclusion must be revisited rather than being told that a general review was completed without a traceable result.

Build three evidence layers. The first is a system log, contract, or interface capture proving what this service actually does. The second is the appropriate primary rule, with provision, version, and checked date. A legal text states the rule but does not by itself prove the product's conduct. The third is specialist interpretation or official guidance that helps apply the text while preserving the limits of both rule and fact. A help-page sentence cannot prove a contract you have not seen. Likewise, listing an EU law does not prove that a user is within its territorial scope. Evidence can conflict: the product specification says no location data are kept, yet network logs show an IP address retained for seven days. Preserve the discrepancy, inspect the operating version, access permissions, and retention. Separating rule sources from evidence of conduct is the central review move.

Use explicit decision states: confirmed by evidence, conditional on a missing fact, referred to a specialist, or rejected for this scope. ‘Confirmed’ does not mean ‘permitted’; perhaps the only confirmed point is that a field reaches a supplier. ‘Conditional’ does not mean leaving a matter ownerless. Name the question, deadline, and result if no answer arrives. Triage by potential harm and how difficult reversal would be. Exposure of people's records, a new data-sharing launch, or a possible notice deadline can require urgent handling; revising a marketing description that triggers no new processing may allow a slower schedule. Do not promise zero risk. Separate a temporary operating decision from a final legal opinion. A dated record allows the decision to change when the law, contract, or product changes.

Connect the register to the previous two skills. Bring the jurisdiction and source column from the scope lesson, and the purpose decision maker and executing party from the actor lesson. Add impact and deadline. A message with four claims needs four entries: ‘We delete email after thirty days’ needs deletion evidence; ‘the supplier has no independent use’ needs contract and implementation; ‘we target nobody in the Union’ needs campaign facts; ‘the image is licensed’ needs a license and its scope. Some may be true and others false. Value comes from giving each promise a way to be corroborated or falsified, not multiplying blank fields. When closing an entry, state which evidence closed it, who reviewed it, and which version was examined. If a legal conclusion requires licensed practice, preserve the referral question instead of granting this educational program authority it does not provide.

Lesson summary

Exercise 2 solution: the hosting row is supported only as to the main database's location, not every network flow. The outside-request row is supported by the captured call from the inspected version, subject to checking configuration. The fields row remains unknown until the request payload, identifiers, and actual recipient are inspected; assume neither that it contains no personal data nor that a regulated transfer has already been proven. The notice row is unsupported, so do not publish the absolute statement. Ask the product owner about transmitted fields, purpose, recipient, country, and retention. A specialist can then review a precise notice. Withhold the claim and any new unreviewed sharing; whether the live page itself must pause depends on the payload and risk. A sound answer separates database hosting from an outside request, uses ‘unknown’ where appropriate, and avoids treating a network call as a final legal conclusion.