An eShram registration should describe the worker's actual occupation and use the worker's own identity, mobile, and bank details. If occupation or account information changes later, keep the earlier registration and the update acknowledgement so the history remains traceable.
Treat occupation selection as a factual classification exercise. Write down the work actually performed, whether it is seasonal or regular, and the employer or self-employment context before choosing an occupation label. If the worker later changes occupation, bank account, or mobile number, preserve both the earlier card details and the update acknowledgement instead of presenting the new record as the original registration.
Treat eShram as a worker-registration record, not as proof of pension enrolment, employment, income, or a later benefit. The occupation entry should describe the work actually performed when the profile is created. Keep the original card details, each update acknowledgement, and the date a bank account, mobile number, address, or occupation changed. A later PM-SYM or other programme application should carry its own eligibility, mandate, contribution, nominee, and status trail instead of being folded into the eShram file.
Classify the worker from the work actually performed
The central registration decision is the occupation entry. Before selecting a label, describe the worker's real activity in ordinary language: what work is done, whether it is seasonal or regular, whether the person is self-employed or works for others, and where the work usually takes place. Use that description to choose the closest available classification. Do not invent employment history, income, or a trade merely because a different label appears more likely to attract a benefit.
Confirm that the identity, mobile number, address, and bank details belong to the worker and are currently usable. These fields support contact and record linkage, but they do not prove employment, income, pension enrolment, or eligibility for another programme. Review every entered value with the worker before finalising registration, especially when someone else is helping at a service point.
Keep worker registration distinct from later programmes
The worker owns the factual occupation and personal details provided. Identity, bank, and mobile records remain controlled by their respective issuers or providers. The eShram channel controls the worker-registration record and its recognised updates. An employer controls its employment evidence, and a separate pension, insurance, or benefit programme controls its own application. A later programme should not be folded into the eShram file simply because it reuses Aadhaar or bank details.
When an occupation, mobile number, address, or account changes, preserve the earlier card or profile details and the update acknowledgement. If the source bank or identity record is wrong, correct it with that owner before copying the new value into the worker profile. If the profile itself contains the error, use the eShram update route. Avoid presenting the revised profile as though it had always contained the new information; the change date may matter when explaining an earlier application or contact failure.
Preserve the worker's history across updates
Build a chronology beginning with the description of work used at registration. Record the registration date, occupation selected, contact and account details used, card or reference issued, and every subsequent update. For each change, note what changed, why, which source record supported it, and when the acknowledgement was received. This creates a defensible history without turning ordinary changes in work into contradictions.
If another programme later raises a mismatch, identify whether it concerns the eShram profile or that programme's own record. Send the issue to the correct owner and keep its response separately. A complete follow-up file should show the worker's registration history, not a supposed promise of benefits. It should also allow the worker to prove when contact, bank, or occupation information changed without overwriting the facts that were accurate at the time of the original registration.
Where the occupation label is broad, keep the worker's plain-language description beside it and update that description when the work genuinely changes. This note helps a later reviewer understand why a classification was selected without fabricating a more formal employment record. It also separates a classification disagreement from an identity, bank, or mobile correction that requires a different response.
eShram Card: source pages and next actions
Read eShram official portal for the current instruction affecting identity, occupation, bank, and nominee details. Keep that eShram Card page and its check date with the application record, and route an error in the underlying source to the issuer or programme channel that owns the disputed fact.