Recorded on 19 November 2026 on the test build: the product's own code with a disposable test database. Test files and role names only; no real person or case appears.
See each workflow run, from the first click to the export
Each recording is one automated run of the workflow, filmed in real time from the first click to the export. Every action waits a quarter of a second and each key screen is held for two and a half seconds, so you can read it. Nothing is cut or sped up. When a second person acts, the recording shows their browser and then returns to the first at the same moment. A download does not appear on screen: where a line says something is exported, the test presses the export button and checks that the file arrived.
This is not the live site. No email was sent, no identity was checked and no legal question was decided. Under each recording is what it shows and what it does not.
1. Process files
Length 0:35
What the recording shows
- A spreadsheet prepared for an FOI release goes in. It has a hidden worksheet, two hidden columns and a hidden row.
- The reviewer keeps the Company field, with the reason "Not personal data", and removes the author fields.
- The result lists what was removed, what was kept and why, and the hidden columns and row still in the file, by sheet and position. The evidence PDF is exported.
- A Word reply to an access request goes in. Its comment and the comment's author are removed and its evidence PDF is exported.
- Each file's SHA-256 digest before and after processing is shown on screen.
What it does not show
- The hidden worksheet is removed without a decision. The hidden columns and row stay in the file for the reviewer to deal with.
- Word and Excel files have the decision step. PowerPoint, PDF, images and batches of files are processed without it.
- The test also checks that no file content was sent to the server. A recording cannot show that.
2. Subject requests
Length 0:59
What the recording shows
- An access request received on 31 October is logged. The deadline is recorded as 30 November, one calendar month later.
- Identity evidence is recorded as a reference and a fingerprint, not the document itself.
- The Word reply is processed from the request, and the file review is linked to it.
- The request moves through review and approval to completion with a delivery receipt reference, and is closed. The register is exported.
What it does not show
- One person takes the request through review and approval. The product does not ask for a second person on a subject request.
- No extension or refusal is shown, and nothing is sent to the requester.
- The identity evidence and the delivery receipt are test references, not a real check or a real delivery.
3. Impact assessments
Length 1:23
What the recording shows
- Before anyone can give DPO advice, a second member with the DPO role, Reviewer B, prepares the DPO record and the owner approves it.
- An assessment is written in its four required sections (description, necessity, risks and measures), with one risk and one safeguard. The risk is recorded as Medium before the measures and Low after them, and the assessment is submitted for DPO review.
- Reviewer B records the DPO advice and approves the assessment. It then shows as approved, and its history lists the submission and the approval.
- The register and the evidence PDF are exported.
What it does not show
- An assessment needs a second member with the DPO role before it can be approved. A team of one cannot complete it.
- The test also asks the server to let the author approve their own assessment, and the server refuses. That call is made directly, so it is not on screen.
- A decision taken against the DPO's advice is not shown.
4. Processing records
Length 0:27
What the recording shows
- A controller record is entered with all nine field groups a controller's record of processing needs, including a transfer to the US under standard contractual clauses.
- The DPO contact is taken from the approved DPO record.
- The record is activated and the register is exported with each field as entered.
What it does not show
- The same person creates and activates the record. Activation is not a two-person step.
- In the export, the transfer details are one cell of raw data that a person has to read.
5. Breaches
Length 0:28
What the recording shows
- A tabletop exercise is logged with the time it happened and the time the controller became aware.
- The authority deadline is recorded exactly three days after awareness, and the page counts down to it.
- Notification to the authority is assessed as required and notification of the people affected as not required, each with its reason.
- The register is exported.
What it does not show
- Nothing is sent to an authority or to anyone affected. The product records the assessment and the decision; people send the notices.
- The history of a breach decision is not shown.
6. Tasks and approvals
Length 0:36
What the recording shows
- A task is created with a priority and a due date, started and completed.
- A request raised from incident response appears in Approvals as pending. The person who raised it is offered no decision, and neither is Reviewer B.
- The approvals register is exported.
What it does not show
- Tasks have no approval step and no export.
- The test also asks the server to let the person who raised the request approve it, and the server refuses. That call is not on screen.
- A ScrubMetadata platform administrator decides an incident response request, not the team.
- The two-person decision inside a team is the impact assessment, shown above.
Try the free check on one of your own filesOr practise on our files first