How to Do a Mail Merge, Step by Step (Without the Headaches)

The short version of how to do mail merge is four steps: prepare the data list, build a template with merge fields, check and test a few records, then run the full batch. Step three is the one people skip. It is also where a header that did not match gets caught while it is still a two-minute fix.

Step 1: Prepare the data list

Open a spreadsheet. Give each piece of information its own column: first name, last name, amount due, due date, unit number. Put one recipient on each row. Keep the headers short and plain, with no trailing spaces, because the header is the name the template will ask for.

A bookkeeper sending invoices needs at least a client name, an invoice number, an amount and a due date. If the template uses a field, that column should have a value on every row.

Step 2: Build the template with merge fields

Write the document once, the way every copy should read. Put a placeholder wherever a personal value goes. Word shows a merge field as «First_Name». Many email platforms and CRMs use double braces, like {{first_name}}. The syntax depends on the tool. The rule does not: Microsoft's guidance for Excel data sources says the column names in the spreadsheet should match the field names you want to insert.

Step 3: Check, then test-merge a few records

Two checks happen here, and they catch different things.

The first is a check of the whole list against the template. Does every placeholder have a column? Does every row have a value for each field the template needs? This is a job for a rule, not for your eyes, because the one blank cell in row 140 looks like every other row when you scroll.

The second is a test merge. Run three to five records and open each one. Look for:

• A date or time that shows up as a raw number
• An amount with no currency symbol
• A long name pushing text off a certificate line
• A first name sitting where a last name should be

The test merge shows you how the document reads. The list check shows you which rows are missing something. Neither one replaces the other.

Step 4: Run the full batch

Once the test records read correctly, run the list. Most tools can output individual files, one combined document, or emails. Pick by what happens next. Individual files suit invoices and certificates, where each person gets their own PDF. A combined document suits a single print job.

A worked example: an appointment-reminder run

This example is made up to show the steps.

1. A clinic exports 150 upcoming appointments: patient name, date, time and provider.
2. The reminder letter has four placeholders, one per column.
3. A test merge of 4 records shows the time as 0.375. A spreadsheet stores a time as a fraction of a day, and 9 divided by 24 is 0.375, so that is 9:00 AM stored as a number.
4. The clinic converts the time column to text in the spreadsheet, reruns the 4 records, reads them, and runs all 150.

The template was fine the whole time. The fix was in the list.

When the test passes and the batch is still wrong

A test merge reads the first few rows, and the first few rows of a list are often the oldest and cleanest. The blank company name, the email typed without an at sign, the record someone added on Friday afternoon: these sit further down. You can raise the odds by testing rows from the top, the middle and the bottom. You cannot read all 150 by hand every month, and nobody does.

There is a second limit, and a tool does not fix it. A row can be complete, well formed and wrong. If the export says 2:30 PM and the appointment moved to 3:00, the letter merges without a flaw. Checking a merge tells you the documents will render. Whether they are true depends on the system the list came from.

Where a pre-send check fits

Word and most email tools will run the merge. They are less helpful at telling you, before the run, which rows will come out broken. That is the gap a pre-send check fills. The Template Merge & Mail-Merge Engine reads a template and a CSV list and grades every row, then gives the template one verdict. On the sample that ships with it, five rows come back as 3 READY, 1 FIX and 1 BLOCK, with the reason beside each: one row is missing a company, and one has an email that is not an email.

Two limits are worth knowing before you buy. It reads double-brace tokens only, so a Word template with «First_Name» fields has to be copied out as text with {{first_name}} tokens first. And it treats a field as optional only when its config file marks it optional, so you set that list for your own columns.

Pairs well with

If the data starts in PDFs or scans, the AI Document Extraction Kit ($99) pulls invoices, receipts and forms into structured data and flags low-confidence fields for a person to review. If you want to know whether this month's list agrees with the system it came from, the Two-List Reconciliation Kit ($49) joins the two on an exact key and marks each key RECONCILED, EXCEPTION or ORPHANED. And when the run leaves you with a folder of output files, the File Naming & Organization Engine ($49) checks names against a four-part convention and marks any two that would end up identical as COLLISION.