Before you apply Electricity name transfer
Electricity name transfer · your situation
The previous consumer cannot or will not provide consent.
Block one
Found in public documents, graded and dated. The statements closest to your situation come first; a single first-person account never outranks the documentary record. Open any source to read it yourself.
Historic clause 36.01 lists ownership evidence, including registered sale deed, khata, succession or heirship certificate, and will, where consent is absent.
Read this with itHistoric binding text; it is an evidence lead, not a verified current checklist.
The BESCOM-hosted Conditions PDF says that, where consent is absent, occupancy proof such as a valid power of attorney, latest rent-paid receipt, or valid lease deed is limited to non-commercial lighting and non-commercial combined lighting-and-heating installations.
Read this with itThis is not a general tenant entitlement or a current acceptance checklist; the tariff/category and current applicability remain unverified.
The BESCOM-hosted Conditions PDF says that, in the absence of the registered consumer's consent letter, the transferee may produce ownership evidence including a registered sale deed, partition deed, khata, succession or heirship certificate, or deed of last will.
Read this with itThe listed succession/heirship and will options are evidence leads for the deceased-consumer route, not proof that any supplied document will be accepted now.
Historic KERC Conditions clause 36.01 says the registered consumer furnishes consent for transfer of the installation and deposits.
Read this with itHistoric binding text; current applicability is not established.
BESCOM’s public Track Name Change page displays “Call 1912” for help.
Read this with itThe visible help label does not establish that 1912 resolves a name-transfer exception.
The current unauthenticated BESCOM Janasnehi name-change URL rendered the common shell but no visible name-change form, exception selector, error text or recovery link.
Read this with itThis is a direct public-render observation only; it does not establish whether the form appears after login or under a different route.
The public BESCOM customer-login page displays User ID, Password and image CAPTCHA controls; no authenticated name-transfer fields were inspected in this pass.
Read this with itDirect public observation of the login controls. This does not establish when or how an applicant reaches account-specific name-transfer fields.
BESCOM's public maintenance page can display a scheduled-upgradation message saying online services are temporarily unavailable.
Read this with itThe page provides no exception-specific retry time, alternate submission route or case queue information.
BESCOM exposes a public billing-related complaint tracker with Request ID, request-raised date and Search controls, but its applicability to name-transfer exceptions is not established.
Read this with itIt is retained as a general recovery lead only; no complaint was created, and the page is explicitly billing-related.
The BESCOM-hosted Conditions PDF says that the registered consumer furnishes a consent letter to transfer the installation and deposits to the transferee.
Read this with itThis records wording in the currently hosted but visibly older Conditions PDF. It does not establish a current authenticated consent field or acceptance decision.
The BESCOM-hosted Conditions PDF says that the transferee executes a fresh power-supply agreement with the licensee for transfer.
Read this with itNo agreement form, current signature process, or completed agreement was inspected.
The BESCOM-hosted Conditions PDF says that no arrears may be outstanding against an installation for transfer.
Read this with itNo account balance or arrears outcome was queried.
The BESCOM-hosted Conditions PDF says that, where the registered consumer has not consented to transfer of the deposit, the transferee pays a fresh deposit as a new consumer.
Read this with itNo deposit calculation, demand, or payment was observed; do not state an amount.
The BESCOM-hosted Conditions PDF says that the transferee executes an Annex 9 indemnity bond for disputes arising from the transfer.
Read this with itAnnex 9 is present in the hosted PDF. No current BESCOM submission route or acceptance of an indemnity bond was observed.
BESCOM's public FAQ directs a name-change applicant to authenticate, select an account ID, complete mandatory fields, upload required documents, submit, retain a request ID, and pay applicable charges.
Read this with itReconciles IND-4, IND-6, and IND-8 duplicate FAQ claims. The public FAQ does not enumerate the current document checklist.
BESCOM's public tracker requests the request ID sent by SMS.
Read this with itReconciles IND-4 and IND-8 duplicate tracker claims.
One person who said their e-Khata had been completed reported that the BESCOM name-change login appeared to require a phone/OTP associated with the builder's contact and asked how to proceed without an offline route.
Read this with itOne 2026 account of a perceived login/contact obstacle. It does not prove the builder's contact was the only possible credential, a builder consent requirement, an e-Khata effect, or a current BESCOM rule.
One prospective name-transfer user reported being unable to check progress because the one-time password was sent to the previous owner's phone number.
Read this with itOne 2026 report of a previous-contact dependency. It does not establish that an OTP is generally required, that it functions as legal consent, that the previous owner was unavailable, or the current correction path.
Block two
Accounts we could not reconcile. We kept both rather than picking a winner.
An older offline-process citizen account reported needing a previous-owner or builder NOC for BESCOM name change.
Read this with itOlder account; conflicting evidence is retained, not resolved by chronology alone.
One 2026 citizen account reported completing an online BESCOM name change after e-Khata update without a builder NOC.
Read this with itOne current citizen account; it does not establish an exception rule.
Block three
Two kinds of thing sit here: questions the published record leaves open, and points where our own reading stopped — at a login we did not cross, or a step we could not observe without applying. Each item says which it is. Both are reasons to ask before you apply rather than after.
This pass produced no BESCOM request ID, exception decision, document acceptance, payment demand, approval, updated bill name or tracker status.
Where we stoppedNo login, account identifier, upload, payment, submission or tracker query was made.
No current unauthenticated BESCOM page reviewed in this pass establishes whether a tenant, successor after death, or applicant without previous-consumer consent is eligible, which documents replace consent, what deposit or arrears treatment applies, or how an exception is approved.
What we checkedFAQ, login, direct JVS route, name tracker, complaint tracker and maintenance page were reviewed without crossing authentication or submitting data. Historical rules in the canonical ledger are not treated as current public workflow evidence.
This pass did not establish a current public BESCOM rule for acceptance of tenant occupancy evidence, deceased-consumer succession evidence, or a no-consent transfer packet in the authenticated Name Change route.
Where we stoppedThe public FAQ was inspected without login and the current hosted Conditions PDF has unresolved applicability. No account-specific validation or submission was attempted.
Block four
Failure points recorded for this situation, with the recovery the record supports — or the absence of one.
Applicant cannot furnish consent to transfer the installation and deposit.
An outstanding balance may prevent transfer.
Public FAQ directs uploads but does not enumerate them before login.
An older account reports needing an NOC while a 2026 account reports completion without builder NOC.
Public BESCOM material exposes a generic authenticated name-change route while the hosted exception Conditions text has unresolved current applicability.
The standard route requires BESCOM customer login with User ID, password and image CAPTCHA; the direct unauthenticated JVS name-change URL exposes no form.
Public BESCOM pages describe a generic name-change document stage but do not identify exception-specific evidence, deposit, arrears or consent-substitute rules.
No name-transfer request, SMS Request ID, complaint query, document decision, payment, approval or updated bill name was produced.
Two citizens reported that a name-transfer login or status check appeared to depend on a previous owner's or builder's recorded phone/OTP route.
Check us
Read them yourself. If one has moved or changed since we checked it, that is worth knowing before you act.
Not your case?
How to read the gradesA — binding law, regulation, commission order or gazette notification. B — current official procedure, form, portal or agency page. C — official but indirect, incomplete, archived, undated or potentially outdated. E — genuine public first-person evidence. Unknown — no usable source.
Research aid, not official advice. It records public evidence and uncertainty; do not submit personal data through this ledger. Evidence collected as of 2026-08-31; nothing on this page is generated when you open it. Every statement is a recorded claim you can trace to the source above, and the unsettled items stay unsettled on purpose.
What our own audit said it could not closeRetain Unknown, Partial, and Contested states; verify a current case through authorized channels rather than treating desk research as an approval path.