Word Document Inspector: check a sharing copy

Word Document Inspector can examine selected hidden-information categories before a copy is handed over. This exercise leaves you with a separately named document and a record of checked or unperformed steps.

Last updated: 18 October 2026.

What does a Word Document Inspector check decide?

Word Document Inspector helps examine hidden document information before you hand over a copy. A workshop outline can have perfectly ordinary visible text while retaining an internal comment or a document property. This exercise separates those hidden-information categories from the wording a recipient needs to read. It does not certify that a file contains no sensitive information.

The procedure is scoped to desktop Word on Windows. Microsoft's platform guide says Word for Mac has no document inspector; manually changing properties is not an equivalent inspection. The web version currently cannot display or change document properties. If your available edition cannot perform the task, prepare a precise request for a checked copy rather than documenting an imaginary success.

The outline and markers below are fictional training inputs, not Anar's experience or a client incident. No Word interface, cleanup, save or reopen test was performed while preparing this article. Their status is NOT RUN. Expected outcomes are instructions for a reader to test, not results obtained by the author.

If you need to locate wording differences between files, use the separate Word document comparison exercise. Here the job is narrower: inspect selected hidden-information categories in one native DOCX sharing copy while preserving its useful visible content.

Create a baseline you can actually recognize

On Windows, search Start for Word, open it and choose File > New > Blank document. Add the heading “Workshop handover practice” and the sentence “Public agenda: introductions, discussion and questions.” Keep that sentence unchanged throughout the exercise. It is your retained-content control: removing unwanted material is not useful if the remaining document no longer serves its purpose.

Select part of the sentence, create a new comment from Review, and enter COMMENT-572. Next open the document properties through File → Info and enter PROPERTY-816 in a Title field you can inspect. If you cannot locate or edit that property, leave the property exercise unperformed. Putting its marker in the document body would test a different thing.

A document property is information about a file rather than the wording on its page. Record the exact field you used. Find both markers again before cleanup. A missing marker after cleanup means little if you never established that it was present in the first place. This baseline makes your later observations interpretable.

1. Use File → Save As to save workshop-original.docx in Documents. Expected output: a named baseline.
2. Use Save As again to create workshop-sharing.docx. Expected output: a distinct working copy.
3. Check the name in the Word window before making changes. If either filename already exists, choose a new one rather than replacing earlier work.

For confusing file names, consult the Windows file extension check. Do not rely on the first item in a recent-files list to identify the copy you intend to clean.

Choose the categories before removing anything

In the sharing copy, follow File → Info → Check for Issues → Inspect Document. Select the categories you intend to inspect and choose Inspect. For this small exercise, concentrate on the comment-related category and document properties. Record the labels you actually see, since the note should describe your installation rather than an assumed screenshot.

Read the inspection results before choosing a removal action. Remove All belongs to the category beside it. It is not a meaningful instruction to erase every category in every business document. A comment-related category may include other review information, so the decision can affect material beyond the single marker you created.

Microsoft warns that Undo may not restore removed information. This is why the original stays separate. Do not extend the exercise by removing unfamiliar XML, header or footer categories merely because they are available. Decide what must remain useful before operating on a real document.

A category removal is not a content-approval decision. The document version approval reference exercise asks whether evidence names a particular state. Inspector does not authenticate an approver or decide whether you have permission to distribute the resulting file.

Inspect the saved copy, not your memory of the clicks

After removing the intended categories, choose Reinspect. Keep the first inspection, removal choice and later inspection as separate entries in your note. They answer different questions: what was reported, what you attempted to remove and what the subsequent check reported. Combining them into a single Passed label loses useful evidence.

With the sharing copy active, press Ctrl+S to save it, then close it. In File Explorer, open Documents and reopen workshop-sharing.docx by its exact name. Inspect the known comment location, the Title field and the visible agenda. Run Inspector again for the same selected categories. These are reader procedures, not a claim that this sequence was executed during article preparation.

Write expectations separately from observations. “COMMENT-572 should be absent” is an acceptance criterion. “I did not find it in the comments area” is an observation only after you actually inspect that area. An absent category finding should not become a broader assertion about every piece of personal information in the file.

Compare the retained agenda with the original. If useful wording or layout has been damaged, the sharing copy is not ready for its intended purpose. Start from another copy of the original and investigate the unnecessary removal choice. Do not keep yesterday's successful-looking note beside a newly changed file.

No document needs to be sent to finish this practice. Later, the attachment and shared-link access check addresses recipient access. A file reopening on your computer is not evidence that the right person can open the right copy elsewhere.

Understand what a clean inspection does not establish

Microsoft documents Word categories including review information, document properties, headers and footers, text formatted with the Hidden font effect, custom XML and objects formatted invisible. These names describe particular mechanisms. They do not mean that every possible technique for concealing information will be detected or removed.

For example, white writing on a white background is not the Hidden font effect checked by the hidden-text inspector. An object covered by another object is not the same as an object formatted invisible. These documented gaps are enough to rule out a universal conclusion that an inspection with no findings proves the absence of sensitive material.

A customer reference typed visibly into an ordinary paragraph also requires a content decision. Do not expect this exercise to identify and redact every sensitive sentence. The PDF redaction guide concerns a different format and tool. Its hidden-content cleanup overlaps conceptually with this job, but its PDF removal steps are not DOCX Inspector commands.

Record unexamined areas plainly, such as other objects not reviewed. This practice does not clean copies already sent, inspect an entire archive or remove a cloud version history. It also does not establish malware safety, factual correctness or legal permission to disclose the remaining text.

On a real handover, the document owner may need additional review. A useful inspection record states its scope rather than presenting a limited tool result as a complete privacy assurance. Keep the tool's category result and the business decision about distribution separate.

Finish with a small, honest handover record

If suitable desktop access is already available, use a short practice session for one document and two invented markers. Fifteen minutes is a planning timebox, not a measured completion promise. If a feature is missing, your useful output can instead be a request identifying the copy, the categories to inspect and the checks needed on its return.

Original filename and location:
Sharing copy filename:
Comment marker and original location:
Property marker and original field:
Selected Inspector categories:
First inspection / removal / reinspection:
Observations after reopening the saved copy:
Retained agenda and layout:
NOT RUN steps and unexamined areas:
Next action and owner:

Open Notepad from Start on Windows and create a new document. Copy the template and enter your observations or NOT RUN entries. Choose File > Save As and save inspector-check.txt in Documents; add a date if that name exists. Close the note, reopen that exact txt from Documents in File Explorer and check the copy name, categories and observations. Leave unperformed steps marked NOT RUN. Do not prefill “clean” in the observation fields simply because the tutorial describes a desired outcome. Another reviewer should be able to identify which file, fields and categories were actually checked.

The practical result is a recognizable copy and a bounded record, not an impressive-looking settings window. If the record is incomplete, keep its next action explicit. That makes the work repeatable without inventing a customer outcome, time saving or guarantee that the file contains no hidden information.