The best time to address bilingual or multilingual capability is at the point of procurement. Get it right early, and language becomes part of the solution. Leave it too late, and it often becomes a costly constraint.
The challenge is to describe language requirements in a way that is clear, practical and proportionate. Too little detail can leave critical user needs unresolved; too much prescription can narrow the market unnecessarily.
This guide helps you define multilingual requirements clearly and practically - so you can secure the functionality users need without deterring suppliers who may otherwise have the right solution.
What's Inside
- The challenges in procuring bilingual software
- Specifying bilingual requirements
- Encouraging suppliers to bid
Related Resources
Bilingual Technology Toolkit
Comprehensive resource to specify language requirements for procurement, development and audit.
Explore Toolkit
Guidance: Websites and Software
Detailed guidance on a broad range of considerations for bilingual technology (websites and software).
View Guide