A convincing first recipient is not enough—read every record, field and rule before personalised text becomes a real message
Use a communication-purpose–authorised-recipient–main-document–data-source–field-name–rule–filter–record-position–blank-value–format–salutation–subject–send-range–test-output–approval–release chain. Treat preview as record-level evidence, not decoration.
Why this English matters now
Reading Word’s Mail Merge Preview Results before sending personalised messages is practical English for students, educators and workplace teams searching how to preview a mail merge, check merge fields or fix wrong names before bulk email or letters.
Microsoft’s current guidance says Preview Results shows merged documents before completion, lets users move to the next or previous record or find a recipient, and works with Edit Recipient List to filter or clear records. For email merges, Finish and Merge asks which address field, subject, format and record range to use.
A perfect-looking first letter does not prove the whole merge is safe. Strong reviewers preserve the main document and source list, define the recipient purpose, inspect field names and rules, preview every record including edge cases, resolve blanks and formatting, verify filters and send range, create a small controlled test, and confirm the exact final messages before broad delivery.
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 communication-purpose–authorised-recipient–main-document–data-source–field-name–rule–filter–record-position–blank-value–format–salutation–subject–send-range–test-output–approval–release chain. Treat preview as record-level evidence, not decoration.
- Microsoft says Preview Results displays merged documents before the merge is completed.
- Microsoft says Next Record, Previous Record and Find Recipient can be used during preview.
- Microsoft says Edit Recipient List can filter the list or clear recipients.
- Microsoft says Finish and Merge can send all records, the current record or a specified range.
Official factual floor
- Microsoft Support: Mail merge — Preview Results
- Microsoft Support: Use mail merge in Word to send bulk email messages
- MOE English Language Syllabus 2020
- IMDA Digital Skills for Life
- Microsoft says Preview Results can show each merged document before completion.
- Microsoft says recipients can be filtered or cleared from Edit Recipient List.
- Microsoft says an email merge can be limited to all records, the current record or a From and To range.
Did You Know?
Preview Results displays one record at a time, but the merge can still be sent to a different record range. The person you preview and the people you release are separate choices, which is why the final send dialog must be read again.
Full chapter index
- 1. Define the communication purpose
- 2. Preserve document and data source
- 3. Map merge fields
- 4. Read rules and conditional text
- 5. Inspect filters and exclusions
- 6. Preview first and last records
- 7. Use Next, Previous and Find Recipient
- 8. Test missing and unusual values
- 9. Check dates, numbers and language
- 10. Read subject and message format
- 11. Prove the send range
- 12. Merge to a controlled output
- 13. Verify the exact released messages
The mechanism
The merge should serve one clear authorised message and audience.
Microsoft says Preview Results displays merged documents before the merge is completed. 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 class reminder is repurposed for a wider marketing list without a new review.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. state the purpose
- 2. name the audience
- 3. define the necessary fields
- 4. assign approval
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Purpose 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.
The mechanism
The main document and recipient list are separate versioned artefacts.
Microsoft says Next Record, Previous Record and Find Recipient can be used during preview. In this chapter, the decisive phrase is preserve document and data source. 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 revised source list is merged with an old template containing last term’s dates.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. save controlled copies
- 2. record filenames and versions
- 3. protect personal data
- 4. limit access
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Provenance language supports accountability. 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.
The mechanism
Field names connect source columns to locations in the message.
Microsoft says Edit Recipient List can filter the list or clear recipients. In this chapter, the decisive phrase is map merge fields. 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: GivenName is inserted where FamilyName belongs.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. list source columns
- 2. match each field
- 3. remove unused personal fields
- 4. read labels aloud
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Field language supports accuracy. 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.
The mechanism
If–Then–Else and greeting rules can change wording by record.
Microsoft says Finish and Merge can send all records, the current record or a specified range. In this chapter, the decisive phrase is read rules and conditional text. 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 blank title produces an awkward salutation for some families.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. inventory every rule
- 2. state its condition
- 3. test true and false cases
- 4. write a safe fallback
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Conditional language supports fair messages. 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.
The mechanism
Edit Recipient List determines which records remain eligible.
Microsoft says Preview Results displays merged documents before the merge is completed. In this chapter, the decisive phrase is inspect filters and exclusions. 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-out student is assumed to have received the deadline notice.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. record active filters
- 2. check cleared recipients
- 3. compare counts
- 4. approve exclusions
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Scope language supports complete 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.
The mechanism
Boundary records can reveal sorting, range and source problems.
Microsoft says Next Record, Previous Record and Find Recipient can be used during preview. In this chapter, the decisive phrase is preview first and last 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 last record is blank because the data range includes an extra row.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. preview the first
- 2. preview the last
- 3. note total records
- 4. check for trailing blanks
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Boundary language supports quality control. 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.
The mechanism
Navigation should prove specific records rather than random examples.
Microsoft says Edit Recipient List can filter the list or clear recipients. In this chapter, the decisive phrase is use next, previous and find recipient. 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: Only records with short names are reviewed because they happen to appear first.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. move sequentially
- 2. find known edge cases
- 3. record reviewed IDs safely
- 4. return to the expected position
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Navigation language supports evidence. 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.
The mechanism
Blank fields, long names and punctuation can break otherwise smooth prose.
Microsoft says Finish and Merge can send all records, the current record or a specified range. In this chapter, the decisive phrase is test missing and unusual values. 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 missing address line leaves two commas and an empty line.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. test blanks
- 2. test longest values
- 3. test punctuation and accents
- 4. test zero and date values
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Edge-case language supports respectful personalisation. 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.
The mechanism
Source formats do not always appear as intended in Word.
Microsoft says Preview Results displays merged documents before the merge is completed. In this chapter, the decisive phrase is check dates, numbers and language. 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 fee date displays as a serial number and a decimal loses its intended precision.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. compare source and preview
- 2. apply justified formatting
- 3. check locale
- 4. proofread multilingual text
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Format language supports clear information. 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.
The mechanism
Email subject, HTML or plain text and body content are separate release choices.
Microsoft says Next Record, Previous Record and Find Recipient can be used during preview. In this chapter, the decisive phrase is read subject and message format. 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 body is correct but the subject still names the previous event.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. proofread the subject
- 2. choose the required format
- 3. check links
- 4. test on representative clients
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Channel language supports reliable delivery. 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.
The mechanism
All, Current record and From–To create different recipient sets.
Microsoft says Edit Recipient List can filter the list or clear recipients. In this chapter, the decisive phrase is prove the send range. 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 test intended for the current record is sent to all recipients.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. pause at Finish and Merge
- 2. read the selected range
- 3. compare with approved count
- 4. use a small controlled test
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Range language supports safe release. 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.
The mechanism
A generated document can be reviewed before printing or sending.
Microsoft says Finish and Merge can send all records, the current record or a specified range. In this chapter, the decisive phrase is merge to a controlled output. 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 real bulk email is used as the first test of the merge logic.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. merge to a new document where suitable
- 2. inspect page and record boundaries
- 3. send to test addresses
- 4. correct the source rather than patching many outputs
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Output language supports verification. 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.
The mechanism
The template, source, merged document and sent messages are distinct artefacts.
Microsoft says Preview Results displays merged documents before the merge is completed. In this chapter, the decisive phrase is verify the exact released messages. 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 approved preview is correct but the send uses an older recipient source.
Preview Results shows how the current record populates the main document. It does not prove the recipient is authorised, every address is valid, every record was reviewed, filters are correct, hidden source columns are safe, the selected send range matches the preview or delivery will succeed.
- 1. reopen source and template
- 2. record final counts
- 3. sample actual outputs
- 4. retain an authorised release record
Preserve the main document and source list; confirm authority and purpose; map every merge field; record filters, sorts and exclusions; preview first, last and every record or an accountable full check; use Find Recipient for known cases; test blanks, long names, punctuation, dates, numbers and multilingual text; check the subject and format; merge to a controlled output or test address; review the exact send range; obtain approval; verify the resulting messages and retain an appropriate release record. 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 main-document version, source-file version, purpose, authorised fields, field mapping, rules, filters, sort, exclusions, total records, previewed records, edge cases, blanks, formatting decisions, subject, format, send range, test output, approver, release time and final output identity.
Transfer: Release language supports education 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.
Four useful discoveries
Define the communication purpose
The merge should serve one clear authorised message and audience.
Boundary: A useful message can still lack consent or authority.
Preserve document and data source
The main document and recipient list are separate versioned artefacts.
Boundary: Copies can preserve unsafe links or stale connections.
Map merge fields
Field names connect source columns to locations in the message.
Boundary: A plausible value can hide a wrong mapping.
Read rules and conditional text
If–Then–Else and greeting rules can change wording by record.
Boundary: Complex business rules may be better repaired in the source system.
Practice with realistic decisions
Inspect filters and exclusions
A filtered-out student is assumed to have received the deadline notice.
- record active filters
- check cleared recipients
- compare counts
- approve exclusions
Preview first and last records
The last record is blank because the data range includes an extra row.
- preview the first
- preview the last
- note total records
- check for trailing blanks
Use Next, Previous and Find Recipient
Only records with short names are reviewed because they happen to appear first.
- move sequentially
- find known edge cases
- record reviewed IDs safely
- return to the expected position
Advice for students, families and educators
For students
- Use a tiny fictional data set to learn mail merge before using real personal information.
- Preview long names, blanks and the final record, not only the first recipient.
For families
- Protect address lists and ask whether every field is necessary.
- Help proofread the output without copying personal data into casual notes.
For educators
- Provide safe synthetic recipient lists for practice.
- Assess filters, edge cases and send-range evidence as well as polished wording.
Frequently asked questions
What does Preview Results do?
Shows field values for a recipient before the merge is completed.
Can I move between recipients?
Yes, with Next and Previous Record.
Can I find one recipient?
Yes, Microsoft documents Find Recipient.
Can I exclude a recipient?
Yes, through Edit Recipient List when authorised.
Why are fields blank?
The source may be blank, filtered, mis-mapped or formatted unexpectedly.
Should I preview only the first record?
No; review the responsible scope and edge cases.
Can I send only one record?
Finish and Merge can use the current record, all records or a From–To range.
Does preview prove an email address works?
No.
What should I verify?
Authority, fields, rules, filters, values, subject, format, range and exact output.
Why English?
Because field, record, recipient, filter, rule, preview and send range describe different decisions.
Useful next reading
- Word Restrict Editing — protect a reusable main document without confusing permissions
- Word Document Inspector — inspect hidden data before releasing generated documents
- Why English Matters in Singapore — connect accurate personalisation to study and workplace communication
Closing thought
Personalisation earns trust only when it is accurate and respectful. Preview the records, read the rules, prove the range and send only after the exact output matches the authorised audience and purpose.