After reviewing usage, and to support you in getting important information into users’ hands quickly, we are making some changes to Disruptions in Passenger Cloud.

You will no longer need to decide whether a disruption to a part of your network should be created as a ‘line alert’ or a ‘stop alert’ when creating a disruption. These have been merged into a single disruption type created by selecting ‘Create a line / stop alert’ from the Disruptions section in Passenger Cloud. You can select any combination of lines or stops affected by the disruption on the following screen.

Disruptions will continue to be displayed where appropriate to users across timetables, departure boards, and service update pages and the disruption will highlight any affected lines and stops.

This change has come about after reviewing how operators use line and stop alerts, when we noticed that in many cases a line alert will also affect some specific stops. A common example we saw is that a diversion on the line will often result in a handful of stops not being served.

When creating a Network alert disruption we will no longer ask you to select the ‘Operators affected’. This form field is only used to generate the autofill headline and description, and, after reviewing how this feature is being used across operators we found that nearly all operators were re-writing the disruption Headline & Description. In light of this, we have removed the form field to simplify creating disruptions.

This change will be released on Friday, 14th June 2024. For any questions, please contact your Customer Success Manager.