Two chances at your name. One at your birthday. Spend them carefully.

What an update actually changes, and where

An update changes a field in a record the Unique Identification Authority of India already holds. It does not create a record, it does not issue a new number, and it does not touch the number you have. The twelve digits are permanent. What moves is the data sitting against them.

That sounds obvious and it is not, because a very large number of people arrive believing that a correction means getting a new Aadhaar, and a smaller but unluckier number have been sold exactly that by somebody at a counter. There is no such thing. A person has one Aadhaar number for life, and an attempt to obtain a second one is not a shortcut but an offence.

The second thing worth establishing early is that the update changes the record at the Authority and nothing else. It does not reach into your bank, your employer, your insurer or your provident fund account and correct the copies they took. Those copies stay wrong until somebody tells each of them, and nobody does it for you.

The one thing Aadhaar has never been

Before any of the machinery, it is worth being clear about what the record is, because a great deal of anxiety about getting a field exactly right comes from a belief about Aadhaar that the statute flatly contradicts.

The record is maintained under the Aadhaar (Targeted Delivery of Financial and Other Subsidies, Benefits and Services) Act, 2016. Section 9 of that Act carries the marginal heading that an Aadhaar number is not evidence of citizenship or domicile, and it provides that the Aadhaar number, or the authentication of it, shall not by itself confer any right of, or be proof of, citizenship or domicile in respect of the holder.

That is a limit written into the statute, and it does not soften because a counter clerk treats the card as the strongest paper you own. What the record establishes is that a resident with those biometrics is on the register. It is an identity record, and nothing in it speaks to nationality, to where you belong, or to what you are entitled to.

Knowing that changes how you should think about the fields. They matter enormously in practice, because so many other systems read them. They do not matter in the way a passport or a citizenship document matters, and a defect in them is an administrative problem rather than a question about your status.

Place Order — no advance, pay after work

The fields that can be changed at all

The Authority sets out what is updatable, and the list is shorter than most people assume. On the demographic side: name, address, date of birth or age, gender, mobile number, email address, relationship status, and the consent governing the sharing of information. On the biometric side: iris, fingerprints and the facial photograph.

Everything else in the record is not a field you can ask to move. There is no free-text note, no alternative spelling stored alongside the main one, and no facility for recording that you are also known by something else. That last point disappoints a lot of people, and it is the reason a separate affidavit exists to establish that two differently spelled names belong to the same person — a document dealt with on the one and same person affidavit page rather than here.

It is also worth noticing what the list implies. Relationship status and the consent field are updatable, and almost nobody ever looks at them. A record created at a camp enrolment a decade ago may carry a relationship entry that was guessed at, and it sits there unread until the day some institution reads it.

Demographic and biometric are two different jobs

This distinction runs through everything that follows, and getting it wrong is the single commonest cause of a wasted visit to a centre.

A demographic update changes written data. It can sometimes be done online, it is verified by somebody reading a document, and it is charged on one scale. A biometric update captures something from your body. It can never be done online for the obvious reason, it requires attendance in person, it is verified by the capture itself, and it is charged on a different scale.

They are not merely different in procedure. They are different in whether they can be combined, which is the part that catches families. A mandatory biometric update, of the kind a child needs at particular ages, is required to be a stand-alone transaction and may not be clubbed with anything else. So a parent arriving to fix a child spelling and capture the child fingerprints in one sitting is making two visits, and no amount of goodwill at the counter changes that.

Correction, change, and the difference that decides everything

Here is the distinction that decides how much a piece of work costs, how long it takes, and whether it is possible at all. It is almost never explained to the people who most need it.

A correction brings the record into line with what it was always supposed to say. The name was always Siddharth; an operator typed Sidharth. The record was wrong from the moment it was made. A change moves the record to something new. The name was Priya Sharma and, after a marriage or a decision or a gazette notification, it is to become something else. The record was right; the facts moved.

The Authority treats these differently, and the difference is counted. Several kinds of correction are expressly not charged against the lifetime limit on name updates: a typographical error made by an enrolment operator, a transliteration error, and a change that follows an update to a regional-language field. Those are repairs of a defect, and repairing a defect does not spend a chance.

Which means the single most valuable thing you can do before approaching anybody is to work out honestly which of the two you have. Presented as a correction, with the right supporting material, a repair costs nothing from your allowance. Presented as a name change — which is how it will be processed if that is what the form says — it spends one of two, permanently, for a result you were entitled to anyway.

Place Order — no advance, pay after work

Read your own record before you touch it

Retrieve the record and read it. Not the card in your wallet, which may be years old and may have been reprinted from a version that has since moved; the record as it currently stands.

Then read it character by character against the document you want it to match. The eye is extraordinarily bad at this, because it reads a familiar name as a shape rather than as letters and slides straight over a missing one. Write the two versions down one above the other. Compare the date digit by digit, not as a date. Check the parent name field, which almost nobody looks at and which is a frequent source of a mismatch that surfaces years later.

A meaningful proportion of the files that come to us end here, with the discovery that the Aadhaar field was correct all along and the problem is in some other record entirely. That is a good outcome and it costs nothing to reach.

When the record is right and everything else is wrong

This situation is common and it is almost always handled backwards. Your Aadhaar says one thing, correctly. Your PAN, your bank, your employer records and your insurance policy say something slightly different. The instinct is to change Aadhaar, because Aadhaar is the one with a visible process and the others feel immovable.

That instinct is wrong, and acting on it is expensive. Changing the correct record to match four incorrect ones means you now have five incorrect records and have spent a limited chance doing it. The right work is at the four, one at a time, against the record that was right.

The particular case of a PAN record and an Aadhaar record disagreeing has its own page, because it has its own consequences and its own trap, and we would send you to the PAN and Aadhaar name mismatch page rather than attempt a worse version of it here. The general principle holds everywhere though: find the record that is right, and make the others agree with it.

Which page this is, and which it is not

This page is about the update machinery itself: the fields, the limits, the exception routes, the document lists, the channels, the charges and the deadlines. It is deliberately not about several neighbouring subjects that are handled properly elsewhere on this site, and pointing you at those is more useful than a thin summary here.

If you are legally changing your name and want the gazette route and the order in which records should then be updated, that is the name change page. If the change follows a marriage, the name change after marriage page deals with it, including the question of whether you need to change anything at all. If what you need is the supporting declaration, that is the name change affidavit page.

If you need an affidavit to establish an address, including the position of a self-declaration by a family member, the address proof affidavit page covers it. And if the change concerns the recognition of a gender identity under the dedicated statutory route, that proceeds before a District Magistrate, it is a recognition rather than a correction, and the transgender name and gender change page sets it out in full.

