Nearshoring has moved from a strategic slide deck to an active line item. New foreign investment into Mexico surged roughly 200% in the first nine months of 2025, the country closed the year with a record $40.87 billion in FDI, and a Deloitte study found 62% of US manufacturers are either already relocating production to Mexico or actively considering it. Mexico climbed six spots — from 25th to 19th — in Kearney's 2026 FDI Confidence Index, one of the largest single-year gains in the ranking.
Every one of those moves creates the same organizational problem, and almost nobody is talking about it: the company now has two workforces, and most HR tools were built for only one of them.
Two workforces, one company
On one side is the US-based corporate team: leadership, finance, sales, and often a growing group of remote hires. They think in English, report in English, and expect the same engagement tooling — pulse surveys, eNPS, manager dashboards — that any US company uses.
On the other side is the Mexican plant or office: hundreds of hourly or salaried employees who need to be surveyed in Spanish, and whose employer is legally required to identify and act on psychosocial risk factors under NOM-035-STPS-2018. This isn't optional — it's a federal labor standard with real inspection risk (see our compliance overview for the fine ranges).
Most companies end up running two completely disconnected processes: an engagement survey tool for the US side, and either a manual NOM-035 project (a consultant, a spreadsheet, a one-time assessment) or nothing at all for the Mexican side. Neither system talks to the other. HR ends up maintaining two vendor relationships, two data sets, and two reporting cadences for what is, organizationally, one company.
Why the usual tools don't solve this
Enterprise engagement platforms built for the US market — the Culture Amps and Lattices of the world — have no NOM-035 content and no Spanish-first workflow; compliance in Mexico is simply outside their scope. On the other side, Mexican compliance consultants who specialize in NOM-035 typically don't offer continuous pulse surveys, eNPS tracking, or an English-language dashboard a US-based VP of People would recognize.
The result is a gap in the middle: nobody sells "one platform, one invoice, both sides of the border." Companies patch it together themselves, usually badly, because the compliance side gets treated as a once-every-two-years project instead of a living program — which is exactly the failure mode most NOM-035 audits catch.
Picture a 400-employee tier-1 automotive parts supplier: engineering and sales run out of a Michigan headquarters, while a manufacturing plant of roughly 280 people operates in Nuevo León. HQ wants a monthly pulse on engagement and manager effectiveness. The plant is legally required to run a NOM-035 psychosocial risk assessment and keep records on file for STPS.
Run separately, that's two vendors, two logins, two languages of reporting, and a real risk that the compliance side quietly lapses once the initial project ends. Run as one program — the Spanish NOM-035 instrument and the English engagement pulses in the same dashboard, under the same escalation rules — HR gets a single view of both workforces, and the psychosocial risk data doubles as the documentation an inspector would ask for.
This is a composite scenario for illustration, not a named Bloomder customer.
What a binational pulse program actually looks like
One question bank, two languages
HQ runs the English engagement and wellness pulses; the plant runs the official NOM-035 instrument in Spanish, which already covers the nine risk-factor domains the norm requires (workload, leadership, work environment, and the rest). Both live in the same organization, and both feed the same dashboard.
One anonymity standard, everywhere
A US team of 12 and a Mexican plant floor of 280 both deserve the same protection: results only surface once enough people have answered to prevent re-identification. Compliance shouldn't come with a lower privacy bar than the corporate side.
One escalation path
Whether a risk signal comes from an engineering team in Michigan or a production line in Nuevo León, it should reach the same dashboard and the same alerting logic — not two separate email inboxes that nobody cross-references.
Documentation that survives an audit on either side
US-side reporting (board decks, eNPS trend lines) and Mexico-side reporting (NOM-035 records, evidence of corrective action) are different documents for different audiences — but they should come from the same underlying data, generated automatically instead of assembled by hand before an inspection.
How Bloomder is built for this
Bloomder ships the official NOM-035 Guia de Referencia III questionnaire (72 items, in Spanish) next to its English engagement templates, in the same organization and the same dashboard: one subscription, the same k-anonymity threshold, the same AI-generated insights for both sides of the border. The platform interface itself is English today; a Spanish interface is on the roadmap.
Run engagement and NOM-035 compliance from one platform
See how a binational pulse program works — no generic script, just your use case.
Book a Demo →