Timeline software for project management

Keep a project's real history in one place: phases as bars, decisions as dated events, and a PDF of the record whenever somebody asks what happened when.

A project plan says what should happen. A project history says what did. Boromlia is for the second one — the record you wish you had when somebody asks, eighteen months later, why the launch slipped.

What a project timeline holds

Every event carries a date or a date range, so a two-week spike and a single go/no-go decision sit on the same timeline without one pretending to be the other. Add the place if it matters, the people involved, the document that decided it, and as many photographs or screenshots as the moment needs.

Chapters group events into phases — discovery, build, pilot, rollout — so a timeline that has run for two years still reads in one pass. Tags cut across the phases: everything tagged "vendor", or "scope change", wherever it happened.

The same record, read five ways

The Spans style draws start-and-end events as bars on one shared axis, which is the view that shows the overlap — the thing that was supposed to finish before the next thing started, and did not. Single dates sit on the same axis, so decisions are visible against the work they affected.

The Log style is those same events as a sortable table, one dense row each: the view to open when the question is "show me everything in March". It is the shape the CSV export writes, so the spreadsheet a stakeholder asks for is one button rather than an afternoon. Log, bulk import and sharing are what the Advanced plan adds.

When somebody asks for the record

Export follows what is on screen: the current style, its view settings, the sort order and any filters left on. A post-mortem PDF covering only the events tagged "incident" is therefore a filter and a button, not a document assembled by hand.

Nothing is public until you make it so. A project timeline usually stays private to the account; Advanced adds a read-only link and an iframe snippet if the record belongs on an internal wiki page instead.

Views worth leaving open

Spans: Start-and-end events as bars on one axis — the view that shows what overlapped what.

Log: One sortable row per event, in the same shape the CSV export writes.

Cards: A quarter at a glance, when the detail is not the point.

Questions

Is this a Gantt chart tool?
It draws one — the Spans style puts start-and-end events on a shared axis as bars — but it does not do the rest of what a Gantt tool does. There are no dependencies, no critical path and no resource levelling. It records what happened rather than scheduling what will.
Can two people keep the same project timeline?
Yes. A timeline can have collaborators, who add events to it alongside the owner. Visibility, style and settings stay with the owner.
How many events fit in one project timeline?
A free account holds one timeline of up to 20 events. Each Basic slot, bought outright at $2.99, adds a timeline of up to 50. Advanced removes both ceilings for $12 a month, which is what a long-running project usually needs.
View on Boromlia