Place Order — no advance, pay after work

The limits nobody reads in time

Three fields in the record are capped, and the caps are counted by the system rather than by you. The Authority states them as name twice in a lifetime, gender once in a lifetime, and date of birth once in a lifetime.

Almost nobody learns this before they need it. The typical sequence is that a person changes a field once without thinking about it, often for a reason that was not really a change at all, and then discovers years later that the chance they needed has already been spent. At that point the route is a much longer one, and in some cases it closes entirely.

Two things make this worse than it needs to be. The first is that people do not know what has already been counted against them, because the count is not displayed anywhere obvious and a change made at a camp in 2014 by somebody else does not feel like something you did. The second is that a great deal of the advice in circulation treats the caps as absolute, when the published procedures provide routes past two of the three, and treats some corrections as consuming a chance when they do not.

The rest of this section of the page takes the three fields one at a time, with what the Authority actually publishes about each.

Name: twice, and the changes that do not count

The ordinary limit is two name updates in a lifetime. The important part is the list of things that are not counted against those two, because it is longer than most people are told and it is where almost all the recoverable value sits.

The Authority procedure on this records that a typographical error made by an enrolment operator does not consume a chance. Nor does a transliteration error, which is the category covering a name that came out differently when rendered between scripts. Nor does a change that follows an update to a regional-language field, where correcting one version properly requires the other to move with it.

That covers a very large share of real Aadhaar name problems. The person whose surname lost a letter at a camp enrolment is not making a name change. The person whose name was rendered one way in Devanagari and another in Latin script is not making a name change. In both cases the record is defective and the repair is a repair.

What determines how it is treated, though, is how it is presented and what it is supported by. A request that arrives looking like a name change is processed as a name change. The work worth doing is in establishing, before anything is submitted, which category the problem falls into and what evidences it.

A complete change of name has exactly one route

Where the chances have been used and the change is a genuine one, the request goes through what the Authority calls the exception handling process. That is decided by a regional office on the papers, not at a counter, and the procedure lists what it will consider and what each case requires.

For a complete change of name — meaning a genuinely different name rather than a different arrangement or spelling of the one you have — the requirement is a Gazette Notification, submitted as proof of identity. Not an affidavit. Not a newspaper advertisement. Not a combination of the two. The Gazette Notification is what the procedure names.

That matters because of what it costs. Obtaining a gazette notification is a process in its own right, with its own steps and its own timeline, and it is the subject of our name change page rather than something to be attempted as an afterthought during an Aadhaar visit. If your change is going to need one, that work comes first and everything else waits on it.

And it is worth saying the converse plainly, because this is where people spend money unnecessarily: a gazette notification is not required for a correction of spelling, for reordering the parts of your existing name, or for a change following a marriage or a divorce. Each of those has its own, much lighter, route.

Place Order — no advance, pay after work

Initials, order and spelling

A large category of name problems is not a change of name at all but a change in how the same name is written, and the procedure deals with these as their own cases.

Adding or editing initials is one of them. This is a very common requirement for people from parts of the country where an initial carries a village name or a parent name, and where one record expanded it and another did not. The procedure provides for it, and the regional office verifies the request against a clarification letter the Authority issued on the subject in September 2020.

Reordering the parts of a name is another, and it is the one for which the procedure lists no supporting document at all. That is a useful thing to know: where the problem is that your given name and surname sit in the wrong order, or a middle name has migrated, you are not necessarily looking for a document you do not have.

Spelling sits slightly differently. A spelling error introduced by an operator is a correction and does not consume a chance. A spelling you have decided to adopt, where the record faithfully reproduced what was submitted, is a change and is treated as one. What separates the two is whether the record strayed from what was handed to it, which evidence settles and preference does not.

The name after a marriage or a divorce

A change of name consequent on marriage, divorce or adoption is one of the cases the exception handling procedure accepts, and the supporting document is the corresponding certificate, submitted as proof of identity.

That is a much lighter requirement than a gazette notification, and knowing it exists prevents a particular and expensive mistake: a person who has already used both ordinary chances assumes a post-marriage change is now impossible, or is told it requires a gazette route, and either abandons it or spends months and money on the heavier process when the certificate would have done.

The prior question, though, is whether the change is needed at all. Nothing about a marriage obliges anybody to change a name, and a great deal of the pressure to do so is social rather than legal. There is also a distinction, constantly muddled, between changing your own name and recording a spouse name in the relationship field, which are different operations with different consequences. Both of those belong on the name change after marriage page, which treats them properly, and we would rather point you there than compress them.

What belongs here is only the Aadhaar mechanics: the certificate is the document, the case is a recognised exception, and the marriage certificate itself has to be sound before it is relied on, because a certificate that spells your name differently from the way you intend to be recorded creates the next problem rather than solving this one.

Gender, and the certificate now required

The ordinary limit on the gender field is one change in a lifetime, and the documentary requirement has tightened in a way many people have not registered.

The Authority procedure records that the gender update was previously permitted without any document at all, and that because of the limits on how often the field may move, an ordinary gender update now requires a medical certificate bearing a photograph, issued by a surgeon or other relevant authority, submitted as proof of identity.

Where the change is to transgender, the position is different and importantly so. The proof of identity there is a certificate issued by the Central Government or a State Government, and no medical certificate is in question. That is the correct result, and it reflects the fact that the certificate in question comes from a statutory process that does not itself turn on medical evidence.

That process — an application before a District Magistrate, resulting in a certificate and a revised certificate, operating as a recognition of identity rather than a correction of an error — rests on a statute of its own and is given proper room on our transgender name and gender change page. It is not an Aadhaar process and should not be approached as one. What happens on the Aadhaar side is that the certificate, once held, is the document the record is updated against.

Place Order — no advance, pay after work

The operator error that resets the count

There is a provision here that is genuinely generous and almost never mentioned, and anybody whose gender field was altered by somebody else should know about it.

Where an enrolment operator wrongly changed the gender field while processing some other update — a very real occurrence, usually a mis-click during an address or name transaction — the resident re-enrols, and the regional office refers the case to the technical centre to be reprocessed with the gender update count reset to zero.

Read that again, because the consequence is significant. The mistake is not charged to your lifetime limit. The counter goes back to nothing, as though the erroneous change had never happened. You are not left having spent your only chance on an error somebody else made.

But this only works if the matter is raised as what it is. Presented as an operator error, with the earlier transaction identified, it is corrected and the count is restored. Presented as a request to change the gender field, it is processed as a gender update, against a limit of one, on a field that an error has already moved. Same facts, entirely different outcome, decided by how the request is framed.

