Asset Timeline & Journal

The timeline is the record of what actually happened, event by event, in order. Everything else in reporting is derived from it.

Event Types

Event	Meaning
gate_in	The asset entered through a gate. Opens a visit.
gate_out	The asset left through a gate. Closes the visit.
location_set	The asset was assigned to a yard location.
mark_in_facility	The asset was recorded on site without a specific location.
reposition	The asset moved within the yard.
expired	The stay aged out of the live view without a recorded gate-out.
ticket_completed	A work ticket against the asset was completed.
exception	A recorded deviation — see below.

Each event carries its timestamp and, where relevant, the gate, carrier and visit it belongs to.

Per-Asset Timeline

Pick an asset and see its complete history: every crossing, every move, every completed ticket, every exception. Filter by event type and date range; long histories page as you scroll.

This is the view for a specific question — a billing dispute, a damage claim, "when did this actually arrive?". It reads best alongside that asset's visits, which summarise the same events into stays.

The Journal

The Journal answers the other question: what happened here? — every event type across every asset, newest first.

What changed

The Journal now reads the full event timeline. Previously it showed a thinner record that carried no gate, no carrier, no visit and no typed event data. Everything the old view showed is still here, with considerably more alongside it.

Unlike the gate activity feed, the Journal is not limited to a recent window by default. A journal is a history view, and quietly hiding everything older than a week behind an empty page is the wrong default for one. Narrow it with the date filter when you want a specific period.

Filter by event type or by a single asset, and export the visible range.

Exceptions

Exceptions appear inline in the timeline, typed by what went wrong:

Subtype	Meaning
capacity_override	A check-in proceeded past a full location.
seal_discrepancy	The exit seal did not match the entry seal.
required_field_override	A required capture field was bypassed.
gate_out_without_gate_in	An asset was checked out with no matching check-in.

Treat these as an operational signal rather than a list of mistakes. Recurring capacity_overrides on one location usually mean its capacity is set wrong. Recurring gate_out_without_gate_in means arrivals are getting into the yard without passing the gate — which will also be quietly under-billing you, because a stay with no gate-in never opens a visit.

Ordering

Events that happen in the same instant read back in the order they were recorded. A single check-in typically appends three — gate_in, location_set, and possibly a capacity_override — and they will always display in that order rather than shuffling between page loads.