# Check a draft against approved document styles

Canonical page: https://agents.paretoid.com/workflows/check-a-draft-against-approved-document-styles/

Category: Operations & Reporting

Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use.

Jurisdiction/provider scope: 

List formatting differences while protecting the document’s wording and quotations.

Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.

Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.

## The problem

List formatting differences while protecting the document’s wording and quotations.

Why it matters: Inconsistent formatting creates rework and can hide changes in a legal document. Checking an approved style profile helps staff separate presentation fixes from wording that must remain untouched.

## Sources and evidence

- pain: [Pain evidence: Grammar police](https://www.reddit.com/r/paralegal/comments/1uk8u56/grammar_police/)
  Grammar police, 2026-07-01, older evidence. OP and comments describe attorney-specific spacing, punctuation and indentation expectations. Proofreading, 2024-04-10, independently describes mistakes after moving to unfamiliar precedents under speed pressure.

- pain: [Pain evidence: Proofreading](https://www.reddit.com/r/paralegal/comments/1c0edo0)
  Additional self-reported public account; no independent identity or outcome verification.

- method: [Method: Microsoft Word styles](https://support.microsoft.com/en-us/word/customize-or-create-new-styles)
  Microsoft Word styles supports consistent formatting and reusable template styles. This does not prove automatic legal proofreading.

Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested.

## Suggested approach

Start when: A draft reaches admin QA

1. check it against an attorney-approved formatting profile

2. Keep source references and report unknowns instead of filling gaps.

3. The responsible reviewer checks the report before any separately approved action.

## What you need

- 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.

- Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.

## How to use

Documentation-verified component path; proposed adaptation, not tested

- 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.

Access and setup:

- Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.

### 1. Inspect formatting in the actual Word file

Tool: Word desktop

Location: Home > Styles; Home > Paragraph dialog launcher > Indents and Spacing; Layout > Margins

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.

Next step: Create an approved metadata-only TXT containing observed properties and the profile; no confidential prose is needed.

Check before continuing: Style name alone does not prove effective formatting. Uninspected properties remain unknown; missing section/paragraph locators block that comparison.

Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested.

Step 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

### 2. Load only the approved AI input

Tool: Acrobat PDF Spaces

Location: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space

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.

Next step: Use the AI Assistant message field in this same space for the next prompt.

Check before continuing: 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.

Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested.

Step 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

### 3. Run the bounded prompt and inspect citations

Tool: Acrobat AI Assistant

Location: The PDF Space AI Assistant message field

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.

Prompt:

```text
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.

Next step: Save the checked draft as style-review.docx; carry source IDs, versions and reviewer corrections into the next review step.

Check before continuing: A paragraph spacing-after value of 12 pt against 6 pt must be flagged; a protected quote is not changed.

Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested.

Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

### 4. Apply only approved formatting repairs

Tool: Word desktop

Location: Working copy > Home > Styles; right-click selected style > Modify

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.

Next step: Use Review > Compare > Compare (legal blackline), select original DOCX and candidate, show results in a new document.

Check before continuing: Do not choose output into Original/Revised. Check that only approved formatting changed; inspect layout in Print Layout.

Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested.

Step 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

### 5. Create and review a separate legal blackline

Tool: Word desktop

Location: Review > Compare > Compare (legal blackline) > Original document / Revised document > More > Show changes in: New document

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.

Next step: Open this comparison document beside the candidate in Print Layout for the final reviewer; inspect every change and all affected rendered pages.

Check before continuing: 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.

Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested.

Step documentation: https://support.microsoft.com/en-gb/word/compare-document-differences-using-the-legal-blackline-option

### 6. Human review and final handoff

Tool: Responsible staff reviewer and lawyer/process owner

Location: Local reviewed report beside the frozen source set

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.

Next step: Approval is formatting review, not legal proofreading or filing acceptance.

Check before continuing: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.

Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested.

Step documentation: https://support.microsoft.com/en-gb/word/compare-document-differences-using-the-legal-blackline-option

## What you will get

Approved assistant workspace for the deviation list; Word desktop to apply approved styles in a separate copy. Output style-deviations.csv.

## Human review and limits

Reviewer accepts profile and repairs; never normalize punctuation where meaning could change. Test with deliberate inconsistent styles and one protected quotation.

The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.

What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.

## Original prepared-input schema

draft.docx; style-profile.csv columns style_id, element_type, property, expected_value, protected_scope; no client identifiers.

Synthetic example input:

```text
Profile: Body paragraph spacing after = 6 pt. Paragraph P12 = 12 pt → report P12 mismatch; leave a quotation marked protected unchanged.
```

Expected synthetic output:

```text
Profile: Body paragraph spacing after = 6 pt. Paragraph P12 = 12 pt → report P12 mismatch; leave a quotation marked protected unchanged.
```

Failure check: Reviewer accepts profile and repairs; never normalize punctuation where meaning could change. Test with deliberate inconsistent styles and one protected quotation.

## Starter files

Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation.

- [Download starter kit](https://agents.paretoid.com/assets/starter-kits/a02-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed.

- [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/a02/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits

- [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/a02/README.txt) — Required inputs, file use, review steps and limits

- [Style profile blank CSV](https://agents.paretoid.com/assets/starter-kits/a02/style-profile-template.csv) — Blank input headers for style-profile.csv

- [Style profile synthetic example](https://agents.paretoid.com/assets/starter-kits/a02/style-profile-example.csv) — Synthetic test records for style-profile.csv

- [Draft preparation](https://agents.paretoid.com/assets/starter-kits/a02/draft-preparation.txt) — Required policy or native-input preparation aid; synthetic when marked example

- [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a02/expected-results.txt) — Compare a pilot result with the planted exceptions

## Optional original prepared-input prompt

Destination: Your firm-approved AI assistant · prepared files

This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping.

```text
Compare this deidentified draft with the supplied approved style profile. List deviations with paragraph/page references. Propose formatting-only repairs in a separate copy. Leave quotations, legal wording, names, numbers and citations unchanged. If the profile conflicts with another supplied rule, flag it and stop on that issue. Do not infer attorney preferences.

INPUTS
draft.docx; style-profile.csv columns style_id, element_type, property, expected_value, protected_scope; no client identifiers.

OUTPUT
Approved assistant workspace for the deviation list; Word desktop to apply approved styles in a separate copy. Output style-deviations.csv.

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.
```

Proposed / not tested · editorial prompt

Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.
