A table of contents in Word can be a field, an instruction Word evaluates to produce a visible result. The same goes for figure captions, cross-references, and page counts. When a field displays "Figure 3," what you see is the displayed result, not the instruction that produced it. The instruction and the result are separate things, and the result may be cached from a previous update. This distinction matters when you need to verify that a long document's structure survived an edit, a tool, or a format conversion.
Not every table of contents is a field. You can type one by hand, and some documents have manually entered contents that look the same on screen but are plain text. Before you test anything, confirm that the element you are checking is actually a field.
The trap is straightforward. A field's displayed result looks like ordinary text. If a tool replaces the field with its displayed result, the page still reads "Figure 3" and the contents page still lists the right headings. Nothing looks broken. But the instruction is gone. Insert a new figure before the old one, press F9 to update, and nothing renumbers. The displayed numbers are frozen at whatever they were when the replacement happened.
You cannot catch this by scrolling. You catch it by toggling field codes and by running a change test.
In Windows Word, Alt+F9 switches between field codes and displayed results, as described on Microsoft's field help page. Press it once and your table of contents turns into something that starts with { TOC }. Press it again and the readable version returns. This toggle tells you whether a given span is a live instruction or plain text.
The change test goes further than looking. Make a disposable copy of your document. In that copy, change something that a live field should respond to. Add a new caption above one of your figures. Update fields. If the old figure number increments and later cross-references adjust, the fields you tested are working. If the numbers stay put, do not assume the fields are gone. The update may not have covered their scope, the update settings may need adjusting, or the target may need checking. Open the field code, verify the bookmark or target it points to, and confirm your update range included that field. Discard the test copy afterward.
Updating fields is its own step with platform-specific quirks. On Windows, Ctrl+A then F9 updates fields in the main story. But Microsoft's update-fields guidance notes that fields inside tables and text boxes may need to be selected separately. Headers, footers, and other text stories can also require their own update pass. A table of contents offers a choice: update only page numbers, or update the entire table. If you added a new heading, only the "entire table" option pulls it in.
One subtlety that trips people up: pressing F9 and seeing no visible change does not prove the field is broken. A field whose inputs have not changed will produce the same result after updating. No change can mean the field is intact and stable. The change test, not the absence of visible F9 activity, is what tells you whether the field is alive.
If a field refuses to update at all, the cause may be a missing target or a broken bookmark. A cross-reference points to a bookmark; if that bookmark was deleted, the field has nothing to resolve. This is why the change test matters more than a one-time visual check. It exercises the system rather than photographing it.
Before you accept any version of a long document, do this. Open it in Word. Toggle field codes and confirm the table of contents, figure captions, and cross-references are instructions, not plain text. Run one change test on a disposable copy. Update fields across all stories, not just the main body. A successful change test confirms that the fields you exercised are live. It does not prove the entire document is intact. Fields you did not test may still be plain text or broken.
Top comments (0)