Counting Identity: Why the Census Should Reflect Tripura, Not Just Category It

DA Editorial Desk (Sara Debbarma)

The Centre has clarified this week that the 2027 Census will not publish separate statistics for the ‘Tripura’ tribe or its mother tongue, despite a formal representation from the state’s own Directorate of Census Operations seeking exactly that. The reasoning offered by the Registrar General’s office is procedural and, on its face, unremarkable: Scheduled Tribes are enumerated strictly according to the officially notified list, and ‘Tripura, Tripuri, Tipra’ already appears at serial number 18 of that list. No rule is being broken. But the fact that a rule is being correctly followed does not settle whether the rule itself serves the people it is meant to count.

This is worth sitting with, because census categorisation is never merely a technical exercise. It is the state’s primary instrument for deciding whose needs are visible enough to plan for. When a community’s population, literacy, occupational patterns and linguistic vitality are folded into a broader Scheduled Tribe aggregate rather than published on their own terms, that community does not disappear from India — but it does disappear from the data that shapes budgets, welfare targeting, and language-preservation policy. A state government trying to design a scheme specifically for Tripura tribe households, or an education department trying to assess how many children speak Kokborok or related dialects as a mother tongue, is left working from estimates and local knowledge rather than the authoritative national count that exists for many other communities.

The Directorate of Census Operations in Tripura clearly understood this when it made its request, and its instinct deserves more sympathy than a one-line bureaucratic rejection has given it. The ‘Tripura’ tribe is not a marginal statistical curiosity — it is the state’s largest indigenous community and the one after which the state itself is named. That a request for its own government to see its own founding community counted distinctly could be dismissed by citing a June communication and a serial number suggests a system optimised for administrative consistency rather than local relevance.

To be fair to the Centre, there is a legitimate concern buried in its caution. Opening the door to disaggregated publication for every sub-group within every notified Scheduled Tribe list, across every state, risks a census exercise that becomes unmanageable, inconsistent, or open to political pressure over which categories deserve separate counting. Uniformity has its own value, and the Registrar General’s office is not wrong to guard it.

But uniform rules can still allow for reasoned exceptions, particularly when a state’s own census machinery — the body best placed to know what data would actually help — is the one asking. The Centre’s response need not have been a flat no. A more constructive path would have involved examining what specific planning or welfare purposes the disaggregated data was meant to serve, and whether a pilot exception, rather than a blanket refusal, might have met both the Centre’s concern for consistency and Tripura’s concern for visibility.

The 2027 Census is still ahead of us. There remains time for this conversation to continue, and Tripura’s political representatives — across party lines — would do well to keep raising it. A census that undercounts the specificity of the people it is meant to serve is not neutral bookkeeping; it is a quiet erasure, however unintentional, of exactly the community whose name the state carries.

Scroll to Top