How to run a bilingual fishing tournament — operational guide.

If your fleet includes captains who fish primarily in Spanish and captains who fish primarily in English, the operational decision isn't whether to be bilingual — it's whether you're bilingual on the surface or bilingual all the way down. This guide covers what bilingual operation actually requires and how to set it up.

The four surfaces where bilingualism lives

• Pre-event communication. Registration emails, briefing materials, rules document.
• Day-of operations. Catch entry interface, jury panel, judge-to-director handoffs.
• Public leaderboard. Spectators following in their language.
• Post-event materials. Results pages, sponsor reports, captain thank-yous.

Communication plan

Every captain message in both languages. Default fallback when a captain hasn't specified — typically Spanish in Nicaragua/LATAM events, English in international events. Confirmation emails go out in the language the captain registered in.

Translation responsibility: assign one person to review every translation before send. AI translation is a draft, not a publishable artifact.

Radio protocol

If your event is bilingual, the radio is too. Common patterns:

• Catch reports in the language of the boat (captain's preference)
• Confirmations rebroadcast in the other language by a bilingual judge
• Major announcements (lines-in, lines-out, weather, incident) in both languages

Judge training

Train every judge in both languages they'll need to operate in. Even monolingual judges need to know how to switch the catch entry interface to the language of the boat — captains shouldn't have to read a foreign-language form to confirm their crew's catch.

Practice the radio protocol in advance. Bilingual judges should know exactly when to translate and when not to.

Registration forms

Default to the user's browser language. Offer a language toggle prominently. Confirmation emails go out in the language they registered in.

Crew name fields should accept all character sets and accent marks.

Public leaderboard

One tap should switch the entire interface. The data underneath stays the same; the labels translate. Same shareable URL across languages.

Common pitfalls

• One-direction translation. Translate from English to Spanish, the Spanish reads stiff. Better: have someone who works in Spanish daily review and rewrite.
• Inconsistent terminology. "Pez Vela" in one document, "Sailfish" in another. Lock species names per language at setup.
• Forgetting the audit trail. Disqualification reasons readable in both languages. "DQ" in English needs "DESC" or equivalent in Spanish.

Where to go next

The LATAM use case covers the regional context. The director blog post covers the same ground with the operator's POV.