Mailing List File Handoff: Columns, IDs and Versioned Exports

A mailing-list file handoff tells the provider which records to use, what the columns mean and which edition your organization has approved. The file and its instructions work together: a spreadsheet of names and addresses alone may leave questions about the selected records, recipient units or values that need to be preserved.

Before preparing the full export, agree the format and a small sample with the person receiving it. That gives both teams a practical way to settle the column map, record count and replacement instructions for the actual job.

Agree the file format and selected data

Ask which file format the provider accepts for this mailing and what preparation instructions apply. A workbook, delimited export or another agreed format may call for different handling. The provider’s instructions should establish what to supply; there is no need to guess that every job starts with the same file type.

If the source contains several worksheets, tables or data ranges, identify the exact selection intended for the mailing. Record its name and how the approved records are selected. Do not rely on a visually filtered view, a highlighted area or a tab called final to communicate that decision by itself.

Keep report titles, notes and reference material distinguishable from recipient records. If the source includes formulas or calculated fields, agree what result is required in the supplied file and check that result in the handoff. Ask the provider what it needs to confirm the selected data before production preparation begins.

Define what one record represents

State whether one supplied record represents a person, a household, an organization, a location or another unit approved for this mailing. That definition affects how the team interprets the count and connects records to the intended pieces.

Two records sharing an address may represent separate intended recipients. Likewise, an organization may have several mailing locations. A shared name or address does not settle whether those records should be combined. Have the organization approve the recipient arrangement instead of leaving that decision to an unexplained file change.

If a consistent record identifier already exists, identify its column and meaning. Confirm whether it refers to the same recipient across exports and whether the provider can retain or return that reference in the agreed work. A spreadsheet row number is a position in one file, so distinguish it from a reference assigned to a recipient across editions.

Supply a column map with the sample

A column map explains each field the provider is expected to use. Include the exact header from your file, its meaning and any instruction needed to interpret it. If the artwork uses a greeting or a version code, identify the source column for that purpose rather than assuming the receiving team will infer it from a similar name.

These fictional field names illustrate the kind of explanation to include. They are not required headers or a template for every provider:

Example field Meaning or decision to document
RecipientRef The organization’s reference for the recipient, including any characters that must stay intact.
NameForMail The approved addressee wording and whether it differs from a greeting elsewhere in the piece.
AddressLine1 and AddressLine2 What each supplied line contains, including any separate unit or other address information.
PostalCode The supplied postal-code value and any leading zeros or punctuation that must be preserved.
EditionCode The approved content version connected to this record, if the job uses different versions.

Identify blank or unexpected values that need an answer. Name the person who can approve a correction or the intended handling. Avoid filling a missing greeting, address part or version assignment with a guess just to make the sample look complete.

Check values after the export

Some fields contain codes rather than quantities to calculate. Tell the provider which values need faithful character preservation. For example, the fictional identifier 00123 is different from 123 when the leading zeros are part of the organization’s reference.

If Excel is used in the process, Microsoft’s guidance on keeping leading zeros and large numbers explains automatic conversions that can change these values. Check the file being handed off against the approved source, rather than relying only on how a value appears in the workbook.

Include relevant cases in the agreed sample, such as a reference with leading zeros, a name with punctuation, a second address line or a longer field. If a value changes during preparation, return the question to the source owner. Do not reconstruct missing characters from a guess about what the field probably meant.

Use a small sample to settle the handoff

A fictional or suitably redacted sample can show the proposed structure before a full recipient file is needed. Include the headers, the intended record unit and examples of the fields that require attention. Use only the fields agreed for the job.

Review the sample with the provider to confirm how it will connect to the mailing. Where the piece contains personalized text or multiple versions, identify the intended relationship between each source field and its use. Ask what further file or artwork review is needed before the actual records can be approved.

Keep the sample’s purpose clear. Agreement on a column structure does not establish that a later full export has the correct selection, count or values. The final file still needs to be identified and checked against the same instructions.

Record counts using the agreed recipient unit

State how many recipient records the selected export contains, using the definition agreed for this job. Explain any separate header, notes or other material so the receiving team can distinguish it from those records. A displayed worksheet row number alone is not a complete count explanation.

If the job has content versions, provide their record counts and check that they account for the intended recipient selection. Keep those counts separate from component quantities, office copies or completed-package quantities when they measure different things.

Ask how the provider will report any later changes to the supplied count. A missing field, duplicate review or campaign exclusion may need its own decision and explanation. Keep an unresolved record visible as a hold rather than silently treating it as an approved removal or a completed mailing.

Identify the export edition and any replacement

Give the supplied file an edition reference and record when it was exported, the source selection it represents and who approved it. An export date identifies the file’s preparation; it does not by itself explain the mailing audience or campaign period.

If a correction is needed, state whether the new file replaces the complete earlier export or supplies an agreed set of changes. Identify the edition it supersedes and the affected records or instructions. Confirm which file the provider will use before further preparation proceeds.

Ask what stage the job has reached before assuming a replacement can be included. Keep the agreed action and resulting count with the file record so an earlier attachment does not remain a plausible alternative after a correction.

Keep the approval instructions with the final file

A useful final handoff identifies:

  1. The job or campaign, accepted file format and exact worksheet, table or export selected.
  2. The recipient unit, source record count and any version counts.
  3. The column map, matching references and values that must be preserved.
  4. The sample decisions, unresolved records and people responsible for answers.
  5. The approved export edition, replacement instructions and person authorized to approve a change.

Keep those instructions connected to the file delivered through the agreed transfer method. Record the provider’s confirmation of the edition and scope it will use, along with any remaining questions. File acceptance, quantity approval and artwork approval should each refer to the same intended job.

To discuss a recipient-file handoff for your printing and mailing project, call Accurate Mailing Service at 602-433-9101. Bring the column map and a sample of the structure so the conversation can establish what the actual job needs before the full file is prepared.

The fastest answer is a person. Call 602-433-9101 and we will talk your mailing through with you.

Or pick your routes and see your price in our free tool, no account needed.

And when this topic turns into a mailing, this is where it starts.

Share This Post

More To Explore