13 min read

Case reports

A case report turns an investigation into the document an analyst hands a decision-maker. It answers "what does this mean for me?" in plain sentences, in the style of a UK intelligence assessment, and every statement in it points back to the source behind it.

The report is generated by fixed rules from the case's records. No language model writes it, so the same case always gives the same report.

Producing one

Build the report in the console's Report workspace (see Build a report and export the case) and download it as Word, HTML or Markdown, or save it as PDF. When the case was run under a playbook, its question heads the report and its manual steps are listed under coverage. Material from restricted or sensitive offline datasets is withheld unless it is explicitly included (see the handling note), and the entities joined by a merge proposal you reject are printed separately (see “One company, several records”).

The HTML is one file with its styling inline. It has no scripts, fonts or images to fetch, so it opens offline, can be attached to an email, and prints cleanly.

What is in it

  1. Heading: title, case name and id, date, and the question. The question is the playbook's if you name one. Otherwise it asks what the records show about the seed.
  2. Key judgements: between three and seven sentences, each with a likelihood and an analytic confidence (see below).
  3. Entities of interest: people, organisations, addresses, properties and vehicles, with their identifiers (company number, LEI, birth month and year, registration mark, and so on). The seed is marked. An entity recorded under several ids is printed once, with the other ids listed.
  4. Timeline: dated records in date order: incorporations, appointments and resignations, changes of control, sanctions designations, notices, judgments, articles and sales. Records without a date are left out.
  5. Mentioned in (only when there are some): dated records that only mention an entity of the case, such as a judgment or article that matched its name. They are not evidence that it took part, so they are kept out of the timeline and the key judgements.
  6. Possibly the same person (only when there are some): people who share a name with someone else in the case, where resolution did not propose them as one person because there is no birth month or Wikidata item to compare. Each entry reads "X shares a name with Y; not assessed as the same person: no date of birth to compare." It is a prompt to look, never a key judgement; the report prints them as separate people.
  7. Connections: links between people, organisations and places in plain words, with their role or nature of control and the likelihood the source gives them. The 40 strongest are listed; the rest are counted.
  8. Coverage and gaps: the jurisdictions the case touched, how likely each placement is, the record types no automated source reached (with the source to check by hand), and the playbook's manual steps.
  9. Sources: every source used, numbered. Each entry gives the access dates, how many records it contributed, the transforms and tree runs that produced them, and the evidence artifacts by digest.
  10. Handling note: what was withheld, and why.

How the language works

Likelihood uses the PHIA probability yardstick described in Assessment language. A judgement reads "It is almost certain that …" or "There is a realistic possibility that …". Each one also states an analytic confidence: high, moderate or low.

Kind of fact Likelihood Analytic confidence
A registry record (confirmed) almost certain high
A strong but not authoritative source (probable) likely moderate
A weak signal (possible) realistic possibility low
A merge proposal the proposal's own term the proposal's own level (high for a shared identifier, moderate for name and birth month)
A sanctions name match the screening band: possible reads as realistic possibility, probable as likely low with no date of birth to compare, moderate with one

A sanctions match is not read at its raw score. A name match of 0.86 with no date of birth to confirm it is a realistic possibility, not "highly likely". The score is printed beside it so the reader can see both.

A link nobody rated, or one rated unverified, never becomes a key judgement. In the connections list it shows as unrated or unassessed.

A sanctions screen of the seed that found nothing is stated as a finding, with no likelihood: "No match was found for Example Infrastructure plc on the UK Sanctions List or the OFAC SDN list as screened on 2026-11-14; this does not rule out listing under another name." No match under the name screened is not evidence that the seed is not listed under another name, so the report does not say "unlikely". The statement cites the screening runs as a source, because a screen that finds nothing writes no records.

Entities are named from their recorded name. Only an entity with no name is called by a record number (company 01234567, LEI …, Wikidata item Q…) or, failing that, its id.

One company, several records

Sources key a company differently: the name the analyst typed, the Companies House number, the GLEIF LEI, the Wikidata item. After every investigation tree or playbook run, Viokit proposes which of these are one organisation and records each proposal.

Basis Likelihood Applied by the report
The same company number, LEI or Wikidata QID, as an identifier or in the id, directly or through another record almost certain, high confidence yes
A name-only record whose legal name matches exactly one registry company (case, punctuation, & and the PLC / LIMITED / LTD / LLP forms ignored) likely, moderate confidence no: stated as a key judgement for a person to accept

If the records would join two different company numbers in one registry, or two different LEIs, the sources disagree and nothing is proposed for that group.

