Key takeaway
A rectangle can conceal a word while leaving the word in the file. Verify the exact saved derivative across the surfaces included in the release.
The page view is one representation
A document reviewer sees a black rectangle over a restricted passage and approves a screenshot. The receiving application later extracts the underlying text. Both observations can be accurate: the picture looked covered, while the PDF still contained the information. The release decision must concern the saved file, not only its appearance in one viewer.
Adobe separates redaction of visible text and images from sanitization of hidden information. Its workflow distinguishes marking an area, applying the operation and saving the result. A drawing annotation that happens to cover text should not inherit those properties merely because it looks similar.
Complete a fictional release review
This hypothetical review uses the marker SYNTHETIC-CHECK-7 on an invented page. A rectangle covers the visible marker, but the scenario’s selection and extraction checks still return it. The same marker is also present in a comment and an embedded text file. No actual confidential PDF or redaction product is tested here.
The completed initial decision is hold. The owner must remove the intended content with an appropriate approved process, address the hidden copies within the declared scope, save a separate derivative and inspect that exact output. Deleting the marker from only the main text layer would leave two other known copies in this fixture.
The table is an evidence map, not a claim that five checks detect every possible sensitive object. Its unresolved row is important: a password-protected attachment that the reviewer could not inspect is not a clean finding. Exclude it under the approved plan or obtain authorized inspection rather than silently counting it as sanitized.
| Synthetic surface | Initial observation | Completed decision |
|---|---|---|
| Rendered page | Marker covered by rectangle | Appearance alone insufficient |
| Selectable/extracted text | Marker remains | Hold; underlying content not removed |
| Comment | Marker remains | Remove or exclude under approved scope |
| Embedded text file | Marker remains | Inspect/remove the attachment copy |
| Uninspectable attachment | No usable inspection result | Coverage unresolved; no clean claim |
Apply, save, then inspect again
Adobe’s current redaction instructions call for applying the selected redactions and saving the output, with a choice to sanitize hidden information. Its sanitization instructions describe removing all or selected hidden information, then saving. Record the action actually taken; a panel showing items marked for a future operation does not identify the file a recipient would receive.
The PDF Association-hosted technical presentation recommends distinct verification steps: trying to select or copy content in redacted areas, checking annotations and using low-level inspection to confirm the underlying elements were removed. These are useful complementary views. None substitutes for deciding which information needed removal in the first place.
For the illustration, reopen the saved derivative as a new input. Review its rendered page and permitted text extraction, then inspect the listed annotations, metadata and embedded files. Identify the tool versions and supported object types. If a check cannot cover a surface included in the package, retain that limitation or narrow the package.
Preserve the difference between removal and coverage
A successful removal check asks whether a known marker survives. A discovery review asks whether the reviewer found everything that should be removed. Those are different questions. A fixture can demonstrate that an inspection path notices selected hidden content without proving that every sensitive item in a large archive was identified.
Keep a restricted source reference, approved removal scope, output identifier, inspection methods, known exclusions and release decision. Record the output hash after the saved derivative is final. The hash identifies which bytes were checked; it does not establish that the inspection was sufficient. Do not circulate the original restricted text in the public-facing release note.
Retain originals only under the company’s applicable records, investigation and preservation instructions. Redacting a distribution copy does not authorize destroying source evidence. Equally, a need to preserve an internal original does not authorize sending that original to a recipient who was approved only for a narrowed derivative.
Make the next handoff smaller
The fictional package is ready for a new release decision only after the owner can identify the saved derivative, show how every known marker surface was treated and state what inspection did not cover. If the attachment remains unresolved, the next request is an attachment decision, not a general statement that the document is safe.
The readiness planner can assign the exact-output checks and their responsible reviewer. An inventory can describe a PDF category without uploading the documents. Effective redaction is one technical preparation question; it does not establish anonymization, the rights to license the remaining content or permission for a named recipient to receive a sample.