How we source data, what we show, and what we don't.
Kaun is a civic transparency tool for Bengaluru. Drop a pin anywhere in the city and see publicly available information about your ward — your elected MLA and MP, tenders awarded in your area, government spending, infrastructure, and active civic issues.
Kaun also covers India's 543 Lok Sabha constituencies: each MP's record, MPLADS spending, and delays and cost overruns on central government projects.
We are not a service portal. We don't file complaints or connect you to officials. We surface information that already exists in public records, aggregated in one place.
Elected representatives
MLA and MP details, assembly attendance, LAD fund utilisation, and declared criminal cases are sourced from Myneta.info and Karnataka legislative assembly records. Data is updated when new election affidavits or assembly records become available.
For Members of Parliament, the roster comes from the Lok Sabha Secretariat (sansad.in), attendance and questions from PRS Legislative Research, declared assets and cases from Election Commission nomination affidavits via Myneta.info, and MPLADS spending from MoSPI's eSAKSHI portal.
Tenders and contractors
Tenders come from the Karnataka Public Procurement Portal (KPPP) for 11 Bengaluru agencies: the five GBA city corporations, BWSSB, BDA, BESCOM, BMTC, BSWML and BMRCL. A ward card shows the latest tenders from its city corporation, not only that ward, because KPPP tenders are not reliably tagged to wards. Tenders refresh weekly; how they are fetched is documented at data.kaun.city.
Contractor records (total contracts, wards covered, payment deductions) are derived from BBMP work orders published on OpenCity.in. A ward's work orders also include those from BBMP's IFMS accounts portal, refreshed weekly. A blacklisting flag, where shown, is a documented case that names its source and date. Tenders a contractor won come from blr-tenders-bids by Vonter (Open Database License). They are matched by company name only, because neither record carries a registration number. Personal names and names shared by several firms are never matched. Payment deduction percentages reflect BBMP work order data — high deductions may indicate quality disputes, delays, or scope changes.
Budget and ward spending
BBMP budget data and ward-level spending figures come from OpenCity.in (CKAN open data portal) and BBMP's published budget documents. Years covered: 2018–23.
Grievances and Sakala
Ward grievance counts are sourced from BBMP's grievance portal via OpenCity.in, refreshed monthly. Sakala performance rankings (government service delivery timelines) come from the Karnataka Sakala portal, refreshed monthly.
Infrastructure & amenities
Ward-level counts for hospitals, pharmacies, ATMs, metro stations, public toilets, and EV charging points are sourced from OpenStreetMap (OSM), cross-referenced with BBMP ward boundaries. Data reflects OSM contributor coverage and may be incomplete in some areas.
Road crashes and air quality
Crash counts for 2024 and 2025 come from Bengaluru Traffic Police records, aggregated to ward level; they reflect reported crashes only. Air quality readings for 2024–25 come from KSPCB and CPCB monitoring stations.
Water quality
Lake water quality data (good / moderate / poor) is sourced from Karnataka State Pollution Control Board (KSPCB) monitoring reports, mapped to the nearest ward.
Bus stops
Ward bus stop counts come from BMTC's published stop lists via OpenCity.in. The lists repeat a stop once for every nearby polling booth, so Kaun counts each physical stop once.
Project records
Long-running Bengaluru projects, such as the Varthur–Gunjur corridor, the Ejipura flyover and the ORR metro, are documented from government orders, court records, parliamentary answers and attributed reporting. Every claim cites its source, and what is not public is stated as a gap. A project's wards are worked out from its mapped route. Delays and cost overruns on central government projects in the India view come from MoSPI's monthly flash reports (PAIMANA).
Trade licences
Ward-level trade licence counts are sourced from BBMP trade licence records via OpenCity.in, refreshed monthly.
News and civic signals
The CityPulse ticker shows recent news about BBMP, BWSSB, and Bengaluru civic issues from public RSS feeds: Citizen Matters, The News Minute, and Google News searches for BBMP, BDA, BWSSB, BESCOM and potholes, which also surface public posts on X. Each item is credited to its original publisher, marked “via Google News” when that is where the link goes. Articles are filtered for civic relevance — public money, contractors, budgets, elected representatives, road safety, flooding, water, waste, power and the environment.
Bengaluru has been redrawn repeatedly: the 2015 198-ward map, BBMP's 2023 225-ward delimitation, the KGIS/DataMeet 243-ward set used by many historical datasets, and the final Greater Bengaluru Authority 369-ward delimitation across five city corporations. Kaun renders the final December 2025 GBA boundary and ward-name update.
This matters because BBMP and IFMS tag every work order, payment and tender with the 225-ward or 243-ward systems, while current GBA ward numbers restart inside each corporation. Kaun resolves a selected place spatially and keeps the source ward key with each historical fact; it does not join old and new records just because their numbers match.
The Kaun Ward Crosswalk
No government or civic source publishes a mapping between the historical 225 and 243 schemes. So we built one — deterministically, by spatial polygon overlap of BBMP's official 225-ward boundaries against the 243-ward boundaries (no name guessing). It is versioned, every row cites its source, and it is open to public correction. Of 225 wards: 123 map cleanly 1:1, 83 have a clear primary 243 ward, and 19 genuinely straddle multiple 243 wards (we assign by largest overlap and record the full split).
Ward spending (2018-23), pothole complaints (2022) and ward committee meetings (2020-22) were recorded on the older 198-ward map, whose numbers name different places again (198 #25 is Horamavu; 243 #25 is Rajeshwari Nagar). A second crosswalk, built the same way, carries them: spend and complaint totals are allocated by the share of each 198 ward inside a ward, and a ward committee's meeting count is never split or added up; each committee is named under the wards it materially covers.
Full methodology, the dataset (CSV/JSON), and how to report an error: data.kaun.city/bengaluru/ward-crosswalk.
Kaun shows the underlying public measures directly: attendance, fund use, declared cases, ward meetings, infrastructure, complaints and contractor flags. It does not collapse unlike facts into one apparently precise ranking.
Why the change matters
Kaun's data records are not generated or gap-filled by AI.
The project research desk runs an AI web search when you ask it a question. Its answers are labelled AI-generated and are not reviewed. They may be cached for up to seven days and shown to other visitors who ask the same question. Only findings a reviewer approves join the project record.
Different datasets update at different intervals:
| Dataset | Refresh |
|---|---|
| KPPP tenders | Weekly (Sundays) |
| BBMP work orders (IFMS) | Weekly (Sundays) |
| Trade licences | Monthly (3rd) |
| BBMP grievances | Monthly (2nd) |
| Sakala rankings | Monthly (4th) |
| CityPulse news | Daily (6am UTC) |
| Civic signals | Daily (2am UTC) |
| MLA data | On election cycle / when new records published |
| MP roster and activity | Weekly (Sundays) |
| MPLADS spending | Monthly (6th) |
| Central projects (MoSPI) | Monthly (5th) |
| Project records | When reviewed; each record shows its review date |
| Budget and ward spending | Loaded once (2018–23) |
| Road crashes, air and water quality | Loaded once; each figure shows its year |
Data accuracy is our top priority. If you find something wrong — a wrong MLA name, an outdated tender, a broken boundary — please report it. We treat data corrections as the highest priority fix.
hello@kaun.city or file an issue on GitHub.
kaun.city presents data sourced entirely from public government records, official portals, and open civic datasets. We do not create, modify, or editorially characterise government data beyond what is stated in the source records.
Data accuracy depends on the source agencies. kaun.city is not responsible for errors, omissions, or outdated information in source data. If you find an error, please report it to hello@kaun.city and we will prioritise correcting it.
Contractor records shown on kaun.city are derived from BBMP work order data. Tenders shown on kaun.city come from the Karnataka Public Procurement Portal (KPPP). Blacklist information, where shown, is a documented case that names its source and date. Payment deduction percentages reflect data in BBMP work orders and may reflect legitimate scope changes, quality disputes, or administrative adjustments.
Criminal cases shown for elected representatives refer to cases self-declared by the candidate in their Election Commission of India nomination affidavit. These are not convictions. kaun.city makes no editorial judgment about individuals.
Net worth figures are self-declared in Election Commission nomination affidavits and are presented as-is. Percentage changes between election cycles are calculated by kaun.city from successive affidavit data.