Timeline

A timeline is a vertical rail of events in the order they happened, where each row names an actor, an action and a time, and the rail carries the continuity between them. Orvain's Timeline family is five blocks split by what a row has to hold: a day's checklist hung off time chips, a mention with the text it quoted, an upload and a scheduled call, an assignment and a reaction beside a notice the system wrote itself, and attachment rows carrying the document they produced.

Most of the design work in a timeline goes into a single sentence. An avatar sits inside it, a filename is inked differently from the words around it, a chip in the middle of the line is a link, and the whole thing still has to read as one sentence when a display name runs to forty characters. The second rule is temporal honesty. Readers treat a rail as append-only, so a row edited or quietly removed costs more trust than it saves: corrections get their own row.

10 blocks

Day checklist

A day of work: what happened when, what is still open, and who did it

Day so far

A live day: what has happened up to now and what is still planned

Day by slot

A long day to scroll: the time you are reading stays pinned

Date and mention

Thread history: the day it happened and who was pulled in

File and call

Audit trails: the upload and the booking, each with its actor

Task and reaction

Team activity: assignments, reactions and the system's own notices

Attachment events

File history: an event plus the documents it produced, each one ticked off as reviewed

Delivery tracker

Orders, shipments and any process with done, current and upcoming steps

Delivery ETA

Tracking pages where the first question is how long until it arrives

Delivery day

Same-day deliveries and any journey where the time between steps matters

01

Using Timeline

Reach for it when

  • An audit trail, where the question is who did what and when.
  • A discussion whose replies only make sense beside the text they quote.
  • A day view of work, mixing what has been done with what is still open.
  • Feeds where automated events sit among human ones and the difference has to be visible.

Reach for something else when

  • A list of things still to do. Those sort by priority and owner rather than by time, which makes them a task list.
  • Machine logs at volume. A virtualised table with columns and filters beats a rail you have to scroll.
  • Work with durations and overlap. A rail shows order only; a calendar or a Gantt chart shows length and collision.
02

Where it shows up

01

Record history

Every change to one customer or one order, gathered in one place. The rail answers the support question directly: it was changed on Tuesday, by this person, from this value to that one.

02

Ticket activity

The life of an issue under its description: assignments, status changes, comments and the file somebody attached. Automated rows are marked differently, so nobody gets credited for what a webhook did.

03

Approval trail

A contract or an expense moving through its reviewers, each step stamped with who signed and when. It is usually read long after the fact, so no row may depend on state elsewhere on the page.

04

Daily work view

What one person got through today, with time chips showing when each thing landed and the still-open items sitting in the same column instead of in a separate list below.

03

Questions

What is the difference between a timeline and an activity feed?

A timeline is anchored to one object and tells its story in order: this document, this order, this ticket, from first event to latest. An activity feed is anchored to a person and gathers events across many objects, usually newest first and filtered to what that person is involved in. One event can legitimately appear in both.

Should a timeline put the newest event first or last?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.