26 Operations
Requisitions
Dispatch board, requisition create flow, list, and calendar.
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.
Requisitions in daily operations
Dispatch board, requisition create flow, list, and calendar.
Commercial & dispatch operations
Requisitions for transport desks and control rooms — typical in Bangladesh paribahan and logistics operators.
Request → approve → dispatch…
Teams use Requisitions when they need request → approve → dispatch workflow — without maintaining a separate spreadsheet or WhatsApp thread.
Passenger count and route purpose
Teams use Requisitions when they need passenger count and route purpose — 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.
Request → approve → dispatch…
Requisitions helps because request → approve → dispatch workflow — recorded inside the VMS audit trail instead of informal channels.
Passenger count and route purpose
Requisitions helps because passenger count and route purpose — recorded inside the VMS audit trail instead of informal channels.
Queue for transport desk assignment
Requisitions helps because queue for transport desk assignment — recorded inside the VMS audit trail instead of informal channels.
Audit trail for corporate travel…
Requisitions helps because audit trail for corporate travel policy — 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.
- Requisitions supports view, add, list, approve — so users do not jump between unrelated tools for the same task.
- Less manual follow-up: request → approve → dispatch workflow
- Less manual follow-up: passenger count and route purpose
- Less manual follow-up: queue for transport desk assignment
- Branch-scoped access means local teams open Requisitions 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 Requisitions with full register access, filters, and exports.
- Branch user (tablet / laptop)Works on branch-scoped Requisitions records — no cross-branch data leakage.
- Field staff (mobile)Submits or confirms Requisitions tasks from phone — limited permissions, faster updates.
- Manager / approverReviews exceptions, approvals, and summaries inside Requisitions without re-keying data.
- Owner / executive (dashboard)Reads KPI widgets fed by Requisitions — 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.
- TripsTrip records pull vehicle, driver, and billing context from Requisitions.
- FleetVehicle master in Fleet feeds live status into Requisitions.
- TransportRequisitions and Transport share the same platform data — no duplicate entry between modules.
- Staff MovementRequisitions and Staff Movement share the same platform data — no duplicate entry between modules.