Language & jurisdiction
What changes between one government and the next.
A platform sold internationally is either built around the things that differ between jurisdictions, or rewritten for each one. These are the differences that matter most, and where each is handled.
Jurisdiction
Six things that are never the same twice.
Each of these is settled during assessment. Treating any of them as a late-stage configuration problem is how an international platform becomes six unrelated forks.
Official languages and scripts
Many governments operate in more than one official language, and the second is often in a different script or direction. Retrofitting that is expensive; assuming it from the first screen is not.
- Multiple official languages
- Right-to-left interfaces
- Non-Latin scripts
- Bilingual documents and records
Data residency and sovereignty
Where public data is legally allowed to sit varies by country, and frequently by classification within a country. It is an architecture decision, not a hosting preference.
- On-premise and national data centres
- Sovereign and government cloud
- Air-gapped environments
- Cross-border transfer restrictions
Identity and authentication
Almost every jurisdiction has its own scheme for proving who someone is, and a citizen-facing service is only as usable as its weakest verification step.
- National ID and civil registry
- eID and smart cards
- Mobile and bank-backed identity
- Staff directory federation
Procurement and delivery models
How a public body is permitted to buy software shapes how it can be delivered — phasing, acceptance criteria and what counts as a milestone are set before design starts.
- Open tender and framework agreements
- Phased acceptance and milestones
- Pilot and proof-of-concept stages
- Source ownership requirements
Accessibility obligations
Public-sector accessibility is generally a legal duty rather than a quality goal, and the applicable standard differs by jurisdiction even where the substance overlaps.
- WCAG 2.2 AA
- EN 301 549
- Section 508
- National accessibility regulations
Records and retention law
What must be kept, for how long, and what happens at the end is set by archival and disclosure law — which makes retention part of the data model rather than a cleanup job.
- Statutory retention schedules
- Archival transfer obligations
- Freedom-of-information regimes
- Legal hold and disclosure
Locale
Handled in the platform, not per country.
Language is the visible part and the smallest. These are the dimensions that decide whether a system is usable by the people it was bought for.
Scripts and direction
Layout mirrors for right-to-left languages rather than being rebuilt, and non-Latin scripts get the type treatment they need instead of a fallback font.
- Latin
- Arabic (RTL)
- Bengali
- Devanagari
- Cyrillic
- CJK
Numerals
Digits are a locale decision, not a font substitution — and grouping differs even where the digits do not.
- Western Arabic (1,234)
- Eastern Arabic (١٬٢٣٤)
- Bengali (১,২৩৪)
- Lakh and crore grouping
Calendars and dates
Fiscal years, public holidays and the calendar itself vary, and a leave system that cannot express the local year is not usable.
- Gregorian
- Hijri
- Solar Hijri
- Buddhist
- Local fiscal years
The working week
Attendance, leave accrual and service-level clocks all depend on which days are working days, and that is not the same everywhere.
- Monday–Friday
- Sunday–Thursday
- Saturday–Wednesday
- Half-day conventions
Names and addresses
Name order, honorifics, patronymics and address structure differ enough that a single field layout excludes real people from a public service.
- Given/family name order
- Patronymic and mononym support
- Honorifics and titles
- Local address formats
Currency and units
Symbol placement, decimal conventions and measurement units are formatting decisions with financial consequences when they are wrong.
- Symbol position and spacing
- Decimal and grouping separators
- Multi-currency reporting
- Metric and local units
Worked example
One of these is demonstrated, not described.
The GovHRM preview carries a working language switch. It renders a non-Latin script, its own numeral system and a Sunday-to-Thursday working week — three of the dimensions above, in one interface, switchable in a click.
- Non-Latin script with its own type treatment and line height
- Numerals rendered in the locale’s own digits
- A working week that is not Monday to Friday
- Every tile, heading, axis and table header switching together
Why a demo rather than a claim
Every vendor’s brochure says the product is multilingual. Very few of them have been through the part where a heading in another script needs different leading, an uppercase transform has no meaning, a number is written with different digits, and a date picker has to start the week on a different day.
Rather than assert that we have, the preview does it in front of you. It is one language pair, not proof of every locale in the list above — but it is evidence of the layer that makes the rest of them tractable.
UXAtom GovTech
Tell us which jurisdiction you are in.
Official languages, where data has to sit, which identity scheme applies and what your accessibility duty is. Those four answers shape most of the architecture, and the conversation is more useful than a feature list.
Or email us directly at hello@uxatom.com