Bilingual Campaign Mail: Layout, Proofing and Distribution

Quick answer

How to produce campaign mail and palm cards in two languages: text expansion, layout strategy, proofing without a bilingual reviewer, and distribution splits.

Bilingual campaign material is standard in most of California, and it produces a specific set of production problems that have nothing to do with the quality of the translation. The translation is usually fine. What breaks is the layout, the proofing, and the distribution split.

Text expands, and layouts do not

Spanish text typically runs longer than the equivalent English by a noticeable margin. Other languages vary in both directions. A layout designed tightly around English copy will not accommodate the translation without either shrinking type or cutting content — and both of those decisions get made late, under deadline, by whoever is available.

The fix is straightforward: design with the longest version. If the English is written first, build the layout with roughly 20 to 30 percent more room in the text areas than English needs. The English version then simply has more white space, which almost always looks better anyway.

Where expansion hurts most

• Headlines set to fill a fixed width
• Buttons, badges and callout shapes sized to the word inside them
• Bulleted lists where each bullet is one line in English and wraps to two in translation
• Captions in tight columns

Two-sided versus two-version

Two approaches, and the choice should be deliberate:

One piece, one language per side. Efficient — one print run, one quantity, no distribution split, and it reaches a mixed household regardless. The cost is that each language gets half the piece, so neither side can be as rich, and neither side can be the "front" that gets seen first.

Two separate versions. Each language gets the full piece. Requires two print versions, two quantities, and a distribution plan that puts the right version in the right hands. Better when the message is substantial or when the audience split is known and geographic.

For mail, separate versions work well because the list can be segmented. For hand-distributed palm cards, the one-piece two-sided approach is often more practical, since volunteers carrying two stacks will mix them.

Proofing when you do not read the language

This is the highest-risk step. Someone has to check the translated version for the things that break in production, and that person should be a fluent reader who was not the translator.

Specific things to check on the translated version:

1. Accented characters. Missing or corrupted accents are the classic font-substitution failure, and they are visible to every reader in that language.
2. Names and titles. Candidate names, office names and ballot designations should not be translated unless they officially differ. This is a common and embarrassing error.
3. Numbers, dates and addresses. These get transposed in re-typesetting more often than words do.
4. Required disclaimers. Check what your jurisdiction requires for the translated version specifically. Do not assume the English disclaimer satisfies the requirement or that a translated one does.
5. Hyphenation and line breaks. Automatic hyphenation applied with the wrong language setting produces breaks that read as errors.

Have the reviewer check the actual proof, not the translation document. Errors are introduced when text moves into layout, so reviewing the source text proves nothing about the printed piece.

Distribution splits

If you are running separate versions, the quantities have to come from somewhere. Options in descending order of reliability: language preference data on your voter file, precinct-level demographic estimates, or a judgment call. Whichever you use, print somewhat more of both versions than the split suggests — running out of one version in the field is worse than having leftovers.

For walk programs, package by version and label clearly, including the version identifier on every bundle. Volunteers working from a mixed box will hand out whatever is on top.

Schedule implications

Bilingual work adds a proofing round in practice, sometimes two. It also adds a dependency: the translation. If the translation is being handled by a volunteer or a staffer with other responsibilities, it will be the thing that arrives late. Set the translation deadline earlier than feels necessary and treat it as a hard gate before layout begins.

The compressed-deadline version of this job — translation arriving the day before the print deadline — is where errors ship. It is worth spending scheduling margin to avoid it.

For the broader mail calendar, our GOTV mail timeline lays out when pieces need to be in production, and our campaign timeline guide covers the sequencing across a full program.