Updated October 4, 2026
Family Level Data Collection Form: Purpose and Submission Routes
What West Bengal's Family Level Data Collection form is for and how the official online and office submission routes work.
The Family Level Data Collection form is the citizen-facing data layer of West Bengal’s Social Registry. Its purpose is to build a household-level record that can be used across welfare systems instead of treating every scheme as a completely isolated database.
Why collect at family level?
The Finance Department says one of the major technical challenges is that different departmental databases do not share a single universal identifier. The Social Registry therefore uses a Family ID to identify the household and improve matching across schemes.
What kind of information is relevant
The exact public form can change, but the system is built around household identity and scheme eligibility. Government and portal material around the 2026 rollout references voter identity, Aadhaar, mobile contact and family-level details used for welfare verification.
How data is reconciled
Finance Department technical clarifications say the ration-card database is used as a base reference when reconciling records. That does not mean a ration card alone decides every scheme; each scheme still has its own eligibility rules.
Online route
The Government of West Bengal Annapurna Yojana page directs users to socialregistry.wb.gov.in for online submission. Because public modules may be changed during rollout, use only the options currently shown on that government domain.
Offline route
The same government scheme page lists BDO, SDO and KMC Ward offices as in-person submission locations. This is important when the online citizen module is unavailable or when a household record needs office-level correction.
Data-quality matters
A Family ID is only useful when members and identifiers are mapped correctly. Spelling differences, outdated mobile numbers, unmatched identity records or family members appearing in different departmental databases can create reconciliation problems.
Do not submit to lookalike forms
Family-level data can include sensitive identifiers. Only use the government domain or designated office. This informational site does not accept forms or documents.
Read the system overview for the technical context and the Annapurna document guide for the government’s mandatory document list.
Family-level design helps de-duplicate scheme records
The registry is meant to reduce the problem of the same household being represented differently in several welfare databases. Finance Department material discusses both real-time and periodic de-duplication and says the lack of a common identifier is the biggest existing challenge.
Ration data is a reference, not universal eligibility
The ration-card database is used as a base database for reconciliation, according to the technical clarifications. That does not make possession of a ration card the sole eligibility rule for every scheme. Annapurna, for example, has its own published age and exclusion rules.
Why mobile number quality matters
The citizen interface uses the mobile number from the application for OTP access. An outdated or incorrectly recorded number can therefore become both a communication and authentication problem, even when the underlying family record is otherwise correct.
Household corrections can affect more than one scheme
Because the registry is designed as cross-scheme infrastructure, an incorrect family mapping is not merely a cosmetic error. It can affect how departments match a person or household against scheme data, which is why claim/correction functions matter.
Mistakes that delay processing
Most delays come from small mismatches, not from big problems. The common ones: the name on the Aadhaar does not match the name on the ration card or EPIC; the mobile number given is no longer active, so OTPs and updates never arrive; the ration card number is entered with a typo; or a family member's details are half-filled and the form is submitted anyway. Each of these sends the application back for correction and costs weeks. Before submitting, read every field back slowly, check that the mobile number can actually receive an SMS right now, and make sure names are spelled identically across documents. If a name genuinely differs between documents — a married name versus a maiden name, for example — get the documents corrected first rather than hoping the mismatch goes unnoticed; the guidance in the documents post covers what to fix.
Online versus assisted submission
You can fill the form yourself on socialregistry.wb.gov.in, or get help at a Duare Sarkar camp, a Tathya Mitra Kendra, or a cyber cafe. If someone else fills it for you, watch the screen and verify every entry before they hit submit — errors made by helpers are still your errors in the system. Never share your OTP with anyone filling the form on your behalf; the OTP is what legally ties the submission to you. Assisted routes are legitimate, but the responsibility for accuracy stays with the applicant.