eduKate Singapore

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.

Next useful routeCanonical hubHELP

Why English? | Reading Word’s Mail Merge Rules Before Creating Conditional Letters

—

by

eduKate Asia
WORD · MAIL MERGE RULES · CONDITIONAL LETTERS

Personalise repeated communication without confusing data fields, prompts, conditions, branches and record numbers—or sending the wrong sentence to the wrong reader

Use a purpose–lawful-recipient–minimum-data–field-dictionary–recipient-selection–base-letter–merge-field–rule-type–prompt-or-condition–true-branch–false-branch–sort-and-filter–record-number–boundary-test–preview–approval–release chain. Write the human rule in plain English before encoding it.

ROUTE 1OrientDefine the communication purposeROUTE 2InterpretSelect and order recipientsROUTE 3ControlWrite If Then Else in proseROUTE 4VerifyPreview representative records

Open the full chapter index ↓

Why this English matters now

Reading Word’s Mail Merge Rules before creating conditional letters is practical English for students, teachers and office teams searching how to use If Then Else in mail merge, add conditional text in Word or personalise bulk letters from an Excel list.

Microsoft’s current guidance says Mailings > Rules can customise a merge after recipients and merge fields are selected. Ask can request one response for repeated bookmarks, Fill-in can request text inserted at a location, If…Then…Else chooses between two texts from a field comparison, and Merge Record # can show a recipient’s position after sorting and filtering.

Automation magnifies wording mistakes. Strong users define the communication purpose, minimise personal data, standardise field names, distinguish blank from missing or unknown values, write both branches in full, test boundary records, preview every category, protect the source list, generate review copies, and verify the exact letters before printing or sending.

Checked against the linked first-party sources on 2 November 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 purpose–lawful-recipient–minimum-data–field-dictionary–recipient-selection–base-letter–merge-field–rule-type–prompt-or-condition–true-branch–false-branch–sort-and-filter–record-number–boundary-test–preview–approval–release chain. Write the human rule in plain English before encoding it.

  1. Microsoft says mail merge rules are set after recipients are selected and merge fields are inserted, so a rule depends on a defined data source and document structure.
  2. Microsoft says Ask enters information once and can display it at repeated bookmarks, while Fill-in prompts for text to insert where that field appears.
  3. Microsoft says If…Then…Else compares a selected field with a value or blank state and inserts one text when the condition is met and another when it is not.
  4. Microsoft says Merge Record # reflects sorting and filtering, so the displayed position is not necessarily a permanent identifier for a person.

Official factual floor

  • Microsoft’s current mail merge overview says Word for the web can preserve settings created in the desktop application but cannot perform a mail merge or edit mail merge settings.
  • The Ask rule can reuse one response through bookmarks, while Fill-in is designed for prompted text at the field location; similar prompts therefore do not imply identical behaviour.
  • A Merge Record number follows the active order after recipient sorting and filtering and should not be presented as an immutable database ID.
Scope: This guide cannot establish a lawful basis for collecting or sending personal data; decide who should receive a message; repair inaccurate source records; make a blank field mean unknown, not applicable or domestic without an agreed definition; encrypt or secure every channel; prevent disclosure through attachments or address fields; replace human review; guarantee that desktop and web Word behave identically; or certify regulatory, legal, financial, medical or safeguarding communication.

Did You Know?

Merge Record # is positional. Microsoft says it reflects sorting and filtering, so the same recipient can receive a different number when the recipient list or order changes. It should not be reused as a permanent identity key.

Full chapter index

  1. 1. Define the communication purpose
  2. 2. Minimise recipient data
  3. 3. Build a field dictionary
  4. 4. Select and order recipients
  5. 5. Choose Ask deliberately
  6. 6. Choose Fill-in deliberately
  7. 7. Write If Then Else in prose
  8. 8. Test blank and boundary states
  9. 9. Use Merge Record carefully
  10. 10. Preview representative records
  11. 11. Reconcile and verify release
CHAPTER 1 OF 11

1. Define the communication purpose

Back to contents

The mechanism

Conditional text should serve a legitimate reader need.

Microsoft says mail merge rules are set after recipients are selected and merge fields are inserted, so a rule depends on a defined data source and document structure. In this chapter, the decisive phrase is define the communication purpose. 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 letter changes tone by category even though every recipient needs the same clear instruction.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. name the purpose
  2. 2. identify the reader action
  3. 3. remove unnecessary variation
  4. 4. assign an owner

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: Personalisation can add risk without adding usefulness.

Transfer: Purpose language supports proportionate automation. 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 11

2. Minimise recipient data

Back to contents

The mechanism

A merge list should contain only fields needed for the approved message.

Microsoft says Ask enters information once and can display it at repeated bookmarks, while Fill-in prompts for text to insert where that field appears. In this chapter, the decisive phrase is minimise recipient data. 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 school notice includes health and family fields that no rule uses.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. list required fields
  2. 2. remove sensitive extras
  3. 3. restrict access
  4. 4. set retention

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: Convenient collection is not the same as authorised use.

