About Transport Chief

Why this exists

Coach and charter operators are, almost without exception, very good at the hard part. They run vehicles safely, they get people where they need to be, and they do it on margins that leave no room for waste. What they are usually not equipped for is the administrative sprawl that has grown up around the job: pricing work by hand, tracking compliance dates in a diary, and holding the week's schedule in one person's head or one shared spreadsheet.

The available software mostly did not help. Generic scheduling tools model a job as a box on a calendar, which is not what a charter is. The serious fleet systems are priced and scoped for operators an order of magnitude larger. So the middle (the operator with four vehicles, or forty) ends up running a real business on tools that were never meant for it.

Transport Chief was built for that middle. It models a charter the way an operator actually thinks about one: a vehicle class rather than a registration number, a passenger count that has to fit, a route with real pickup points, a driver with the right licence, empty running at both ends, and a price assembled from several rate types at once.

How we work

We are small, and we would rather be honest about that than dress it up. In practice it means three things that matter to you:

• You deal with the people who built it. When you report a problem it goes to someone who can fix it, not to a first line reading from a script.
• What operators ask for is what gets built. There is no roadmap set by a product committee that has never dispatched a coach. If something in the system is awkward for the way you work, say so: that feedback is the main input into what we do next.
• We will tell you when the answer is no. If a feature is not there, or is not coming soon, you will hear that rather than a vague "it is on the roadmap". You cannot plan around a maybe.

New Zealand built, and it shows

Certificate of fitness rather than MOT. Road user charges. Dates the right way round. Time zones handled properly, so a booking taken in one place and driven in another does not quietly shift by an hour. Hosted here, so your customers' details are not sitting on the other side of the world.

None of that is a headline feature. It is the accumulation of small things that make imported software feel like it was built for someone else's country, and their absence is one of the clearest signals that a tool was made for the job you actually do.

Where we are heading

The direction is straightforward: keep closing the gap between an enquiry arriving and a job being confirmed, scheduled and driven, with as little re-typing in between as possible. The online booking storefront is the clearest expression of that so far: it removes the slowest step in the whole chain, which is a human working out a price by hand while the customer waits.

Beyond that, more of the same: fewer places for a detail to fall through, better visibility of what the fleet is actually doing, and compliance that surfaces itself before it becomes a problem.