Apply an approved document style profile 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 - Word desktop with formatting controls; approved explicit style profile and working copy of the actual DOCX, including protected quotations/signature blocks. - 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 - PDF/text extraction does not reveal actual Word style inheritance, direct formatting, section margins or paragraph properties. No automatic complete style-metadata export is claimed. 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: Inspect formatting in the actual Word file Tool: Word desktop Open: Home > Styles; Home > Paragraph dialog launcher > Indents and Spacing; Layout > Margins Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. In a separately named working copy select each in-scope paragraph; record the highlighted style, visible font settings and actual Paragraph dialog values. Inspect each section’s margins in Layout > Margins/Custom Margins rather than assuming one document-wide value. Record paragraph/section locator, property, observed value/unit, approved expected value, protection status and reviewer. Cancel inspection dialogs without changing values. Expected output: Manually observed style-properties ledger; actual style profile and protected-scope list. Use it next: Create an approved metadata-only TXT containing observed properties and the profile; no confidential prose is needed. Check: Style name alone does not prove effective formatting. Uninspected properties remain unknown; missing section/paragraph locators block that comparison. 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/word/customize-or-create-new-styles https://support.microsoft.com/en-us/word/adjust-indents-and-spacing-in-word https://support.microsoft.com/en-us/word/training/change-margins 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 observed formatting ledger, approved style profile and protected-scope list. 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 Compare only the supplied actually observed Word formatting properties against the approved style profile. Return paragraph_or_section_id,property,observed_value,expected_value,source_ref,protected_scope,deviation,proposed_format_only_action. Do not claim to inspect the DOCX or infer missing formatting from prose. Flag conflicting rules and unknown units/properties. Do not change protected quotations, wording, punctuation, names, numbers, citations or signatures. Return proposed repairs for review; do not edit files. Expected output: Property-level formatting deviation list with unknown/conflicting rules visible. Use it next: Save the checked draft as style-review.docx; carry source IDs, versions and reviewer corrections into the next review step. Check: A paragraph spacing-after value of 12 pt against 6 pt must be flagged; a protected quote is not changed. 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: Apply only approved formatting repairs Tool: Word desktop Open: Working copy > Home > Styles; right-click selected style > Modify Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Reviewer approves deviations first. Apply the correct existing approved style to the intended paragraphs, or modify the relevant style for this document only. Inspect all affected paragraphs because one style change can affect many locations. Apply section margins separately only when expressly approved. Expected output: Separate formatted candidate DOCX and list of applied property changes. Use it next: Use Review > Compare > Compare (legal blackline), select original DOCX and candidate, show results in a new document. Check: Do not choose output into Original/Revised. Check that only approved formatting changed; inspect layout in Print Layout. 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/word/customize-or-create-new-styles https://support.microsoft.com/en-gb/word/compare-document-differences-using-the-legal-blackline-option STEP 5: Create and review a separate legal blackline Tool: Word desktop Open: Review > Compare > Compare (legal blackline) > Original document / Revised document > More > Show changes in: New document Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Select the unchanged original DOCX as Original document and the separate formatted candidate as Revised document. Expand comparison settings and include text and formatting; include comments and other affected elements as appropriate to the approved scope. Show results in New document, never Original or Revised. Read any tracked-change warning carefully; preserve both inputs and do not accept or reject their tracked changes. Compare and save the resulting new comparison document separately. Expected output: New version-specific comparison DOCX, with preserved original and formatted candidate. Use it next: Open this comparison document beside the candidate in Print Layout for the final reviewer; inspect every change and all affected rendered pages. Check: Check that no wording, numbers, quotations, citations or protected material changed. A blackline does not replace visual review of margins, pagination, tables and other affected layout. 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-gb/word/compare-document-differences-using-the-legal-blackline-option STEP 6: 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. Reviewer checks the blackline and all affected rendered pages. Reject substantive differences; record approved profile/version and final document version. Expected output: Reviewed formatting-only candidate and deviation/disposition log. Use it next: Approval is formatting review, not legal proofreading or filing acceptance. 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://support.microsoft.com/en-gb/word/compare-document-differences-using-the-legal-blackline-option 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.