Running a bilingual tournament — English and Spanish at the same time.

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. Surface-level bilingualism is a banner in two languages. Deep bilingualism is the entire operation in two languages, switchable at any time.

The four surfaces

Where bilingualism actually has to live:

• Pre-event communication. Registration emails, briefing materials, rules document. If half your captains can't read your briefing, half your captains will misunderstand the rules.
• Day-of operations. Catch entry interface, jury panel, judge-to-director handoffs. Bilingual judges should not have to translate every catch in their head.
• Public leaderboard. Spectators should be able to follow in their language. Family at home, fans on phones, sponsor staff watching for their logo placements.
• Post-event materials. Results pages, sponsor reports, captain thank-you messages. The permanent record should be accessible to all participants.

Communication plan

Your event needs a documented bilingual communication plan covering:

• Which messages go out in both languages (every captain message; sponsor messages depending on audience)
• Translation responsibility — who reviews translations before send
• Default language fallback — when a captain hasn't specified, which language do they get
• Radio protocol — what language are radio calls in, and how do bilingual judges communicate calls in both languages

Judge training for bilingual events

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 they're handling — captains should not have to read a foreign-language form to confirm their crew's catch.

Practice the radio protocol in advance. If radio is bilingual (e.g. catches called in Spanish, confirmed back in English for the international audience), every judge needs to know the protocol cold.

Registration forms

The registration form should default to the user's browser language but offer a language toggle prominently. Confirmation emails go out in the language the captain registered in.

If you collect crew lists, the angler name field should accept all character sets and accent marks. (You'd be surprised how many systems don't.)

Public leaderboard

One tap should switch the entire interface — column headers, category names, button text, status badges. The data underneath stays the same (boat names, catches, points), but the labels translate.

The URL should be stable across languages — a Spanish-speaking spectator and an English-speaking one should be able to share the same link, and each see it in their language.

Common mistakes

• Translating one direction only. Director writes in English, then translates to Spanish. The Spanish version reads stiffly because it's a translation. Better: have someone who works in Spanish daily review and rewrite, not translate.
• Inconsistent terminology. "Pez Vela" in one document and "Sailfish" in another causes captain confusion. Lock the species names per language at setup and use them everywhere.
• Forgetting the audit trail. Disqualification reasons should be readable in both languages so a captain can understand what was logged. If you write "DQ" in English, write "DESC" in Spanish.

Where to go next

The LATAM use case covers the regional context. The Game Fish SJDS case study shows bilingual operation at scale.