BLO App Major Update: Why SIR Forms Are Being Rejected? Know the Solution to Logical Discrepancies

BLO App Update: Significant news has emerged for all Booth Level Officers (BLOs) across West Bengal. While the Special Intensive Revision (SIR) work is currently in full swing, a new update to the BLO App has become a cause for concern for many. Despite submitting numerous forms, many are being returned due to ‘Logical Discrepancies’. Below is a detailed guide on why this is happening and how to quickly resolve these issues.

New Feature in BLO App: Logical Discrepancies

A new option titled ‘Reverify Logical Discrepancies’ has been added at the very bottom of the ‘Special Intensive Revision’ section in the BLO App. Clicking here reveals that several previously submitted forms have not been accepted by the system and have been returned for specific reasons. The exact reason for the form being sent back for re-verification is mentioned under each name.

Main Reasons for Form Rejection

The system algorithm operates based on specific logic. Whenever there is a mismatch between the 2002 data and the current information, it is marked as an objection. The primary reasons for this include:

• Family Linkage or Gender Issues: When mapping voter card details with 2002 data, if the applicant is linked to someone other than the father (such as mother, grandfather, or grandmother), the system often misinterprets the gender. This is a major cause for verification flags.
• Father’s Name Mismatch: Forms are being returned if the father’s name on the current EPIC (Voter Card) does not match the father’s name in the 2002 data. Often, the hardcopy list of 2002 might have the full name, but the online database might only show the surname (e.g., ‘Dutta’ or ‘Roy’), which causes a mismatch with the current full name.
• Spelling Differences: Even minor spelling variations are causing issues. For instance, if the name was ‘Narendra Nath’ in 2002 and is ‘Narendranath’ currently, the system might identify them as different individuals.
• Age-Related Inconsistencies: If the age gap between the applicant and the person they are linked to (parent) is less than 18 years, it is treated as a logical error. Additionally, if someone over 45 years old claims their name was not present in 2002, that record also falls under scrutiny.

Solutions and Actions for BLOs

Provisions have been made within the app to resolve these issues. BLOs need to take action according to the specific situation:

1. If Information is Correct (No Action Required): If the BLO verifies that the applicant’s data and family relationships are factually correct (e.g., linking with the mother is valid in that specific case), there is no need to worry. In such cases, selecting the ‘No Action Required’ option and clicking ‘Yes’ will update the record.

2. Document Upload: If it is found that the name appears incomplete in the 2002 data due to a system error (e.g., only the surname is visible), one must go to the ‘View’ option and upload supporting documents (such as an Aadhaar card or a copy of the old voter list with the full name) to update the information.

3. Correction of Information (Edit): If there is a genuine error in the name spelling or phone number, it must be manually corrected using the ‘Edit Detail’ option.

Warning: Technical Glitch in the App

Currently, a significant technical issue or ‘bug’ has been observed in the BLO App. When attempting to select or click on the first person’s name in the list, the second person’s profile opens automatically. This glitch poses a serious risk of accidentally altering someone else’s data while intending to work on another.

Workaround: To avoid this problem, experts suggest starting the work from the very bottom or end of the list instead of the top. Alternatively, clicking on the name immediately preceding the target name may open the desired profile. Special attention is required to ensure no errors occur during this process.