Transfer: Privacy language supports responsible communication. 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 11

3. Build a field dictionary

Back to contents

The mechanism

Rules need stable field names, allowed values and blank meanings.

Microsoft says If…Then…Else compares a selected field with a value or blank state and inserts one text when the condition is met and another when it is not. In this chapter, the decisive phrase is build a field dictionary. 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: Status contains Yes, Y, Confirmed and a blank, so one condition misses valid recipients.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. name each field
  2. 2. define allowed values
  3. 3. define blank and unknown
  4. 4. standardise formats

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: Cleaning must preserve evidence of corrections and source ownership.

Transfer: Definition language supports reliable conditions. 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 11

4. Select and order recipients

Back to contents

The mechanism

Rules run within the chosen recipient set and Merge Record depends on order.

Microsoft says Merge Record # reflects sorting and filtering, so the displayed position is not necessarily a permanent identifier for a person. In this chapter, the decisive phrase is select and order recipients. 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 filtered test group is mistaken for the final recipient list.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. record filters
  2. 2. record sort order
  3. 3. count recipients
  4. 4. save the selection state

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: A correct rule can still reach the wrong people if selection is wrong.

Transfer: Scope language supports safe batching. 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 11

5. Choose Ask deliberately

Back to contents

The mechanism

Ask collects one response that can appear through repeated bookmarks.

Microsoft says mail merge rules are set after recipients are selected and merge fields are inserted, so a rule depends on a defined data source and document structure. In this chapter, the decisive phrase is choose ask 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 meeting date is typed separately in three places and one instance remains old.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. create clear bookmarks
  2. 2. write a precise prompt
  3. 3. place the rule before use
  4. 4. test every bookmark

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: Prompted input still needs validation and an authorised operator.

Transfer: Prompt language supports consistent repeated text. 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 11

6. Choose Fill-in deliberately

Back to contents

The mechanism

Fill-in requests text for insertion at its field location during the merge.

Microsoft says Ask enters information once and can display it at repeated bookmarks, while Fill-in prompts for text to insert where that field appears. In this chapter, the decisive phrase is choose fill-in 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: An operator enters a date without a year and the resulting invitation is ambiguous.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. write a complete prompt
  2. 2. specify format
  3. 3. test cancellation
  4. 4. review inserted text

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: Repeated manual prompts can create inconsistent batches.

Transfer: Input language supports usable prompts. 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 11

7. Write If Then Else in prose

Back to contents

The mechanism

The human condition should be understandable before it is encoded.

Microsoft says If…Then…Else compares a selected field with a value or blank state and inserts one text when the condition is met and another when it is not. In this chapter, the decisive phrase is write if then else in prose. 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 rule uses Country is blank to mean domestic without documenting that convention.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. state the field
  2. 2. state the comparison
  3. 3. write the true text
  4. 4. write the false text

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: A binary rule may oversimplify a multi-state reality.

Transfer: Conditional language supports transparent branching. 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 11

8. Test blank and boundary states

Back to contents

The mechanism

Real records contain spaces, misspellings, nulls and unexpected values.

Microsoft says Merge Record # reflects sorting and filtering, so the displayed position is not necessarily a permanent identifier for a person. In this chapter, the decisive phrase is test blank and boundary 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: A single space is treated differently from a truly empty field and selects the wrong branch.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. test exact match
  2. 2. test blank and whitespace
  3. 3. test unusual values
  4. 4. define an exception path

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: No finite test set covers every future data error.

Transfer: Boundary language supports resilient output. 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 11

9. Use Merge Record carefully

Back to contents

The mechanism

The number represents position after active sorting and filtering.

Microsoft says mail merge rules are set after recipients are selected and merge fields are inserted, so a rule depends on a defined data source and document structure. In this chapter, the decisive phrase is use merge record carefully. 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 waitlist number changes after one record is removed but is described as permanent.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. freeze the recipient set
  2. 2. record the sort
  3. 3. preview first and last positions
  4. 4. avoid identity claims

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: Position is not priority unless the ordering rule says so.

Transfer: Order language supports honest numbering. 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 11

10. Preview representative records

Back to contents

The mechanism

Preview Results should cover every branch, not only the first recipient.

Microsoft says Ask enters information once and can display it at repeated bookmarks, while Fill-in prompts for text to insert where that field appears. In this chapter, the decisive phrase is preview representative records. 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 first letter is correct, while all blank-status records show an unfinished sentence.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. choose one record per branch
  2. 2. inspect punctuation
  3. 3. check dates and names
  4. 4. generate review copies

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: A sample review should be paired with automated counts and exception checks.

Transfer: Preview language supports complete review. 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 11