Date of birth: what the rule actually says

This is the field on which the gap between what is published and what is reported is widest, and it is worth going slowly.

The Authority public enrolment and update material states the ordinary rule plainly: date of birth, once in a lifetime. That line is repeated across an enormous volume of secondary writing, usually as though it settled the matter, and it is the sentence quoted at people by counter staff when they come back a second time.

The Authority also publishes a Standard Operating Procedure for date of birth update dated 24 December 2025, which supersedes its earlier procedure of 19 July 2021 and has since been amended by a corrigendum to its annexures. That document is more precise, and the precision matters.

It begins from the proposition that an individual can have only one date of birth, and that a change ought therefore not to arise in the ordinary case. It contemplates a first update where the recorded date was declared or approximate — which describes a very large number of records created in the early camp enrolments, where nobody was asked and a default was entered — or where an operator entered the date wrongly.

And then it says the thing that the reporting leaves out. Further updates are not foreclosed. They are confined to exceptional cases. The door is narrow and it is guarded, but it is a door, and a person being told that nothing further is possible is being told the ordinary rule rather than the whole rule.

A second change, and what you sign away

If the exceptional route is open, it is worth knowing exactly what it asks for, because one of its requirements is unusual and permanent.

The documentary requirement is a birth certificate. Where the original birth certificate was itself wrong and has been corrected, the corrected certificate must bear the same birth registration number and must have been issued by the same registrar as the original. That is a precise requirement and it defeats a common workaround: a fresh registration, from a different authority, with a new number, is not a corrected certificate and will not serve. More generally, a corrected document must come from the same authority, bear the same description and the same year, and differ from the original only in the date itself.

Alongside the certificate the procedure requires an affidavit in the form it prescribes. And here is the part to read twice before signing: by that affidavit the applicant accepts that no further date of birth update will be available to them. It is not a formality. It is the consideration for the exception, and it closes the field permanently.

Which leads to the only sensible advice on this route. If you are going through it, the date you submit must be right, evidenced, and consistent with every document you are relying on. There is no third attempt. People who approach the second change casually, with a date they have not verified against the certificate they are submitting, are spending something they cannot get back.

Place Order — no advance, pay after work

The procedure that changed in September

Anybody researching this subject in the last few weeks will have encountered a great deal of writing about a new name-update procedure, and it is worth being careful about what is actually established.

What is established, from the Authority own circulars page, is that a Standard Operating Procedure to be followed for updating name in Aadhaar was uploaded there on 18 September 2026, and that it is the only name-update item on that page. The document exists, it is recent, and it is published where anybody can read it.

What we have not done is reproduce its contents, and the reason is a deliberate one. A number of accounts of that procedure are now in circulation attributing to the Authority specific figures, absolutes and document requirements. Some of those may well be accurate. They are not, however, what the Authority publishes in the material we have been able to read, and this page states the Authority own published material and nothing else.

So the honest position is this. The limits and routes set out on this page come from the Authority published enrolment and update material and from its standard operating procedures of 28 October 2021 and 24 December 2025, each named and dated so you can check them. If your file turns on the precise terms of the September 2026 procedure, read that document itself on the Authority circulars page rather than any account of it, including this one.

Four lists, and the one that applies to you

The Authority publishes a consolidated list of acceptable documents for enrolment and update, and it is arranged in four lists. Knowing which one applies to you removes most of the confusion about what you can submit.

List I governs enrolment of children up to five years. List II governs children aged five to under eighteen. List III governs persons of eighteen and over. And List IV governs updates to an existing Aadhaar, at any age.

List IV is the one that matters for everything on this page. It is also the longest, running to a substantial number of entries, and it is broader than people expect: alongside the obvious documents it includes a marriage certificate, a divorce decree, a property tax receipt, a bank passbook, a Kisan photo passbook and a self-declaration from an immediate family member.

The common error is to work from List III because it is the one people have heard of, or from a list copied onto some other website years ago. Lists I and II also provide for head-of-family based enrolment, and the published material makes separate provision for overseas citizens of India, for Nepalese and Bhutanese nationals and for foreign nationals. We have not reproduced the lists here, deliberately: they are long, they are amended, and a stale copy of a document list is worse than no copy.

The four kinds of proof, and what each is for

Within each list the documents are organised by what they prove, and this is the single most useful thing to understand about them. There are four categories: proof of identity, proof of address, proof of relationship and proof of date of birth.

A document is not simply acceptable or unacceptable. It is acceptable for particular purposes. The same passport may serve as proof of identity, proof of address and proof of date of birth. A utility bill may serve as proof of address and nothing else. A marriage certificate may serve as proof of relationship and, in the specific exception cases, as proof of identity.

Almost every rejection we see comes from ignoring that structure. A person wants to change a date of birth and submits a document that establishes very convincingly who they are and says nothing whatever about when they were born. The document is genuine, the person is who they say they are, and the request fails, because the field being changed is not the field the document proves.

So the discipline is: name the field first, then find the document that proves that field, then check it is in List IV. Not the other way round, and never by starting from what happens to be in the drawer.

Place Order — no advance, pay after work

What a corrected certificate must look like

Where the supporting document is itself being corrected before it is submitted — usually a birth certificate — the published procedure is specific about what will be accepted, and the specificity is there to defeat a particular abuse.

A corrected certificate must come from the same authority that issued the original. It must bear the same description and the same year. And it must differ from the original only in the particular being corrected. In the date of birth context the requirement is tighter still: the corrected certificate must carry the same birth registration number and must have been issued by the same registrar.

What that rules out is the fresh registration. A person whose birth was registered decades ago, with a date they say is wrong, cannot simply register the birth again somewhere else and present the new certificate as a correction. That is a second registration, not a corrected one, and the number and the registrar will not match.

If you are in that position, the work is at the registering authority: a correction to the existing registration, through whatever process that State provides, producing a certificate that traces back to the original entry. The birth certificate page deals with that side. It is slower than the alternative people are tempted by, and it is the only one that will actually be accepted.

The declaration route, and its narrow door

There is provision for a self-declaration in place of a document, and it is narrower than people hope but wider than they are usually told.

In the date of birth procedure, where the error was the enrolment operator and the document originally relied on is no longer valid or is no longer held by the applicant, a self-declaration in the prescribed form is provided for. That is a real route and it addresses a real situation: somebody enrolled fifteen years ago, on a document that has since expired or been lost, whose record carries an error that was never theirs.

Note the conditions though, because all of them have to hold. The error must be the operator. The original document must be genuinely unavailable or no longer valid. And the declaration is in the form prescribed, not a general affidavit drafted to taste.

