Implementation deadlineCore obligations enforceable — 13 May 2027

Time left—

Govern & prove · Live Testing

Test the systems, not the questionnaire

Some duties can be checked by doing them. Withdraw a consent and see whether the marketing stops. Ask for a deletion and look for copies. Live Testing runs these checks on your connected systems and records what it found.

What it does

Live Testing in practice

Connect, then test

Connect the vault or any system with a web API. Where there's no API, someone can confirm the result by hand. Each connection unlocks the tests it supports.

Shows how it knows

Every result says whether it came from the system, was confirmed by a person, or couldn't be checked. They are never merged into one green tick.

No free pass for our own vault

A setting in the vault is evidence. Only a test shows the duty is met, and that includes our own vault.

Also included

The details that matter

  • Every test is written out: what it needs, its steps and the expected result.
  • Sample results are always labelled as samples.
  • Clear counts of what hasn't been tested yet.

Questions

About Live Testing

All questions
Will tests change production data?

Each test says what it needs and what it touches before you run it. You choose which systems are connected and which tests run. Nothing runs on a system you haven't connected.

What if a system has no API?

Someone checks by hand and records who checked, what they saw and when. It counts, and it's labelled as a manual check.

See Live Testing on your own systems

A 45-minute working session. Bring a notice or consent form you use today and we will check it with you.