The Real Reason Tamil Nadu Doesn't Trust an Empty Text Box

The Data Problem Hiding Inside a Text Box Scheduled Castes and Scheduled

Tribes have never been counted through an open text field. Their enumeration draws on fixed lists notified under Articles 341 and 342 of the Constitution - a respondent picks from a defined set and the Census produces clean, tabulable categories every time.

Backward Classes have never had that structure in a Census. When the 2011 Socio-Economic and Caste Census tried open self-declaration for caste, it produced over 46 lakh distinct entries - spelling variations, sub-caste names, regional titles - a dataset so fragmented it could never be meaningfully tabulated and much of the SECC caste data was effectively shelved as unusable.

Tamil Nadu's resolution is not really a demand for "recognition" in the abstract; it is a demand to avoid repeating a specific, already-documented data failure.

Why a Drop-Down List Is a Federalism Question, Not Just a Design Choice Here is

where the constitutional dimension enters. Unlike the SC/ST lists, which exist as a single central Presidential Order framework, BC/MBC/DNC lists are notified by both the Centre and individual States - and they don't always match.

Tamil Nadu's own reservation architecture, covering 69% of state government posts, rests on state-specific BC and MBC classifications that a Centre-only pre-loaded list might not fully capture. So the resolution's request - "pre-load the lists... notified by the Central and State governments"

• is doing real constitutional work: it is asking the Centre to build Census methodology that respects state-specific classification authority over Backward Classes, rather than importing a single national list that would flatten state-level distinctions States have spent decades codifying.

What "Accurate" Actually Requires Here This is the

detail a general "caste census, yes or no" framing misses entirely: the debate is not about whether OBCs should be counted - virtually every political actor now agrees they should be - it is about whether counting them through an open column (fast to design, nearly impossible to tabulate) or a structured, state-plus-Centre list (harder to build, but the only version that produces usable data) is used.

Tamil Nadu's Assembly is arguing, with the 2011 SECC as its evidence, that the format of the question determines whether the answer is ever usable for policy at all. For the exam, the sharper insight is this: enumeration methodology is itself a social-justice instrument - a badly designed question can technically "count" a community and still produce data too fragmented to ever inform a single reservation or welfare policy decision, which is exactly the trap the 2011 SECC fell into and Census 2027 is now being asked not to repeat.