Separately, a self-declaration from an immediate family member appears in List IV, which is a different thing: that is a document type for establishing certain particulars, most commonly used for address, and it is dealt with alongside the other address routes on the address proof affidavit page. The two get confused constantly, and they do different work.

A child record, and the documents it takes

A child record is treated differently from an adult one, on documents and on biometrics both, and parents are frequently caught by the documentary side.

On date of birth, the restriction is strict. For ages nought to five and five to eighteen, the birth certificate is the only permitted document. Not a school record, not an immunisation card, not a passport held by a parent. The birth certificate. For adults, by contrast, any acceptable date of birth document in List IV may be used, which is a much wider field.

That catches a particular family: the child whose date of birth was entered approximately at a camp enrolment, whose birth was registered late or not at all, and whose parents assume a school leaving record will serve because it does for so many other purposes. It will not, and the work is to get the birth registered or corrected first.

The enrolment lists for children also provide for head-of-family based enrolment, which is the mechanism by which a child without documents of their own can be enrolled against a parent record. Where a child circumstances involve a guardian rather than a parent, the underlying authority for that is a separate matter, and our guardianship certificate page deals with how such authority is established.

Living abroad, and the record left behind

People who have left India keep their Aadhaar record, and it keeps being read by institutions in India on their behalf, which makes a defect in it harder to live with rather than easier to ignore.

The published material makes specific provision here. For non-resident Indians under eighteen, a date of birth update may be supported by a birth certificate or an Indian passport. The enrolment documentation also makes separate provision for overseas citizens of India and for Nepalese, Bhutanese and other foreign nationals, each with its own documentary basis.

There is also a restriction worth knowing. For resident foreigners, the date of birth update is available only where the cause was an operator error. That is a materially narrower position than applies to citizens, and somebody in that category planning a correction on any other basis should know it before they begin.

The practical difficulty from abroad is not documents but presence. Anything requiring biometric authentication requires you, and that cannot be delegated, couriered or arranged by a relative holding a letter. Where an update must be done in person, it waits for a visit, and it is worth planning around rather than discovering on arrival. Where documents issued abroad are involved, the question of whether they are usable in India at all is a separate exercise — our degree verification and related pages deal with that family of problems.

Documents we will not put in a file

It is worth being direct about this, because the temptation is real and the consequences are badly understood.

We will not put forward paperwork whose authenticity we doubt. We will not submit a document obtained to produce a particular answer rather than to record a fact. And we will not help present a date, a name or a parentage that the client has told us is not accurate, however sympathetic the reason and however small the difference looks.

The reason is not only principle. It is that the published procedure sets out precisely what happens when an invalid or false document is used, and it is severe: a final opportunity to correct the record, the Aadhaar deactivated in the meantime, and reactivation only on a genuine and verifiable birth certificate, a full biometric update and a prescribed affidavit, with cases concerning minors additionally verified through the State portal.

That is a far worse position than the one the person started in. A record with a wrong date is an inconvenience. A deactivated record is an emergency, because everything downstream of it stops at once. Nobody who has seen the second would choose to risk it to avoid the first.

Place Order — no advance, pay after work

Four ways to submit, and one of them is online

A request reaches the Authority through one of a small number of channels, and the channel is not a matter of preference. It is determined by the field you are changing.

There is the online portal, which handles a narrow set of things very conveniently. There is the full update client at an enrolment centre, which handles everything. There is the lighter update client, which handles most demographic work but not biometrics. And there is the document update, which is its own exercise and is dealt with separately below because it is not a change of data at all.

People choose the channel by convenience and then discover that it cannot do the thing they came for. The order should be the other way round: identify the field, find out which channels can move it, and go to whichever of those is nearest. That sounds pedantic and it saves entire mornings.

The portal, and the one field it really serves

The Authority describes the online mode as offering address update. That is a precise statement and it is worth reading precisely, because a good deal of writing implies the portal can do rather more than that.

The mechanics are straightforward. You need a registered mobile number. You log in with a one-time password sent to it. You upload proof of the new address, and that proof is verified afterwards by a processing team rather than by anybody in front of you. The free document update also runs through the portal.

The limitation is equally straightforward. There is no biometric authentication happening, only an OTP, and that is why the portal handles the field it handles and not the others. A name, a date of birth or a gender change moves something far more consequential than an address, and the Authority has not placed those behind an OTP.

So the portal is excellent for what it does and simply unavailable for most of what people want it for. A client planning a name correction online is planning something that does not exist, and it is better to know that before taking a day off work for it.

The full-service counter

The Authority names the complete facility Update Client Standard. Through it, all biometric and demographic fields may be updated, together with the local-language rendering of the record.

Two features of it matter in practice. The biometric checks are performed at the back end rather than resolved in front of you, which means a clean capture at the counter is not the same as a completed update and the result comes later. And it issues a URN, an update request number, which is the thing you track with and the thing to keep.

This is the channel for anything involving fingerprints, iris or a change the lighter client cannot reach. It is also the channel for the local-language field, which is worth pausing on: where a record carries a name in two scripts and one of them is wrong, mending only the script you can read leaves its twin broken, and that defect tends to announce itself at the least convenient hour, in front of whichever office happens to read the version you ignored.

Not every centre runs the full client. That is the single most useful thing to establish by telephone before travelling, and almost nobody does it.

Place Order — no advance, pay after work

The lighter counter, and when it is enough

Update Client Lite covers all demographic fields, the photograph and the local language. It uses biometric authentication — your fingerprint confirms it is you — and it issues an EID, an enrolment identification number, as the acknowledgement.

The distinction people miss is between using biometrics to authenticate and updating biometrics. The lighter client does the first and not the second. It will confirm your identity by your fingerprint and then change your name. It will not capture a new set of fingerprints to replace the ones on file.

For the great majority of adult demographic work, this is entirely sufficient and often quicker. The cases where it is not are specific: a child needing a mandatory biometric update, an adult whose fingerprints have degraded to the point where authentication itself fails, and anybody needing the iris or fingerprint record refreshed for any other reason.

The degraded-fingerprint case deserves a mention of its own because it affects older applicants and people in manual trades disproportionately, and it is circular in a cruel way: the authentication that would let you update your biometrics is the authentication your biometrics are failing. That situation needs the full client and sometimes needs the exception machinery, and it is not solved by trying repeatedly at the same counter.

Choosing the channel from the field, not the convenience

Put the preceding sections together and the method is simple enough to write on a card.

