Understand more. Delegate better. Keep the record clean.
Qarhami Fleet OS V5.0 focuses on three parts of the operating day that become harder as a rental fleet grows: understanding route evidence, giving the right people the right access, and correcting records when something was logged by mistake.
Three upgrades. One clearer operating model.
Each update removes a different kind of ambiguity: what happened on the road, who is allowed to do what, and whether the vehicle record still reflects what actually happened.
Understand the route
Tracking connects date-based history, driving-event context, numbered merged journeys, and exportable records into a more explainable evidence flow.
Delegate with boundaries
Co-Hosting lets the primary host scope team access to selected vehicles and selected permissions instead of sharing the owner account.
Correct the record
Maintenance records can be reviewed, updated, or deliberately removed when a task was reported by mistake, keeping history useful.
Tracking that keeps the route explainable.
V5.0 makes historical movement easier to read as evidence. Operators can move from recent context to the day, the trip, the event, and the exact journey inside a merged route without losing identity along the way.
- ✓Date-aware history: trips are grouped by operating day with daily mileage context.
- ✓List-to-map evidence: driving-event indicators on the trip list connect to corresponding markers on the route.
- ✓Numbered merged journeys: original trips stay identifiable in the list and on the map, and a single trip can be isolated for closer review.
- ✓CSV evidence handoff: merged trip data can leave the screen as a structured record for further review.
Tracking data is evidence that still needs trip, timing, guest and operating context. Exported records can support review; they do not replace platform, insurer, legal or law-enforcement judgment.
Delegate the work. Keep the boundaries.
Growing fleets need more hands without turning every team member into the account owner. Co-Hosting turns delegation into a controlled, vehicle-scoped workflow inside Qarhami.
- ✓Add by identity: invite a Co-Host by email and keep the primary host as the account owner.
- ✓Choose the vehicle scope: assign only the cars that person actually manages.
- ✓Choose the permission scope: vehicle controls, earnings visibility and maintenance actions can be separated by role.
- ✓Change access without starting over: edit an assignment, apply a consistent role across shared vehicles, or remove a vehicle-level assignment.
Engine-related items shown in Co-Host permissions are access settings, not a demonstration of a vehicle command. Actual controls remain dependent on compatible hardware, installation, plan, permission, connectivity and a safe vehicle state.
Correct the record when the record is wrong.
Maintenance history should preserve what happened—not lock a mistaken entry into the workflow forever. V5.0 gives operators a cleaner correction path while keeping each action tied to the vehicle record.
- ✓Duplicate-aware reporting: when an issue already exists, the operator can review the current vehicle context before creating another log.
- ✓Vehicle-specific history: the issue, mileage, details and available record actions stay attached to the correct car.
- ✓Delete a mistaken task deliberately: verify the exact record and remove the incorrectly reported maintenance task.
- ✓Update instead of recreate: when the record is valid but details need correction, edit the service information and supporting details.
Deletion is presented here as a correction control for a mistakenly reported maintenance task. This page does not claim that every class of historical service record can be deleted.
Watch all of V5.0 in one walkthrough.
The full release film connects the three workflows in sequence: understand the evidence, delegate the work, then keep the operating record accurate. The chapter previews above are for fast scanning; this is the canonical release walkthrough.
Less ambiguity where growing fleets feel it most.
A fleet operating system should reduce the work required to understand the fleet, control who can do what, and preserve an accurate operating record.
Already using Qarhami? No app-store update is required.
Qarhami is delivered through its Progressive Web App experience. Open or relaunch your Qarhami app link to use the current release available to your account.
Built for fleets that keep growing.
Clearer tracking. Stronger evidence. Controlled team access. Cleaner records. See what V5.0 changes in your own operating day.