Flags for other people.
Flag every finding about someone other than the requester, grouped by person and role, so a reviewer can confirm each redaction.
The problem.
Most document sets contain other people. Checking what has been redacted about them is the review that takes longest, and when it is done by hand it happens page by page with no consistent record of why a mark was made or removed.
What Redactics does.
Every finding about a person other than the requester is marked as third-party, redacted automatically, grouped by that person and their role, and shown with surrounding context. Mixed sentences, where the requester's information and a third party's are intertwined, are highlighted at sentence level. Reviewers confirm or adjust each redaction and record a reason, using reason templates your organisation controls.
- Third-party findings grouped by person and role
- Mixed content highlighted at sentence level
- Reason templates written and maintained by your organisation
- Decision, reason, reviewer and time recorded per finding
Grievance meeting notes
During the meeting PS described her own concerns about workload and said she had raised them with her manager in February, before returning to the substance of the grievance.
Your decision
- For your teamA queue, not a re-read
- Third-party review becomes a list of redactions to confirm, each with context, instead of a second pass through the whole set.
- For your recordsEvery adjustment has a recorded reason
- If a redaction is questioned later, the reason, the reviewer and the context are already recorded.
- For your security reviewYour policy, applied consistently
- Reason templates and redaction defaults are configured per organisation, so adjustments follow your policy rather than individual habit.
Redact your first document set.
Try Redactics on a synthetic sample set, or talk to us about your documents.