VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why English? | Reading Word Field Codes Before Proofreading References

WORD · FIELD CODES · CROSS-REFERENCES

Know whether you are reading an instruction to Word or the result shown to the reader

Use a document–field–target–display–update–proofread–export chain. Preserve the source document, identify which braces are genuine fields, switch deliberately between code and result, verify each reference target and label, update only within the intended review scope, then proofread and export the exact reader-facing result.

Open the full chapter index ↓

Why this English matters now

Reading Word field codes before proofreading references is practical English for students searching why Word shows braces such as REF, PAGE or DATE, why a cross-reference changed, or why a report displays code instead of a page number.

Microsoft explains that fields insert content that can update, including dates, page numbers, graphics and cross-references. Word can display either the field code or its result; Microsoft documents Alt+F9 for switching all fields and Shift+F9 for a selected field.

Strong readers separate the instruction stored in a field from the result currently displayed. English matters because code, result, update, unlink, reference, target and current describe different parts of the document relationship.

Checked against the linked first-party sources on 30 October 2026. Interfaces, managed-device rules and school procedures can change, so reopen the current source before a live assessment, disclosure or account decision.

The practical reading method

Use a document–field–target–display–update–proofread–export chain. Preserve the source document, identify which braces are genuine fields, switch deliberately between code and result, verify each reference target and label, update only within the intended review scope, then proofread and export the exact reader-facing result.

  1. A field code is an instruction Word interprets; the field result is the text or value the reader sees. Proofreading only one view can miss a broken relationship or an unintended instruction.
  2. Updating a field asks Word to recalculate or retrieve its result. It does not prove that the target heading, caption, date or source is academically correct.
  3. Cross-references depend on document targets and can move when content changes. A correct number before editing can become stale after sections, figures or pages are rearranged.
  4. Unlinking converts a dynamic field into ordinary text. That can stabilise a recipient copy while removing the future update relationship, so it should not be used as a casual repair.

Official factual floor

  • Microsoft says fields can insert content such as dates, page numbers, graphics and cross-references and can update when the document changes.
  • Microsoft says Alt+F9 switches between all field codes and their results, while Shift+F9 switches the selected field; F9 updates selected fields.
  • Microsoft says a cross-reference that appears like {REF _Ref…} is displaying field code rather than field result and can be toggled back to the reader-facing value.
Scope: This guide cannot repair a corrupted document, decide the correct citation style, verify a source, guarantee identical shortcuts on every device or authorise the removal of assessment evidence. Work on a copy and follow the school or publication brief.

Did You Know?

Two readers can look at the same Word file and report different visible text if one view shows field codes and another shows results. The document has not necessarily changed; the display layer has. Good proofreading records which view was checked.

Full chapter index

  1. 1. Recognise a real Word field before changing it
  2. 2. Separate field code from field result
  3. 3. Read common field names without guessing
  4. 4. Use Alt+F9 and Shift+F9 at the right scope
  5. 5. Update selected fields deliberately
  6. 6. Verify the target behind a cross-reference
  7. 7. Proofread page numbers after layout changes
  8. 8. Treat dates as evidence with a time meaning
  9. 9. Understand switches and formatting instructions
  10. 10. Distinguish unlinking from updating
  11. 11. Check references for meaning, not only mechanics
  12. 12. Collaborate without creating competing field states
  13. 13. Export and inspect the reader-facing PDF
CHAPTER 1 OF 13

1. Recognise a real Word field before changing it

Back to contents

The mechanism

Word fields are structured instructions, usually shown with braces when codes are visible. Typed braces are not automatically fields.

A field code is an instruction Word interprets; the field result is the text or value the reader sees. Proofreading only one view can miss a broken relationship or an unintended instruction. In this chapter, the decisive phrase is recognise a real word field before changing it. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A student types {PAGE} and expects Word to replace it with the current page number.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. select the suspicious item
  2. 2. toggle the selected field
  3. 3. look for Word's field behaviour
  4. 4. avoid retyping the code

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Not every brace-delimited expression is a field.

Transfer: Object recognition supports templates and publishing. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 2 OF 13

2. Separate field code from field result

Back to contents

The mechanism

The code describes the instruction; the result is its current output. Both views are useful for different checks.

Updating a field asks Word to recalculate or retrieve its result. It does not prove that the target heading, caption, date or source is academically correct. In this chapter, the decisive phrase is separate field code from field result. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A report shows {REF _Ref…} and the team thinks the page number has been deleted.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. quote the visible view
  2. 2. toggle code and result
  3. 3. name what each view proves
  4. 4. return to the reader view

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Toggling display does not itself update the value.

Transfer: Layer reading supports formulas and databases. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 3 OF 13

3. Read common field names without guessing

Back to contents

The mechanism

Labels such as PAGE, DATE, REF and TOC indicate different operations and dependencies.

Cross-references depend on document targets and can move when content changes. A correct number before editing can become stale after sections, figures or pages are rearranged. In this chapter, the decisive phrase is read common field names without guessing. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A live DATE field is mistaken for a fixed submission date written by the author.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. identify the field name
  2. 2. locate its target or rule
  3. 3. state whether it can update
  4. 4. compare it with the brief

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: A familiar label can still include switches or settings that change its result.

