Crashfree India School Safety Index DELHI · JAIPUR · PUNE

Schools / Jaipur

Road-environment audit · SSI v0.3

The road outsideRajasthan Sadhna Public School

B-45, Vishnu Vihar, Jagatpura, Jaipur, Rajasthan 302017, India26.83113, 75.82988audited 2026-08-06
0/100
Critically unsafeprovisional band
Critically unsafe. Almost nothing on this road protects a child from traffic on the way to the gate.
Of the five things we check, 5 are missing entirely.
This road · 0
0 · no protectioncomplete protection · 100
Checked twice, independently
Two AI readers on separate accounts · corrections logged in public
3
Confirmed
2
Corrected
0
Unresolved
See how each was judged
Of 153 roads scored so far, this one ranks 1 (worst first). The others scored between 0 and 41.
0points earned
/
67.9points we could see (68%)
=
0.0%provision
×
1exposure — local
=
0.0provision × exposure
→
0SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (68% of the rubric here); the rest is left uncounted rather than guessed. A road with full protective infrastructure scores near 100.

The road in context · derived from public data

Where this road sits

Before the checks: what kind of road this is, how it meets other roads, and what passes it. These lines describe the road and its surroundings — they do not change the score.

Road layout around the gate, drawn from OpenStreetMap
Road layout · drawn from OpenStreetMap · blue dot = school coordinate · red = fatal-crash points (Jaipur Police)
Satellite view of the same area© Google
Satellite · © Google · retrieved 2026-08-13 (capture date not published by the imagery API)
FrontageThe gate opens onto a local street, on its S side
Junctionthe gate area sits at a 4-leg junction
Street activityno bus stop or shops mapped within 150 m (OpenStreetMap)
Crash recordno road death within 500 m of the gate in the Jaipur Police crash data
Exposure contextModerate — 22/100. Describes how much traffic and crash risk passes this road — context only, never part of the road score (method: exposure v1, Data page)

Road layout data © OpenStreetMap contributors (ODbL), retrieved 13 Aug 2026 · crash data: Jaipur Police · derivations: `exposure_v1` on the Data page.

What we found · five checks · IRC:SP:32-2023

Five things we checked — and the photo behind each

Each check was read once, then verified blind by a second reader on a separate account. The photo each finding came from sits right beside it. Tap “see how this was judged” for the full reasoning.

✕
Slowing traffic downP1 · Physical speed control

Nothing slows traffic at the gate

No speed hump, table or rumble strip on the approach — vehicles reach the gate at full speed.

Absent
Also cited for this check
0 of 30 points
LevelNone (L0)
Points0 of 30
ConfidenceHigh
Coverage seen≈72%
VerificationConfirmed — both readers agreed
The full reasoning

No speed hump, table, rumble strip or raised crossing on any approach or at the gate; carriageway is plain compacted dirt throughout.

✕
Getting across the roadP2 · Safe crossing

No safe place to cross

No marked or raised pedestrian crossing at or near the gate.

Absent
Also cited for this check
0 of 25 points
LevelNone (L0)
Points0 of 25
ConfidenceHigh
Coverage seen≈70%
VerificationConfirmed — both readers agreed
The full reasoning

No marked crossing, stop line, table or refuge anywhere; gate frontage is bare dirt so no markings possible; single undivided lane.

✕
Walking without stepping into trafficP3 · Footpath & separation

No footpath — children share the road

No usable walking edge; children walk in the traffic lane.

Absent⟳ Corrected in review
NoneNone

An independent second reader changed this — the two readings disagreed, and the evidence below settled it.

Also cited for this check
0 of 25 points
LevelNone (L0)
Points0 of 25
ConfidenceHigh
Coverage seen≈72%
VerificationCorrected in the second reading
The full reasoning

