1. Purpose and users
The Dashboard is the first operational command center for users with dashboard access. It is used by managers, operations leads, branch managers, fleet teams, finance users, tracking users, and executives who need a fast view of current system activity.
The page does not replace the detailed modules. It summarizes the live state of trips, revenue, cost, fleet readiness, tracking health, KPI alerts, monthly projection, and recent legacy trip or truck activity so users know where to act next.
2. Login and workspace routing
After signing in, the system sends each user to the workspace their role can use. Users with general dashboard permission see the main dashboard. HR dashboard users without general dashboard access are redirected to the HR dashboard. Fuel users without general dashboard access are redirected to the Fuel dashboard.
This keeps users from landing on a page they cannot use. It also means a missing dashboard menu is usually an access decision, not a broken page.
3. Branch scope and operating context
The Dashboard can be scoped by branch. Branch selection changes the trips, trucks, clients, tracking metrics, revenue, cost, utilisation, monthly projection, and alerts shown on the page.
Branch scope is important because a manager reviewing one operating branch should not mix that branch with another branch by accident. Users should confirm the selected branch before acting on dashboard figures.
4. Operational and executive metrics
The system calculates summary metrics for active work, executive status, revenue versus cost, trip status, and cost mix. These figures help users identify whether the business is moving, delayed, profitable, or carrying unusual cost pressure.
The charts are a starting point. If a metric looks wrong, users should open the related module or report to see the records behind it, such as trips, invoices, fuel logs, workshop job cards, or finance entries.
5. Tracking, fleet utilisation, and KPI alerts
The dashboard includes tracking health and active trip alert metrics. Users can see whether trucks are reporting tracker signals and whether active trips have movement or signal issues that need tracking follow-up.
Fleet utilisation and monthly projection show whether the asset base is being used effectively and whether the current month is on track against expected work or revenue targets. KPI alerts surface exceptions that management should review before they become bigger operational problems.
6. Legacy trip and truck review
The dashboard also loads recent trip and truck context for quick operational scanning. Users can review visible trips, truck status, client context, depot allocation, scheduled dates, departure, delivery, and closure signals.
This area is useful for quick supervision, but it should not be treated as the full trip file. The full Operations, Fleet, Tracking, Finance, and Reports workspaces remain the source for detailed record work.
7. Daily use from start to finish
A normal day starts by opening the dashboard, confirming the branch scope, checking high-level metrics, reviewing tracking and KPI alerts, looking at fleet utilisation, and then opening the module that owns the issue.
The day ends by using reports to validate what happened. The Dashboard shows the current pulse; Reports and module histories provide the evidence needed for review, meetings, and audit.