Tone and Formality in Government Communication

A housing helpline agent, told to be friendly, switched to a casual Hindi that a senior citizen heard as a tout. Another agent, told to be official, produced noting-style Hindi on WhatsApp that a low-literacy caller could not finish. Both vendors said tone could be 'tuned in the prompt'. Neither had examples in the eval.

Indian public language is a stack of registers: the Gazette, the noting, the counter, the SMS, the political dais, the family. An agent that blends them will either offend or over-promise.

This guide is how to specify tone and formality as scored rows, not as adjectives in a statement of work.

Registers you already have

Authentic instrument: formal, bilingual where the Act requires, no jokes, no first names. Officer noting: Manual of Office Procedure habit, citations, restrained verbs. Counter and helpline: respectful second person, short, next step first. SMS and WhatsApp: shorter still, identifiers locked, no fake intimacy. Internal draft: can be rougher, never sent as-is.

Write which register the agent is in on every workflow. A model left to guess will pick the internet.

The pronoun is policy

In Hindi and several other Indian languages, second-person choice and verb agreement mark age, status and distance. Default to the respectful form in citizen replies unless a documented campaign uses another. Do not let the model 'match the citizen's casualness' on a benefits line. A citizen may be casual. The State is not their cousin.

In English, the risk is different: American customer-support warmth, emoji, and 'happy to help you with that!' in front of a rejection. Rejections must be plain, cited and kind. They must not sound like a subscription cancellation.

Tone fails to put in the pack.

Fail	Example	Why it matters
False intimacy	Casual pronouns on a pension line	Sounds like a tout; erodes trust
False order	Helpline SMS that reads as a Gazette command	People obey unofficial pages
False promise	'Aapko zaroor mil jayega'	Creates a right the officer cannot honour
Blame	'Aapne galat form bhara'	Citizens stop using the channel
Gender guess	Wrong participle from a name	A personal insult produced from data

Promises and empathy

Empathy is allowed. A promise is a legal event. 'We understand this is hard' is a tone. 'You will receive the amount this week' is a commitment unless the MIS says so. Lock commitments to retrieved facts. Ban stock promises from the decoder.

Empathy that names a medical or caste fact the citizen did not use in this turn is not empathy. It is a leak.

Eval and ownership

Add a tone slice to the departmental pack: ten items that should be rejected for intimacy, harshness, promise or blame, even if the facts are right. The language cell and the public-information officer jointly own the style card. The model vendor does not.

When a political office wants a warmer campaign voice, version it. Do not silently overwrite the default helpline voice for a month and forget to switch back.

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.

Young users want casual language.

Some do. A benefits line still defaults to respectful. You can version a youth-campaign voice with a start and end date. You cannot let a model guess who is young.

Tone is subjective. We cannot fail a bid on it.

False promises, blame, gender guess and the wrong register on a speaking order are not subjective. Fail those. Argue about the rest in the style card.

Our officers themselves write casually on WhatsApp.

Officers can be trained. The published number cannot freelance. If officers post casually, that is a separate discipline problem. Do not automate it.

A larger model has better style.

A larger model has more styles. Without a card and an eval it will pick one you do not want. Style is specified, not discovered.

Promises are not tone

Warmth is a register. A date of payment is a fact. Mixing them is how a kind sentence becomes a representation the officer cannot honour. The style card should say so in one line that a model can be failed on.

If a political office wants warmer copy for a campaign week, version the card and put an end date. A permanent 'friendly' default on a rejection line is how the corridor fills with sweets.

Ten days to a style card

Steal last month's worst three replies and last year's best official SMS. That is the curriculum.

1. Day 1: name the registers you actually publish in.
2. Day 2: write the default pronoun and the gender-guess ban.
3. Day 3: write the promise ban and the rejection verb.
4. Day 4: collect good and bad examples per register.
5. Day 5: add a ten-item tone slice to the eval.
6. Day 6: bind register to workflow in the agent config.
7. Day 7: stop prompt inheritance across workflows.
8. Day 8: brief the PIO and the language cell as joint owners.
9. Day 9: sit the current agent. Fail intimacy and promises even when facts are right.
10. Day 10: file the style card version.

How this shows up in the file

The note should say: register is specified per workflow. Citizen defaults are respectful, not intimate. Commitments are retrieved, not generated. Gender is not guessed from a name. Tone fails are scored. This card is owned by the PIO and the language cell.

Attach the card and the ten-item slice.

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

“Tone and Formality in Government Communication” fails in the field if you only tested officers. A P1 CIO/CTO should hear a first-generation student, a rural caller, or a Hinglish grievance before claiming “government communication tone AI”.

Tone is not decoration. In Indian languages it marks respect, distance and whether a sentence sounds like an order. Specify register the way you specify language. 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 “Tone and Formality in Government Communication” 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 P1 CIO/CTO, not “the vendor.”

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

What must be true before you file this

If “Tone and Formality in Government Communication” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “government communication tone AI”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “government communication tone AI” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

What the next file must contain

“Tone and Formality in Government Communication” earns a line in the noting only if a P1 CIO/CTO can attach proof of “government communication tone AI.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “government communication tone AI.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.