Check PDF-to-Word conversions 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 - Existing Word desktop and Acrobat Pro Compare files access; the actual source PDF, converted DOCX and an explicit approved intended-change list. - 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 - Acrobat Compare accepts PDFs, not a direct source-PDF versus DOCX pair. Word legal blackline requires two Word versions; do not invent an authoritative source DOCX by re-converting the same PDF. - Native comparison and visual page review do the QA; AI only explains a supplied reviewed difference record and cannot certify conversion fidelity. 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 conversion pair Tool: Word desktop Open: Open the converted DOCX > File > Save As > choose PDF Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Preserve source.pdf and converted.docx unchanged. Save a separate converted-render.pdf from the exact candidate DOCX and record filenames/versions. Obtain the intended-change list from its owner; no intended changes means an explicitly empty approved list, not guessed consent. Expected output: Source PDF, exact candidate DOCX and candidate-render PDF plus intended-change list. Use it next: Open source.pdf and converted-render.pdf together in Acrobat Pro. Check: Both must be the same claimed conversion version; a later DOCX edit invalidates the render/report. 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://support.microsoft.com/en-us/accessibility/word/use-a-screen-reader-to-save-a-document-in-word STEP 2: Run native comparison and page review Tool: Acrobat Pro Open: All tools > Compare files > select old/new PDF > Compare Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Set source.pdf as old and converted-render.pdf as new. Choose the document type/page scope intentionally; do not select text-only for the visual/layout pass. Inspect Compare Results with Go to First Change and subsequent changes, then manually view every source/candidate page for missing text, numbers, tables, headers, footers and line numbering. Record page pairs explicitly. Expected output: Native Compare Results document and manually checked findings with both locations when they exist. Use it next: Copy only sanitized findings/short excerpts into conversion-findings.txt; include the exact intended-change list and coverage statement. Check: A dropped clause has a source locator and may legitimately have null converted_locator. No detected difference is not a guarantee; unreviewed pages stay unreviewed. 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/compare-documents.html STEP 3: 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 conversion-findings.txt, sanitized intended changes and coverage notes. The native report or original PDFs may be added only if each is separately approved for cloud processing; they are not automatically visible. 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 4: 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 native comparison findings, visual-review observations and approved intended-change list. Return document_alias,source_version,candidate_version,source_locator or null,converted_locator or null,difference_type,exact observed evidence,intended_change_id or null,review_action. Separate explained changes from unexplained text/number/layout differences. Retain all findings and page-coverage gaps. If text is absent in the candidate, keep its candidate locator null; do not fabricate one. Do not repair legal wording, infer missing clauses, claim to inspect Word formatting from text or declare filing readiness. Expected output: Explained/unexplained conversion-QA queue with preserved native evidence and coverage gaps. Use it next: Save the checked draft as conversion-QA-review.docx; carry source IDs, versions and reviewer corrections into the next review step. Check: Reconcile AI rows to every native/manual finding, particularly omissions and changed numbers. 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 5: 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. Staff checks all pages and each unexplained difference; lawyer approves substantive changes. Any repair is made in a separate DOCX copy, rendered again and rechecked. Expected output: Reviewed conversion report and version-specific disposition. Use it next: Release only the human-approved version; keep source and comparison artifacts unchanged. 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/using/compare-documents.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.