PAICE.work Is Now Fully Available in Spanish, French, and Portuguese

In April, we launched multilingual support for the PAICE assessment flow in Spanish, French, and Brazilian Portuguese. That release covered the core experience: the behavioral assessment itself, the AI interaction, and the results. But every other page on PAICE.work — About, Baseline, FAQ, Accessibility, system status, all our blog posts — remained English-only. If you navigated away from the assessment, the language switched back.

That is no longer the case.

As of today, the entire PAICE.work website is available in Latin American Spanish, French, and Brazilian Portuguese. These three languages have graduated from beta to fully supported.

What Changed

The April release translated the assessment flow: the conversational interface, prompts, scoring feedback, and result pages. This release extends translation to every public-facing page on PAICE.work:

Home, About, and Baseline — the pages that explain what PAICE measures, why it matters, and how organizational engagements work
FAQ — all 55 questions across 13 categories, fully translated with structural parity to the English original
Individual, Cohort, and History — assessment entry points and session management
Accessibility documentation — our WCAG assessment, EN 301 549 conformance, ADA/AODA compliance, and CAN-ASC-6.2 mapping
Blog - All ~150 posts (except our weekly updates, details below)
System status, Overview, and Papers index — every static public page

That is 17 fully translated pages per language, plus 809 UI strings covering every button, label, toast notification, error message, and navigation element in the interface.

What Was Not Translated (and Why)

Three core pages remain English-only for now: Security, Privacy Policy, and Terms of Service.

These are legal documents. Translating legal text is not a localization task — it is a legal task. A machine-translated privacy policy or terms of service could create obligations we did not intend or fail to preserve obligations we require. Each translated version needs review by counsel familiar with the relevant jurisdiction's language and legal framework.

We will translate these documents. But we will do it correctly, with in-language legal signoff, not as part of a website localization sprint. Until then, these three pages link to their English originals.

Blog posts are translated, with one exception: the weekly development updates. Those posts are time-sensitive and technical in nature — they document what shipped that week for the engineering audience following along. By the time a translation would land, the next update would already be live. Every other blog post, including the long-form pieces on methodology, industry applications, and product announcements, is available in all three languages.

Why This Matters

The original multilingual announcement made the case for native-language behavioral assessment: when a professional takes an AI collaboration risk assessment in a second language, you are measuring a blend of their behavioral reliability and their English proficiency. Those are different signals, and conflating them weakens the governance evidence.

That argument applies beyond the assessment itself. An organization evaluating whether to deploy PAICE across their Latin American offices should be able to read the methodology, review the FAQ, and understand the Baseline engagement model in the language their decision-makers think in. Forcing a Spanish-speaking compliance director to evaluate an English-only product page adds friction that has nothing to do with the product's value.

Full-site translation removes that friction. The evaluation experience is now native-language end to end: from the first page a prospect visits through the assessment itself through the results they receive.

What "Fully Supported" Means

During the beta period, we asked native speakers to report anything that felt unnatural — a phrase that missed the mark, a translation that sounded like a machine wrote it, a term that should have stayed in English. That feedback, combined with structured validation passes across the full UI string dictionary, content files, and FAQ corpus, produced the version shipping today.

"Fully supported" means:

Structural parity: every page, every UI element, every FAQ question that exists in English exists in all three languages
Brand term preservation: PAICE, PAICE Score, PAICE Pro, and PAICE.work PBC appear verbatim in every language — these are product names, not translatable concepts
Validated translations: each language passed behavioral validation confirming that translated content preserves meaning, register, and technical accuracy
Production routing: paice.work/es/, paice.work/fr/, and paice.work/pt/ serve fully localized experiences with no English fallback on any translated page

It also means these languages are now covered by our standard quality process. When we add a new page or update existing copy in English, the corresponding translations ship in the same release.

How We Translate

Our translation pipeline runs on an open-weight language model — Google's Gemma 4 — executing locally on our own hardware. No content leaves our infrastructure during translation. The model runs on a local GPU, processes the source text, and produces the translated output without any external API call.

This has a big practical advantage: it is fast and inexpensive and part of our publishing workflow. We can translate the full UI dictionary, all content pages, and the entire FAQ corpus across three languages in under an hour, which means translations do not bottleneck releases. Translations happen on the same machine where the source content lives.

For edge cases where the local model produces output that does not meet our quality bar, the pipeline automatically falls back to Claude Sonnet via the Anthropic API. This happens per-batch, not per-language — if one group of strings needs a second pass, only those strings go through the fallback. In practice, the local model handles the vast majority of translations without assistance.

The same pipeline that produced the initial translations runs on an ongoing basis. When new English content ships, the translation tooling detects the gap, translates the new strings, and the update goes out in the same release. There is no manual translation queue and no delay between the English version and the localized versions.

The Numbers

	English	Spanish	French	Portuguese
UI dictionary keys	809	809	809	809
Content pages	5	5	5	5
FAQ categories	13	13	13	13
FAQ questions	55	55	55	55
Blog posts	188	150	150	150
Public pages	17	17	17	17

Full structural parity. No missing strings. No placeholder text. No English leaking through.

Other languages?

Our original goal back in April was to have PAICE available in 18 European languages by the end of Q2, one month in advance of the EU AI Act's August 2nd effective date. However, as we've covered that deadline has since moved to December, 2027. We adjusted our output accordingly, focusing only on these Western Hemisphere languages, our core markets today.

We learned a lot along the way, and we've optimized so any new translations will go much faster. If there is significant interest, we would love to port PAICE to your language of choice. Please let us know!

For the languages shipping today, the next step is translating the legal pages (Security, Privacy, Terms) once in-language legal review is complete.

PAICE.work is available in English, Latin American Spanish, French, and Brazilian Portuguese. Take the assessment in your language or learn about PAICE for organizations.