State Transition Matrix

UX & Product Architecture • Design Systems & Engineering

A state transition matrix is a table that shows which events can trigger a transition from each state and what state follows. UX teams use it to design actions, feedback, and recovery paths for objects such as bookings, tickets, and purchase requests.

How do you read a state transition matrix?

Rows show current states. Columns show events, which can come from a user or an external system. A cell identifies the next state for that combination. When a transition depends on a rule, record the condition, also called a guard.

Example of a booking state transition matrix

In this example, an agent submits a booking and waits for the supplier to confirm it. Cancellation also requires a supplier response. While cancellation is pending, the agent can see the request status and cannot submit a second request.

Current state Submit booking Confirm booking Request cancellation Accept cancellation Decline cancellation
Draft Awaiting confirmation — — — —
Awaiting confirmation — Confirmed — — —
Confirmed — — Cancellation pending — —
Cancellation pending — — — Canceled Confirmed
Canceled — — — — —

A dash means the event has no valid transition in this example. Confirming the booking and accepting or declining cancellation are supplier events. The booking moves out of Draft once a complete submission succeeds. An agent can request cancellation only when their role and the fare rules allow it. If the supplier declines cancellation, restore Confirmed status and show the reason if available.

This example covers the confirmation path and two cancellation outcomes. Extend the model for booking rejection, timeouts, and other cases your product supports.

How does the matrix inform ORCA actions?

The Calls to Action part of ORCA identifies actions people need, organized initially in a CTA Matrix. The matrix helps specify how those actions behave at each stage of the object's lifecycle. For example, agents can see “Cancellation pending” in the booking list and open the detail view to check when the request was sent.

Record what users see when an event fails or arrives late. If a booking changed after the agent opened it, refresh its status and explain why the requested action cannot proceed. Use the same rules in list and detail views.

Review the table with design, engineering, and operations. Walk through one routine case, one blocked action, and one delayed response. Add missing transitions or feedback before the workflow is built.

Sources