Case visualizer: how a typical ITMR matter can unfold
From the first inquiry to the result: this module shows typical matter paths as an anonymised flow chart. It is not a risk checker, but a transparent look at structure, roles, documents and possible next steps. This shows you how a typical ITMR matter can unfold.
What the case visualizer does
From the outside, matters often seem abstract: a contract, cease-and-desist letter, data breach, platform report, AI project or brand launch. The case visualizer translates typical matter situations into a clear process: which information counts first? What is reviewed? When does a strategy emerge? Which implementation steps are typical? And which result can realistically be achieved?
Select the type of matter
Choose an anonymised case type. The flow chart, document list and result logic adjust automatically.
Flow chart of the matter
The process begins with quickly recording the incident, deadline and affected data. This is followed by legal review, notification and communication strategy, implementation and a documented result.
Inquiry and immediate triage
First, the incident, time, affected systems, persons, data categories and running deadlines are assessed. What matters is whether immediate preservation, notification or communication is required.
The five phases of a typical matter
The specific handling always depends on the individual case. As orientation, however, the process can often be structured in five phases.
Inquiry
The matter is recorded with its occasion, goal, deadlines, documents and economic significance.
Review
The legal position, evidence, contracts, communication, platform status or technical documentation are evaluated.
Strategy
The possible paths are prioritised: fast, out of court, negotiating, documenting or contentious.
Implementation
Depending on the case, letters, contract versions, notifications, clauses, processes, roadmaps or court steps are produced.
Result
The end result is not just a document, but a robust position for action with a comprehensible rationale.
What typically matters in the selected case
The following areas change with the selected type of matter. This shows quickly which information is particularly helpful for an initial assessment.
Useful documents
For data breaches, the incident description, times, system information, affected data categories, internal communication and measures already taken are particularly helpful.
Typical review questions
What matters is whether there is a notification obligation, which risks to data subjects must be assumed, whether data subjects need to be informed and how the evidence file should be built.
Possible picture of the result
The goal is a clear notification line, a comprehensible risk decision, clean documentation and a plan of measures that can be implemented internally.
Matter logic at a glance
The matrix shows how typical types of matter differ. It does not replace an individual review, but helps you prepare an inquiry.
| Type of matter | Common trigger | First focus | Typical implementation |
|---|---|---|---|
| Data protection / authorities | Incident, complaint, access request, letter from supervisory authority | Deadline, risk, evidence, communication | Notification, statement, documentation, process fix |
| IT contract / SaaS | Project start, negotiation, dispute, renewal | Services, liability, data protection, exit, security | Contract review, clauses, redline, negotiation strategy |
| Cease-and-desist / conflict | Deadline letter, claim, urgent opposing party | Basis of claim, evidence, injunction risk | Response, modification, settlement, litigation strategy |
| Platform / content / reputation | Review, post, account block, media inquiry, takedown | Factual basis, rights, platform route, preservation of evidence | Report, counter-statement, removal, communication line |
| AI / digital compliance | Use of tools, product launch, customer demands evidence | Role, risk, data, contracts, governance | Register, policy, clauses, roadmap, documentation |
Sensible next steps
If the case needs a more specific assessment, these ITMR entry points can help depending on the occasion.
Summary for an inquiry
The following text is generated automatically from the selected case type. It can be copied and used as orientation for a contact request.
Summary copied.
Important note on this overview
The processes shown are anonymised, typical structural examples. They do not replace a legal review of the specific case. Depending on the facts, deadlines, claims, responsibilities, communication risks and sensible steps can differ considerably. How we conduct contentious proceedings is described in the area litigation; in urgent cases, our page on preliminary injunctions.