2016 Puducherry Legislative Assembly election
Union territory election in India
The legislative assembly election in the Indian union territory of Puducherry was held on 16 May 2016 to elect members of the 30 constituencies in the non-contiguous territory to constitute the Fourteenth Puducherry Legislative Assembly.
Background
It is a legal requirement that the election must be held at an interval of five years, or earlier if the assembly is dissolved by the President. The previous election was conducted on 13 April 2011 and its term would have naturally expired on 2 June 2016. The election was organised and conducted by the Election Commission of India (ECI).
The Indian National Congress and the Dravidia Munnetra Kazhagam were in an alliance and contested 21 and 9 seats respectively. Ruling AINRC, BJP & AIADMK will contest separately.
The polling booths in three Assembly constituencies in Puducherry (out of total 30 segments) were equipped with Voter-verified paper audit trail (VVPAT) machines along with EVMs.
Parties and alliances
Prominent Parties
Other Parties
NOTE: A total of 374 candidates (including independents) were in the fray for the election, of whom 305 forfeited their deposits.
Candidates
Voting
The election was held on 16 May 2016 in a single phase and 84.11% voting was recorded. The votes were counted on 19 May and results were declared on same day.
This brief starts where responsible research should: with the source description of “2016 Puducherry Legislative Assembly election” as union territory election in India. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as union territory election in India. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Sep 25, 2026. The linked authority identifier is Q23930036. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2016 and 2011.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “2016 Puducherry Legislative Assembly election”, its source revision and the description used here.
- Expand the search: follow 2016 Puducherry Legislative Assembly election primary sources, 2016 Puducherry Legislative Assembly election archive and Puducherry research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “2016 Puducherry Legislative Assembly election”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “2016 Puducherry Legislative Assembly election” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.