Mail Merge

Every prior chapter treated a Word document as one single, self-contained thing. Mail Merge turns that idea inside out: one document becomes a template, and an external table of data — most naturally, an Excel worksheet — supplies as many personalized versions of it as there are rows. This is also the most direct connection point between the two apps this course covers: the data source Mail Merge reads is exactly the kind of Excel Table Excel Fundamentals Chapter 7 taught you to build.

The Problem Mail Merge Solves

Imagine sending a personalized letter to 200 people — each one needs their own name, address, and a specific amount owed. Manually creating 200 separate documents, or find-and-replacing placeholder text 200 times in one document, is exactly the kind of repetitive, error-prone task that shouldn't be done by hand. Mail Merge produces all 200 personalized documents from one template and one data table, correctly and automatically.

The Two Ingredients: A Template and a Data Source

A merge always needs exactly two things:

• A template — a normal Word document, written once, with placeholder fields marking where personalized content goes.
• A data source — a table of records, one row per recipient, one column per piece of information. Most commonly, this is an Excel worksheet — and ideally, an actual Excel Table (Excel Fundamentals Chapter 7), whose column headers become the exact field names Mail Merge offers.

Setting Up the Merge

Mailings → Start Mail Merge, choosing the document type (Letters, Envelopes, Labels, or Email Messages), then Select Recipients → Use an Existing List, browsing to the Excel workbook and picking the specific worksheet or named Table it should read from.

Inserting Merge Fields

Mailings → Insert Merge Field lists every column found in the connected data source — inserting one drops a placeholder like «FirstName» or «Amount» directly into the template at the cursor's position. Preview Results toggles between seeing these raw placeholders and an actual preview populated with one real row's data, letting you confirm the layout looks right before running the full merge.

Matching Fields: The Same Exact-Match Discipline as XLOOKUP

Mailings → Match Fields exists because Word's own expected field names (like "First Name") don't always exactly match whatever the Excel source's actual column headers are called (say, "FName" instead). This dialog lets you map Word's expected names onto the source's real column names explicitly — skip this when they genuinely don't match, and merge fields come through blank, or paired with entirely the wrong column, with no error shown.

This is precisely the same discipline Excel Fundamentals Chapter 5 demanded of XLOOKUP: an exact match is required for a lookup to succeed, and a near-miss (different capitalisation, an extra space, a slightly different name) fails silently rather than obviously — just applied here across a whole template's worth of field names at once, instead of one single lookup key.

Completing the Merge

Mailings → Finish & Merge offers three outputs: Edit Individual Documents (combines every recipient's personalized version into one new document, one after another), Print Documents (sends the entire batch straight to a printer), or Send Email Messages (for an Email Messages-type merge, sending each personalized version directly to that row's own email address).

Hands-On Exercises