The public e-Khata Application Status page accepts an EPID for status lookup.
Evidence BRecord verifiedBasis observation
Read this with itIt does not document BESCOM mapping.
The public e-Khata Application Status page exposes Stage, From, received and sent timestamps, Sent To, Status, and Remarks for an EPID lookup.
Evidence BRecord verifiedBasis observation
Read this with itObserved without entering an EPID; no property-specific state was accessed.
The public e-Aasthi Pending Mutation Report displays registered-deed or mutation date, property EPID, seller, purchaser, and pending-owner fields.
Evidence BRecord verifiedBasis observation
Read this with itThe visible report does not establish a completed buyer-facing record.
The public e-Khata Application Status page displays No Data Available for an empty lookup.
Evidence BRecord partialBasis observation
Read this with itAn empty lookup result, not a property-specific rejection explanation.
The public e-Khata Application Status page publishes helpline 9480683695 for issues.
Evidence BRecord partialBasis observation
Read this with itThe public page publishes the number; its case-resolution scope was not tested.
BESCOM's current public homepage exposes a service labelled Name Change with EPID.
Evidence CRecord partialBasis observation
Read this with itReconciles IND-4 and IND-6 duplicate observations; this does not verify eligibility or a mapping contract. Downgraded from Grade B on 2026-08-29: the available citation is a general-site reference rather than claim-specific evidence.
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.
Evidence BRecord verifiedBasis observation
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.
Evidence BRecord verifiedBasis observation
Read this with itReconciles IND-4 and IND-8 duplicate tracker claims.
One citizen reported that a recent municipal mutation had completed but they had not received an expected BESCOM initiation message.
Evidence ERecord partialBasis observation
Read this with itThis identifies an individual missing handoff, not proof that every completed mutation should generate a message.
One citizen reported that the e-sign stage displayed an error for several days before later advancing.
Evidence ERecord partialBasis observation
Read this with itAn individual timing and outcome, not a service-level timeline or documented recovery route.
One citizen reported a name-transfer error saying that an application of the same type was already open while reporting that no open application was visible to them.
Evidence ERecord partialBasis observation
Read this with itAn individual report; it does not prove why the state occurred or that any response route resolves it.
One citizen reported that the name-transfer flow remained on a loading screen after identity proof was uploaded.
Evidence ERecord partialBasis observation
Read this with itA reported upload-stage failure only; no reliable cause or recovery is established.
Citizen accounts report EPID-entry, login/reset, unseen-open-application, and upload-stall failures in BESCOM flows.
Evidence ERecord partialBasis observation
Read this with itReports identify failure modes only; no backend cause, support outcome, or general workaround is established.