Dispatcher
Assigns the vehicle and driver, reviews permit information and follows execution.
Menu
Fleet and routes
Qayta Fleet
Vehicle routes, driver jobs and location-based evidence of collection activity.
- Waste carriers
- Operators and disposal sites
- Industrial facilities
Platform role
One module in an end-to-end process
Qayta Fleet links an approved request to the vehicle, driver, route and recorded outcome. Dispatch teams see a trip in batch context rather than an isolated GPS track.
Dispatchers struggle to connect a request, assigned vehicle, permits and actual route when each lives in a separate system.
Participants
Who does what
Driver
Receives the route and checkpoints and records the required trip confirmations.
Transport customer
Reviews the request, movement and outcome without reconstructing them across systems.
Capabilities
What the operating layer covers
Dispatch
Assigns work to vehicles and drivers and links it to the collection request.
Route record
Shows available tracks and operation checkpoints.
Permit dates
Records validity information for assigned vehicle and driver permissions.
Workflow
How the workflow runs
- 01
Assign
A dispatcher selects a vehicle and driver for an approved request.
- 02
Operate
The platform relates the available route data to operation checkpoints.
- 03
Close
The trip result becomes part of the batch history for later review.
Data and control
Inputs, outputs and human control
Inputs
- approved request and route points
- vehicle, driver and permit information
- available GPS/GNSS track
Outputs
- trip record
- checkpoint timeline
- transport outcome linked to the batch
Controls
- assignment checks
- location events
- exception and incomplete-trip review
Integrations
Integration scope made explicit
The label shows the maturity of the public claim. Final scope is always agreed after discovery.
GPS/GNSS devices
Defined per projectProtocol and telemetry support are confirmed for the selected equipment.
Qayta Core
Configurable capabilityThe trip receives request context and returns recorded events to the batch history.
Maps and geofences
Defined per projectControl zones and exception rules are configured for the operating process.
Implementation
Boundaries are agreed before the pilot
The pilot agrees device types, telemetry availability, vehicle master data, geofence rules and responsibility for closing a trip.
Expected outcome: The request, trip and recorded result remain connected in one reviewable chain.
FAQ
Common questions
Is Fleet only vehicle tracking?
No. Its purpose is to connect movement and checkpoints to the request, batch and recorded result.
Can existing trackers be used?
That depends on protocol, message content and data quality.
Does the system automatically penalise a deviation?
No. It records an event for review; the customer defines the response.