Every redaction has a source.
Every redaction points to its source file, page, paragraph and span. Every change keeps who made it, when and why.
The problem.
When a redacted document is questioned, the questions are simple: where did this come from, and why was it redacted or left in? A manual process cannot answer them without repeating the work, and often cannot answer them at all.
What Redactics does.
Redactics records provenance for everything it produces. A finding keeps a link to its source: file, message, attachment, page, paragraph and character span, with the original retained beside the extracted text. A reviewer's change keeps the reviewer, the time and the reason. Nothing is derived without a pointer back to where it came from.
- Source file, message, attachment, page, paragraph and span for every finding
- Original retained alongside extracted and transcribed text
- Reviewer, timestamp and reason on every change
- Evidence export for a set, finding or person
Finding F-0912
DisclosedWhat was found
Where it came from
What was decided
OH-assessment-DO-Mar24.pdf, page 2
OCCUPATIONAL HEALTH ASSESSMENT, CONFIDENTIAL
¶3Following the period of absence, the assessment recommends a phased return over four weeks with adjusted duties and a review with his line manager at the end of the period.
Audit trail
- For your team"Where did this come from?" in seconds
- Open any redaction and see the source. Open any change and see the reason. No searching, no reconstruction.
- For your recordsA record you can stand behind
- You can show the chain from source to finding to redaction to output for every page in the export.
- For your security reviewAppend-only evidence
- Evidence records cannot be edited or deleted for the life of the set. Corrections are recorded as new events.
Redact your first document set.
Try Redactics on a synthetic sample set, or talk to us about your documents.