Name the field. Establish whether the field is demographic or biometric. If it is biometric, you are attending in person at a centre running the full client, and if it is a mandatory update for a child it is travelling alone. If it is demographic and it is the address, the portal will probably do it. If it is demographic and it is anything else, you are at a centre, and the lighter client will usually suffice.

Then ask the question almost nobody asks before setting out: does anything else on my list conflict with this one. Because the moment a mandatory biometric update appears alongside something else, the plan splits into two visits, and it is better to know that while making the plan.

Write the list down. Mark each item demographic or biometric. Mark the mandatory biometric update, if there is one, as a visit of its own. What remains is your actual schedule, and it is frequently not the single afternoon people imagine.

The registered mobile number, and the wall it builds

The registered mobile number is the quiet obstacle in this entire subject, and it blocks far more people than any documentary requirement does.

The online route is authenticated by a one-time password. If no mobile number is registered against the record, or if the number registered is one you no longer have, the OTP goes nowhere and the online route is simply closed. There is no alternative authentication, no email fallback and no workaround.

And the remedy is itself in person. Registering or changing the mobile number is done at a centre, with biometric authentication, because otherwise anybody who got hold of your details could redirect the authentication for your record to a phone they control. The security logic is sound and the practical consequence is that the first visit is unavoidable.

This catches older applicants constantly. A record created at a camp in 2012 against a number that belonged to a son who has since changed it. The parent has no idea the number is wrong until the day something requires an OTP. If you are helping an elderly relative with anything on this page, check the registered number first, before planning anything at all, because everything else depends on it.

Place Order — no advance, pay after work

What happens after you press submit

A submitted request is not a completed update, and the gap between the two is where most of the anxiety on this subject lives.

What happens next is verification. Somebody reads the document you submitted against the field you asked to change, and decides whether the one proves the other. Where biometrics were captured through the full client, the biometric checks run at the back end. None of this happens in front of you, and none of it is done by the person at the counter, who has taken the request rather than granted it.

That is why a cheerful assurance at the counter means very little. The operator has submitted what you gave them. Whether it holds is somebody else decision, made later, on the papers. We have had a good many clients arrive distressed because the centre said it was done and then a message said otherwise, and the two statements are not actually in conflict: one described the submission and the other described the outcome.

The useful consequence is that the quality of what you submit is decided entirely before you arrive. Nothing can be explained to the verifier afterwards. The file has to speak for itself.

The number you are given, and what to do with it

You leave with an acknowledgement, and it is the only thing connecting you to the request. Keep it.

Where the full update client was used, that acknowledgement is a URN, an update request number. Where the lighter client was used, it is an EID, an enrolment identification number. Either way it is printed on the slip you are handed, and either way a surprising number of people throw it away or photograph it badly.

Photograph the slip, legibly, and send the picture to yourself. Type the number into a note as well, because a thermal-printed slip fades and some of them are unreadable within weeks. If you are doing this for a relative, keep a copy yourself rather than relying on them to produce it in three weeks.

Without it you cannot track the request, you cannot establish when it was made, and if it fails silently you have no way of demonstrating that it was ever submitted. It is a small piece of paper carrying all of the evidence.

How long the wait actually is

We state a period of 7 – 30 days for a file, and most of that is waiting rather than working. We do not state it as a guarantee, and here is why that matters more than it sounds.

The Authority does not publish a guaranteed processing time for an update. Anybody who gives you a firm date is either repeating a figure they read somewhere or telling you what you want to hear. A straightforward demographic update, with a document that cleanly proves the field, is often quick. That is a tendency, not a promise.

What genuinely lengthens things is identifiable in advance. Anything travelling through the exception handling process is decided by a regional office rather than at a counter, and that is a different order of time entirely. Anything where the document is marginal invites a closer look. Anything resubmitted after a rejection starts again.

The honest planning advice is to work backwards from the deadline that actually matters — the examination form, the pension application, the visa appointment — and to start far enough ahead that a single rejection does not sink it. One rejection is normal. Two is unusual. Having no margin for the first one is the avoidable part.

Place Order — no advance, pay after work

What the Authority charges, field by field

These are the Authority own published figures, and they are the only update charges stated anywhere on this page.

A document update is free through the online portal until 14 June 2027, and seventy-five rupees at an Aadhaar centre. A demographic update is seventy-five rupees where it is done on its own, and free where it accompanies a biometric update. A biometric update is one hundred and twenty-five rupees where no concession applies.

Read the second of those again, because it contains a genuine saving that almost nobody exploits. A demographic update is free when it travels with a biometric update. So a person who needs both — and who is not caught by the stand-alone rule discussed below — pays for the biometric update and gets the demographic one at no charge, where doing them separately would cost both.

Everything else you may be asked for is not on this list, and that is the point of printing it. If a figure is quoted to you that does not appear here, ask what it is for.

The free window, and when it closes

The free document update is the most valuable thing on this page for the largest number of people, and the smallest number know about it.

It is free through the online portal until 14 June 2027. After that date the same exercise costs seventy-five rupees at a centre. That is not a large sum, but the relevant difference is not the money: it is that the free route runs online and the paid one requires attending.

What it does is refresh the supporting documents held against a record whose data is already correct. It changes nothing you can see. Its value is that a record supported by documents from a decade ago is more likely to produce friction later than one supported by current ones, and the exercise closes that quietly.

If your data is right and your documents are old, this is the thing to do, it is free, and it has a deadline. There is very little else on this subject that can be stated so simply.

The concession that already lapsed

There was a further concession making the biometric update free for children between seven and fifteen. It ran until 30 September 2026, and it has therefore ended.

We are stating that plainly because a very large amount of advice still in circulation has not caught up with it, and because the lapse is recent enough that a parent reading something written in the summer would have no reason to doubt it. An article from August is not wrong about what it described. It is describing something that no longer applies.

The practical effect is that a child in that age band whose biometric update was being put off is now in a chargeable transaction where they were previously in a free one. For a single child that is a modest amount. For a school arranging this across a cohort, or a family with several children, it is not trivial.

What survives are the two mandatory biometric updates, in the five-to-seven and fifteen-to-seventeen brackets, which remain free. Those are the first and second mandatory updates, they are age windows rather than deadlines, and they close on a birthday.

Place Order — no advance, pay after work

The ten-year story, and what it actually is

You will have read that Aadhaar must be updated every ten years. It is one of the most widely repeated claims about the subject, and on the material we have relied on it is a misreading.

The Authority frames the free document update by reference to residents who have not changed any demographic detail in the last eight to ten years. Read that as written: it is describing who is eligible for a free facility. It is a condition of eligibility, not an obligation, and it answers the question who may use this rather than the question who must do this.

