Journey approval and live monitoring
Journeys are planned with route, rest stops and a risk assessment, then approved before departure. Once live, position is compared to the plan and deviations, overdue arrivals and curfew breaches raise alerts.
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 connected to the same operational 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 is actually happening today — and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01Journey approval lives in a spreadsheet.
Or a WhatsApp group. Either way it cannot be produced quickly when a client audits it.
- 02Behaviour is judged annually.
A driver is coached on a form months after the events that should have prompted it.
- 03Evidence is scattered.
Camera footage in one place, telematics in another, the journey plan in a third, and an incident investigation that 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 hardware 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 behaviour events by severity.
- 4
Act and evidence it
Supervisors are alerted in the moment, coaching tasks are raised with the footage attached, and completion is recorded against the driver.
/ What you get /
Capability, not just visibility.
Behaviour detection from vehicle data
Accelerometer and CAN data detect speeding, harsh braking, harsh cornering and excessive driving time. Thresholds can differ by vehicle type, road and client standard.
AI camera events with video
Camera-detected fatigue, distraction and phone use arrive as events. The clip is attached to the trip and driver record, so review starts with the evidence.
Scorecards and coaching workflow
Events roll up into driver scorecards. Repeated or severe events open a coaching task for a supervisor, and completion and follow-up are tracked.
Rest, route and curfew compliance
Driving hours, rest breaks, approved routes and night-driving windows are checked against the rules set for each client standard, and breaches are logged.
Audit packs per journey or contract
Plans, approvals, events, video and coaching records are compiled per journey, driver or contract, and exported for client audits or investigations.
/ Use cases /
Where teams put it to work first.
Approve journeys before departure
Plan routes, rest stops and risk, approve them digitally, and compare the live journey against the plan once it starts.
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 it 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 evidence attached, not reviewed after an incident has already happened.
02
Operations
Deviations, overdue arrivals and curfew breaches reach a journey manager in time to make a decision.
03
Contracts
Compliance with client standards is shown continuously, and audit packs come from one record instead of four.
04
Drivers
Scorecards are built from events drivers recognise, so coaching is specific, fair and based on what actually happened.
/ In practice /
What it looks like on an ordinary Tuesday.
Three moments where the platform earns its place. 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 operating to major client HSE standards replaced manual journey approval with a live workflow — and cut the time to produce an audit pack from days to minutes.
Story pending customer confirmation/ What you measure /
Numbers that replace arguments.
The indicators this solution produces 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 journey approval process, and the vehicles, cameras and systems already 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 join on the same workflows and scorecards. Weeks, not quarters, per wave.
/ Security & sovereignty /
Sovereign is a place, not a promise.
In-Kingdom residency
Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.
Built to national controls
Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.
Isolated by tenant
Tenant isolation, role-based access and a full audit trail across users, actions and devices.
Your cloud or site
Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.
/ Built on IoT Cube /
Runs on the platform, not beside it.
Products already running this solution on the shared foundation.
Built on IoT Cube
JMS
Journey safety for planning, approving, tracking and monitoring employee and contractor journeys.
Built on IoT Cube
Garix
Journey management to plan, monitor and manage business journeys and improve transportation safety.
Built on IoT Cube
TEFCO
Saudi IoT and telematics hardware — GPS tracking, RFID, AI cameras, sensors and RTLS, installed and supported.
Built on IoT Cube
GoPulse
Family vehicle safety — visibility of your vehicles and loved ones, with security and peace of mind.
/ Questions /
Frequently asked.
Does it meet the journey management standards our clients require?
It was built against them. Send us the client standard you are held to and we will map it screen by screen.
Do drivers accept it?
Better than they accept an annual review based on nothing. Scorecards drivers can see, with events they recognise, is the part that changes behaviour.
Can we use our existing cameras?
In most cases yes.
How is driver data handled under PDPL?
Driver identity, behaviour and video are personal data. Access is role-based and audited, retention is configurable, and data stays in the Kingdom — designed to support your PDPL obligations.
Does it connect to our HSE and incident system?
Yes. Journeys, events and investigation packs can be pushed to HSE, HR and client contractor portals through APIs, webhooks or scheduled exports.
What happens to camera footage on remote routes?
Events are recorded on the device and clips upload when coverage returns. The event itself reaches the platform first, so the alert is not held back by the video.
/ Explore more /
Other solutions on the same foundation.
Fleet & Asset Operations
Know where assets are, how they are performing, and where attention is needed.
Cold Chain & Compliance
Monitor conditions continuously and create the operational record while products move.
Predictive Maintenance
Use condition and usage data to move from failure response to planned work.
Bring us the decision that takes too long today.
Start with the problem. IoT Cube provides the foundation underneath.