The admin platform, screen by screen

The chosen period in six figures: how many departures you scheduled, how many ran, how many were cancelled or late, and how many passengers you carried. Change the range at the top and all six recalculate.

Trip status as bars, and beside it the cancellation and delay rates as percentages — the number you compare month to month.

Top routes, switchable between passengers and revenue. This is where you see what carries the company and what merely occupies the timetable.

Pick the day from the strip or the calendar, then narrow to one company. Search takes a route name or a trip code.

Every trip states where it is — scheduled, left the garage, boarding, departed, arrived — and a delay shows on the row itself, in minutes.

Occupancy per row: how many seats are sold, how many held, how many still free. The bar says it at a glance.

Nothing is refreshed by hand. The page holds an open subscription, and every sale, hold or cancellation on any channel refetches the list you are looking at — filters and page included.

A reservation made on the website appears here immediately. There is no order behind it yet — a hold is a booking with no order for as long as the payment window lasts — so the table folds it in as an ordinary row and marks it as order-less.

Every row carries the channel it came from — the website, a counter, the driver's app, a partner's API — so one list answers both what sold and where from.

The trip's status, its delay in minutes, and the Live marker. The trip's own settings and the route's settings open from here.

Departure, estimated arrival, occupancy, takings, the vehicle and the crew — on one row.

The seat map for the selected segment: what is free, what is taken, and who is sitting where.

The channel is a choice at the moment of writing, not a setting buried elsewhere: e-mail, SMS, WhatsApp, Telegram, Viber. The same text goes out on whichever one you pick.

Recipients are resolved from the tickets — you never type an address. Anyone with no reachable contact is listed and marked as skipped before you send, not discovered afterwards.

Before sending you see exactly what will happen: how many receive it, how many are skipped and for what reason. A large send asks for a second confirmation.

Three selling states: open on every channel, staff-only at the counter and on board, or closed. Tickets already reserved stay payable in any of them.

Seats above capacity, for controlled overbooking — or strict capacity, selling exactly what the vehicle has. The seat-feature surcharge is switched off here too.

Cloning makes a NEW departure on the same route with the stops and fares copied — but no tickets, vehicle or crew, and the original untouched.

Three documents from the same departure: the official summary, the passenger manifest, and the sales report broken down by seller and by channel.

Page format, whether the passenger list is included, whether it is grouped by boarding stop. The document is built in the browser — nothing leaves for an external service.

The result: a filed record with the operator's letterhead and number, the crew and vehicle, the manifest and the takings — ready to print, save as PDF or open in Excel.

Search by name or code, filter by company and by status. At 219 routes that is the difference between finding and scrolling.

A new route is built in the same place: stops, timetable, fares and the seat plan, step by step.

Shown or hidden — you take a route off the website without deleting it and without touching tickets already sold.

The strategy decides how a fare is computed: a rate per kilometre, or a fixed price per segment. The accepted currencies are chosen here, and every price is shown in all of them.

A floor price per currency — the threshold a short segment cannot fall below, however small its distance.

The origin → destination matrix. Every cell is a real fare, in each chosen currency, and any of them can be overwritten by hand.

Filter by availability to see immediately what is free for a trip and what is already committed.

Each vehicle carries a seat plan — that plan is the map a passenger sees when choosing a seat.

Available, how many trips it is assigned to, or its next departure with the date and time. One glance tells you why it is not free.

The element palette: seats and the driver's seat, access and comfort (door, toilet, wheelchair space), fittings and structure.

A seat can carry add-ons — a socket, a table, extra legroom. The badges on each seat show them, and the control below highlights every seat that has one.

Double-deckers are drawn deck by deck, and the total capacity adds itself up.

The role is the starting point, not the ceiling: it grants a sensible set, and everything after it is an individual decision. Nobody can grant a role above their own.

Seventy-six permissions, grouped the way the work is grouped — vehicles, network, departures, sales, people, documents, the driver's app. Search cuts across all of them.

Selling a ticket and cancelling one are different permissions, and so are editing a departure and recording its progress. A cashier gets the first of each pair and not the second.

A grid, not a single switch: a dispatcher can take operational events on push and sales only by e-mail, without giving up either.

The channels are the ones people actually read — the app itself, e-mail, a phone push, and the messengers. A channel the company has not connected shows disabled rather than hidden.

Under the category grid sit the exceptions: one specific event forced on or off regardless of its category, for the person who wants everything except one thing.