Context

A regional transport authority informs passengers about construction work, technical faults, strikes and emergencies across several transport operators. Every event is published in German and Italian and goes out to many channels at once: social media, messenger apps, station displays and a VDV 736 interface for other systems.

The Problem

Operators wanted to publish quickly, while the authority needed to keep control over what passengers see. At the same time, staff had no clear overview of which message had already reached which channel.

Event List

A dense table with filters for cause, period and transport mode. Affected lines, consequences and the delivery status per channel (first, main and final message) are visible directly in the row, without opening the event.

Approval Workflow

Operators request approval, the information manager approves or rejects with a reason. Each state (pending, approved, rejected) has its own status chip and view, and rules such as operating hours are checked before anything is sent.

Banner Messages

I explored a checkbox inside the form and a toggle in the message header. We chose the toggle, because the banner setting applies to the whole event, not to a single message.

Handoff

Spec cards with the full conditional logic, a tooltip reference for every button and Jira stories written together with development.