Check the final PDF for residual approved-redaction targets
Get the source data and prepare the review

Documentation-verified component path; proposed adaptation, not tested

WHAT WAS CHECKED
Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Menus/features are vendor-documented; prompts, field maps and human gates are editorial adaptations. No actual client work, account login, installation, connection, external write or site edit occurred.

BEFORE YOU START
- Qualified local PDF reviewer; lawyer-approved target token/region list; preserved original and an exact final redacted derivative; Acrobat Pro and existing approved PowerShell for the documented SHA-256 route.
- Existing firm-approved Acrobat Studio, AI Assistant add-on, or another plan including Acrobat AI; online services/cloud storage, language and region must be permitted. No purchase, login or connection is part of this verification. The manual route works without AI.
- Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized.

DATA ACQUISITION LIMITS
- AI does not inspect or certify redaction safety. It sees only minimized completed inspection records. Real target values and the final PDF stay local.
- A no-match text search, hidden-information panel or black rectangle cannot establish safe redaction; images, layers, attachments, metadata and annotations need explicit local review.
- No automatic native hidden-information CSV/report export is claimed. Findings are manually recorded; denied extraction or unsupported layers remain blocked.

WHEN THIS CAN RUN
Blocked until actual sources, permissions and required human approvals are supplied; no real inputs were available in this verification.

STEP 1: Identify the exact final derivative
Tool: Existing approved PowerShell
Open: Get-FileHash -LiteralPath 'C:\approved\final.pdf' -Algorithm SHA256
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Copy the returned SHA-256 into a local inspection log with file_id,version,page_count and reviewer. Keep the target-value mapping restricted; assign non-sensitive token IDs for later reporting. Do not overwrite or sanitize the evidentiary original.

Expected output: Final-file identity and a lawyer-approved target-ID/region inventory.
Use it next: Open this same final file locally in Acrobat Pro for every following inspection.
Check: If the file changes at any point, all affected inspections must be repeated against the new hash.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash?view=powershell-7.5

STEP 2: Perform text and image inspection locally
Tool: Acrobat Pro and qualified reviewer
Open: Select text/copy; Find; page navigation/rendered page view
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Search approved target values locally and attempt text selection/copy around each approved region, comparing visible and extracted text. Visually inspect every relevant page including image-only regions; check coverage outside target regions as required by the approved review protocol. Record positive matches by token ID, source page/region and layer; do not send actual target values to AI.

Expected output: Observed visible/hidden-text and image-review findings, including failed/partial inspections.
Use it next: Continue to hidden information, attachments and layers; a text-only result is incomplete.
Check: Text absence cannot prove image redaction; copies/search can miss encoding and OCR errors. Do not claim a whole-file pass from sampling.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/using/reusing-pdf-content.html
https://helpx.adobe.com/acrobat/desktop/protect-documents/redact-pdfs/redactable-data.html
https://helpx.adobe.com/acrobat/desktop/get-started/learn-the-basics/navigation.html

STEP 3: Inspect hidden information and attachments without removing it
Tool: Acrobat Pro
Open: All tools > Redact a PDF > Sanitize document > Selectively remove; Menu/File > Document properties > Description > Additional Metadata > Advanced; View > Show/Hide > Side panels > Attachments
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Use the Hidden Information panel to inspect findings only; do not click Remove, Remove all or Save. Review metadata and annotation/layer findings. Inspect the Attachments list and safely review each permitted attachment; blocked or unsupported attachments remain unchecked. Inspect applicable layers in the Layers panel and all visual variants required by the approved protocol; do not save visibility changes. Manually record categories, token-ID findings and unchecked scopes.

Expected output: Local hidden-information/metadata/annotation/layer/attachment inspection log.
Use it next: Recompute SHA-256 to confirm that these inspection records still refer to the exact unchanged final file.
Check: The panel is one aid, not an exhaustive certification. Do not bypass security warnings or open active/untrusted executable content.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/protect-documents/redact-pdfs/sanitize.html
https://helpx.adobe.com/acrobat/desktop/edit-documents/edit-pdf-properties/view-metadata.html
https://helpx.adobe.com/acrobat/desktop/edit-documents/use-links-and-attachments/open-attachment.html
https://helpx.adobe.com/acrobat/desktop/edit-documents/pdf-layers/manage-layers.html
https://helpx.adobe.com/acrobat/desktop/protect-documents/redact-pdfs/redactable-data.html

STEP 4: Prepare minimized inspection evidence
Tool: Local text editor
Open: Restricted inspection log > separate metadata-only AI input
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Copy only file_id,final_sha256,target IDs,region/page references,observed finding IDs/layers,coverage flags and reviewer IDs. Every inspection must carry the final hash; use true,false,unknown rather than treating a blank as checked. Keep target strings, original/final PDFs and alias keys outside the AI input.

Expected output: Final-files/targets/findings/inspections review input; optional CSV kit is a manual log, not an Acrobat export.
Use it next: Paste/upload this approved metadata-only input to PDF Spaces, never the raw redaction targets.
Check: Missing hash, target scope or qualified inspection evidence blocks review.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash?view=powershell-7.5
https://helpx.adobe.com/acrobat/desktop/protect-documents/redact-pdfs/sanitize.html

STEP 5: Load only the approved AI input
Tool: Acrobat PDF Spaces
Open: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Add only the minimized file-hash/target-ID/finding/coverage logs. Do not load the final PDF, original PDF, real redaction values or identifying token map. Use clear source/version labels and verify the Files panel. Do not add originals that have not separately been cleared for Adobe processing.

Expected output: Visible approved source set in the PDF Space; no account integration is implied.
Use it next: Use the AI Assistant message field in this same space for the next prompt.
Check: Confirm every named source is actually loaded and readable. PDF Spaces supports up to 100 files, 100 MB and 600 pages per file; unsupported/password-protected/handwritten material blocks affected extraction.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/supported-formats-limitations.html
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/pdf-spaces-faq.html

STEP 6: Run the bounded prompt and inspect citations
Tool: Acrobat AI Assistant
Open: The PDF Space AI Assistant message field
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Paste the prompt below. Open each source-number citation, check it, and use Copy to transfer the answer into a new local Word document or text file. Correct errors using the originals before reliance.

PASTE THIS PROMPT
You are reviewing inspection records, not inspecting a PDF. Use only supplied metadata. Require every finding and inspection to match the final file_id and SHA-256. Match findings to approved target IDs without reproducing sensitive values. Return file_id,sha256,target_id,page,layer,finding_id,exception,source_ref and a coverage checklist. Flag residual matches, stale hashes, missing inspections and any false/unknown text,hidden,metadata,annotation,layer,attachment or visual coverage. No matches with incomplete coverage is INCOMPLETE, never safe. Do not decide redaction scope, certify confidentiality, inspect hidden PDF content, alter a file or authorize release.

Expected output: Residual-target and stale/missing-inspection exception register only.
Use it next: Save the checked draft as redaction-inspection-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Verify all target/coverage rows and hash matches locally; a report with zero findings is not release approval.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

STEP 7: Human review and final handoff
Tool: Responsible staff reviewer and lawyer/process owner
Open: Local reviewed report beside the frozen source set
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Qualified reviewer and lawyer independently check the exact final derivative and approved scope. Keep all uncertainties on hold. Any later remediation creates a new derivative/hash and requires reinspection.

Expected output: Version-specific human inspection disposition.
Use it next: Only the authorized human may approve release; no confidentiality certification is produced.
Check: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash?view=powershell-7.5

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.