Beyond the classroom: How school districts are rethinking translation

Translation isn't just a corporate problem. Across the United States, public school districts are responsible for some of the most complex and high stakes language access work out there.

Individualized Education Program (IEP). Special education reports. Enrollment documents. Parent communications. And for many districts, providing meaningful access isn't simply a matter of good practice. Federal requirements, including Title VI language access obligations and the Americans with Disabilities Act (ADA), place real responsibilities on public schools to ensure students and families can effectively access essential services and information.

Yet the reality on the ground is very different. Many school districts are still managing this work manually, relying on staff, spreadsheets, email, and disconnected translation workflows to keep up with an ever growing volume of content. At the same time, they're working within tightly controlled state and, in some cases, city funded budgets, where adding new technology can be difficult to justify, even when the cost of doing things manually is already significant.

We sat down with Julie Perez, Business Development Manager at memoQ, who spends her days talking to language access coordinators, translation supervisors, and administrators at school districts nationwide, to understand what's really happening behind the scenes, why these teams are under so much pressure, and what it could look like to rethink translation as a strategic part of how schools serve their communities.

What got school districts on your radar in the first place? 

"Honestly, the scale of the need. People tend to think of translation as something companies deal with, expanding into new markets, and localizing a product. But districts are dealing with real, ongoing translation demand, and a lot of it is legally required. Students with disabilities, whether that's ADHD, dyslexia, or other learning differences, are protected under federal law, and there are similar protections in other countries too. Part of that protection means families need access to documents in their own language. If a parent doesn't read English, their child's Individualized Education Plan must be translated so they can participate in decisions about their kid's education.

On top of that, districts serve immigrant and refugee families who need everything from enrollment forms to report cards translated. This isn't a nice-to-have. It's often mandated."

Who inside a district actually owns this problem? 

"It varies. Some districts have a language access coordinator, sometimes a person who is also a working translator themselves. Others have a small in-house translation team, or one person juggling translation alongside other admin duties. A few have a dedicated department that oversees every translation request across the district, both general and special education.

What's consistent is that almost none of them started with proper tools. Most were working entirely in Word and Excel. Manually recreating IEP templates for every student. Copying and pasting between documents. A few districts send work out to contractors with no shared translation memory or terminology consistency in place. It's slow, and it's hard to keep quality and terminology consistent across that many language pairs. On top of that, outsourcing translation gets expensive fast, and these teams are already working with tight budgets. Those budgets are usually set annually, so bringing in new software takes real planning and evaluation before it gets approved."

Can you give a sense of what that actually looks like day to day? 

"Sure. Take a district on the East Coast I spoke with. Their educational translation and interpretation department oversees requests for 26 schools. One of their specialists described spending huge amounts of time just recreating an old IEP template from scratch for every new document, then manually sending it out to a translator. That's before any actual translation happens. And their volume keeps increasing too.

Similarly, take a district in the Pacific Northwest with 28 schools and around 20,000 students, supporting close to 100 languages and dialects between them. Their language access coordinator was doing everything for IEPs manually and knew she needed to modernize. She'd used other TMS solutions in a previous role and had heard good things about memoQ.

Then there's a district in Maryland where the translation team didn't have any TMS at all. They were assigning translations to outside contractors with no shared translation memory, no terminology consistency, nothing. Now they're trying to update that in-house work, while translating special education documents faster, and making their website accessible in more languages. They can do more because they have the right tool with memoQ."

What languages are we talking about? 

"It depends heavily on the community the district serves. English into Spanish is close to universal. Beyond that, we've seen Chinese, Korean, Vietnamese, Portuguese, Haitian Creole, Cape Verdean Creole, Arabic, Russian, and K'iche', among others. Some districts are supporting a dozen or more language pairs at once."

Does this extend beyond K-12, into higher education as well?

"It shows up in higher education as well, just differently. One university we spoke with has an in-house team handling internal translation work like administrative memos, and they’ve built up a large backlog because they’d rather keep that work in-house than send it to outside vendors. Interestingly, this same institution used to teach translation technology courses using tools like memoQ and Trados, so their staff already had some familiarity with translation management systems going in. That translation teaching work has since moved to a different department, but the institutional knowledge is still there."

A lot of these districts sound resource-constrained. Does that change how you approach the conversation?

"Yes and no. We always start by listening to what a partner actually needs, no matter who we're talking to. But with school districts, we lean into that even more, knowing they're often working within a specific set of circumstances, so it's more about tailoring.

We've gotten too tied up in the details before. Talking specs and functionality when what these teams actually want to know is: can this make my job less overwhelming? People in this space often already trust memoQ, or have heard good things from peers, before we even get on a call. What they need from us is less about convincing and more about understanding what they're up against and showing how we solve it."

If a district reading this is nodding along, what's the actual next step?

"Get on a discovery call. That's really it. We don't push trials as the default first move, because for a team still using Word and Excel, a trial without context can feel like more homework. A conversation first, understanding their language needs, their document types, their team size, and especially their challenges, gets everyone to the right starting point faster."

Working in language access for a school district or university and dealing with IEPs, special education documents, or multilingual communications? We'd love to hear what you're navigating.

Book a discovery call to talk through it.