Independent prototype — synthetic data

Department & public insights

Where the days actually go

Turnaround for every step of every scheme, computed from the access-event timeline of 20 applications. Grey is time a file spent waiting in a queue before anyone opened it. Blue is an officer actually working.

Slowest step right now
Village officer inspection
Held at
Village Accountant, Sedam
Median time
7.4 days (target 7)
Of which queue
4.2 days (57%)

Misses its 7-day target in 50% of applications.

Social Welfare · Karnataka

Post-matric scholarship

StepOfficeMedianTargetWaiting vs handlingBreach
Application receivedScholarship Cell0.6d1d0.2d · 0.4d0%
Checking your ID and bank detailsScholarship Cell1.9d2d0.9d · 1d29%
Confirming you live in this districtqueue bottleneckTaluk Office, Sedam3.8d3d3d · 0.8d93%
Checking your family incomeRevenue Dept, Kalaburagi3.9d5d1.1d · 2.9d29%
Checking your category certificateSocial Welfare Dept2.2d3d1d · 1.1d7%
Checking your Class 12 marksheetqueue bottleneckDistrict Education Office, Kalaburagi7.1d3d5.7d · 1.1d100%
Approving paymentTreasury3.2d5d1.8d · 1.6d0%

Averages 7.1 days. 5.7 of them are queue time before any officer opens the file — a staffing decision, not a training one.

Revenue · Karnataka

Income certificate

StepOfficeMedianTargetWaiting vs handlingBreach
Application receivedTaluk Office, Sedam0.5d1d0.1d · 0.4d0%
Checking your IDTaluk Office, Sedam2.1d2d1d · 1.2d50%
Village officer inspectionVillage Accountant, Sedam7.4d7d4.2d · 3.1d50%
Signing the certificateRevenue Dept, Kalaburagi2.1d3d1.1d · 0.9d0%

Misses its 7-day target in 50% of applications.

One engine, every department

These two schemes sit in different departments — Social Welfare and Revenue — and share zero custom code. A scheme is a list of steps in a table: a name, an office, a target, and the documents each step needs. Adding a department is a row, not a rebuild.

The same is true across states. The workflow rows change; the tracking layer does not.

See a citizen's viewWhat is real here