FleetCoRAI software MVP

Client Login

Lite PlanDraft setup

Selected pathway

Lite Plan

Use existing driver scores

Ingests the provider score out of 100.

What this unlocks

Setup workflow

Lite setup workflow

White-label platform layer

Behavioural intelligence above fleet systems

Input systemsTelematics, FMC, OEM, HR, safety and policy data
FleetCoRAI layerBehaviour scoring, AI Personas, coaching, rewards and audit trail
Branded outputsManager portal, driver app, reports and partner dashboards

Tenant safety model

Client data separation

Commercial packaging

Partner and client options

Bolt-on deployment

How customers access it

Customer Settings

Package, branding, modules and controls

Package control

Active plan and included modules

Branding

White-label profile

Sally engagement

Campaign and reward settings

Security

Tenant and role controls

Lite pilot workflow

Customer handover pack

Use this screen to explain exactly what a Lite pilot customer needs to provide, what FleetCoRAI will show, and where the Lite boundary sits.

Trial mode Lite MVP Near real-time imported scores and breach records
1

Set up pseudonymous drivers

Each driver receives a unique driver ID and driver login. Real names are not required for the pilot.

  • Driver ID, depot, state and vehicle reference
  • Driver login ID for the driver app
  • Current score, previous score and breach counts
2

Import Lite breach records

The customer can provide breach files from a telematics/FMC/OEM source. The Lite MVP displays what is supplied.

  • Breach type, date, time and location label
  • Latitude and longitude for map display
  • Severity or review status where available
3

Show driver and manager views

Managers see trends, report evidence and audit actions. Drivers see their own Lite score, recent events and persona guidance.

  • Sage, Sally and Jon are available in Lite
  • Marshall and Trish are not included in Lite
  • Evidence is mapped only when coordinates are supplied
!

Confirm Lite exclusions

Lite does not validate false positives and does not make legal findings. It does not ingest continuous trip data, video or live GPS streams.

  • No false-positive validation
  • No route, shift or depot timing analysis
  • No collision investigation workflow

Pilot readiness

Current backend sample

Drivers-
Fleet score-
Mapped events-
BackendSync
Uses the same Lite backend as the Manager Dashboard.

Lite pilot access

Pseudonymous pilot users

Use this as the pilot access sheet. Drivers can log in with a unique ID, while the customer keeps the real-name mapping outside FleetCoRAI.

Privacy model FleetCoRAI stores driver IDs and login IDs for the Lite pilot. The customer can hold any real-name lookup separately in their own HR or fleet system.
No pilot users loaded yet.Sync the Lite backend to show the current driver login list.

Production pathway

MVP to production readiness

This area separates what is ready for a controlled Lite pilot from what must be coded and hardened before using real customer data at scale.

Current stage Lite Pilot Demo login only. Production auth still required.
Ready for controlled demoClient admin experience

Front-page login, admin workflow screens, pilot users, imports, dashboard, driver app and reports.

Ready for controlled demoPseudonymous Lite pilot data

Driver IDs, login IDs, scores, breach counts and mappable event records without real names.

Build nextProduction authentication

Secure password storage, sessions, roles, tenant-level access checks and password reset.

Build nextProduction database

Replace local JSON storage with a tenant-aware database, backups and migration controls.

Build checklist

Security and backend work required before live customer data

Prototype login is for demonstration only. Real customer data needs the production security layer.

Client administration

Secure upload centre

This is where a customer would load the files FleetCoRAI needs for a Lite pilot. The MVP simulates the workflow; production will add secure storage, scanning and import approvals.

Current mode MVP pilot Sample files and local import workflow only

Upload queue

Customer files required for Lite pilot

Files should use pseudonymous driver IDs. Real names should not be uploaded for the Lite pilot unless the customer has approved that data handling model.
Production security controlsFile type limits, size limits, antivirus/malware scanning, encryption at rest, import audit history and role-based upload permission.
Tenant protectionEach upload must be attached to a customer tenant ID before processing so files cannot cross into another client workspace.
Import approvalManagers can review file summary, skipped rows and validation warnings before data appears in dashboards or driver apps.
Data minimisationLite requires driver IDs, score data and breach records only. Continuous trip data, video and real names are excluded from the pilot workflow.

Data Import

Lite pilot score and breach import

Drivers imported42
Scores received66-99
Median score79
Active today40
Ready for pseudonymous Lite pilot data.
Lite imports provider-supplied score, breach counts and incident locations. It does not validate false positives.

FleetCoRAI Engine

Lite engine mode

Company Knowledge

Tenant-isolated document upload and AI source control

Active tenantten_northline_demo
WorkspaceNorthline Transport Demo
Data boundaryNo cross-client retrieval
Drop company files herePolicies, handbooks, toolbox talks, NHVR/CoR references, SOPs, training material, telematics definitions and CSV exports.Demo mode: files are mocked, tagged, indexed and restricted to the active tenant.

Driver DNA

42-driver roster

AI Personas

Tenant-scoped persona workbench

Marshall Compliance

Policy, evidence and audit requirements

Jon Road Rules

State-aware rule reference, not coaching

Jon + Sage Vehicle Library

Make, model, year and handbook intelligence

Sage Coaching

Driver safety coaching, evidence and trend review

Sally Engagement

Rewards, streaks and campaign engine

Event case preview

How personas create an audit-ready evidence trail

Emergency escalation

Trish phone-call workflow

Driver Event Detail

Event evidence

Driver application

Your safety. Your progress. Your rewards.

Scores and breach acknowledgement, rewards, coaching and fleet rankings. Screens show demonstration data. Scroll inside the rewards and coaching phone to explore the full view.

Driving and breaches

Review safety and eco scores, trip details and breach evidence.

✓ Compliance metDemo status
Driver app showing overall, safety and eco scores and a hard-braking breach acknowledgement

Rewards and coaching

Scroll to see DriveCoins, streaks, trip mapping and persona guidance.

Sally rewards showing DriveCoins, streaks and a double-points campaign
Sally encouragement, trip breach map and Sage coaching feed

Fleet leaderboard

See progress alongside other drivers and the weekly safety digest.

Driver leaderboard showing ranked safety scores and Sage weekly digest

Environmental telematics

Sustainability intelligence layer

Company trend

Fuel, CO2e and idling movement

AI Persona use

How Sage and Sally use environmental data

Event Case File

Fatigue alert evidence trail