21 Fleet, Movement & Maintenance
Owner Release
Owner vehicle release, re-entry, overdue return, and custody blocking controls.
Illustrations on this page are conceptual examples — not screenshots of the live system.
How you can use it
The same Fleet module supports different transport models — pick the scenarios that match your operation.
Owner Release in daily operations
Owner vehicle release, re-entry, overdue return, and custody blocking controls.
Vehicle & movement control
Owner Release for fleet and workshop managers — typical in Bangladesh vehicle-heavy organisations.
Release and return checklists
Teams use Owner Release when they need release and return checklists — without maintaining a separate spreadsheet or WhatsApp thread.
Settlement status before close
Teams use Owner Release when they need settlement status before close — without maintaining a separate spreadsheet or WhatsApp thread.
Benefits for your team
What improves when vehicle data lives in one place instead of spreadsheets and phone calls.
Release and return checklists
Owner Release helps because release and return checklists — recorded inside the VMS audit trail instead of informal channels.
Settlement status before close
Owner Release helps because settlement status before close — recorded inside the VMS audit trail instead of informal channels.
Blocks trips when owner rules…
Owner Release helps because blocks trips when owner rules fail — recorded inside the VMS audit trail instead of informal channels.
Owner communication history
Owner Release helps because owner communication history — recorded inside the VMS audit trail instead of informal channels.
Makes daily work easier
Less chasing, less re-entry, fewer surprises on the morning dispatch board.
- Owner Release supports view, dashboard, add, settings — so users do not jump between unrelated tools for the same task.
- Less manual follow-up: release and return checklists
- Less manual follow-up: settlement status before close
- Less manual follow-up: blocks trips when owner rules fail
- Branch-scoped access means local teams open Owner Release without seeing other depots' records.
Multi-user & mobile-ready
Different roles see different slices — desktop for planning, mobile for field, dashboard for leadership.
- Operations lead (desktop)Plans and supervises Owner Release with full register access, filters, and exports.
- Branch user (tablet / laptop)Works on branch-scoped Owner Release records — no cross-branch data leakage.
- Field staff (mobile)Submits or confirms Owner Release tasks from phone — limited permissions, faster updates.
- Manager / approverReviews exceptions, approvals, and summaries inside Owner Release without re-keying data.
- Owner / executive (dashboard)Reads KPI widgets fed by Owner Release — not day-to-day data entry screens.
Works with your other modules
Fleet is the vehicle master — other modules read from it so data stays consistent across the platform.
- Vehicle OwnersOwner Release and Vehicle Owners share the same platform data — no duplicate entry between modules.
- FleetVehicle master in Fleet feeds live status into Owner Release.
- Vehicle AssetsOwner Release and Vehicle Assets share the same platform data — no duplicate entry between modules.
- GPS Location SharingLive movement from GPS sharing supports client updates tied to Owner Release.
- PlaybackRoute replay evidence supports disputes managed in Owner Release.
- ReportsReport hub aggregates Owner Release metrics for branch and management packs.