A useful Word template should remember the structure of your work without remembering the last person you worked for. Replacing the name on the first page is only the beginning: an old address might remain in a footer, a reviewer’s comment, or an embedded worksheet.
This walkthrough uses Word for Microsoft 365 on Windows, in the desktop app. You will prepare an ordinary, macro-free template, then check a fresh document made from it. The goal is a reusable starting point with deliberate placeholders and no discovered legacy personal details. It is not a guarantee of anonymity for everything you later create.
1. Separate reusable structure from yesterday’s job
Work in a private preparation folder. Keep the original unchanged and save a separately named working copy. Do not begin by putting an unfinished template in a shared team folder: someone could use it before the cleanup is complete.
In a hypothetical consultancy, a completed project brief contains a client contact, a delivery address, a reviewer’s mobile number and a budget worksheet. The reusable parts are the headings, table layout and prompts for scope and approval. The people, figures and attached working material belong to that project.
Write a short replacement map before editing:
- Named client and contact details become
[CLIENT ORGANISATION]and[CONTACT NAME]. - Specific deadlines and prices become
[AGREED DELIVERY DATE]and[APPROVED FEE]. - Personal signatures and project screenshots are removed; any necessary example is rebuilt with invented material.
- Organisation branding stays only if you are authorised to distribute it.
If the source has many attachments, complicated automation or uncertain provenance, build a new blank document and recreate only the necessary structure. Spending time reconstructing a simple table can be more dependable than trying to explain every inherited object.

2. Finish the old review before replacing its content
In Review, choose All Markup; under Show Markup, include insertions, deletions and all reviewers. Inspect each pending change and use Accept or Reject according to the wording you intend to retain. Then turn off Track Changes before replacing project details. Hiding markup or stopping tracking alone leaves existing revisions in the file, as Microsoft’s tracking documentation explains.
For the hypothetical brief, rejecting a deletion might restore the former client’s address. That is why you settle revisions first and replace details second. Do not blindly accept everything just to make the page look clean.
Read comments for instructions you still need, transferring only generic guidance into the template’s ordinary text. Later, remove the old comments during inspection. A resolved discussion is not useful template content merely because it no longer demands attention.
Checkpoint: the working copy should now express one intended version. If you cannot decide which revision is authoritative, stop using that source as a foundation and obtain an approved baseline or rebuild the structure.
3. Make every blank an instruction
Replace project values throughout the document, including tables, captions, text boxes, headers and footers. Examine first-page and other section variants where present. Check hyperlink destinations as well as their displayed wording: “Contact us” is an inadequate replacement if its destination still identifies a former contact.
Search for distinctive fragments from the old project: a surname, email domain, street name and project code. Treat each match as a decision, not an invitation to use Replace All. Then visually review the pages; a search result list is not a complete inspection of pictures and objects.
Prefer prompts that tell the next author what to supply. [DATE] is ambiguous; [APPROVAL DATE — day month year] is actionable. An apparently realistic sample fee can survive unnoticed into a proposal, so use a conspicuous prompt rather than a plausible amount.
For structured entry, Microsoft documents plain-text and date controls in its template guide. Enable Developer through File > Options > Customize Ribbon. Insert a Plain Text Content Control where needed. To customise its prompt, turn on Developer > Design Mode, edit the placeholder, then turn Design Mode off. Ordinary bracketed prompts are sufficient for a small template.
Checkpoint: every variable item should announce itself as unfinished. Ask whether a colleague could mistake any remaining example for an approved fact. If so, replace it with an explicit instruction.
4. Inspect selectively, then check the damage
Save a checkpoint before cleanup. Microsoft warns that Document Inspector removals may not be reversible. Its categories include properties and personal information, comments and revisions, hidden text, custom XML, and headers and footers. Hidden-text detection does not catch white text on white backgrounds, and invisible-content detection does not catch objects covered by other objects.
- Open File > Info > Check for Issues > Inspect Document.
- Select the available categories relevant to this file and choose Inspect.
- Review each result. Use Remove All for unwanted categories, including legacy personal properties and review material.
- Read the result of each removal before continuing. Microsoft’s Inspector reference says a module error leaves that module’s data unchanged.
Do not remove a category solely because it was detected. A neutral page-number footer may be necessary. Edit a contaminated footer manually; removing the whole category could destroy useful layout. Likewise, properties cleanup can convert data-bound fields to their last text value. For a simple template, replace such dependencies with ordinary prompts before cleanup, then verify that they still behave as intended.
Remove unnecessary embedded documents rather than trusting their preview. If a worksheet must accompany the template, prepare a separate clean example from invented data and review that file independently. A visible total does not tell you what else its workbook contains.
Checkpoint: save, reopen and inspect again. No unwanted personal-property or review-history finding should remain. Record why any retained category is acceptable. A clean result in selected categories is evidence about those checks, not certification of the entire file.
5. Save the master, then test its offspring
Follow Microsoft’s Windows template procedure: choose File > Save As, open This PC, give the file a neutral name such as Project-brief-master.dotx, and select Word Template in Save as type. Save in the Custom Office Templates folder offered by Word. Choose the file type through Word rather than changing a filename extension.
Close the master. Use File > New > Personal and select your template; Microsoft notes that the tab may be called Custom. Save the resulting document separately as Template-check.docx.
In this disposable document, fill the prompts with explicitly invented details. Add enough text to extend a table and create another page. Check whether the instructions remain understandable, page numbering survives and any old project details reappear. Run Document Inspector on this saved document too.
Reopen the master through File > Open to inspect the template itself. Its prompts should remain unfilled. If the invented test values appear there, you edited the master: restore the clean checkpoint, save the template again, and repeat the new-document test.
6. Release only the checked master
If cleanup breaks a field or removes necessary content, return to the checkpoint and rebuild that feature using neutral material. Do not paste the entire original section back into the cleaned file. That can restore the very history or objects you removed.
For signed, protected or rights-managed inputs, Microsoft says automatic hidden-information removal is unsupported. Obtain an authorised editable source and perform inspection before signing or applying those protections.
Keep preparation files private and distribute only the checked master, with a short instruction to create a new document and replace every prompt. Recheck whenever the template changes. Future authors can introduce their own names, comments and client details, so each completed document needs its own review before external sharing.
Sources, versions & scope
The steps describe the documented controls and expected checks; they are not a claim that every device or software release has been physically tested. Platform and version differences are stated with the procedure.
Knowligent Editors
First published · Updated
Documentation-led digital-life guidance, with AI-assisted research and drafting. Examples are identified, source links are provided, and device-testing limits are stated.
Editorial standards

