Planned · individual development
School and social transport, built to your requirements
This is a planned direction, with no dedicated solution implemented yet. Once a customer provides their requirements, we will agree the routes, schedules, passenger records and reporting, then develop the service around that brief.
What we will agree before development
Route and timing
Agree pickup points, the destination and required arrival time. Recurring schedules and exceptions should be discussed as part of the service setup.
Suitable people and vehicles
The operator selects a vehicle and driver that meet the passenger’s needs. Agree accessibility, equipment and any accompanying person with the customer before accepting the work.
A record the customer can review
Agree what the customer needs to see after a journey: completed routes, actual times, passenger records and attendance. The required fields and report formats will form part of the development brief.
From requirements to an individual solution
Development starts with a concrete customer brief. We define the required workflow together, agree the scope and then implement and test it. The existing general order archive is shown below as a reference.
Agree the service brief
Collect the route, dates, passenger needs and responsible contacts. Define what the customer needs to see after each completed journey.
Design the workflow
Agree how schedules, passenger lists, boarding records and exceptions should work. The logic will be designed around the confirmed requirements.
Develop and verify
Implement the agreed functions and test them against the customer’s scenarios before launch. Development scope, timing and cost are agreed separately.
One service. A connected team.
For the owner
Define the customer’s requirements, service conditions and acceptance criteria for the future solution.
Explore the toolsFor the dispatcher
Describe how routes, schedules and changes should be coordinated. These requirements will shape the dispatcher’s tools.
Explore the toolsFor the driver
Agree which trip details, passenger information and confirmations the driver needs. The workflow will be developed to that specification.
Explore the toolsPricing
1%Pay as your fleet completes orders
When a company creates and completes an order itself, it pays DispHub 1% of the full order value once. When the order is passed to another company and completed by that company, the company that passed it on and the company that completed it each pay DispHub 1% of the full value of that order. No subscription or per-driver fees.
App branding is a one-time payment. Individual development and marketing services are ordered separately.
Before you get started
Is this service already available?
No. School and social transport is currently a planned direction. A dedicated solution has not been implemented, as there is no customer requirements brief yet. It will be developed individually when such a request is agreed.
Will there be schedules and boarding records?
They can be included in the customer’s requirements. Recurring routes, passenger lists, boarding records and accompanying-person tasks will be designed and developed to the agreed scope.
How is individual development priced?
We agree the scope, cost and timing after reviewing the requirements. Custom development is paid separately; the platform fee applies to completed orders once the service is operating.
Tell us what your service needs
Share the routes, schedules, passenger needs and required records. Together we will define the scope for an individual development project.