Vidimus
Explainer videos NL Start free

VIDIMUS/CASES

Scenario, not a customer story — names, companies and amounts are fictional

You are the QP. What do you do when the claim comes in?

Five cases, each in six steps: the situation, the problem, what happens without anchoring (and what it costs), what was already on record with anchoring, and the outcome in euros and hours. The course of events is exactly how the platform works; the ending is a scenario. Names, companies and amounts are fictional — these are not customer stories and not a track record.

FARMA-2026-VAC-007 · COLD CHAIN · GDP CLAIM

Vaccine delivery — temperature deviation suspected

Sarah Vermeersch — QA Manager / Qualified Person · BioPharm Belgium NV · Liège

Tuesday 08:47 (UTC+2) — the situation

"Urgent: temperature deviation suspected"

Yesterday a shipment of VaccinX (2–8 °C) was delivered to UZ Gent (Ghent University Hospital) — 240 doses, €21,000. The receiving department logged 8.9 °C when the box was opened. GDP (Good Distribution Practice) requires 2–8 °C. Demand: the full temperature log and the chain of custody within 24 hours.

The problem

Three systems, three clocks

Your logger says max 6.1 °C up to delivery. Their logger says 8.9 °C on opening. The carrier has a third export, from its TMS. At stake: the load (€21,000), a GDP finding at the next inspection, and the contract with the hospital.

Without anchoring

  • Days 1–3: emails back and forth, screenshots of loggers, "just send the raw data" — every export comes from a system its owner can change, and everyone knows it.
  • Day 4: the insurer asks for an independent expert.
  • Week 3: the expert cannot rule out that an export was edited afterwards.
  • Outcome: you pay for the full load and record a GDP deviation.

COST: €21,000 + ± 40 HOURS + GDP FINDING

With anchoring

  • Your logger was a measurement source in Vidimus, with the unit °C and a fixed range. Your monitoring system forwarded every measurement with that logger's key: hashed, signed, anchored every five minutes, and because you were a customer organisation, each group usually also received a qualified timestamp (eIDAS) within six hours — 288 measurements in one series, anchored before anyone knew of a claim.
  • On delivery, the receiving department signed the handover through the share link, with its own key: "received, 5.8 °C at handover" — 14:06 (UTC+2).
  • 08:51 (UTC+2) — four minutes after the email: you export the logger's series and send the bundle and the verification link of the handover. Their IT verifies on its own, without Vidimus.
  • The 8.9 °C "on opening" came after their own signed handover.

CLAIM HANDLED — IN 4 MINUTES

4 minto handle
€21,000not paid
288measurements as proof

Those 288 measurements came from one measuring device: €15 a month, and the first device is free. Against that: €21,000.

BOUW-2026-MW-047 · EXTRA WORK · FINAL ACCOUNT

Extra work block B — "never approved"

Tom De Backer — site manager · shell construction project management · Bouwbedrijf Demo NV · Antwerp

Site, 10:42 (UTC+2) — the situation

"Go ahead with that extra reinforcement"

The client is standing next to you at the foundation slab. €38,500 of extra work. You carry it out. Four weeks later, at the final account: "We never approved that extra work. Show me the document." There is a three-word text message and an invoice drawn up after the fact.

The problem

Fixed price = your risk

Under a fixed-price contract, you can in principle only charge extra for additional work if the client agreed to it in writing (Art. 1793 of the former Belgian Civil Code). Your site report comes from your own system — "your version". The text message has no amount and no description.

Without anchoring

  • You forward the text message. The client "remembers it differently".
  • Your lawyer: a 50/50 chance, with costs higher than the extra work.
  • You drop the extra work to get the final account settled.
  • Next site: same story.

COST: €38,500 LOST + ± 8 HOURS + THE RELATIONSHIP

With anchoring

  • Right there on site: an extra-work order in the app — description, amount, photo of the reinforcement. You sign on your phone; the client confirms on theirs at 10:44 (UTC+2), with their own key.
  • Order + photo anchored at 10:47 (UTC+2); for customer organisations, the qualified timestamp on the group usually follows within six hours as well. Both parties have the same file.
  • Final account: you do not send "our word" but the verification link of the order and of their own confirmation.
  • Their lawyer sees: signed by both parties, unchanged since anchoring, minutes after signing. Whether that is the written agreement Art. 1793 asks for is for the court to assess; in any case, the document is on the table.

PAID WITHIN THE PAYMENT TERM

€38,500paid instead of lost
0 hof dispute
2signatures, each on its own device

Recording the extra work was one record: free up to 100 a month, then €0.08. Not recording it cost €38,500.

VERHUUR-2026-AFG-182 · DAMAGE · RETURN

Aerial work platform back with a dent — "that was already there"

Els Janssens — rental desk · departure & return · Demo Rent BV · Wijnegem

Friday 16:40 (UTC+2) — the situation

Boom lift dented, hydraulic hose damaged

Repair €18,400. The hirer: "That dent was already there at departure — your photos are of a different machine." Your handover report is a PDF from your own system.

The problem

Your document, your system

Without a handover report drawn up by both parties at departure, the hirer is presumed to have received the equipment in the condition in which they return it — the burden of proof is on you. The hirer scribbled a signature in a hurry, the return took place without them present, and photo metadata is trivial to change.

