Safety built into
every journey.
GrabCab is being designed with safety controls that connect rider verification, driver readiness, trip context, trusted contacts and human operations support.
Safety is a system.
It begins before pickup and continues through trip completion, support and incident review.
Driver readiness
Pickup verification
Incident workflows
Human support
Safety does not begin when something goes wrong.
GrabCab can layer safety controls across driver onboarding, pickup, active trips and operational response.
Driver readiness
Driver and vehicle eligibility can be checked before dispatch access is available.
Vehicle confirmation
Riders can review driver and vehicle details before entering the vehicle.
Pickup PIN
A supported ride can require verification before the trip begins.
Trip context
GrabCab maintains trip-state and location context during an active journey.
Trip sharing
Riders can share trip information with trusted contacts.
Operations support
Authorized teams can review incidents and support active trips.
Driver Verification
Trust starts before a driver goes online.
GrabCab’s driver architecture is designed so dispatch readiness can depend on identity, driver documentation, vehicle status and applicable market requirements.
Eligibility can be re-evaluated as records or requirements change.
Identity
Driver identity information can be reviewed as part of onboarding.
Licence & documents
Required driver credentials can be tracked for readiness.
Vehicle information
Vehicle details can be associated with an approved driver profile.
Market requirements
Eligibility rules can vary by country and operating market.
Verify before the journey begins.
Pickup Verification
Start the correct trip with the correct rider.
GrabCab can use a temporary pickup PIN to help confirm that a rider and driver are beginning the intended journey.
Verification before trip start
The trip should not transition into its active state until the supported verification step succeeds.
Simulated pickup PIN
Trusted Contacts & Trip Sharing
Keep someone you trust informed.
A rider can share relevant trip information with a trusted contact without giving that person control of the rider account.
Trusted contact
Demonstration contact
Active trip
New Kingston → Half Way Tree
Give safety teams the context to respond.
When an incident or emergency workflow is triggered, relevant trip context can be preserved and surfaced to authorized operations.
Incident & Emergency Workflow
Safety events need context, escalation and human response.
GrabCab can preserve active-trip information and surface relevant context when a supported safety or incident workflow is triggered.
Human-controlled response
Technology can surface information and assist workflows. Sensitive safety judgments remain subject to authorized human review and established policy.
1. Safety signal
A supported SOS or incident workflow is initiated.
2. Trip context preserved
Relevant trip, rider, driver and location context can be made available to authorized operations.
3. Operations review
Authorized personnel assess the event and available context.
4. Controlled action
Follow-up action is taken according to policy and authorized review.
Privacy & Control
Safety should not require unnecessary exposure of personal data.
GrabCab’s architecture can separate access by role, trip context and operational purpose while preserving appropriate auditability.
Access controls
Sensitive operational information should be restricted to authorized roles.
Purpose-limited visibility
Users and operations teams should only see information relevant to their role and workflow.
Account security
Authentication, sessions and security controls protect access to GrabCab accounts.
Auditable actions
Important administrative and operational actions can be preserved for accountability.
Safer mobility requires technology and accountable people.
GrabCab Intelligence can assist operations, while sensitive safety decisions remain governed by authorized review and policy.