Jetformat

Inspect a DOCX before selecting an automation step

A document may contain tables, headers, images, or content controls that influence the next operation. A structural inventory gives a script a better starting point than the filename.

Published · 2 min read

By allentatakai

Decide what success means

Use the structure to choose a task, then inspect that task’s output separately. Counts describe objects; they do not certify page fidelity or business correctness.

Prepare and run

Run inspection before mutating the document. Keep the JSON with the job record when it is useful for diagnosing a changed template.

These examples use local sample filenames. Substitute your own paths and check jetformat word inspect --help against the installed version before running the task. Put paths containing spaces inside quotes.

jetformat word inspect contract.docx --json

Inspect before choosing an edit strategy. Counts for paragraphs, tables, images, headers, and content controls help distinguish a text document from a template.

Inspect the saved result

Save the JSON when an agent needs a machine-readable preflight; counts describe structure, not visual fidelity.

Scope and repeatability

This is a free utility or read operation. It does not need a paid conversion to inspect the result.

Run jetformat word inspect --help to compare options with your installed version.

See the word command reference for the surrounding workflow.

Keep the input revision with the result so a later reviewer can reproduce the decision. For a write operation, choose a new output path first; use overwrite flags only when replacing a previously reviewed result is intentional.

See the word inspect options and examples for the command reference. Browse related word commands when the next step requires a different operation.

Last updated