Road-environment audit · SSI v0.3

The road outsideScholars International School

Shree Narayan Campus, Kalwar Rd, near Jaipur, Manglam City, Govindpura, Jaipur, Rajasthan 302044, India26.95701, 75.70033audited 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

Confirmed

Corrected

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

73.75points we could see (74%)

3.4%provision

1exposure — local

3.4provision × exposure

→

3SSI · rounded to nearest · v0.3

Only what the imagery could actually resolve is scored (74% 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 — Satellite · © Google · retrieved 2026-08-13 (capture date not published by the imagery API)

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

Junctionthe gate area sits at a 3-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 contextLow — 17/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≈80%

VerificationConfirmed — both readers agreed

The full reasoning

Carriageway is unpaved dirt/sand across the frontage and both approaches; no sound hump, table, rumble strip, or any physical speed-control device visible in any view. Painted markings are not possible on this surface.

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

VerificationConfirmed — both readers agreed

The full reasoning

No marked, raised, or signalised pedestrian crossing and no refuge anywhere in the zone; the unpaved carriageway carries no paint or crossing infrastructure.

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

VerificationConfirmed — both readers agreed

The full reasoning

No built footpath either side. School (south) frontage is a sandy tree-lined verge, not a walkable footpath; opposite side has only discontinuous private tiled house aprons at varying levels, not a continuous edge. A pedestrian is seen walking on the carriageway (Npd_cwTYOnaN_h108, HKt-pz_vMUL6_h108). Permanent condition; parked vehicles ignored.

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

VerificationConfirmed — both readers agreed

The full reasoning

No school-warning sign, speed-limit sign, carriageway speed stamp, or any 2023-identity/zone asset on any visible pole or frontage across the approaches. Only commercial shop/wall signage present (iJW68YY_1emm_h108, Npd_cwTYOnaN_h108). Heavy tree cover near the frontage limits certainty that no small sign is hidden.

◑

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

Reads differ (audit L0, blind L1). Deciding images: the two 2026-04 gate_wide frames. Re-examined: both clearly show a sandy setback verge between the traveled dirt carriageway and the boundary wall — a full-size car parks on it broadside in Npd_cwTYOnaN_h195_f90_gate_wide and a motorcycle plus a row of planted trees occupy it in iJW68YY_1emm_h177_f90_gate_wide. This positively refutes the audit's inference that the wall 'runs flush... opens directly onto the carriageway' (L0); the audit's read fell. A modest setback plus wall-and-partial-railing barrier supports L1. The exact gate opening stays tree/vehicle-occluded, so assembly-space quality, any separate pedestrian opening, and any pick-up bay are unassessable — L2+ excluded; L0 is positively excluded, so the residual L1/L2 pair resolves to L1. Observability settled 0.4 (visible frontage setback lifts it above the audit's 0.3; occluded gate holds it below the blind 0.45); confidence MED (the setback grounding L1 is clearly seen in two consistent frames).

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