Without anchoring

  • Discussion at the counter, emails, "we will sort it out".
  • Usually you pay half, or all of it.
  • Ten such damage cases a year; on average €2,400 not recovered + 4 hours per case.
  • Your insurance no longer wants to cover it without better handover reports.

COST: ≈ €24,000 DAMAGE + €3,000 HOURS / DEPOT / YEAR

With anchoring

  • Departure Monday 08:12 (UTC+2): condition recorded together with the hirer — six photos per side, hour meter 1,412. Both parties sign; anchored within minutes. Photo 4: no damage.
  • Return Friday 16:40 (UTC+2): same discipline. Hirer absent, so the rental desk signs and the hirer gets the share link with 24 h to dispute. Photo 4: dent. They did not dispute.
  • Monday, one email: two verification links. Two photos of the same boom, each anchored in a group with (for customer organisations) a qualified timestamp, their signature under the first.
  • Their insurer checks the bundles itself.

REPAIR INVOICED AND PAID

€18,400recovered
10 minat the counter instead of 4 hours
2records, each existing no later than its anchoring time

Departure and return are two records: free up to 100 a month, then €0.16 together. The dent cost €18,400.

HAVEN-2026-AFL-913 · DELIVERY · CMR

Container "late and damaged" — three years later

Karim Aydin — planner · planning & customer service · Demo Transport BV · Antwerp

Three years after delivery

The claim — and your own doubt

Container MSKU 452 118-0 was "late and damaged". You have doubts yourself: was that delivery in the TMS changed during a migration? The terminal's history says 09:41 (UTC+2), the TMS 09:38 (UTC+2), the recipient has an email from 10:15 (UTC+2). Three clocks.

The problem

Every party its own system, its own clock

Without reservation on delivery, the CMR (the international road transport convention) creates a presumption that the goods were delivered in good order (Art. 30) — but whoever relies on it must be able to prove the delivery and its time. Three years and one migration later, nobody can show any more what the original record was.

Without anchoring

  • Your legal counsel reconstructs from exports and emails. The counterparty disputes every export.
  • The insurer settles.
  • Eight such disputes a year; on average €7,500 in shared costs + 6 hours per case.
  • And every time: "whose history?"

COST: ≈ €60,000 + €3,600 HOURS / YEAR

With anchoring

  • Already three years ago: your TMS forwarded every delivery — hashed, signed, anchored at 09:46 (UTC+2), and as a customer organisation, the group usually also received a qualified timestamp within six hours.
  • The terminal's reception confirmed through the share link with its own key: "received 09:41 (UTC+2), without reservation" — itself anchored at 09:50 (UTC+2).
  • Check: ten seconds. All checks match — the content in the vault is, byte for byte, what was forwarded at the time.
  • You send the bundle and link to the counterparty's insurer; their IT runs the verification script: unchanged · 7 of 8 checks match · 1 not recomputed; they compare the Bitcoin block online themselves.

CLAIM REJECTED — IN ONE EMAIL

10 secto check
€7,500not shared
3 yearslater still identical byte for byte

This case was actually run as a demo on app.vidimus.be — see the bundles with the scenarios.

DATA-2026-GATE-2201 · GATE SCANS & SENSOR DATA · MANIPULATION

The record that disappeared overnight

Nadia El Amrani — IT manager · systems & data · Terminal Demo NV · Antwerp

Thursday 09:15 (UTC+2) — the situation

A gate-out that looks different

There is a dispute about a night delivery. While preparing the file, you notice something: the gate-out of 23:47 (UTC+2) suddenly shows a different container number than in last week's report — and a second scan from that same night has disappeared completely.

The problem

Whoever manages the database manages the truth

Gate scans and sensor measurements are digital records in an ordinary database. Someone with write access changes or deletes one with a single command — and the history that would show it is in the same database. By accident or on purpose: the trail erases itself.

Without anchoring

  • Internal investigation: weeks of comparing backups, without any certainty that the backup itself is right.
  • Nobody can show any more what the record originally was — or even that a second scan existed.
  • The dispute about the night delivery is settled: your strongest piece of evidence is now itself under suspicion.
  • And internally the question remains: who, and why?

COST: WEEKS OF INVESTIGATION + SHARED CLAIM + ZERO CERTAINTY

With anchoring

  • Every gate scan and sensor measurement was automatically hashed when it was created and anchored in a batch every five minutes — before anyone had an interest in it.
  • The "disappeared" record still exists: as an anchored fingerprint in the ledger and as an encrypted original in the vault.
  • The edited gate-out shows up at once: its current content does not match the anchored fingerprint, and the change has its own timestamp — after the facts.
  • The ledger, in which each entry hashes the previous one, shows the gap within ten seconds, and also when it appeared.

DELETING IS POSSIBLE IN YOUR SYSTEM — IN THE LEDGER IT STANDS OUT

2manipulated records — both visible
5 minbatch anchoring, fully automatic
10 secto make the gap visible

Even an administrator with all rights loses to the mathematics here.

Fictional people and organisations; amounts are realistic examples, not customer figures. The port case was run as a demo on app.vidimus.be — see the real bundle and verification links.

Do you recognise your claim? Work it out for your records.

One disputed load, one unpaid piece of extra work, one dent a year — that is usually already more than anchoring a whole year of records costs.