Somewhere between the publication and the reporting, an eligibility condition became a mandate, a range became a round number, and an invitation became a deadline. We have not stated it as a compulsory ten-yearly re-documentation because the Authority material we have relied on does not state it as one.

This matters practically because the two framings lead to different behaviour. Read as a mandate, it produces anxiety and sends people to centres to pay for something they could do free. Read as it is written, it says something much more useful: if your data is correct and your documents are old, there is a free facility available to you until a stated date, and you may use it.

The biometric update that is compulsory

Children are the one group for whom an update is genuinely mandatory, and the reason is biological rather than administrative.

A child enrolled very young does not have stable biometrics. Fingerprints and iris patterns change as a child grows, and a record captured at three does not authenticate the same person at twelve. The mandatory biometric update exists to re-capture them at the points where they have settled enough to be useful.

There are two, and the Authority describes them as the first and second mandatory biometric updates: one in the five-to-seven bracket and one in the fifteen-to-seventeen bracket. Both are free within those brackets.

The thing to understand is that these are age windows, not announcements. Nobody writes to tell you the window has opened, and nobody tells you it is closing. It closes on a birthday. A parent who misses the five-to-seven window has not lost the ability to do the update; they have lost the free one, and will pay for it later. Put both dates in a calendar when the child is enrolled, because nothing else will remind you.

Why a biometric update cannot be bundled

Here is the rule that wastes the most time, and it is stated flatly in the Authority own material: a mandatory biometric update shall be a stand-alone transaction only, and may not be clubbed with any other transaction.

Not discouraged. Not subject to the operator discretion. It may not be combined. Which means the family arriving to do a child biometric update and correct the spelling of the child name in the same sitting is making two transactions, and quite possibly two visits, however reasonable the request sounds and however willing the person at the counter is.

This produces a predictable and avoidable scene at centres every day. A parent has taken a morning off, brought the child, queued, and is told that only half of what they came for can be done. The information was published. It simply was not anywhere they were likely to look.

So plan the sequence. Do the mandatory biometric update on its own. Do everything else separately. If both are needed and the centre is far away, ask when you call whether both can be done on the same day as separate transactions, because that varies with how busy the centre is and it is the only part of this that is negotiable.

Place Order — no advance, pay after work

What a centre is allowed to collect

The charges set out above are the Authority published figures. What a centre may actually collect from you is governed separately, and the Authority publishes on that too: its circulars page carries an office memorandum of 21 September 2025 on revised rates of financial assistance to registrars and the fees they may collect for Aadhaar services.

The existence of that document is the useful fact. What a centre charges is not a matter for the centre to decide. It is set, and it is published, and a centre collecting something else is doing something it is not authorised to do.

The Authority also publishes a circular of 12 March 2025 setting out its policy for action against defaults or violations of its regulations, processes, standards, guidelines or orders by registrars, enrolment agencies and other service providers. There is, in other words, a disciplinary framework, and it is not decorative.

None of which helps very much in the moment, standing at a counter being asked for more than you expected. But it tells you two things worth knowing: the figure is not discretionary, and there is somebody to complain to. Ask for a receipt, and ask what the charge is for. The request alone resolves a surprising proportion of these.

Paying at the counter, and the receipt to keep

Always take a receipt, and look at what it says before you walk away.

It should state the transaction, the amount, the date and the centre. Check that the transaction described is the one you asked for, because a receipt for a demographic update when you came for a biometric one is the earliest possible warning that something has gone wrong, and it is far easier to resolve while you are standing there.

Keep the receipt with the acknowledgement slip. Together they establish what you asked for, what you paid, when and where, which is everything you need if the request fails and somebody later suggests it was never properly made.

And if the amount does not match the published figure for what you are having done, ask. Not aggressively, and not as an accusation: there may be a reason, such as the transaction being classified differently from the way you understood it. But ask, because the published figures exist to be checked against.

The cost of getting it wrong twice

The published charges make an update look cheap, and in isolation it is. What is not cheap is the second attempt, and the third.

Count properly. A rejected request costs the fee, the journey, the time off work and the wait, and then the whole of that again. If the rejection was for a document that could never have proved the field, the second attempt costs the same unless somebody has worked out why the first one failed. Many people simply resubmit the same thing, and it fails the same way.

Then count the things that are not denominated in rupees at all. A limited chance spent on a change that was really a correction cannot be bought back at any price. A date of birth moved under the exceptional route, on a date that turns out to be wrong, is final. Those are the expensive outcomes on this subject, and none of them appears on a fee table.

Which is the argument for spending time at the start rather than money later. Everything that prevents these costs nothing: reading the record, deciding which document is the defective one, classifying the change honestly, and checking what has already been spent.

Place Order — no advance, pay after work

Why requests get rejected

Rejections cluster, and almost all of them are preventable from the chair you are sitting in now.

The largest group is the document that does not prove the field. A genuine document, a real person, and no connection between what was submitted and what was asked to change. The second group is the document that is not in the applicable list, usually because somebody worked from a list for enrolment rather than the list for updates, or from a copy on a website that has not been refreshed in years.

Then there is the mismatch inside the request itself: a name on the supporting document that does not match the name being requested, a date that differs from the certificate by a digit, an address that does not match the proof in some detail nobody checked. Then the quality problems — an illegible scan, a document photographed at an angle with a corner missing, a seal that has not reproduced.

And then the structural ones, which are the worst because they are not really about the document at all: a request made against a limit that has already been exhausted, or a change presented in a category it does not belong to. Those do not fail because of a fixable defect in the paper. They fail because the route was wrong.

Reading a rejection properly

A rejection comes with a reason, and the reason is usually terse. Reading it properly is the difference between one more attempt and three.

Start by establishing which of two things it is saying: that something about the paperwork was inadequate, or that the request itself could not be granted as framed. Those lead in completely different directions. The first is fixed by a better document or a better scan. The second is not fixed by any document at all, because it is telling you the route was wrong, and a better version of the same request fails identically.

Where the message is unclear — and they often are — the useful questions are: what field was being changed, what document was relied on, and does that document actually prove that field. Running those three honestly resolves the majority of ambiguous rejections without anybody needing to interpret the wording.

What does not help is reading the rejection as arbitrary. They very rarely are. In almost every case we have examined, the reason was visible in the file before it was submitted, and the person who submitted it had not asked themselves the three questions above.

The resubmission trap

The instinct after a rejection is to submit again quickly, and it is almost always the wrong instinct.