Nothing in the graph is rewritten: every record keeps its id and its relations, and the proposal records what was shared and the evidence it rests on. The tree summary lists the proposals. The report prints the records an almost-certain proposal joins as one entity, under the seed's id and name when the seed is among them, with all identifiers and every source cited. A merge can be left out of one report, and recording proposals can be switched off for a run.

One person, several records

People are resolved the same way, after every investigation tree or playbook run:

Basis Likelihood Applied by the report
The same Wikidata QID, as an identifier or in the id almost certain, high confidence yes
The same name and the same birth month and year: Companies House officers under different officer ids, PSC records, and any other person record with a birth month and year or date of birth. SURNAME, Forenames and Forenames SURNAME read the same; case, punctuation and a leading title (Mr, Mrs, Dr …) are ignored likely, moderate confidence no: stated as a key judgement until an analyst accepts it

A name alone never makes one person. Two people with the same name and different birth months are different people: no proposal is made and neither is offered as the other. A person with no birth month who shares a name with another is listed in the tree summary as possibly the same person, with no proposal. Records that give two different full dates of birth, or two different Wikidata items, are proposed as nothing.

A party on a sanctions list is left to its screen. A screen's proposal is never applied by the report, whatever its score; an analyst who accepts one sees "accepted by …" added to the sanctions judgement, and the listed party is still printed separately.

The tree summary lists person proposals. Recording them can be switched off for a run. An applied person merge is printed as one person, with every officer id or record it was found under in “also recorded as”.

Accepting and rejecting a proposal

Every merge proposal in the case (organisation, person and sanctions) can be listed with its basis, likelihood, analytic confidence and status: pending, accepted or rejected, with who decided, when and why, and whether the report prints the two as one. An analyst can accept or reject a proposal, with an optional reason; the decision is recorded in the case history, attributed to the acting person with the time. Nothing is edited: the proposal stays, the decision is another record, and the latest decision on a proposal stands. Repeating the standing decision records nothing.

Decision The report Later resolution runs
none applies an almost-certain proposal; states a likely one as a key judgement do not propose the pair again
accepted applies it, likely or not (not a sanctions screen), and says "accepted by … on …" do not propose the pair again
rejected never applies it and drops it from the key judgements never propose the pair again, nor join its two sides through another record

The report also refuses to join a rejected pair through other proposals: if A is B and B is C were both applied but A and C were rejected, C stays separate. A merge can still be left out of a single report, on top of all this.

How key judgements are chosen

The ranking is fixed and printed in every report:

  1. confirmed registry facts about the seed, read across every record it was resolved from: its status and company number, registered office, incorporation date and LEI (almost certain when GLEIF gives it, likely when only another source does);
  2. insolvency events and court cases (a winding-up order reads "entered compulsory liquidation: a winding-up order was published on …");
  3. sanctions candidates;
  4. sanctions screens of the seed that found no match;
  5. ownership and control (persons with significant control, parent companies, owners);
  6. merge proposals (the same person or company found twice);
  7. shared addresses.

