# Review, Protect, and Deliver Word Documents

Inspect revisions, compare Word documents, resolve approved changes, protect output, update fields, and prepare DOCX files for delivery.

Treat review and delivery as explicit stages after content generation or modification. Inspection should not accept revisions accidentally, and protection should not be used as a substitute for validation.

## Review changes

`Compare-OfficeDocument -ReferencePath .\Before.docx -DifferencePath .\After.docx` returns `AreEqual`, `Differences`, and the native Word comparison in `NativeReport`. Add `-OutputPath .\Redline.docx` to save the redline. `Get-OfficeWordReview` exposes comments and revisions. Use `Resolve-OfficeWordRevision` only after the acceptance rule is known; filter by author, revision type, or review decision instead of accepting everything by default.

## Finalize document state

Before delivery:

1. update fields and the table of contents;
2. inspect comments and unresolved revisions;
3. verify required controls, links, and document properties;
4. apply protection when recipients should not freely edit the result;
5. save to the delivery path and reopen it read-only.

`Protect-OfficeDocument` and `Unprotect-OfficeDocument` make the protection boundary explicit. `Update-OfficeWordField` and `Update-OfficeWordTableOfContents` handle calculated presentation state.

The [approval-checklist recipe](https://github.com/EvotecIT/OfficeIMO/blob/3b680b1b6fb15a268ff5525a4ca6cdd70b2f6613/PowerShell/PSWriteOffice/Examples/Word/Recipe-Word-ApprovalChecklist.ps1) demonstrates content controls and a watermark. Combine it with [read and inspect](/docs/pswriteoffice/word-read-inspect/) for delivery readback.

<!-- PowerForge markdown source sha256:CDD4A0BFF1A3CD02CF086ADAF4E495C3680622854277F0B71E84D4F2699463C7; title=True -->

<!-- PowerForge markdown artifact sha256:53284C1D404CCDEF531BF436CB1D216F1A53D25A764394A60218EE53A4E7C784 -->
