1. How the Safety Score works
Every ride starts at a score of 100. Each time GatiKavach detects something unsafe during that ride, points are deducted — how many depends on how serious the detection is (see the table below). A ride's score can never go below 0, and it's calculated fresh for every single ride; nothing carries over from one ride to the next.
What you see on your Dashboard for each rider is an average of their individual ride scores:
- Today — the average score across every ride that started today. Shows 100 if they haven't ridden yet today.
- Last 30 Days — the average across every ride in the last 30 days. Shows 100 if there's no ride history yet.
2. How a ride is detected — starting and stopping automatically
Everything in Section 1 only applies once a ride is actually being tracked. This section explains how GatiKavach decides a ride has started and, later, that it's ended — entirely automatically, with no action needed from the rider. (A rider can also tap Start Ride / End Ride manually at any time from their app, which skips the detection steps below and starts tracking immediately.)
Starting a ride
To avoid draining battery, GatiKavach doesn't run GPS constantly in the background. Instead it uses a two-stage "wake ladder":
- Watching (no GPS, negligible battery use). The app watches two free signals — the phone's own motion sensors and Android/iOS's built-in activity recognition — for anything that isn't "still". This stage can run all day with the app closed.
- Confirming (GPS switches on for up to 60 seconds). The moment movement is sensed, GPS turns on to check whether this is a real ride. A ride is confirmed only when both of these are true within that 60-second window: speed above 15 km/h sustained for about 8 seconds, and the phone has genuinely moved at least 100 metres in a straight line from where it woke up. Requiring both, rather than either alone, is deliberate — a brief GPS speed spike by itself (common indoors, near reflective surfaces, in a lift) can't start a false ride.
If neither condition is met within the 60 seconds, GatiKavach quietly goes back to Watching and tries again the next time it senses movement — a real ride that took a little longer to confirm will still be caught on the very next attempt, usually moments later.
Stopping a ride
Once a ride is active, any one of the following four independent checks ends it — whichever condition is met first:
| Check | Condition | Why it exists |
|---|---|---|
| Stationary | Speed stays under 3 km/h for 90 seconds straight. | Catches a vehicle that's simply come to a stop and stayed stopped. |
| Parked and walking off | Speed stays under 10 km/h and the phone's motion sensors/step count say the rider is on foot, sustained for 60 seconds. | A parked vehicle with the rider walking away sits above the 3 km/h stationary threshold indefinitely (walking pace is faster than that) — this check catches that case on its own. |
| Backstop (no activity signal required) | Speed stays under 15 km/h for 5 minutes straight, regardless of what the motion sensors report. | A safety net for the rare case where the on-foot signal above doesn't fire for some reason — this still ends the ride eventually rather than leaving it running forever. |
| No signal at all | Zero location updates for 5 minutes while a ride is active. | Covers a tunnel, underground parking, or a dead zone — if GPS has gone completely silent rather than just showing low speed, the ride is treated as having ended rather than staying "Active" indefinitely. |
3. What each detection type does
GatiKavach checks for eight kinds of events. Six of them can be turned off per rider (see the next section); two run automatically on every ride and can't be disabled, since they're the app's own safety net against a device going dark or being tampered with.
| Detection | What it means | Severity | Points off | How it's throttled |
|---|---|---|---|---|
| Accident | A crash or major impact was detected from the phone's motion sensors, corroborated against GPS speed. | Critical | −25 | At most one alert (and one score hit) every 2 minutes, so a burst of sensor spikes from one real impact doesn't repeat as several separate incidents. |
| Distraction (phone call) | Rider is talking on a call while riding. The alert tells you whether they're using headphones or not — but the score impact is the same either way. | High | −10 | At most one alert (and one score hit) every 2 minutes for the same continuous call. |
| Hard braking | Sudden, heavy deceleration. | High | −10 | You may see more than one alert close together on a rough stretch of road — that's intentional, so nothing real goes unreported — but the score is only docked once every 2 minutes. |
| Zigzag / erratic riding | Sustained weaving, confirmed against both the gyroscope and the direction GPS shows the vehicle actually turning — a single pothole jolt isn't enough to trigger this on its own. | High | −10 | Same as Hard braking — every real detection alerts you, score docked at most once every 2 minutes. |
| Location turned off | The rider's device location was switched off, or became unavailable, mid-ride. | High | −10 | Every time location genuinely goes dark. Location coming back on is reported too, but never costs points — it's a resolution, not a violation. |
| Overspeeding | Riding above the speed limit you've set for that rider. | Medium | −5 | At most one alert (and one score hit) every 5 minutes for one continuous violation — overspeeding is a sustained state, not a single spike, so re-alerting every few seconds wouldn't add information. |
| Sudden acceleration | A sharp, rapid burst of speed. | Medium | −5 | Every real detection alerts you; score docked at most once every 2 minutes. |
| Geofence entry / exit | Rider entered or left one of the safe zones you've configured for them. | Informational | None | Not a safety violation — this one is purely for your awareness (e.g. "left School"), so it never affects the score. |
4. Turning a detection on or off
Every rider has their own independent settings — turning something off for one rider doesn't change it for any other rider you're watching.
- Open GatiKavach and go to your Dashboard.
- Find the rider you want to change, and tap the small edit (pencil) icon on their avatar.
- Scroll down to Safety Telemetry.
- Use the switches to turn each detection on or off. Changes save immediately — there's no separate "Save" step for these toggles.
| Detection | Can you turn it off? | Default |
|---|---|---|
| Crash detection (covers Accident alerts) | Yes | On |
| Hard braking | Yes | Off |
| Overspeed detection (also sets the speed limit itself, 30–120 km/h) | Yes | On, limit 75 km/h |
| Zigzag detection | Yes | On |
| Distraction detection | Yes | On |
| Geofence detection (also where you manage safe zones) | Yes | On |
| Sudden acceleration | No — always on | — |
| Location turned off | No — always on while a ride is being tracked | — |
Turning a detection off doesn't hide history you already have — past alerts and score deductions from before you turned it off stay exactly as they were. It only stops new ones from being generated going forward.
5. A few things worth knowing
- This is a supplementary safety aid, not a guarantee. Detection depends on network connectivity, GPS accuracy, and the phone's own sensors, and can be delayed, degraded, or fail entirely — for example if the device has no signal, its battery is dead, or its location services are off. Don't rely on GatiKavach as a sole safety measure in place of good judgement and safe riding practice. See our Terms of Use for the full statement.
- Cooldown windows exist to keep alerts meaningful, not to hide problems. They control how often the same type of event can affect the score or send a fresh push notification during one continuous situation — they never suppress a genuinely new, separate incident.
- Only a Guardian can change these settings — a Rider can't turn their own detections off from their side of the app.
- For what data is collected and how long it's kept, see our Privacy Policy.
Questions about how scoring works for your family? Reach us at [email protected].