Odia Language Deadline with Capacity Gaps
You are the administrative head of a state department in Bhubaneswar. A 45-day deadline has been set to make Odia the language of official correspondence in all district offices. An internal audit finds that 58% of current files are in English; only 22% of 180 staff can draft a formal letter in Odia; the online grievance portal has no Odia font; and 1,100 pending public complaints include 300 from elderly citizens who read only Odia. The translation unit has three people and a backlog of 4,000 pages. Staff unions say Odia typing is slower and that errors will invite penalties. A newspaper reports that a woman's pension application was rejected because the clerk could not read her Odia attachment. The state has issued no extra funds, but the deadline is public and the minister has promised compliance.
1. Design a 45-day implementation plan that does not deny services.
Read the worked answer
Reasoning: The capacity numbers make a full switch in 45 days unrealistic: only 22% of staff can draft formally in Odia, the translation unit is tiny, and the portal cannot display Odia. A coercive order would produce errors, delays and more rejections like the pension case. The goal should be a credible, phased start that protects the public's right to be understood.
Plan: In days 1–10, fix the portal font, issue bilingual templates for the 20 most common public forms, and set up a rapid reading help desk for Odia attachments. In days 11–25, make all public-facing notices, receipts and grievance acknowledgements bilingual; train staff in functional Odia typing with practice files; and prioritise translation of pending complaints and pension-type cases. In days 26–45, require Odia or bilingual correspondence for district public offices, while internal technical files may continue in English with an Odia summary. Do not impose penalties during the transition. Track rejection rates, complaint disposal time, translation backlog and the number of staff trained. Report honestly that full compliance will need more translators, Unicode software and training in the next phase.
2. How will you handle staff resistance and the pension case?
Read the worked answer
Reasoning: Staff resistance is partly rational: they fear slower work and punishment for errors. The pension case shows the human cost of language exclusion, so it must be corrected immediately rather than used only as an example.
Pension case: Retrieve the application, have the Odia attachment read and acted upon, issue the pending pension if eligible, and send a written apology explaining the correction. Record it as a language-access grievance and review similar pending cases.
Staff: Meet unions and explain that the first 45 days are a learning phase with no punitive targets. Provide short practical training, bilingual templates and typing support. Recognise offices that improve public-facing service. Address workload by hiring temporary translators or redeploying Odia-literate staff to reading desks. Make clear that language compliance is a service obligation, but errors made in good faith during training will be corrected, not punished. This lowers resistance while keeping the policy credible.
3. What indicators will show success by day 45?
Read the worked answer
Reasoning: Success should be measured by public access and service continuity, not by the number of files converted. A narrow file-count target could push staff to produce poor Odia and delay decisions.
Indicators: At least all public-facing notices, receipts and grievance acknowledgements are bilingual; the pension-type rejection rate due to unreadable language falls to near zero; the portal displays Odia correctly; the 4,000-page translation backlog is reduced by a stated proportion, with pending public complaints translated first; at least half of district staff complete basic Odia drafting training; average grievance disposal time does not rise; and a sample audit shows that citizens can file and understand replies in Odia. Publish a simple progress note and identify the remaining gaps, especially translator strength and software, for the next phase.