Check authorization-packet completeness
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
- Responsible professional supplies the exact packet and a current approved list of applicable requirements, with evidence rules and approval references.
- 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
- The workflow checks documentary evidence presence only. A representation letter, filename, completed checkbox or visible signature cannot establish authority, validity or legal sufficiency.

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: Freeze the actual authorization packet
Tool: Acrobat desktop and approved requirements document
Open: Open each supplied PDF; page navigation and Select text
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Keep the packet unchanged. Assign file/version IDs, record the displayed PDF page count, and visually identify any printed page labels separately. Copy only approved necessary passages to labelled text blocks with file/page IDs; unreadable pages remain unreadable. Obtain the lawyer-approved requirement list rather than asking AI to decide which authorizations are needed. Record an explicit coverage manifest listing every packet file/version/page and whether each page was inspected or excerpted.

Expected output: Minimized packet excerpts and requirement_id/applicability/evidence_rule/approval_ref list.
Use it next: Review the excerpts against the originals; load the approved excerpt set and requirement list together.
Check: Do not upload health details or signatures unless independently authorized and necessary. No source packet or requirement list means blocked.
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/get-started/learn-the-basics/navigation.html

STEP 2: 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 the minimized packet excerpts, lawyer-approved requirements and explicit full-packet/excerpt coverage manifest.  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 3: 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
Use only the supplied packet excerpts and approved requirements. For each requirement return requirement_id, present|missing|uncertain|not_required, file_id, source_version, PDF page, printed page label if supplied, exact quote and reason. Missing evidence locations must be null. Report missing only within a human-confirmed complete inspected packet scope. If the sources are excerpts or page coverage is incomplete, absence means uncertain and HOLD pending full-packet review; never claim the full packet lacks an item. A filename or representation letter does not establish authorization. If a required item is missing or uncertain return HOLD; otherwise REVIEW_ONLY. Do not certify authority, identity, signatures, scope, validity or compliance; alter files; mark approval; or send a request.

Expected output: Requirement-by-requirement evidence matrix, HOLD or REVIEW_ONLY, with null locators for missing items.
Use it next: Save the checked draft as authorization-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Manually check all claimed presence and every required item against the full packet; cropped excerpts cannot prove absence from the full packet.
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 4: 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.

Responsible professional checks the complete original packet, authority, identity, scope and signatures using their normal legal review. Record item dispositions and reviewer/date in the local matrix.

Expected output: Human-reviewed completeness matrix; absent/unreadable evidence remains on hold.
Use it next: Any records request or disclosure requires a separate human-approved final action.
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://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

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.