Transfer: Command vocabulary supports software and coding. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 4 OF 13

4. Use Alt+F9 and Shift+F9 at the right scope

Back to contents

The mechanism

Microsoft distinguishes switching all field codes from switching a selected field.

Unlinking converts a dynamic field into ordinary text. That can stabilise a recipient copy while removing the future update relationship, so it should not be used as a casual repair. In this chapter, the decisive phrase is use alt+f9 and shift+f9 at the right scope. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A learner toggles the whole report and is overwhelmed by codes when only one reference needed inspection.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. select one field when possible
  2. 2. use the documented shortcut
  3. 3. confirm the display change
  4. 4. restore the intended final view

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Keyboard mappings and application versions can differ.

Transfer: Scope control supports editing and debugging. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 5 OF 13

5. Update selected fields deliberately

Back to contents

The mechanism

F9 updates selected fields in Word. Updating can change numbers, dates, references or other generated results.

A field code is an instruction Word interprets; the field result is the text or value the reader sees. Proofreading only one view can miss a broken relationship or an unintended instruction. In this chapter, the decisive phrase is update selected fields deliberately. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The team selects the entire report, presses F9 and changes a date that was meant to preserve the submission day.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. define the update scope
  2. 2. save a review copy
  3. 3. update selected fields
  4. 4. compare before and after

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Update is not a universal correctness command.

Transfer: Controlled recalculation supports spreadsheets and reports. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 6 OF 13

6. Verify the target behind a cross-reference

Back to contents

The mechanism

A cross-reference points to an existing item such as a heading, figure or numbered paragraph.

Updating a field asks Word to recalculate or retrieve its result. It does not prove that the target heading, caption, date or source is academically correct. In this chapter, the decisive phrase is verify the target behind a cross-reference. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Figure 3 now points to a different chart after the group reordered captions.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. open the referenced location
  2. 2. check label and content
  3. 3. confirm the intended target
  4. 4. repair the relationship rather than the surface number

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Matching numbers do not prove matching meaning.

Transfer: Target verification supports hyperlinks and citations. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 7 OF 13

7. Proofread page numbers after layout changes

Back to contents

The mechanism

Page-dependent results can change with margins, fonts, images and inserted sections.

Cross-references depend on document targets and can move when content changes. A correct number before editing can become stale after sections, figures or pages are rearranged. In this chapter, the decisive phrase is proofread page numbers after layout changes. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A table of contents was correct before a late appendix moved every later page.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. finish material layout changes
  2. 2. update page-dependent fields
  3. 3. scan first and last entries
  4. 4. compare the exported PDF

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: A stable screen view does not guarantee identical pagination elsewhere.

Transfer: Layout verification supports applications and printing. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 8 OF 13

8. Treat dates as evidence with a time meaning

Back to contents

The mechanism

A DATE-related result can represent a dynamic current value rather than a historical event date.

Unlinking converts a dynamic field into ordinary text. That can stabilise a recipient copy while removing the future update relationship, so it should not be used as a casual repair. In this chapter, the decisive phrase is treat dates as evidence with a time meaning. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A report reopened next week displays a new date and appears to have been submitted later.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. identify the date field type
  2. 2. state the intended event
  3. 3. replace with approved fixed text when necessary
  4. 4. retain the original evidence separately

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Do not freeze or change dates to misrepresent submission history.

Transfer: Temporal language supports records and contracts. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 9 OF 13

9. Understand switches and formatting instructions

Back to contents

The mechanism

Field codes can contain switches that change formatting or behaviour. Read them as part of the instruction.

A field code is an instruction Word interprets; the field result is the text or value the reader sees. Proofreading only one view can miss a broken relationship or an unintended instruction. In this chapter, the decisive phrase is understand switches and formatting instructions. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A reference displays an unexpected capitalisation because a formatting switch was copied with the field.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. view the complete code
  2. 2. separate target from switch
  3. 3. check the intended display
  4. 4. test on a copy

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Do not delete unfamiliar syntax from a live report without understanding it.

Transfer: Parameter reading supports commands and data tools. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 10 OF 13

10. Distinguish unlinking from updating

Back to contents

The mechanism

Microsoft documents unlinking a field separately from updating or toggling it. Unlinking removes the dynamic relationship.

Updating a field asks Word to recalculate or retrieve its result. It does not prove that the target heading, caption, date or source is academically correct. In this chapter, the decisive phrase is distinguish unlinking from updating. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A student unlinks every reference to stop one error and later cannot update the report after edits.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. preserve a dynamic master
  2. 2. identify the recipient need
  3. 3. unlink only with a reason
  4. 4. rename the static copy

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Unlinking can be difficult to reverse.

Transfer: Irreversibility reading supports publication workflows. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 11 OF 13

11. Check references for meaning, not only mechanics

Back to contents

The mechanism

A field can point successfully to a target that is irrelevant, misleading or incorrectly labelled.

