Bus Ticketing Software ยท Guide
Bus Ticket Counter Checklist: Seats, Refunds, Mistakes
Bus counters fail in small, repeated ways: a seat that was held and forgotten, a refund given without a record, an agent who never settles. A checklist does not make staff clever, but it makes them consistent. Print the lists below, adapt them and review them monthly.
Opening checklist
- Check that every departure for the day has a bus, a driver and a conductor assigned.
- Confirm the seat layout matches the actual bus.
- Release expired holds from yesterday and phone bookings that were never paid.
- Block seats reserved for owners or staff and note who they are for.
- Check the festival or special fare table is loaded if it applies.
- Start the cash drawer with a counted float, recorded by two people.
Selling checklist
- Seat chosen from the live map, never promised verbally.
- Passenger name and a working phone number recorded.
- Boarding point confirmed and shown on the ticket.
- Fare stated clearly before payment.
- Payment mode recorded: cash, QR or bank.
- Ticket printed or sent to the passenger\'s phone.
Refund and change checklist
- Check the company policy for the time of request.
- Record the reason and the user who approved the refund.
- Release the seat immediately.
- Pay the refund in the same mode where possible and record it.
- For changes, link the new ticket to the old one.
Departure checklist
- Print the manifest and give it to the conductor.
- Call passengers who have not arrived near the departure time.
- Offer unsold seats at the counter and update the manifest.
- Record the final passenger count and any trip expense paid in cash.
Closing checklist
- Run the counter closing report: sold, cancelled, refunded and amounts by mode.
- Count the cash in front of a second person.
- Compare with the report and record any difference with the reason.
- Hand the cash and signed report to the accountant or owner.
- Note agent seats returned and agent payments received.
Common mistakes and their cost
| Mistake | What it causes |
|---|---|
| Promising a seat without entering it | Double sale and angry passengers |
| Phone holds that never expire | Empty seats on departing buses |
| Refunds without a reason or approver | Cash leakage and disputes |
| Sharing one login among clerks | No accountability for differences |
| Letting agents sell without limits | Large unpaid balances |
| No second person at cash count | Doubt when cash is short |
| Printing the manifest too early | Late bookings missing on the list |
A short walkthrough
It is five in the evening before a weekend. The clerk opens the counter, releases yesterday\'s unpaid holds and sees that the Pokhara night bus has only a few seats left. A caller wants two seats; the clerk holds them for an hour and notes the number. A walk-in buys a seat; the clerk picks it on the map, takes QR payment and sends the ticket on WhatsApp. The caller does not return; the hold expires and the seats are sold to a passenger waiting at the counter. A passenger cancels with a good reason; the clerk records it, releases the seat and returns the amount under policy. At departure, the manifest prints, the conductor calls two late passengers and the bus leaves. At closing, tickets and cash agree. Each action is ordinary; what matters is that every one was recorded.
Making it stick with software
In our bus ticketing software, many checklist items are enforced: holds expire on their own, refunds need a reason, each clerk has a login and the closing report is generated, not typed. For passenger flow at busy counters, a token system from queue management software can also help.
Monthly review
Once a month, review the cancellation rate, the cash differences, agent balances and routes with the lowest occupancy. Choose one change, such as shorter hold times or a different departure hour, and test it for the next month. Small adjustments repeated through the year are how a transport company becomes better organised than its neighbours.
Next step
Print the closing checklist and use it tonight. If the numbers do not match, you have found your first leak. To see a system that automates the checks, message WebsNP on WhatsApp at +977 9846280400.
Get a demo and quote for Bus Ticketing Software
Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.
Chat on WhatsAppOr call / WhatsApp +977 9846280400
More guides on Bus Ticketing Software
How to Choose Bus Ticketing Software in Nepal
What a bus or coach company should check before buying a ticketing system, from live seat maps to counter closing reports.
Read guide โบHow to Run Bus Counter Sales and Daily Closing
The daily counter routine that keeps seats, passengers and cash in agreement from the first ticket to the closing sheet.
Read guide โบBus Company Records and Festival Rush in Nepal
A practical guide to festival advance bookings, passenger records, route documents and VAT-ready books for bus companies.
Read guide โบBus Ticketing Software vs Ticket Book: Cost Comparison
A fair comparison of paper ticket books and software for a bus company, with ways to measure leakage in your own counters.
Read guide โบ