A record linked at less than likely (a judgment that only matched the company's name, for example) is never a key judgement; it is listed under "Mentioned in". Within a category, facts that involve the seed come first, then the more likely ones, then alphabetical order. Up to four registry facts and at most two from each other category are taken in the first pass, so one busy category cannot crowd out the rest. The list is then filled in rank order up to seven. If the records support fewer than three, the report says so.

Tracing a statement

Every judgement, entity, timeline entry and connection carries bracketed numbers, such as [2][5]. These are the sources (in HTML, links to them) whose records assert the fact. A source entry names the source, its access dates, the lookups and tree runs that produced its records, and the digest of each artifact. To check a statement, open the artifact itself, or read the steps in the case history.

Merge proposals cite "Viokit correlation", because they are derived from the case's own records rather than fetched. The seed cites "Investigation seed". A screen that found nothing cites an entry named after the list, giving the screening runs and their date.

Handling note: what is never printed

A report applies the same withholding rules as the evidentiary export: an artifact redacted from the case is withheld, and so is an artifact read from a restricted or sensitive offline dataset, unless you chose to include that dataset.

Every record that cites a withheld artifact is left out of the report, even where other sources say the same thing. The report is built only from the remaining records. A fact known only from withheld material is not stated, and an entity known only from it appears as [withheld entity], because its id can carry a name. The handling note says how many artifacts were withheld, gives each one's digest prefix and reason, and counts the records and facts left out. It also lists artifacts the records cite that the evidence store could not produce.

Watching a case: what is new since last time

A case can keep watches, so it can be run again later and show only what changed. A watch is a playbook with a seed, or a plain tree from a seed such as a domain. You can run every watch on the case, and ask for the changes since the last watch run or since a date.

A watch run re-runs the tree and asks cache-first sources again instead of reading the cache. It then compares the case before and after the run and returns one line per change, each with the steps, evidence and sources behind it:

  • New event: Winding-up order, dated 2026-11-10; concerns Acme Widgets Ltd (almost certain (95–100%))
  • Acme Widgets Ltd: company status changed from Active to Liquidation
  • Jane Doe — director of — Acme Widgets Ltd: ended 2026-11-09
  • New address: 2 New Street; Acme Widgets Ltd located at it (almost certain (95–100%)); previously recorded: 1 Old Street

When the last watch run found changes, the report opens with a New since section listing them, each with its source and acquisition date. The date is the latest acquisition the case held before that run. Changes that rest only on withheld material are left out.

Watches and watch runs are stored beside the run records, not in the case's records, so they survive restarts and never travel with an export.

Checking on a schedule

A watch can be checked on a schedule, in the local time of the machine running Viokit: for example every day at 08:00, every 6 hours or every Monday at 08:00, or off. You can see every scheduled watch, soonest first, see what scheduled runs found (including ones already seen), and mark alerts as seen.

While Viokit is running it checks for due watches once a minute and runs them one at a time. Each run shows in the case history as a "scheduled watch run". The next run is worked out from the last one, so a watch whose time passed while Viokit was stopped runs once when it starts again. Whoever runs Viokit can turn scheduled runs off. A scheduled run that finds changes raises an alert: the console's top bar shows "3 new changes", and if an alert address has been set up the alert is also posted onward.

Printing and PDF

The HTML report prints on A4 with a header naming the case and date and page numbers where the browser supports CSS paged media (Chrome and Edge do). Each major section starts on a new page, backgrounds are dropped, and source references and source addresses are kept. In the console, the report dialog's Print / Save as PDF opens the browser's print dialog; choose “Save as PDF” there.

Limits

  • The report states what the gathered records support, not what is true. A gap in the records is not evidence of absence.
  • Coverage gaps are recomputed from the entities in the report and the transforms that ran. Jurisdictions that packs infer from phone numbers are not included.
  • The playbook is not recorded with the case, so name it when you generate the report to get its question and manual steps.
  • Wording is generated from templates. It is plain but sometimes stilted, for example "the director of BETA HOLDINGS LTD (Jane SMITH)".

Sample

A shortened Markdown report for a company seed:

# Case report: ACME WIDGETS LTD

- **Case:** Acme due diligence
- **Date:** 2026-11-14
- **Question:** What do the records show about ACME WIDGETS LTD (organization)?

## Key judgements

- It is almost certain that ACME WIDGETS LTD (company number 01234567) is recorded as in liquidation (Companies House, high confidence). [2]
- It is almost certain that ACME WIDGETS LTD's registered office is 1 High Street, London EC1A 1AA (Companies House, high confidence). [2]
- It is almost certain that ACME WIDGETS LTD was incorporated on 2015-03-01 (Companies House, high confidence). [2]
- It is almost certain that ACME WIDGETS LTD entered compulsory liquidation: a winding-up order was published on 2024-02-10 (The Gazette, high confidence). [6]
- No match was found for ACME WIDGETS LTD on the UK Sanctions List or the OFAC SDN list as screened on 2026-11-12; this does not rule out listing under another name. [9][10]
- It is almost certain that ACME WIDGETS LTD is controlled by BETA HOLDINGS LTD (ownership of shares 75 to 100 percent) (Companies House, high confidence). [5]
- It is likely that the director of BETA HOLDINGS LTD (Jane SMITH) is the same person as the director of ACME WIDGETS LTD (Jane SMITH) (officer resolution: name and birth month, moderate confidence). [4]

## Timeline

- **2015-03-01** — ACME WIDGETS LTD incorporated [1][2]
- **2017-06-01** — ACME WIDGETS LTD came under the control of BETA HOLDINGS LTD [5]
- **2024-02-10** — Winding Up Orders: Gazette notice 4000001, involving ACME WIDGETS LTD (insolvent-company) [6]

## Mentioned in

- **2023-05-05** — Article: Acme widens its range, involving ACME WIDGETS LTD [7]

## Sources

2. **Companies House** — accessed 2026-11-10; 4 records; evidence aaaaaaaaaaaa (live)

## Handling note

2 artifacts were withheld. 5 records citing them were left out, and 4 facts known only from withheld material are not stated. The material remains in the case.
Withheld 9999999999999999… (third-party): names a journalist's source
Docs

↑↓ to moveEnter to openEsc to close