Bilingual is structural, not a translation step.

Most "bilingual" campaigns in the US nonprofit and education sectors are English campaigns with a Spanish translation step appended at the end. The English version is the work; the Spanish version is the deliverable. The brief is in English. The story selection is in English. The headline is workshopped in English. Then a translator gets the final files, and four days later the Spanish version goes out.

Spanish-speaking audiences notice. They are accustomed to it. They have lower expectations of it. The materials read fine, technically — and they read like materials made for someone else.

This essay is about the difference between bilingual-as-translation-step and bilingual-as-structure, and why the second is harder, more expensive, and worth doing.

What translation-step bilingual looks like

The signs are subtle if you don't speak the second language and obvious if you do. The Spanish copy is grammatically correct and culturally awkward. Idioms have been translated literally. Photos in the campaign feature people who could be the audience but weren't selected with the audience in mind. Stories that work in the English campaign — the founder's biography, the donor anecdote, the program statistics — appear in identical structure in the Spanish version, even though those stories may not be the ones a Spanish-speaking audience would prioritize hearing.

None of this is a translator's failure. Translators do the job they were given. The job they were given was: render this English campaign in Spanish. That is a different job than: build a campaign for this Spanish-speaking audience.

"None of this is a translator's failure. Translators do the job they were given. The job they were given was a different job than the one needed."

What structural bilingual looks like

The brief is bilingual. Not translated — written from the start with both audiences in mind, by someone who can think in both languages.

Story selection is audience-specific. The English version of a campaign for, say, a children's services nonprofit might lead with the donor anecdote. The Spanish version might lead with the family who used the service, because the audience cares more about that, and because the donor anecdote presupposes a fundraising context that doesn't translate culturally. Both versions can be true. Both versions can advance the same campaign. Neither needs to be derived from the other.

Headlines are written for each language, not translated. Sometimes the same idea works in both. Sometimes the same idea takes a different shape — different word order, different emphasis, sometimes a different metaphor. A campaign team that speaks both languages can hold both versions side by side and ask whether each one does the job in its own language. A campaign team that doesn't can only check the Spanish version against the English original, which is the wrong question.

Visual and photo selection accounts for cultural fluency. The same campaign may use different cover images for English-language and Spanish-language deployments, not because either version is dishonest, but because the audience each version is talking to is different.

Why this is harder than it looks

Structural bilingual campaigns cost more upfront than translation-step bilingual. They take longer. They require a campaign lead who works in both languages or a senior translator empowered to argue with the English-language team about what should change. They require photographers and designers who can deliver assets that work for two audiences without flattening either.

The reason most organizations don't do this work is not that they don't believe in it. The reason is that the budget conversation about "bilingual" defaults to a per-word translation rate. Per-word rates produce translation-step output. They don't produce campaigns.

The fix is at the budget stage, not the translator stage. Bilingual line items in nonprofit campaign budgets should look more like a percentage of the campaign budget than a translation invoice. Twenty percent of a real campaign budget on the bilingual layer produces structural bilingual. The translation invoice produces what the translation invoice produces.

Why it pays back

Spanish-speaking audiences in the US are not a niche, secondary, or supplementary audience for most nonprofits in the sectors that most need them — education, public health, family services, immigrant services. In many cases they are the majority audience. Treating them as a translation step has real costs in donor recruitment, family engagement, and brand trust.

Earlier in my career, working on national NGO communications, an integrated bilingual campaign architecture — built bilingual from the brief stage — contributed to a campaign that doubled the organization's web traffic. Some of that came from the structural choice to develop both language versions in parallel rather than sequentially. The Spanish-language outlets that picked up the story did so because the story was made for them, not retrofitted to them.

I run bilingual campaigns now at School in the Square, a PreK–12 dual-language English/Spanish charter network in Washington Heights and Inwood. Family communications there are not translated; they are bilingual at the brief stage. Open rates and engagement reflect it.

What to ask your team

If you run communications at a nonprofit, education organization, or public-health institution that serves Spanish-speaking communities, two questions are worth asking before the next campaign:

One: When does Spanish-language work appear in our campaign timeline? If the answer is "after the English version is finalized," the architecture is translation-step.

Two: Who on our team or among our consultants is empowered to disagree with the English-language version on behalf of the Spanish-speaking audience? If the answer is "no one," the architecture is translation-step.

Both of those problems are fixable with intent and budget. Neither is fixable by working harder on translation.