Video summary

Anomaly Voter के साथ BLO की खतरनाक गलती || महाराष्ट्र SIR (21) | #sir

Main summary

Key takeaways

News and Commentary

Main issue discussed (Maharashtra SIR voter “anomaly” category)

The video addresses Maharashtra’s ongoing SIR (Special/State Integrated Revision) process where admission/enumeration forms are being filled.

A major concern raised is that a large share of voters—claimed as 50–60%—have been placed under an “anomaly” category (described as suspicious/doubtful voters).

The speaker argues that the key problem is that BLOs (Booth Level Officers) often don’t adequately explain:

  • why a voter was marked anomalous
  • what documents are required for removal from that category
  • how/when those documents must be uploaded

Responsibility and consequences (BLO vs voter)

The speaker emphasizes that BLOs must collect and upload required documents immediately; otherwise voters may:

  • have their form rejected, and/or
  • see their name removed from the draft list

It is asserted that this is a software-based system, meaning hard-copy documents won’t be accepted later.

The video also states that the corporator should ensure BLOs collect and upload documents for every anomaly-category voter.

How voters can exit the anomaly category (examples of anomaly sub-cases)

The speaker lists several anomaly types where a voter can be cleared once the correct documentation and/or remapping is done:

  1. Parents/children mapping issues (more than 3 children mapped incorrectly)

    • Some cases involve mapping where only a limited number of voters/children are linked to a parent.
    • After remapping so that children are mapped to the appropriate mother/father, the voter’s anomaly status can be removed automatically when the BLO uploads the document.

  2. Old mapping with uncle/relative changed to another relative

    • If mapping was originally done with one relative (e.g., uncle/elder brother) and later changed incorrectly, BLO verification and correct remapping can remove the voter from the anomaly category.

  3. Age-gap related anomalies

    • Example: a very large age gap between father and child leads to anomaly classification.
    • Suggested fix: remap with the mother (reducing the age mismatch) or perform mapping consistent with family records.

  4. Spelling/name/surname differences (mismatch from the 2002 list)

    • Voters whose names/spelling/age don’t match the earlier list are also placed under anomaly/NML.
    • The speaker claims they can be removed by linking school certificate/TC + Aadhaar (uploaded properly).
    • It is also stated that the EPIC/ePAC number was generated by the system based on the older list.

Critical instructions to voters when filling forms

The speaker repeatedly stresses that documents must be uploaded at the same time as the enumeration/admission process.

For voters with unmapped relatives (where relatives/parents/grandparents aren’t listed in the 2002 data):

  • The enumeration form has a “relative” column.
  • The voter must enter the name of any relative whose name exists in the 2002 list.
  • Leaving the relative column blank may cause the voter to be flagged again as a discrepancy (logical discrepancies).

The speaker also claims that during verification, the ERO can accept the enumeration form using specified documents, and the voter can be included in the draft voter list once requirements are satisfied.

Overall message/opinion

The central claim of the video is that many anomaly-category voters are stuck due to BLO non-explanation and/or failure to upload documents correctly, rather than voter mistakes.

It urges BLOs, corporators, and voters to follow the process precisely because missed uploads/document handling cannot be fixed later within this software workflow.

Presenters / Contributors

  • Sheikh Imtiaz Ahmed — speaker/presenter, “Imtiaz Ahmed Official Vision Point”

Original video