Schools / Delhi

Road-environment audit · SSI v0.3

The road outsideNotre Dame School, Najafgarh

Kair, Delhi, 110043, India28.61340, 76.92561audited 2026-08-06

10/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, 3 are missing entirely.

This road · 10

0 · no protectioncomplete protection · 100

Checked twice, independently

Two AI readers on separate accounts · corrections logged in public

Confirmed

Corrected

Unresolved

See how each was judged

Of 153 roads scored so far, this one ranks 72 (worst first). The others scored between 0 and 41.

8.75points earned

84.75points we could see (85%)

10.3%provision

1exposure — local

10.3provision × exposure

→

10SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (85% 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

Satellite view of the same area — Satellite · © Google · retrieved 2026-08-13 (capture date not published by the imagery API)

FrontageThe gate opens onto a local street, on its E side

Junctionthe gate area sits at a 3-leg junction

Street activityno bus stop or shops mapped 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 contextLow — 17/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≈90%

VerificationConfirmed — both readers agreed

The full reasoning

No vertical speed-control devices (humps, tables, rumble strips, thermoplastic bumps) anywhere in the zone. Carriageway surface is visible on both gate approaches and across the full ~128 m traverse; it is plain asphalt with line markings only. Absence is observed, not inferred.

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≈85%

VerificationConfirmed — both readers agreed

The full reasoning

No marked pedestrian crossing (zebra or otherwise) at the gate or anywhere in the zone. Road carries only a faint centre line and edge lines. Immediate gate-front surface is partly under Google privacy blur, but the carriageway beyond it and along the traverse is clearly visible with no crossing markings. Undivided single carriageway, so no refuge question arises.

◑

Walking without stepping into trafficP3 · Footpath & separation

A broken walking edge

A walking edge exists but is broken or blocked for most of the frontage.

Partial

Also cited for this check

6.25 of 25 points

LevelMinimal (L1)

Points6.25 of 25

ConfidenceHigh

Coverage seen≈90%

VerificationConfirmed — both readers agreed

The full reasoning

Local street, so assessing continuous clear walkable edge (no raised-footpath requirement). No constructed/paved footpath exists anywhere in the zone. Informal earthen/grass shoulders run along both sides and are walkable in stretches (notably alongside the fields at VaE5zL4qWNMQ and znw2lhNP0SYI) but are discontinuous due to permanent causes: compound walls meet the carriageway edge near the gate and at FSdtGj3S4jG0, utility poles sit in the verge, and the shoulder drops to adjacent fields. No continuous clear usable edge on either side, so below L2. L0/L1 boundary is a judgement (earthen shoulder quality), hence MED.

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≈80%

VerificationConfirmed — both readers agreed

The full reasoning

The only roadside boards at the frontage are red institutional name/notice boards (school name), not traffic-control signage. No school-warning (triangular) signs, no speed-limit sign, no carriageway speed stamp, no zone-start/transition or 2023-identity assets, no beacon hardware seen on either approach. Board content is only partly legible, hence MED; but their form is clearly name-board, not warning sign.

◑

The gate itselfP5 · Gate environment

A small setback at the gate

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

Partial

Also cited for this check

2.5 of 10 points

LevelMinimal (L1)

Points2.5 of 10

ConfidenceMed

Coverage seen≈60%

VerificationConfirmed — both readers agreed

The full reasoning

Built form: a compound wall with a gate in it provides a barrier, and there appears to be a small paved/earthen strip between the gate area and the narrow carriageway (dD_w2J4D-aAt_h000_f90_road.jpg). No clear evidence of a generous off-carriageway assembly setback, a separate pedestrian opening, a continuous rail to a crossing, or a drop-off bay. The gate leaf and its immediate forecourt are substantially occluded by bougainvillea and by privacy blur, limiting observability, so scored at minimal-setback L1.

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