For clients · Before you upload

How to Send Me Your Evidence

I test whether your system ran. I don't need your secrets to do that, and I don't want them. A reviewer who never holds your personal data can never leak it, lose it, or be asked to hand it over. Here's exactly what to send, what to strip out, and how.

The short version

Send me

  • Exactly what's on your evidence list, nothing more
  • Dated records: minutes, approvals, sign-offs, tickets
  • The risk register and Statement of Applicability
  • Internal audit and corrective-action records
  • Log or report extracts that prove a control ran

Don't send me

  • Personal data. Names become roles.
  • Passwords, keys, tokens or credentials of any kind
  • Network diagrams, architecture drawings, system configurations
  • Customer data or contract values
  • Anything you'd regret leaving the building
The sanitising rules

Strip It Clean. Here's Exactly How.

Sanitise everything to a standard your own DPO would sign off before it leaves your network.

  • Replace every person's name with a role or a consistent token. "J. Patel, Head of IT" becomes "IT Lead", and a named user becomes "User-07". Use the same token for the same person across every file, because I'm testing whether your evidence chain holds together, and that only works if User-07 in the access review is the same User-07 in the leaver log.
  • Remove email addresses, phone numbers, employee IDs and signatures. A control is proven by what was done and when, not by who signed it, so none of this costs you anything in the diagnosis.
  • Mask internal hostnames, IP addresses, network ranges and cloud tenant or account IDs. Swap them for labels like "SRV-A" or "TENANT-1", because a map of your infrastructure shouldn't sit in anyone's inbox, including mine.
  • Cut every password, API key, token and connection string out of screenshots and config exports. Check the edges of screenshots too: browser tabs, logged-in usernames and notification pop-ups give away more than the thing you meant to capture.
  • Strip document metadata before you export. Author fields, tracked changes, hidden comments and revision history carry names and internal discussions you never meant to share, so save clean copies or export to PDF with metadata removed.
  • Remove customer names, contract values and anything commercially sensitive. Your supplier register only needs to show that suppliers are assessed, not who they are or what you pay them.
  • Leave HR records out entirely. Where a control touches people (screening, training, disciplinary), send the record that the process ran, with the person reduced to a token.
  • Rename files that carry names. "Sarah_Jones_Access_Request.pdf" undoes the redaction inside it.
  • Send only what your evidence checklist asks for. Anything beyond it is data I didn't ask for and don't want.

Keep these exactly as they are

  • Dates and timestamps. They're the evidence. Never redact a date.
  • Reference numbers: risk IDs, ticket numbers, clause and control references.
  • Approvals as facts. Replace the name with the role, but keep "approved by Head of IT, 14 Feb".

How to redact properly

Instead ofWrite
Sarah JonesHead of IT
[email protected][Head of IT email]
Two people with the same roleIT Engineer A, IT Engineer B (the same letter every time)
Customer: Acme Retail plcCustomer 1
  • Spreadsheets: find and replace each name with its role across the whole workbook, including hidden sheets and comments.
  • Word documents: find and replace, then accept all tracked changes and delete comments before you save.
  • PDFs: use a real redaction tool (Acrobat's Redact, or similar). A black box drawn over text leaves the text underneath, copyable.
  • Screenshots: crop to what proves the point. Blur or block usernames, emails and avatars.
  • File properties: remove the author and "last modified by" fields. Most office apps have an "inspect document" option that does it.

Sanitised evidence is enough, for the same reason your auditor works the way he does: he tests whether a control operates and whether the record proves it, not whose name is on it. If evidence fails once the names are gone, it was going to fail with them in.

The rules I work to

How Your Evidence Is Handled

  1. The NDA is in force before a single file moves. I'll sign any reasonable NDA of your own as well.
  2. Your evidence list is written for your company only and sent after payment.
  3. Upload through your private link only. It's password-protected, upload-only and expires. No email attachments, no shared drives.
  4. Stored on an access-controlled server in the EU. Only I can open it.
  5. Used only to write your report. Never shared, never published, never shown as an example.
  6. If something sensitive slips through, I tell you and delete it. You're still covered by the NDA.
  7. Permanently deleted within 24 hours of your report, with no copies kept in backups or version history. Deletion is confirmed by email.
  8. I never contact your certification body.
The clock

When the Clock Starts

The clock starts when everything on your evidence list has arrived and I've confirmed it's complete: two weeks for the Full Diagnostic, 72 hours for the Probe, on time or your fee back. Send it in one go if you can. If an item genuinely doesn't exist, don't create it for me. Upload a one-line note saying so. A missing record is a result in itself, and an honest one is worth more than a hurried one.

If your team can't find something in ten minutes, that's not a delay. That's your first finding.

Questions about the list? Email [email protected] and you'll get a written answer.

Audit Premortem is a trading name of Affinity Cafe Ltd, company number 11661600, registered in England and Wales · 8 Mortimer Terrace, London NW5 1LH · Terms · Privacy