An identical resubmission fails identically. That sounds too obvious to need saying, and it is far and away the most common thing people do. The request was rejected, nothing about it has changed, and it is sent again in the hope that a different person looks at it. A different person applies the same test.

Worse, the attempts are finite in a way that compounds. On a field with a lifetime limit, a sequence of failed approaches is not free: the structural rejections are telling you the route is wrong, and continuing to push at the wrong route while the limit sits behind it wastes the time in which the right route could have been prepared.

So: stop, read the reason, decide whether it is a paperwork problem or a route problem, and change the thing that was actually wrong. If it was a route problem, the next submission is a different kind of request entirely, possibly through the exception process, and it needs preparing rather than repeating.

When a record is deactivated

Deactivation is the serious end of this subject and it deserves to be understood before anybody takes a risk that might lead there.

The published date of birth procedure describes the circumstances. Where a person enrolled in the nought-to-five bracket was in fact older, or enrolled in the five-to-eighteen bracket was in fact an adult, the procedure treats the matter as fraud: the update request is rejected, the Aadhaar may be deactivated, and legal action may follow. Where an invalid or false document was used, a final opportunity is given, and the record is deactivated in the meantime.

What deactivation means in practice is that everything downstream stops at once, and without warning to any of the places that will stop. Authentication fails. Whatever depends on authentication fails with it. The person discovers this not through a notice but through a transaction that will not complete.

To be fair to the Authority, none of this is a penalty applied casually or at the discretion of a counter. It attaches to specific findings. But it is the reason that the advice elsewhere on this page about documents is stated as firmly as it is: the gap between an inconvenient record and a deactivated one is a single bad decision about a piece of paper.

Place Order — no advance, pay after work

Getting a deactivated record back

Reactivation exists, and the published route for it is deliberately heavy.

On the procedure as published, it requires a genuine and verifiable birth certificate, a full biometric update, and an affidavit in the prescribed form. Where the person concerned is a minor, the case is additionally verified through the State portal. Each of those is a real step and none of them is quick.

Notice what the combination is doing. The birth certificate establishes the fact that was in doubt. The full biometric update establishes that the person standing there is the person on the record. The affidavit puts the applicant on the hook for what they have said. It is a route designed to be available but not easy, and that is a reasonable design.

For anybody in this position the practical advice is short: this is not a route to improvise on, the documents have to be genuinely sound rather than arguably sound, and the time it takes is not within anybody control. And for everybody not in this position, it is the clearest possible argument for the caution recommended earlier about what goes into a file.

The cases the procedure treats as fraud

The procedure distinguishes between being wrong and being dishonest, and it is worth knowing where it draws the line, because the two are not treated remotely alike.

An error is an error. A declared or approximate date entered at a camp enrolment, an operator typing mistake, a transliteration that came out badly: none of these is anybody wrongdoing, and the procedures provide routes for all of them, several of which do not even consume a lifetime chance.

What is treated as fraud is specific: enrolling in an age bracket the person did not belong to, and using an invalid or false document. In the first case the request is rejected, the record may be deactivated and legal action may follow. In the second there is a final opportunity, with deactivation in the meantime.

The reason to set this out on a page like this is not to frighten anybody with a genuine problem. It is the opposite. Most people who arrive anxious about an Aadhaar error are in the first category entirely, and are worrying about a consequence that does not attach to them. Knowing where the line actually sits lets you stop worrying about the wrong thing and get on with the work.

Verifying that the update actually took

Do not assume the update happened because nothing told you it had not. Go and look.

Retrieve the record again and read the field that was supposed to change. Read it the same way as before: character by character against the document it was meant to match, not as a quick glance to confirm what you expect to see. This is the stage at which partial updates get discovered — the Latin-script name corrected and the regional-language one left as it was, or a date changed in one place and not another.

Check the fields that were not supposed to change, too. It is uncommon, but a transaction that touches a record can occasionally disturb something adjacent, and the gender-reset provision discussed earlier exists precisely because that happens.

Then save a copy of the corrected record, dated. You will need it for the next stage, which is telling everybody else, and a dated copy is useful evidence of when the record became correct if anybody later queries a mismatch in the period before that.

What still has to be told afterwards

The update corrects the record at the Authority. It corrects nothing else, and this is the stage at which most people stop, which is why mismatches resurface years later.

Every institution that read the old value is still holding it. The bank. The employer and the payroll record. The provident fund account. The insurer, and the nomination details inside the policy. The investment accounts. The utility connections. The school or college. None of them will revisit it, and none of them will be told by anybody but you.

Work through them in order of consequence rather than convenience. Anything connected to money or identity verification first, because that is where a mismatch stops a transaction. Then the records that matter when something goes wrong rather than day to day — insurance nominations, and whatever will be read by somebody else after a death, which is the subject the legal heir certificate page deals with. Then the rest.

Some will need updating in their own right with their own processes: the voter record, the driving licence, the passport, a domicile certificate, a senior citizen card, an educational record requiring a migration certificate. Keeping the corrected record and its supporting document in one place, including in a DigiLocker account, makes the rest of this considerably less tedious.

Place Order — no advance, pay after work

What the record reaches, and what it does not

An Aadhaar record is quietly wired into a very large number of other records, and that is the whole reason a wrong field in it is expensive. A bank reads it at account opening. An employer reads it. A telecom operator reads it. A subsidy register reads it. A school reads it. None of those bodies rechecks it afterwards, which means an error entered once is copied outward silently and then has to be chased backwards through every copy.

One of those downstream readers is worth singling out, because the failure it produces is so badly misread. A health-scheme verification matches you against this record, so a name spelled two ways, a mobile number nobody holds any more or biometrics that will not read all return something that looks exactly like being told you are not eligible. Families give up at that point on an entitlement they hold. Our Ayushman card page separates the two.

That is also why the order of work matters. Correcting Aadhaar after you have already corrected six other records means doing the six again. Correcting it first means the rest follow from a source that is finally right. The order in which records should be touched during a change of name is set out in detail on the name change page, and after a marriage on the name change after marriage page, and we would rather send you there than restate it badly here.

What the record does not reach is worth saying with equal firmness. It does not reach your citizenship, your domicile, your right to reside anywhere, or your entitlement to any particular benefit. It is a number attached to a set of demographic fields and a set of biometrics, and the statute that created it says so in terms.

The mistakes that cost people months

Almost every long, miserable Aadhaar file we see began with one of a small number of avoidable decisions, and none of them looked like a mistake at the time.

The first is spending a lifetime chance on something that was never a change of name at all. A typing error made by an operator, a transliteration that came out wrong, or a spelling that shifted when a regional-language field was updated are all repairable without consuming a chance, provided they are presented as what they are. Presented instead as a name change, they are processed as one, and the count goes down by one for nothing.

