BWSSB's FAQ says status can show the application's stage and designation, ward/service-area selection routes it to the concerned sub-division AEE, engineers may contact the registered number, and the engineer should pre-inform the applicant of an inspection visit.
Evidence BRecord partialBasis observation
Read this with itOfficial FAQ guidance, not a case observation; its email/password route differs from the current mobile-OTP entry.
The official consumer manual describes a five-screen sequence: Consumer Details, Site Details, Building Details, Documents, and Review.
Evidence CRecord partialBasis observation
Read this with itOfficial manual sequence; post-login screens were not opened in a live account. The original official endpoint is currently unavailable; this claim is retained as incomplete historical/public evidence, not a current complete procedure.
The manual describes applicant/communication fields and connection-address routing fields, an existing BWSSB connection/RR number, BESCOM account verification, and site fields for PID/khata, construction date, purpose, flat/toilet counts where applicable, sital/built-up area, and NOC/RWH/OC information.
Evidence CRecord partialBasis observation
Read this with itManual-described fields; no property-specific validation, PID lookup, RR verification, or BESCOM request was run. The original official endpoint is currently unavailable; this claim is retained as incomplete historical/public evidence, not a current complete procedure.
The current public Jaladhare page exposes a mobile-number OTP entry, an application-number status lookup, and a Show All Application link; it says to use the same mobile number to know application status.
Evidence CRecord partialBasis observation
Read this with itOnly controls and labels were inspected. No phone number, OTP, application number, or property data was entered. The original official endpoint is currently unavailable; this claim is retained as incomplete historical/public evidence, not a current complete procedure.