11. Reconcile and verify release

Back to contents

The mechanism

Recipient count, output count and failures should be recorded.

Microsoft says If…Then…Else compares a selected field with a value or blank state and inserts one text when the condition is met and another when it is not. In this chapter, the decisive phrase is reconcile and verify release. 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 printer jam produces duplicates for some families and omissions for others.

Mail Merge Rules are conditional document instructions evaluated against recipient data and prompts. They automate selection among prepared text. They do not interpret a person’s circumstances, validate the source data, decide whether contact is appropriate or remove the need for human review.

Decision sequence
  1. 1. record the final count
  2. 2. sample outputs
  3. 3. log failures
  4. 4. confirm the released batch

Define the communication purpose, owner and authorised recipients; identify the lawful and minimum data needed; create a field dictionary with allowed values and meanings for blank, missing and unknown; clean duplicate records; preserve the source list; select the correct mail merge document type; connect the approved data source; filter and sort recipients deliberately; write a complete base letter that remains respectful in every branch; insert ordinary merge fields; state each conditional rule in plain English; choose Ask when one prompted response must appear through named bookmarks; choose Fill-in when prompted text belongs at the field location; choose If…Then…Else for a documented field comparison; choose the field name and comparison; enter the comparison value only where required; write both true and false texts; use Merge Record # only when the current sorted position is meaningful; test blank, exact-match, non-match, unusual character, duplicate and boundary records; inspect punctuation and spacing around fields; preview results across every category; generate Edit Individual Documents for a controlled review set; search for unresolved merge markers; check dates, titles, pronouns, salutations and attachments; have the communication owner approve the wording; secure source and output files; print or send through the authorised route; sample the final output; reconcile recipient count; record exceptions and failures; and archive or delete personal data according to the approved retention plan. 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 purpose, communication owner, lawful basis or institutional authority, recipient source and version, field dictionary, blank and missing meanings, filters and sort order, document type, ordinary fields, each rule type and plain-language logic, prompts, true and false text, bookmark names, Merge Record use, test cases and expected outputs, preview sample, reviewer, recipient count, exceptions, send or print route, retention action and released batch identifier.

Important boundary: A later data correction requires a controlled rerun, not an informal duplicate send.

Transfer: Release language supports accountable communication. 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

Define the communication purpose

Conditional text should serve a legitimate reader need.

Boundary: Personalisation can add risk without adding usefulness.

Minimise recipient data

A merge list should contain only fields needed for the approved message.

Boundary: Convenient collection is not the same as authorised use.

Build a field dictionary

Rules need stable field names, allowed values and blank meanings.

Boundary: Cleaning must preserve evidence of corrections and source ownership.

Select and order recipients

Rules run within the chosen recipient set and Merge Record depends on order.

Boundary: A correct rule can still reach the wrong people if selection is wrong.

Practice with realistic decisions

Choose Ask deliberately

The meeting date is typed separately in three places and one instance remains old.

  • create clear bookmarks
  • write a precise prompt
  • place the rule before use
  • test every bookmark

Choose Fill-in deliberately

An operator enters a date without a year and the resulting invitation is ambiguous.

  • write a complete prompt
  • specify format
  • test cancellation
  • review inserted text

Write If Then Else in prose

The rule uses Country is blank to mean domestic without documenting that convention.

  • state the field
  • state the comparison
  • write the true text
  • write the false text

Advice for students, families and educators

For students

  • Write the If…Then…Else rule in one plain sentence before opening the dialog.
  • Create harmless test records for every branch instead of using real personal data for practice.

For families

  • Ask the learner to explain what a blank field means and who sees each branch.
  • Help proofread test letters without handling unnecessary recipient data.

For educators

  • Provide synthetic datasets for mail merge exercises.
  • Assess privacy, field definitions, boundary tests and review logs alongside correct output.

Frequently asked questions

When are mail merge rules added?

After selecting recipients and inserting the relevant merge fields.

What does Ask do?

It prompts for information that can be reused through named bookmarks.

What does Fill-in do?

It prompts for text inserted at the Fill-in field location.

What does If Then Else do?

It compares a data field and inserts one of two prepared texts.

What does Merge Record # show?

The recipient’s position after current sorting and filtering.

Is the record number permanent?

No; it can change with the recipient set and order.

Can Word for the web run the merge?

Microsoft says it preserves desktop settings but cannot perform or edit the merge.

Should a blank mean domestic or no?

Only if the field dictionary explicitly defines and validates that meaning.

What must I verify?

Recipients, fields, prompts, both branches, boundaries, previews, privacy and release.

Why English?

Because ask, fill in, compare, blank, otherwise, record and recipient describe different rule states.

Useful next reading

Closing thought

A good conditional letter feels personal because it is accurate and respectful, not because software inserted a name. Define the data, write both branches carefully and review the people at the edges of the rule before any batch leaves the computer.