Distinguish the controls

Redaction removes selected content from an output copy. Information classification governs handling. Retention and legal holds govern how long records may be kept and whether disposition is permitted. None replaces the others.

A redaction proposal or no-match result is not proof that a document contains no sensitive information. Detection coverage must be tested and accepted for the intended document population.

Run a bulk redaction project

  1. Open Processing → Bulk redaction where enabled. Define the policy and select current cleared source versions.
  2. Test representative samples using supported patterns, exact phrases or published-schema AI fields. Inspect detections and page geometry.
  3. Accept the tested policy through the permitted approval path and run the batch.
  4. Independently inspect generated outputs, adjust supported masks where required and resolve exceptions.
  5. Approve eligible outputs separately before releasing redacted copies. Ensure a redaction-only package excludes originals.

Check the actual output

Supported rendered PDF/image outputs physically remove the specified regions and retain output verification evidence. The source version, OCR and mask geometry must match. Do not rely on a visual overlay alone as proof of secure removal.

Availability of renderers, formats and detectors depends on deployment. Originals are retained under their own access/retention controls and may contain the unredacted information.

Handle retention and holds

Review source and output periods independently in the library controls. Holds, organisation minimums and shared dependencies can block disposition. A retention preview identifies candidates for the disposition workflow; it is not confirmation of physical deletion or removal from external destinations.

Test the produced copy

Include repeated values, scanned text and difficult layouts in a representative redaction test. Verify the actual generated copy and retained removal evidence, not only a mask preview. The original remains sensitive. For legal holds, check source/output scope and saved hold state; an elapsed retention period is not authority to delete held material.