Tamil-first citizen portals: a design checklist
Most portals are built in English and translated afterwards. That order shows. Here is a checklist that flips it.
· 3 min read · For departments and district offices building citizen portals
Most citizen portals are built in English first, then translated to Tamil as a late step. The translation shows: form fields that clip Tamil text, error messages that stay in English, PDFs that render Tamil as boxes. A portal that is genuinely Tamil-first is built the other way round, and it shows in how many people finish the form without calling the help desk.
Signs your portal needs this
- Your help desk gets calls asking what a field means, even though there is a translation next to it.
- Completion rates drop sharply for older applicants or for people applying from smaller towns.
- Your Tamil text is machine-translated once and never checked by someone who actually reads notices for a living.
What a good one does
- Designs the Tamil version first, or at least alongside English, so layouts are not squeezed to fit a shorter English word.
- Uses one clear font stack that renders correctly on the low-cost Android phones most citizens actually use.
- Keeps error messages, receipts and status updates in Tamil, not just the form labels.
- Lets a person switch language without losing what they already typed.
- Publishes notices and gazettes in both languages as separate, searchable documents, not one PDF with two columns.
Questions to ask any vendor
- Who checks the Tamil text — a translator, or someone with department domain knowledge?
- Does the search work in Tamil, including common alternate spellings?
- Is the portal usable on a small Android screen with an average network connection?
- What happens to a half-filled form if the citizen's data connection drops?
What it costs you
The honest cost is review time — someone who reads Tamil well needs to check every screen, not just the home page. Departments that budget for this upfront ship a portal citizens actually use. Departments that treat Tamil as a translation checkbox end up rebuilding it after complaints. It is cheaper, and far less embarrassing, to catch this before launch than after a citizen forwards a broken screen on social media. A short trial run with one taluk office, before a state-wide rollout, usually surfaces most of these problems early.
How we can help
We build government and public-facing systems bilingual from the start, using Sol, our Tamil, English and Hindi language model, for search, forms and citizen answers. See how we approach this — AI for government and public bodies — or talk to us with the portal you are planning.
