Redact
Release records sooner, with the legal reason recorded.
Redact reads every document in a records request and flags the pages and people that need a decision, each under a named provision. Your officers decide every redaction, and each one keeps its legal ground through to the release.
For FOI, public records and other release work. Configured to each jurisdiction’s law and each agency’s workflow.
How it works
It starts from the request
An officer opens a case and answers questions about the request: who applied, who the key people are, and whether proceedings are under way. The Smart Flags are told those facts when they read each page.
Redact reads PDF and Office files, emails and mailboxes, and zip and other archives. Scanned pages are read with text recognition. It finds copies, repeated pages and blank pages first, and setting one aside takes a reason.
Smart Flags find what needs a decision
Each Smart Flag asks one question about one provision, of every page or every person in the request. Flags look for things such as a confidential source, legal privilege, material given in confidence, and personal information.
A page a flag raises arrives filed under that provision, marked Strong, Possible or Weak, with the likely paragraphs shown. The officer applies the redaction, rejects it for that ground, or dismisses it.
One person, decided once
Redact finds each person the documents name and matches them across every document. The officer confirms the matches, then decides what to release about each person once, by category.
The decision applies wherever that person appears.
Your officers decide every redaction
A suggestion never redacts anything by itself. Officers can mark any words or area by hand, and withhold a page or a whole document.
Every redaction needs a ground the workflow accepts. Where the ground needs a public interest test, Redact asks for the factors first.
Nothing goes out half done
Before a case can be sealed, Redact checks it against a list that cannot be skipped. Every document must be read, every suggestion answered, and every redaction given a reason the workflow accepts.
Sealing asks the officer to sign in again.
A release pack you can defend
Text under each redaction is removed from the file, not covered over, and checked before the pack is built.
The applicant gets the release copy, a labelled copy with the ground on each redaction, and the schedule of documents. The agency keeps a marked-up copy for review and a signed record of every decision.
Hosting and security
- Hosting
- Hosted by AccuFind in your country, or deployed into your own AWS account.
- Sign-in
- Officers sign in to work a case, and sign in again before a case is sealed.
- Protective marking
- Your agency’s protective marking shows at the top and bottom of every screen.
- Record
- Every decision is recorded with who made it and when, in a signed record that can be checked later.
How a pilot runs
- 01
Set up
We map your process and your law into the product. Your security review runs at the same time.
- 02
Pilot
Your staff use it on your own documents, alongside the current process.
- 03
Decide
You get measured results, such as time saved and issues found.
Try Redact on your own documents
A pilot runs on your own documents, alongside your current process.
Start a pilot