Skip to content

Built for the work behind a SAR.

Redactics does the finding, extracting, classifying and organising. Your team makes the decisions. Sources, people, findings, decisions and the response all live in one connected case.

Try RedacticsTalk to us

Automate the bulk. Keep the judgement.

The repetitive work of finding, extracting, classifying and organising runs first. Reviewers see the relatively small number of items that need professional judgement.

  1. Source items

    8,868

    Emails, documents, spreadsheets and scans

  2. Relevant findings

    1,428

    Classified, scored and linked to people

  3. Need judgement

    48

    Queued for a reviewer with the source attached

  4. Decided by

    A person

    Every decision named, timed and reasoned

Automated, before anyone opens a file:

  • Text and scans extracted
  • Duplicates grouped
  • People resolved
  • Personal data classified
Sample case SAR-2026-0417. All data is synthetic.

From request to response.

Redactics runs collection, extraction and resolution. Your team leads the review and approves the response.

  1. 01

    Collect

    Bring together emails, documents, attachments, scans and source material.

    Redactics

  2. 02

    Extract

    Turn mixed formats and scanned content into structured information.

    Redactics

  3. 03

    Resolve

    Identify people, aliases and relationships across sources.

    Redactics

  4. 04

    Review

    Surface the items that need attention.

    Your team

  5. 05

    Disclose

    Prepare the reviewed response and preserve the audit trail.

    Your team approves

Read the SAR Method

Stay ahead of the clock.

Every case shows its due date, the days left, review progress, unresolved items, processing state and the actions still outstanding.

SAR-2026-0417/Overview

Statutory due date

2 Sep 2026

11 days left

Received 3 AugDay 19 of 30Due 2 Sep
Review progress
71%
Unresolved items
48
Processing
3 of 5
Outstanding actions
4

Outstanding actions

  • 1

    Confirm an ambiguous identity

    A. Whitlock

  • 47

    Decide flagged items

    A. Whitlock, R. Mensah

  • 7

    Second review of withheld items

    M. Doyle

  • 1

    Approve the response for release

    J. Adeyemi, case owner

The case clock for the sample case, day 19 of 30. All data is synthetic.

Catch what should not leave.

Potential third-party information, sensitive data and possible exemptions are flagged before release, each with a suggested action. A reviewer makes every call.

SAR-2026-0417/Pre-release checks

5 flags before release

A reviewer decides each one. Nothing is released until they have.

2 high risk2 check1 decision

  • Third party detectedHigh risk

    Priya Shah · Line manager

    Grievance meeting notes, page 1, paragraph 6

    Her own workload concerns, not the requester's data.

    Suggested action: Redact

  • Sensitive informationHigh risk

    Health data about Aisha Okafor

    RE: Welfare call, message 3

    Refers to a relative's hospital stay.

    Suggested action: Redact

  • Possible exemptionCheck

    Legal advice

    Advice re grievance, 4 Jun 2024

    From the Trust's solicitor about the grievance.

    Suggested action: Consider withholding

  • Low confidence matchCheck

    D Okafor Deliveries · 54% match

    Supplier payments FY21.xlsx, row 214

    Different address and phone number from the requester.

    Suggested action: Keep separate

  • Decision requiredDecision

    Mixed content

    Grievance outcome letter, page 2, paragraph 4

    The requester and a colleague in the same sentence.

    Suggested action: Redact part of the sentence

Release locked: 5 decisions outstanding

Pre-release checks in the sample case. Redactics suggests; the reviewer decides.

Find what matters.

Email, attachments, documents, spreadsheets and scans in one case, with aliases, identifiers and duplicate references resolved to the right person.

People/Daniel Okafor

Person record

Daniel Okafor

Data subject. Confidence 98%.

1,963 mentions across 611 sources, from 5 identifiers.

Identifiers linked

5

  • Daniel Okafor

    HR case file

  • d.okafor@northgate-ht.example

    Mailbox export

  • D. Okafor

    OH-assessment-DO-Mar24.pdf

  • Employee NG-40217

    Payroll adjustments Q3.xlsx

  • Dan

    Handwritten margin note

Kept separate D Okafor Deliveries, 54% match. Appears only in supplier invoices. Different address and phone number from the requester.

The requester, found under five identifiers. A similar name stays separate until a reviewer decides.

Keep judgement with people.

Redactics handles the workload. Your team makes the decision, and every approval is recorded with the person, the time and the reason.

  1. 1

    Confirms the scope of the request

    Case owner, approval point

  2. 2

    Collects, extracts, classifies and links people

    Redactics, automated

  3. 3

    Confirms uncertain identities

    Reviewer, approval point

  4. 4

    Decides third-party, sensitive and exempt items

    Reviewer, approval point

  5. 5

    Signs off anything withheld

    Second reviewer, approval point

  6. 6

    Approves the response for release

    Case owner, approval point

Every capability, one case.

Security and trust

Make SARs manageable.

Try Redactics yourself or talk to us about your current process.

Try RedacticsTalk to us