Something was redacted that should not have been

A redaction has been applied to something that should have been released. What you do depends on whether the document has gone out yet.

If it has not been released

Fix it before release.

1. Open the document from the request's Case/Media tab.
2. Open it in the redaction editor.
3. Remove the redaction that should not be there.
4. Finish the session. The output goes back through verification.

The change is recorded in the request's activity log with your name and the time.

If it has already been released

The released file cannot be repaired, because redaction removes the underlying content rather than covering it. There is nothing beneath the redaction to restore.

What you do instead is produce a corrected release:

1. Go back to the source document, which is untouched. Redaction produces a new file rather than altering your record.
2. Redact it correctly.
3. Approve it and send it to the requester as a new package, saying plainly that it replaces the earlier one.
4. Consider revoking the earlier package link, which stops further access to the over-redacted version.

Revoking does not retrieve anything already downloaded. It stops further access, and the revocation is recorded.

Record why

Whichever route you take, write an internal note explaining what was over-redacted and why the corrected version is right. An over-redaction that is quietly fixed looks worse in an audit than one that is fixed and explained.

Why over-redaction happens

Detection finds patterns rather than meaning. The commonest false positive is a public official's name in a message about their official duties: the pattern matches, the withholding does not apply.

The check is the review. Proposals are a starting point, and stepping through them properly is faster than producing a corrected release.