A Substitute Driver Is Also Transport Resilience: What Laiyi’s Happiness Bus Can Teach Taiwan’s 55 Indigenous Townships
Original Chinese title: 幸福巴士再補人力：來義可把司機備援、無障礙運輸與即時班次接成原鄉交通韌性服務
Laiyi Township Office posted a recruitment notice for a substitute driver for the accessible Happiness Bus vehicle Xiao-Ai-Jie on August 24. The notice highlights a basic but often overlooked point in rural mobility: vehicles, routes and booking systems cannot provide resilient service without driver backup. Laiyi’s network already includes school, daily-life, tourism and medical services, several of them reservation-based.
Yuan Media AI Editorial Desk
Yuan Media AI Editorial Desk follows official updates across Taiwan’s 55 Indigenous townships, Indigenous education, language technology, AIGC, agricultural resilience, traditional-knowledge governance and digital public services.
On August 24, 2026, Laiyi Township Office in Pingtung County posted a recruitment notice for a substitute driver for its Happiness Bus vehicle “Xiao-Ai-Jie.” At first glance, this is a staffing notice. In the context of rural public transport, however, it exposes a more important operational issue: a route is resilient only when a qualified person is available to drive it.
In a city, a driver absence can sometimes be absorbed by another route, another departure or another mode. In an Indigenous township, a single missed departure can mean a student cannot get to school, an older resident misses a medical appointment, or a booked community shuttle disappears for the day. Driver availability therefore belongs in the same resilience conversation as vehicles, roads, schedules and digital booking.
The Ministry of Transportation and Communications’ Highway Bureau currently lists multiple Happiness Bus services in Laiyi, including school-return routes, township daily-life services, tourism routes, medical routes and study-support services. Several are reservation-based and require booking at least one working day before travel. See Highway Bureau | Happiness Bus and Happiness Taxi operating information.
The Highway Bureau also reported that the accessible minibus Xiao-Ai-Jie entered service on April 1. At that point Laiyi had eight vehicles and eight Happiness Bus routes. The new vehicle was intended to support school transport to Nanhe Elementary School and community services, and its wheelchair-accessible design expanded mobility options for residents who need barrier-free transport. See Highway Bureau | Laiyi Township Happiness Bus adds a new accessible vehicle.
Taken together, the staffing notice and the operating network point to a practical lesson for Taiwan’s 55 Indigenous townships: digital mobility should not start with a large “smart transport” platform. It can start with a reliable daily operations layer.
1. Make “Can the service run today?” a shared operational status
A simple internal status board can track five fields: vehicle availability, driver availability, route status, reservations and backup plan. Vehicles should be marked available, under maintenance or accessible; drivers should be marked scheduled, absent, substitute or standby; routes should be normal, delayed, suspended or rerouted; reservations should include passenger count and service needs; and every critical route should have a documented fallback.
The first goal is not public transparency for every internal detail. It is a single operational truth shared by dispatchers and township staff. Once the status is confirmed, a much smaller public view can be generated.
2. Residents usually need only four answers
For most passengers, the essential questions are simple: Is the bus running today? Do I need to reserve? What is the reservation deadline? Who do I contact if something changes?
A mobile webpage, LINE menu or lightweight chatbot can answer those questions without exposing backend complexity. If a vehicle fails, a driver becomes unavailable or a road condition changes, the public status should explicitly switch to “changed” rather than leaving an old timetable visible.
AI can summarize confirmed information, but it should not decide that a bus is operating merely because the regular timetable says so.
3. Accessibility needs must survive vehicle and driver substitutions
The significance of Xiao-Ai-Jie is not simply that Laiyi received another vehicle. An accessible vehicle makes a different level of service possible for wheelchair users, people with limited mobility and accompanying caregivers.
Reservation records therefore should not treat every booking as identical. A dispatcher may need to know whether a wheelchair lift is required, whether a companion is travelling, whether extra boarding time is needed, or whether an accessible vehicle is essential. If a last-minute substitution cannot preserve the required accessibility, the system should flag the case for human follow-up rather than silently replacing the vehicle.
4. Driver backup should be managed like disaster-response backup
A substitute-driver recruitment notice is a reminder that backup staffing should be explicit rather than informal. A small driver capability matrix can record which vehicle types each driver can operate, which routes they know, whether they have accessibility-service training, and when they can be called in.
When the scheduled driver is absent, dispatch can follow a fixed sequence: assign a qualified backup familiar with the route; if necessary, change vehicle while preserving service requirements; adjust the departure only when unavoidable; and suspend a service only after the alternatives are exhausted. Recording these exceptions also reveals whether the real problem is overall staffing, particular time slots, a shortage of drivers qualified for certain vehicles, or overdependence on one person.
5. RAG and chatbots should be the query layer, not the dispatch authority
Once route, booking, vehicle and staffing data are structured, a retrieval system can help residents ask natural-language questions such as: “Do I need to reserve the Chaozhou route tomorrow?” “Which medical route runs on Monday?” or “Is an accessible vehicle available?”
The key safeguard is that the model may only report a status that the operating team has confirmed. If the daily status has not been verified, the correct answer is “Today’s operating status is awaiting confirmation; please contact Laiyi Township Office,” not a prediction based on the normal schedule.
This design can be reused across the 55 Indigenous townships. The towns do not need the same software or brand, but they can share a minimum data model: route, departure, reservation rule, vehicle status, accessibility capability, driver backup, last verification time and human contact.
6. From “A Bus to Ride” to a Service That Does Not Break Easily
The broader lesson is simple. Rural transport resilience is not measured only by the number of vehicles or routes. It is measured by whether the service can continue when a person is absent, a vehicle is unavailable or a reservation requires a different level of accessibility. When staffing, vehicles, routes, reservations and fallback plans are managed as one service map, digital public service becomes part of everyday mobility rather than another website residents must interpret.
Sources
AI use and content-safety disclosure
This English translation was prepared with AI assistance from the Traditional Chinese article based on official Laiyi Township Office and Highway Bureau sources. Operational-status and RAG recommendations are service-design proposals, not claims that the agencies have adopted those systems.