The second is guessing at the field. People update a date of birth because a school record disagrees with Aadhaar, without first establishing which of the two is wrong. If the school record is the wrong one, the Aadhaar update was unnecessary, irreversible in practice, and has now spent the only straightforward correction available.

The third is running an update in the middle of something else. A loan under sanction, a passport application in progress, a tax filing season, a visa decision pending: during any of those, the record is being read by somebody, and changing it mid-read produces a mismatch rejection at the far end rather than a clean result.

The fourth is the bundle. People arrive at a centre intending to fix the name, the address, the photograph and the fingerprints in one visit, and discover that one of those cannot legally travel with the others. The visit is wasted and the fee is spent.

The three questions we ask first

Before we agree to run a file we ask three things, and the answers decide whether there is any work to do.

What does your record say now, exactly. Not what you remember it saying. We want the record as it currently stands, field by field, because roughly a third of the time the field the client wants changed is already correct and the problem is somewhere else entirely.

Which document do you want the record to agree with, and is that document itself right. An update aligns Aadhaar to a document. If the document is the defective one, the update propagates the defect into the most widely read record you own.

Has this field been changed before, and how many times. Because the caps are counted by the system and not by you, and a client who believes a field is untouched is frequently wrong about it. If a chance has already been spent, the route for the next change is a different and much longer one, and we would rather say so on the first call than discover it at a counter.

Place Order — no advance, pay after work

Five minutes before you start

Open your own record and read it. Compare it, character by character, against the one document you most want it to agree with. Write down the differences rather than holding them in your head, because the eye slides over a familiar name and misses a missing letter in it.

Then ask the question almost nobody asks: which of these two is actually wrong. It is not always Aadhaar. Where the other record is the defective one, the work belongs to the body that issued it, and touching Aadhaar would make the situation worse rather than better.

That comparison costs nothing and takes a few minutes. It is the single most useful thing on this page, and it prevents the only genuinely irreversible outcome available here, which is spending a limited chance on a field that did not need to move.

How we run this file

We start by reading the record with you and establishing what is actually different, which is a shorter conversation than most clients expect and occasionally ends with us telling them there is nothing to do.

Where there is work, we identify the field, the applicable list of documents, the channel that field can legally travel through, and whether a chance has already been spent. We then tell you which documents will hold and which will not, which is where most of the value sits, because a rejected request costs a fee and a wait and teaches you nothing about why it failed.

We prepare the file, present it through the correct channel, keep the acknowledgement, and track it. When the result comes back we check it against what was asked for, in writing, rather than assuming it went through. And if it was rejected we read the reason properly before anything is resubmitted, because a second identical submission fails identically.

What we do not handle

We do not issue, correct or obtain the underlying document. If the birth certificate is wrong, or the marriage certificate spells a name differently from the way you sign it, that is work at the issuing authority and it happens before anything here. An update cannot improve on the document it is built from.

We do not advise on whether you should change your name, your gender marker or anything else about how you are recorded. Those are yours to decide. Where the decision is the recognition of a gender identity under the dedicated statutory route, that is a different exercise with a different authority and its own page, and it is not something to be approached as an Aadhaar correction.

We do not update anybody else's record, and we do not act on an authorisation that arrives by message from a person we have never spoken to. The record belongs to the holder and the biometric authentication exists precisely so that it cannot be moved by somebody who is not them.

And we do not promise outcomes on the exception routes. Where a request has to travel through a regional office for a decision, the decision is theirs. We can present a file properly. We cannot guarantee what somebody else will do with it.

What we charge, and what UIDAI charges

We ask ₹399 to run an update file, against a typical span of 7 – 30 days in which the queue, not us, accounts for nearly all the clock. It covers reading your record, establishing which field is actually wrong, identifying the route and the channel, telling you which documents will hold, preparing and presenting the request, keeping and tracking the acknowledgement, and checking the result against what was asked for.

Separate from that, and payable to the authority rather than to us, are the update charges UIDAI itself publishes. Those are set out above with the Authority's own figures and its own deadlines, and they are the only update charges stated anywhere on this page.

Outside both sits the work of getting the source document issued or put right, travel to a centre where the field requires attendance in person, and any work at a different authority altogether.

Place Order — no advance, pay after work

The figures on this page, and where they come from

Every update charge, deadline and limit stated on this page is taken from material the Unique Identification Authority of India publishes itself, and from nowhere else. That is a deliberate restriction and it is worth explaining, because this is a subject on which the internet is unusually unreliable.

Aadhaar update rules move frequently, they move by circular and standard operating procedure rather than by amendment to the Act, and a great deal of what circulates about them is either out of date or was never right. Fee tables appear on sites that have no connection to the Authority. Deadlines get reported as permanent. A limit that exists with a documented exception route gets reported as absolute. We have stated the Authority's own figures, named the documents they come from and given their dates, so that you can check any of it against the source rather than against us.

We have also left things out on purpose. We do not state a processing time as a promise, because the Authority does not guarantee one. We do not reproduce the document lists in full, because they run to dozens of entries across four lists and a stale copy of such a list is worse than no copy. And we do not tell you what a particular regional office will decide on an exception request, because nobody outside that office knows.

Court work is for your advocate, whose fee is engaged and paid by you directly; we do not quote, collect or share it

One more reason the linked mobile number earns its own place on that list. The national register of unorganised workers runs its verification through this record, and a worker whose number is not the one held here cannot complete that registration from their own phone at all. Our guide to e-Shram card assistance explains the workaround and why fixing the link is the better answer.

A separate point on the documents you upload here. Supporting documents have to be legible after they have been reduced to whatever size the portal accepts, and the commonest cause of a rejected supporting document is not the document at all but a file that was compressed until the text went soft. Our guide to PDF compression and resize for portals covers doing that without destroying the original.

The date to put in your calendar

If your record carries documents that are eight or ten years old and you have not touched a demographic field since, the free online document update is the cheapest thing available to you, and it is available until 14 June 2027. After that date the same exercise carries the ordinary charge at a centre.

If you have a child between five and seven, or between fifteen and seventeen, the compulsory biometric update is free in those windows and is charged outside them. Those are age windows rather than calendar dates, which means they close on a birthday and not on an announcement, and a window missed is simply a fee incurred later.

And if you were relying on the concession for children between seven and fifteen, it is worth knowing plainly that it ended on 30 September 2026 and that the update is now chargeable for that group. That is recent enough that a great deal of advice still circulating has not caught up with it.

Asked at the counter, and asked again later