Split: audit L0, my blind L1. Deciding images -XhJYg1Rv_NI_h266/_h086, KzeAaJVw5EQf_h271/_h091, x2O8Vd1WmWQn_h202/_h022, mOFbmaLOQvjI_h068/_h248. On re-examination the carriageway and its margins are a single undifferentiated dirt/sand surface with no curb, level change or paved strip demarcating a walking edge; the only raised surfaces are discontinuous private entry plinths at individual thresholds, which do not connect into a through path. Under 'permanent built condition only + positive evidence', there is no walkable edge that 'exists but is broken', so L0 is the better fit. My blind read fell — it over-credited informal margins/plinths as an edge. Well and repeatedly seen, so HIGH.

✕
Being seen and expectedP4 · Signage & zone identity

No school-zone signs

Drivers get no warning that a school gate is here.

Absent
Also cited for this check
0 of 10 points
LevelNone (L0)
Points0 of 10
ConfidenceHigh
Coverage seen≈68%
VerificationConfirmed — both readers agreed
The full reasoning

Only the school's own name/achievement board and a 'SADHANA' advertising banner present (identity, not traffic signage). No school-warning sign, speed sign/stamp, zone-start or 2023-identity asset seen on any approach.

✕
The gate itselfP5 · Gate environment

The gate opens onto the road

Children step from the gate straight toward moving traffic.

Absent⟳ Corrected in review
NoneNone

An independent second reader changed this — the two readings disagreed, and the evidence below settled it.

0 of 10 points
LevelNone (L0)
Points0 of 10
ConfidenceLow
Coverage seen≈40%
VerificationCorrected in the second reading
The full reasoning

Split: audit L0, my blind L1. Only the two -XhJYg1Rv_NI gate frames view the entrance, and in both the actual gate leaf/wall-base is occluded by a utility pole and a parked car/van; no setback, railing, pedestrian opening or drop-off bay is positively visible. L1 requires positive evidence of a minimal setback/partial barrier; my blind L1 inferred a setback from an undifferentiated dirt expanse and a receding lane, which is inference not positive evidence, so it falls to the L0 floor. The two reads' observability differ by ~0.15; that gap is entirely the immediate gate-opening/wall-base segment hidden by the pole and parked van. Gate genuinely not in frame, so LOW.

At the gate
On the frontage road
Along the street
Some captures sit on neighbouring lanes; older ones are shown greyed and were used only for context.
What must be fixed · 5 actions

What would make this road safe — and who owns each fix

Each action maps to a failing check, the relevant IRC:SP:32-2023 clause, and the responsible agency. Agency labels are provisional and correctable through the dispute channel.

01Lifts P1

Install a speed table or twin speed humps within 30 m of the gate

IRC:SP:32-2023 §5.13 · Table 5.1MCD / PWD · provisional

Speed humps near schools roughly halve child-pedestrian injury odds (Tester 2004); 30 km/h calmed zones ≈ 40% fewer casualties (Grundy 2009).

02Lifts P2

Mark a crossing within 20 m of the gate — table-top preferred

IRC:SP:32-2023 §5.4.3MCD / PWD · provisional

Raised crossings cut vehicle speeds at the exact conflict point.

03Lifts P3

Provide a continuous clear walking edge on the school side

IRC:SP:32-2023 §5.4.1MCD / PWD · provisional

A continuous footpath keeps children off the carriageway on the approach, not only at the gate.

04Lifts P4

School-zone warning signs on both approaches with the speed limit

IRC:SP:32-2023 §5.8MCD / PWD · provisional

The zone must announce itself to drivers before the gate.

05Lifts P5

Add space and a marked pick-up bay off the carriageway at the gate

IRC:SP:32-2023 §5.2MCD / PWD · provisional

Children should not step from the gate into a moving traffic lane.

Responsible-agency labels come from the CFI field instrument’s mapping and are correctable via the dispute channel.

Re-audit timeline

2026-08-06Audited
2027-02-06Re-audit due

Every published road is re-read every six months, or as soon as new Street View imagery lands, or on a sustained dispute.

Something wrong on this page?

The entrance, the imagery, a finding — if any of it is wrong, tell us. A dispute pauses this page while the audit is re-verified, and the correction is logged in the public record.

Dispute this audit