Translating Circulars Without Losing Legal Meaning

A registrar asked for 'automatic Hindi versions of every circular by evening'. The model was fluent. It turned 'may be permitted by the competent authority' into a Hindi sentence that read as if permission were already granted. Three departments issued the draft. A student union quoted it. The English original still said may.

That is not a wording quibble. That is a rights change produced by a synonym.

Universities, secretariats and PSUs are under real pressure to speak more languages faster. The Official Languages Act already makes specified Union instruments bilingual in Hindi and English. None of that pressure is a reason to let a decoder-only draft become the copy that people obey. This guide splits instruments from pamphlets and tells you where a model may sit.

What the Act actually asks — and what it does not

Section 3 of the Official Languages Act, 1963 keeps English alongside Hindi for official purposes of the Union and for parliamentary business. Section 3(3) requires both Hindi and English for listed classes of instruments: resolutions, general orders, rules, notifications, certain reports and press communiqués, and specified contracts, licences, permits, notices and tender forms.

That is a duty on the Union's own issuing process. It is not a product specification for an agent. It is not a licence to generate twenty-two unofficial versions and call the portal compliant. State universities and state departments sit under state official-language law plus their statutes. Read those before you buy a language pack.

Where Hindi and English versions are both authentic, alignment is a legal task. Where only one version is authentic, the other is a service. Write which is which on the file. Models blur that distinction by sounding equally official in both.

Split the instrument before you split the model

Class A: creates or changes a right, a fee, a penalty, an eligibility, a date of commencement, or a delegation. Human legal pass required. Model may draft. Model may not publish.

Class B: explains a Class A instrument to the public. Human pass on operative facts. Model may draft the explanation. Link the authentic text.

Class C: logistics — tent dates, mess menus, shuttle timings, webinar links. Lighter review. Still lock names and numbers.

If you cannot classify a circular in thirty seconds, treat it as Class A until a competent officer says otherwise.

What a model is allowed to touch.

Class	Example	Model role	Publish rule
A — operative	Fee notification, exam ordinance, delegation OM	Draft only, glossary-locked	Human legal sign-off, bilingual authentic if required
B — explainer	Student FAQ on the same fee notification	Draft plus retrieval of the authentic text	Label unofficial if not signed; link the instrument
C — logistics	Hostel mess timing, bus roster	Draft and, if risk is low, assist publish	Numbers locked; officer still owns the notice board

The words that must not drift

Shall and may. Notwithstanding. Provided that. Without prejudice. Competent authority. Deemed. From the date of publication. As amended from time to time. These are not style. A glossary should pin them to the department's accepted equivalents, including the official Hindi or regional forms already used in earlier authentic texts.

Scheme titles, section numbers, form numbers and URLs do not translate unless an official short title exists. Leave them. A model that helpfully expands an acronym into the wrong expansion has rewritten the instrument.

Dates and amounts stay in the same numerals the authentic text used, unless your official-language practice says otherwise. Do not let a model localise a figure into words and lose a zero.

A safe pipeline on a campus or in a secretariat

Retrieve the authentic text and any existing official translation memory first. Draft with the glossary locked. Highlight every operative sentence for the legal or registrar pass. Store the model hash, the glossary version and the officer's acceptance. If you later fine-tune on accepted pairs, you are building a translation memory with an audit trail, not a creative writer.

Do not send unpublished circulars that name students or staff to a hosted translation API unless the transfer note is written. A draft ordinance is still personal data when it lists a roll number.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

We do not have Hindi officers on strength.

Then you cannot honestly issue an authentic Hindi instrument. Buy human capacity or keep one authentic language and label the rest unofficial. A model is not a gazetted translator.

BHASHINI already translates government content.

Public tools can draft. They do not take the registrar's or the under-secretary's responsibility. Use them inside the same class system.

Students only read the unofficial page anyway.

That is an argument for a better human pass, not for skipping it. Reliance follows the page they can read.

Legal review will make language support too slow.

Review Class A. Speed up Class C. If everything is urgent and operative, you do not have a translation problem. You have a drafting-discipline problem.

Who signs

A model does not sign. A registrar, an under-secretary or a warden signs. If your workflow has no named signer for Class A, you do not have a translation protocol. You have an auto-publish accident waiting for a student union.

Put the signer in the same place you put the glossary version. A later inquiry will ask both questions in the same minute.

Two weeks to a circular-translation protocol

Write the protocol once. Reuse it for every model, including ours.

1. Day 1–2: inventory last semester's circulars. Tag Class A, B and C with the registrar or the section officer.
2. Day 3: collect official bilingual pairs you already issued. That is your first glossary and memory.
3. Day 4–5: lock shall/may and the ten most dangerous phrases in both languages.
4. Day 6: write the publish rule. Who may press send on each class.
5. Day 7: decide where the model runs. No undeclared hosted hop for unpublished instruments.
6. Day 8–9: trial the pipeline on three old circulars whose official translations already exist. Diff them.
7. Day 10: write the label for unofficial pages and the link back to the authentic text.
8. Day 11–12: brief wardens and section officers. WhatsApp is a publishing channel.
9. Day 13–14: put the protocol in the file. Refuse any vendor who wants the model to auto-publish Class A.

How this shows up in the file

The note should say: machine translation is a drafting aid. Authentic text remains what the competent officer issues under the Official Languages Act, state official-language law or the university's statutes. Class A instruments require a human legal pass. Unofficial translations are labelled and linked.

Attach the class list, the glossary version, and three diffs from the trial.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation, linguistics or engineering advice. Confirm against the current Gazette, Official Languages Act and Rules, state official-language law, GIGW, RPwD Act, DPDP text and Rules, CERT-In directions, departmental manual and your counsel before you file it.

How to test this with real speech, not staff English

“Translating Circulars Without Losing Legal Meaning” fails in the field if you only tested officers. A P3 University should hear a first-generation student, a rural caller, or a Hinglish grievance before claiming “government document translation AI”.

A circular is not a paragraph. It is duties, dates and defined terms. Translate the pamphlet with a model if you must. Do not let the model become the authentic text. Twenty-two scheduled languages is a Constitution fact, not a model fact. Script support is not language support. Official language rules may require bilingual output even when the model prefers one script.

• Name the languages and scripts in the eval set.
• Include code-mix and scheme-name tests.
• Measure comprehension, not BLEU alone.
• Design a human fallback when language fails.

Close this loop before the next CAB

Put “Translating Circulars Without Losing Legal Meaning” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P3 University, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “government document translation AI” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.