Cross-references depend on document targets and can move when content changes. A correct number before editing can become stale after sections, figures or pages are rearranged. In this chapter, the decisive phrase is check references for meaning, not only mechanics. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The cross-reference says Table 2 and opens Table 2, but the sentence is discussing a different dataset.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. read the surrounding claim
  2. 2. inspect the target evidence
  3. 3. compare nouns and scope
  4. 4. revise the prose or target

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Technical validity is not argumentative validity.

Transfer: Evidence alignment supports examinations and research. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 12 OF 13

12. Collaborate without creating competing field states

Back to contents

The mechanism

Co-authors can update, unlink or paste references differently. Agree on the master document and review stage.

Unlinking converts a dynamic field into ordinary text. That can stabilise a recipient copy while removing the future update relationship, so it should not be used as a casual repair. In this chapter, the decisive phrase is collaborate without creating competing field states. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: One student pastes static numbers while another continues adding figures to a shared report.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. name the master file
  2. 2. assign the update checkpoint
  3. 3. avoid manual duplicate numbering
  4. 4. record the final reviewer

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: Collaboration history does not replace a final proofread.

Transfer: Workflow language supports group projects and work. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 13 OF 13

13. Export and inspect the reader-facing PDF

Back to contents

The mechanism

The recipient usually sees results, not codes. The export is a new object that deserves its own check.

A field code is an instruction Word interprets; the field result is the text or value the reader sees. Proofreading only one view can miss a broken relationship or an unintended instruction. In this chapter, the decisive phrase is export and inspect the reader-facing pdf. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Word looks correct, but the uploaded PDF contains an old table of contents from the wrong copy.

Field literacy separates three claims: the code identifies what Word was instructed to do, the result shows what Word currently calculated, and the author decides whether that result makes sense in the argument. None of those layers replaces the others.

Decision sequence
  1. 1. export from the named master
  2. 2. open the exact PDF
  3. 3. search key headings and captions
  4. 4. verify the uploaded object

After the field decision, show field results, update within the approved scope, inspect every numbered reference and page-dependent item, save a named review copy, export the PDF and compare the PDF against the intended headings, figures, tables and citations. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record the document version, field type, visible code or result, target, update date, unexpected output, correction and exported filename. Do not paste confidential document text into a troubleshooting note.

Important boundary: A successful export does not prove the correct source file was used.

Transfer: Recipient verification supports admissions and careers. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

Four useful discoveries

Recognise a real Word field before changing it

Word fields are structured instructions, usually shown with braces when codes are visible. Typed braces are not automatically fields.

Boundary: Not every brace-delimited expression is a field.

Separate field code from field result

The code describes the instruction; the result is its current output. Both views are useful for different checks.

Boundary: Toggling display does not itself update the value.

Read common field names without guessing

Labels such as PAGE, DATE, REF and TOC indicate different operations and dependencies.

Boundary: A familiar label can still include switches or settings that change its result.

Use Alt+F9 and Shift+F9 at the right scope

Microsoft distinguishes switching all field codes from switching a selected field.

Boundary: Keyboard mappings and application versions can differ.

Practice with realistic decisions

Update selected fields deliberately

The team selects the entire report, presses F9 and changes a date that was meant to preserve the submission day.

  • define the update scope
  • save a review copy
  • update selected fields
  • compare before and after

Verify the target behind a cross-reference

Figure 3 now points to a different chart after the group reordered captions.

  • open the referenced location
  • check label and content
  • confirm the intended target
  • repair the relationship rather than the surface number

Proofread page numbers after layout changes

A table of contents was correct before a late appendix moved every later page.

  • finish material layout changes
  • update page-dependent fields
  • scan first and last entries
  • compare the exported PDF

Advice for students, families and educators

For students

  • Toggle one field at a time when diagnosing, then return to results for proofreading.
  • Keep a dynamic master and a separately named submitted copy.

For families

  • Ask which document and export were actually checked instead of manually correcting every number.
  • Help preserve versions without changing the learner's evidence.

For educators

  • State whether dates, references and tables of contents should remain dynamic.
  • Assess both correct reference relationships and meaningful use of evidence.

Frequently asked questions

What is a Word field?

A structured instruction that produces an updateable result such as a page number, date or cross-reference.

Why do I see braces and REF?

Word is displaying the field code instead of its result.

How do I switch all codes and results?

Microsoft documents Alt+F9.

How do I switch one selected field?

Microsoft documents Shift+F9.

What does F9 do?

It updates selected fields in supported Word contexts.

Does updating prove the reference is correct?

No. It proves Word recalculated the field; verify the target and meaning.

Can I type the braces myself?

Typed braces do not automatically create a functioning field.

What does unlinking do?

It converts a dynamic field to ordinary text and removes future updating.

Why inspect the PDF?

It is the object the recipient may read and can differ from the source view.

Why English?

Because code, result, target, update and correct describe different layers.

Useful next reading

Closing thought

Dynamic references make long reports easier to maintain, but only careful language makes their relationships visible. Name the field, inspect the target, update deliberately and proofread what the reader will actually receive.