MOS Word Expert (MO-111) common mistakes
MOS Word Expert (MO-111) · Understand the traps and how to avoid them.
Changing Word's default settings only inside the current document (for example editing styles in one file) and expecting new documents to inherit them, when the task asks for a change that applies going forward.
Candidates conflate document-level formatting with application-level defaults; Word stores defaults in the template (Normal.dotm) and in Word Options, not in the open file, so edits made in a document do not persist to new documents.
What to do instead
Decide first whether the requirement is document-scoped or application-scoped. For application scope, edit the Normal template (open it via File > Open with the template filter, change styles, save) or use Word Options > Advanced/Save settings; for document scope, keep changes inside the file. Verify by creating a brand-new blank document and checking the setting.
Leaving compatibility mode on after opening a legacy .doc file, so newer layout, numbering, and formatting features are unavailable or behave differently during the task.
Word opens older-format files in Compatibility Mode by default and the title bar note is easy to miss; candidates then wonder why a feature is greyed out or why spacing changes.
What to do instead
Check the title bar for 'Compatibility Mode'. Convert with File > Info > Convert, or File > Options > Advanced > Compatibility options, then re-check the document's layout. Confirm the file is saved as .docx if the task requires modern features.
Building multi-level numbering by typing numbers and pressing Tab, or by applying list numbering to paragraphs without linking list levels to heading styles.
Manual numbering looks correct on screen but breaks on edits, and candidates do not realise that Define New Multilevel List has a 'Link level to style' control that ties each level to Heading 1, Heading 2, etc.
What to do instead
Use Home > Multilevel List > Define New Multilevel List, set each level's number format and indent, and link each level to the matching heading style. Test by inserting a new Heading 2 and confirming the numbering updates automatically.
Using section breaks only where a page break is needed, or inserting a page break when the task requires different headers, columns, or orientation for part of the document.
Page breaks and section breaks look similar in the document but only section breaks create independent page setup and header/footer scopes; candidates default to Ctrl+Enter.
What to do instead
For any change to headers/footers, orientation, margins, columns, or page numbering restart, insert Layout > Breaks > Next Page (section break). Use Ctrl+Enter only for a simple page break. Verify with the Show/Hide ¶ marks and by checking 'Link to Previous' is off in the new section's header.
Applying direct formatting (bold, font size, colour) on top of styles instead of modifying the style definition, so a later style change does not update the text.
Direct formatting is the fastest visible action and Word gives no warning that it overrides the style; candidates then fail tasks that require the change to flow through all instances of the style.
What to do instead
Select one instance, right-click the style in the Styles gallery, choose Modify, and change the format there (or use 'Update Style to Match Selection' after formatting). Clear stray direct formatting with Ctrl+Space and Ctrl+Q, then confirm every paragraph using that style changed.
Inserting a table of contents as typed text or a static list rather than a field based on heading styles, so it does not update when headings change.
Candidates build the TOC manually to control appearance, not realising References > Table of Contents generates a field that depends on heading styles or TC fields.
What to do instead
Apply Heading 1–3 styles (or mark entries with References > Add Text), then insert References > Table of Contents > Automatic Table. Update with F9 or 'Update Table' and choose 'Update entire table' to refresh page numbers and entries.
Creating a custom building block or Quick Part but saving it to the wrong gallery or template, so it is unavailable in other documents or does not appear where the task expects.
The Create New Building Block dialog defaults to the current template and a gallery the candidate does not check; building blocks saved to Normal.dotm are available globally while those saved to a document are not.
What to do instead
Select the content, choose Insert > Quick Parts > Save Selection to Quick Part Gallery, then set Name, Gallery (e.g., Quick Parts, AutoText, Table), and 'Save in' to Building Blocks.dotx or Normal.dotm for cross-document use. Confirm by opening a new document and inserting it from the gallery.
Inserting cross-references or captions as plain text, so figure and table numbers do not renumber when items are added or removed.
Typing 'Figure 1' is faster than using References > Insert Caption, and candidates do not know that captions are SEQ fields and cross-references are REF fields that update.
What to do instead
Use References > Insert Caption for each figure/table (choose the label and position), then References > Cross-reference to point to it. After edits, select all (Ctrl+A) and press F9, or update the cross-reference field directly, to refresh numbers.
Protecting or restricting a document without checking which editing exceptions were granted, so reviewers cannot edit the intended regions or can edit too much.
The Restrict Editing pane combines formatting restrictions, editing restrictions, and exceptions in one place; candidates set one control and assume the others follow.
What to do instead
Use Review > Restrict Editing: tick 'Allow only this type of editing', choose the type (e.g., No changes, Comments, Filling in forms), then select the regions to exempt and tick 'Everyone' or named users under Exceptions. Click 'Yes, Start Enforcing Protection', set a password if required, and test by trying to type in both an allowed and a blocked region.
Running a mail merge without checking the data source mapping and preview, producing blank fields, duplicate records, or merged documents with wrong recipient names.
Merge fields bind to column names in the data source; a renamed or missing column yields «Field» placeholders, and candidates skip Mailings > Preview Results and the Edit Recipient List filters.
What to do instead
In Mailings, use Select Recipients, then Match Fields to map data columns to Word fields, insert merge fields via Insert Merge Field (not typed chevrons), filter with Edit Recipient List, and step through Preview Results before Finish & Merge. If fields show as text, press Alt+F9 to check field codes and re-insert the correct field.