Timeline: events in order, with room for the ones that matter

Dated events in order, for a history people will enjoy or a project they have to follow.

2 live examples

The example: Thirty years of a family boatyard

A history: 13 entries, five given more room

Thirty years of a family boatyard

Open the exampleThe names and numbers are made up.

What to notice

  • Thirteen entries cover 1997 to 2027, and five of them are set larger: the founding, Hull No. 1, the February storm, the new sign and the thirtieth year.
  • A strip above the first entry marks all thirteen years as dots on one line, so the gaps between them show before you scroll.
  • It ends on an invitation for Saturday, June 12, 2027, and says how to reply: tell Júlia by Tuesday, June 1.

The prompt that starts one like it

Make a timeline of [organization]'s history as a single HTML page, for our [anniversary]. Here are the dates and stories: [paste notes]. Run it top to bottom with the year beside each entry, in two or three chapters. Give the [four or five] turning points a bigger heading and more room. Open with a strip showing every year at a glance, and end with the invitation: [date, time, place, how to reply]. Make it read well on a phone, then publish it on sharable.link.

The example: Moving a 30-person office in twelve weeks

A project: 4 phases, 16 dates, who does what

Moving a 30-person office in twelve weeks

Open the exampleThe names and numbers are made up.

What to notice

  • Three dates come before the schedule, each under its own label: move weekend April 24–25, first morning April 26, keys back April 30.
  • Of sixteen dated steps, the five that need something from everyone are in red and repeated in their own list, "Your five dates".
  • A black square marks the three dates that can't move: the internet order, the move weekend and the day the lease ends.

The prompt that starts one like it

Make a project timeline as a single HTML page for [project], which ends on [fixed date]. Here are the phases and key dates, each with an owner: [paste list]. Put the two or three biggest dates at the top in large type, then a strip of numbered weeks with the phases under it. List every date in order with its weekday and owner, and pull out the ones where everyone has to act. It must work on a phone. Then publish it on sharable.link with a password.

A timeline is a list that takes dates seriously. Two finished ones are here: a family boatyard's thirty years, sent out before its anniversary, and the twelve weeks of an office move, sent to the thirty people moving. They share a spine of dates and almost nothing else, so pick the one closer to your job.

Who it's for

The history kind is for a company, a club or a family with an anniversary coming, and it goes to everyone who was part of the story. It can end with an invitation, but a page can't collect replies, so say how guests should answer.

The project kind is for a move or a launch with a fixed end date and a crowd that needs to know what happens when. If you need to see what a delay does downstream, make a Gantt chart instead. A timeline shows order, and leaves out what waits on what.

What a good one contains

  • Dates in one format, down one edge. The history uses bare years, and the move uses weekday, month and day. The eye should find the date in the same place every time.
  • Unequal weight. Thirteen entries tell the boatyard's story, and five are set larger. A timeline where every year gets the same two lines reads like meeting minutes.
  • An overview before the detail. The history opens with thirty years as dots on one line. The move puts twelve numbered weeks, with four phases under them, ahead of its first step.
  • Short entries with one concrete thing each. "He pays half in cash and half in firewood" does more than a paragraph about humble beginnings.
  • Chapters or phases. Three chapters break up the history, and four phases break up the move. Without them a long list has no shape.
  • For a project, an owner on every date. Each of the move's sixteen steps names who does it, and the five that fall to everyone are in red.
  • A mark on the dates that can't move. The lease ends April 30, and a black square says so.

How each kind fails

Histories fail by being complete. Ask the oldest person involved for the five days they still talk about, and build around those. Then check each year with someone who was there, because an anniversary page with a wrong date gets corrected in public.

Project timelines fail on weekdays. "Friday, April 30" has to be a Friday, and a reader who catches one wrong day stops trusting the rest. Check the gaps too. The move's internet is ordered on February 12 because the provider quotes up to nine weeks, and the line is tested nine weeks later to the day.

How to send it

As an open link. A history is meant to be passed around, so the boatyard's link is open. The office move names staff and says when the old office empties, so send that kind with a password.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in strategy and finance

  • Business plan: A one-page plan an owner sends to a bank, a landlord or a partner ahead of the full version.
  • SWOT analysis: Strengths, weaknesses, opportunities and threats for one organization, each backed by evidence.
  • Gantt chart: One project's tasks as bars across weeks, with owners, milestones and a line for today.
  • Executive summary: One screen that tells executives what a longer report found and what they're being asked to decide.
  • Org chart: Who reports to whom in a small company, with teams, open roles and what each person looks after.
  • Mind map: One central idea with branches and twigs, sent to collaborators so they can say what's missing.
  • All use cases

Keep reading