Every year, some networks start the new school term with no trips at all in Pysae. In most cases their service had not changed: it was the validity dates of their calendars that had stopped at the end of the previous school year.
In other words, "I haven't changed anything" is no protection. It is not your service that expires, it is the period it is declared over.
And nothing warns you in advance: the plan is still shown as active and no alert is sent. The first sign is often a driver calling on the first morning back, when there is no comfortable way left to fix it.
✅ The check to run right now
Open "Trips" > "Trips" and select a date in the week the term starts. If the list is empty, your calendars stop before that date.
1. Check the validity dates of your calendars
Every calendar in your transport plan has a start date and an end date. Past that end date, Pysae generates no trips at all — even though your routes, your stops and your timetables are still in place.
A plan built for one school year therefore ends in June or July. Nothing extends it on its own.
⚠️ Why this pitfall is hard to spot
In "Resources" > "Transport plan", your plan is still displayed with the "Active" status. That status only tells you this is the plan in service: it says nothing about the validity of its calendars. Everything looks normal right up to the day your drivers have no trips.
The reliable check is the future-date one described above. Depending on your permissions, the selector in the "Trips" view may be limited to 7 days ahead: in that case, run the check again as the start of term approaches.
Two situations to fix it:
Plan produced by another tool and imported into Pysae — a new export covering the coming period must be generated, then imported. Allow for that lead time with whoever handles the export.
Plan built in Pysae — open the plan, then the "Calendar" tab, and extend the validity period of each calendar. Detailed steps: Adding, editing and deleting a calendar.
💡 While you are there, declare the coming year's school holidays straight away.
2. Update your service if it changes
If your timetables, routes or stops change, update them before publishing.
For an imported plan, go to "Resources" > "Transport plan", then "Add a transport plan" > "Import a file". Pysae accepts GTFS and Hastus files, and shows you what it detected before you confirm the import.
Two things to watch:
Periods must not overlap. If the old and the new service coexist in the same plan, only one may be active on any given date, otherwise your drivers will see duplicate trips.
File quality is best checked upfront. Pysae validates your plan when you publish, but a check before importing saves time: Quality control of the GTFS feed before importing.
Full procedure: Importing a transport plan.
3. Publish at the right time
A plan with the "Draft" status goes into service via the "Publish" button. Pysae then opens a two-step window.
Step 1 — "Verification and scheduling"
Pysae checks your plan and displays the result: "Your transport plan is conform!", or the number of errors and warnings found.
A warning does not prevent publication. If a blocking error is found, Pysae shows "Publication impossible" and points you to the "Verification" view. This is also where you choose the date and time the plan goes live.
Step 2 — "Deviation compatibility"
Pysae compares your active deviations against the new plan: those that will be carried over, and those that become incompatible, with the precise reason. Not a step to skim past if you have roadworks running.
The final button reflects your choice: "Publish tonight at 03:00" by default, "Publish on … at …", or "Publish now".
⚠️ Avoid publishing during the day. Between 6 am and 9 pm, Pysae warns you: trips already started may lose the display of their recorded stop times. A publication scheduled overnight is always preferable.
Once the plan is live, ask your drivers to restart Pysae Driver before their first trip.
4. Update Pysae Driver
Check that the latest version of the driver app is installed on all your devices.
With the Google Play Store — the update rolls out automatically. Leave the devices switched on and connected to the network.
Without the Play Store — install the latest APK manually: Downloading Pysae Driver.
Plan a few days ahead: start each device once and check that it connects properly.
5. Refresh your resources
In "Resources", review your operational data.
"Drivers" — archive those no longer in service, create the new arrivals: Managing drivers.
"Vehicles" — update your fleet: Managing vehicles.
"Users" — add your new colleagues, archive unused accounts: Managing users.
The other back-to-school pitfalls
These points come up every year. Checking them takes a few minutes.
The split between operators after an import. Check in "Resources" > "Subcontracting" that it is still in place. Without an assignment, a driver sees every trip on the network.
New stops in bus stations. When departure and arrival happen at two different bays, create one stop per bay. That is what allows the terminus to be validated correctly.
Duties left open from the previous day. A driver who has not ended their duty stays attached to it the next day, and their vehicle does not appear on the map.
The start-of-duty form. If your instructions have changed, review the questions asked of drivers in "Service" > "Service forms".
💡 Good to know
A transport plan can be published ahead of time: it is the dates in your calendars, not the publication date, that determine which trips are visible.
The right time to prepare is the week before, not the day before.
The future-date check is just as useful before every holiday period.
A question? Our support team is here to help — write to us via the chat 💚