Three headers, same booking, same content underneath. Each frame is a fixed 560 pixels tall and scrolls inside itself, so what you see is the honest proportion on a laptop rather than a diagram of one. Scroll each frame to feel the difference, and scroll H3 in particular, because its whole argument is what happens after the first inch.
Your ruling on the tabs is already applied: Activity and Discussion have left the tab row and live in a right rail that is present on every record. Seven tabs remain. The rail belongs to the trip container rather than the booking, which is why it sits outside the tabs and stays put while you work.
Drawn fresh from the Untitled kit and the system’s ruled tokens, not restyled from the originals.
On scroll the header reduces to the three things a person keeps asking for: the reference, the status and the gate.
You asked for a crossed state, and designing it turned up something worth saying plainly: the gate should make crossing impossible, so a crossed meter is never a normal reading. It happens when money leaves after issuance, a reversed payment, a chargeback, or a revoked credit release. That is an exposure incident, not a workflow step, and it should look like one.
It is not a space saving trick. Issuing items is the one job on this page where a person is repeatedly asking the same question, "can I still issue this one", and the answer lives sixty pixels above the fold the moment they start scrolling. The reduced bar keeps the gate, the reference and the status on screen for exactly as long as the work takes.
Every other state is information. This one is a claim on somebody's afternoon, so it is the only place in the entire operator interface where a block of solid ink carries a message. The overrun is drawn as a real quantity in red rather than as a tick that happens to sit in the wrong place, because the number the agency needs is not "you crossed" but "by how much".