Journey approval and live monitoring
Journeys are planned with route, rest stops and a risk assessment, then approved before departure. Live position is compared with the plan, and deviations, overdue arrivals and curfew breaches alert.
Driver Safety & Journey Management
One serious incident costs the contract. Everything before it was visible.
Journeys planned, approved, monitored and evidenced, with driver behaviour, camera events and coaching on the same record.
- Built for
- HSE, transport and contract managers
- Connects
- Telematics, AI cameras and driver ID
- Deploys
- Sovereign cloud, private cloud or on-site
/ The shift /
What happens today, and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01Journey approval sits in a spreadsheet or a WhatsApp group, and cannot be produced when a client audits it.
- 02A driver is coached on a form months after the events that prompted it.
- 03Footage, telematics and the journey plan sit in three systems, so an incident investigation takes a week to assemble.
/ How it works /
From signal to decision in four moves.
Each step runs on the shared IoT Cube foundation, so nothing here is a separate system to maintain.
- 1
Connect vehicle and cabin
Telematics, AI cameras, driver ID and panic devices report into one record per vehicle, whatever the brand.
- 2
Tie events to the journey
Every event is linked to the approved journey, the identified driver and the client contract it was driven for.
- 3
Decide on the risk
Rules compare the live journey with its plan, rest rules and curfews, and score events by severity.
- 4
Act and evidence it
Supervisors are alerted in the moment, coaching tasks open with the footage attached, and completion is recorded against the driver.
/ What you get /
What driver safety & journey management gives you.
Behaviour detection from vehicle data
Accelerometer and CAN data detect speeding, harsh braking, harsh cornering and excessive driving time, with thresholds per vehicle type, road and client standard.
AI camera events with video
Camera-detected fatigue, distraction and phone use arrive as events with the clip attached to the trip and driver record.
Scorecards and coaching workflow
Events roll up into driver scorecards. Repeated or severe events open a supervisor coaching task, with completion and follow-up tracked.
Rest, route and curfew compliance
Driving hours, rest breaks, approved routes and night-driving windows are checked against each client standard, and breaches are logged with the journey.
Audit packs per journey or contract
Plans, approvals, events, video and coaching are compiled per journey, driver or contract for client audits and investigations.
/ Use cases /
Where teams put it to work first.
Approve journeys before departure
Plan routes, rest stops and risk, approve digitally, and compare the live journey against the plan.
Intervene on fatigue
Send camera-detected fatigue and distraction events to the journey manager with the clip, while the driver can still stop.
Coach from real events
Raise coaching tasks from repeated or severe events, attach the footage, and record completion against the driver.
Produce a client audit pack
Compile plans, approvals, events, video and coaching for a contract or period, and export for the client’s HSE team.
/ Benefits by team /
Every team gets a different answer from the same record.
01
HSE
Risk is handled on the road, with the evidence attached.
02
Operations
Deviations, overdue arrivals and curfew breaches reach a journey manager in time to decide.
03
Contracts
Compliance with client standards is shown continuously, and audit packs come from one record.
04
Drivers
Scorecards are built from events drivers recognise and can check.
/ In practice /
Three moments from a working week.
Each one starts with a signal and ends with someone acting on it. The scenarios are illustrative.
The signal
An AI camera detects repeated eye closure on a driver heading to Khurais at 03:05.
- 1
The in-cab alert sounds and the event reaches the journey manager with a clip.
- 2
The journey manager calls the driver and directs a stop at the next rest area.
- 3
The journey plan is updated and a coaching task is raised for review.
The outcome
The risk is handled on the road, and the record shows what was done.
/ Technology /
Four layers. One record underneath.
Device-neutral at the bottom, open at the top, and sovereign all the way through.
01
Devices in the field
Keep the hardware you already have
- Telematics units
- AI dash cameras
- Driver ID and fatigue sensors
- In-cab displays
- Panic and lone-worker devices
02
Connectivity & protocols
Any carrier, any protocol
- MQTT
- CAN / J1939
- Tracker-native TCP/UDP protocols
- RTSP / camera vendor APIs
- BLE driver ID
- 4G/5G via any Saudi carrier
- Satellite for remote routes
03
IoT Cube platform
Sovereign, multi-tenant, AI-neutral
- Workflow automation
- AI model runtime
- Rules & alerting engine
- Geospatial engine
- Role-based access & audit
- Reporting & exports
04
Your systems of record
Data lands where decisions are made
- HSE and incident systems
- HR and driver records
- Client contractor portals
- Training systems
A transport contractor working to major client HSE standards replaced manual journey approval with a live workflow, cutting audit pack preparation from days to minutes.
Story pending customer confirmation/ What you measure /
The numbers this produces.
Measured continuously, per asset, per site and per contract.
Journeys approved before departure
Share of journeys with a completed plan and approval before the vehicle moved.
Behaviour events per distance
Speeding, harsh driving, fatigue and distraction events normalised by kilometres driven.
Coaching completion
Coaching tasks raised versus completed, and time from event to conversation.
Rest and curfew breaches
Journeys that exceeded driving limits or ran outside permitted hours.
Alert response time
Time from a critical event to acknowledgement by a journey manager.
Audit pack turnaround
Time to produce the full record for a journey, driver or contract.
/ Rollout /
Start with one decision. Scale what works.
- Phase 1
Map standards and journeys
We review the client HSE standards you work to, your approval process, and the vehicles, cameras and systems in place.
- Phase 2
Run a pilot contract live
One contract’s vehicles and drivers move to digital journey approval, with telematics and camera events connected to each trip.
- Phase 3
Prove coaching and audit
Supervisors run coaching from real events, and a sample audit pack is produced and checked against the client standard.
- Phase 4
Roll out across contracts
Remaining contracts, sites and subcontractors adopt the same workflows and scorecards, one contract at a time.
/ Security & sovereignty /
Where your data lives, and who can reach it.
- In-Kingdom residency
- Built to national controls
- Isolated by tenant
- Your cloud or site
/ Built on IoT Cube /
Products already doing this.
Each one runs this solution on the shared foundation.
Built on IoT Cube
JMS
Journey safety: planning, approving, tracking and monitoring employee and contractor journeys.
Built on IoT Cube
Garix
Journey management for planning, monitoring and running business journeys and transport safety.
Built on IoT Cube
TEFCO
Saudi distributor of IoT and telematics hardware: trackers, dashcams, sensors, RFID, routers and EV chargers, fitted and supported.
Built on IoT Cube
GoPulse
Family car safety: live location, arrival alerts, driving scores, crash detection and car health in plain language.
/ Questions /
Frequently asked.
It was built against them. Send us the client standard you are held to and we will map it screen by screen.
/ Explore more /
Other solutions on the same foundation.
See driver safety & journey management on your own assets.
Bring the hardware you already run. We will connect a sample of it and show you the operating picture it produces.