Crashfree India School Safety Index DELHI · JAIPUR · PUNE

Schools / Pune

Road-environment audit · SSI v0.3

The road outsideIndira National School Pre-Primary

survey.No 85/8B, NH 48, Tathawade, Pimpri-Chinchwad, Maharashtra 411033, India18.61009, 73.75003audited 2026-08-06
3/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, 4 are missing entirely.
This road · 3
0 · no protectioncomplete protection · 100
Checked twice, independently
Two AI readers on separate accounts · corrections logged in public
4
Confirmed
1
Corrected
0
Unresolved
See how each was judged
Of 153 roads scored so far, this one ranks 14 (worst first). The others scored between 0 and 41.
2.5points earned
/
69.25points we could see (69%)
=
3.6%provision
×
0.75exposure — arterial
=
2.7provision × exposure
→
3SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (69% 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
FrontageThe gate opens onto an arterial road (Service Road), on its W side
Junctionthe gate area sits at a 5-leg junction
Street activity1 bus stop · 1 mapped shop within 150 m (OpenStreetMap)
Crash recordcrash-location data is not yet available for Delhi — this line will be added when a public source lands
Exposure contextElevated — 60/100 (partial: no crash component yet). 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≈75%
VerificationConfirmed — both readers agreed
The full reasoning

No speed humps, raised tables, rumble strips, or transverse bar markings visible anywhere on the service-road frontage in either direction; carriageway is worn asphalt with unpaved edges and no traffic-calming devices.

✕
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
ConfidenceMed
Coverage seen≈65%
VerificationConfirmed — both readers agreed
The full reasoning

No marked pedestrian crossing, remnant zebra, refuge, or signalised crossing visible anywhere in the zone on the service lane or across the barrier-separated main carriageway.

✕
Walking without stepping into trafficP3 · Footpath & separation

No footpath — children share the road

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

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

Arterial class requires a raised footpath; none exists on either side of the service lane. School side is an unpaved dirt shoulder along a corrugated-sheet hoarding; opposite side is the concrete barrier/embankment of the main carriageway. Pedestrians visible walking on the carriageway and dirt shoulder.

✕
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≈65%
VerificationConfirmed — both readers agreed
The full reasoning

No school warning signs, speed-limit signs, carriageway speed stamps, or 2023 school-zone identity assets visible on either approach; only a blue keep-straight/lane-direction sign on the corridor (not school-related).

◑
The gate itselfP5 · Gate environment

A small setback at the gate

A little setback or partial barrier — limited space off the road.

Partial⟳ Corrected in review
NoneMinimal

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

Also cited for this check
2.5 of 10 points
LevelMinimal (L1)
Points2.5 of 10
ConfidenceMed
Coverage seen≈40%
VerificationCorrected in the second reading
The full reasoning

Disagreement L0 (audit) vs L1 (blind), decided by the four gate frames. Re-examined all four: I8eafBBBCO2F h294 zoom/wide show buses flush against the fence below the name boards; NPTMXV_PZWQI h223 zoom/wide show continuous corrugated fencing with no opening in frame. The gate leaf is indeed never visible — the audit is right about that. But the audit's L0 ('gate opens directly onto carriageway') fell: both wide frames show a continuous unpaved verge several metres deep between the fence line and the service-lane carriageway along the entire frontage, in two independent panoramas. Wherever the gate sits in that fence, it opens onto this set-back verge, not directly onto the carriageway — positive built evidence for minimal setback (L1). The audit itself scored L0 'as a default, not as a confirmed absence', which conflicts with awarding the bottom level when the built setback is visible. L2 is not supportable: the verge is unsurfaced, undemarcated, and has no railing or built assembly space. Final L1, MED confidence (setback seen in two panoramas but exact gate position unverified). Observability gap (blind 0.5 vs audit 0.3, >0.15): the gap is the gate aperture itself (unseen, per audit) versus the frontage verge (well seen, per blind); settled 0.4 since setback is assessable but pedestrian opening and bay elements are not.

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