Build dated, dependency-aware timelines for incidents, DR tests and projects. Timeline, table and board views, CSV import, PDF export. Free, in-browser.
Build a dated, dependency-aware event timeline in the browser and export it as a PDF report or a CSV. Add events with a date, time, description, category and status; link each one to the event it depends on; then view the result as a vertical timeline, a sortable table or a status board, and export it for a post-incident review, a change record or a project update.
This is aimed at the timelines that IT and security teams actually have to produce: the hour-by-hour reconstruction after an incident, the runbook for a disaster-recovery test, the sequence of a migration cutover. Those documents have specific requirements — precise timestamps, a record of what depended on what, a status per step, and an output that can be attached to a ticket — that a generic diagramming tool handles badly.
Everything is local. Nothing is uploaded, there is no account, and no incident detail leaves your machine — which matters given that incident timelines routinely contain hostnames, customer names and unremediated findings.
Three templates load a complete, pre-sequenced event set that you then re-date:
The Coordinated Recovery template is the one worth studying if you are writing a DR plan, because it shows a real branch: forensics and customer communications proceed in parallel with the technical recovery rather than blocking it, which is how the fastest recoveries are actually structured.
A post-incident timeline gets read by people who were not there, sometimes months later, sometimes by an auditor or a customer. A few habits make the difference:
| Do | Instead of |
|---|---|
| Record the time something was observed, and separately when it started | Collapsing both into one entry, which hides detection lag |
| State the time zone once in the synopsis and use it consistently | Mixing local and UTC across entries |
| Write what was done and by which role | Passive constructions that erase who decided what |
| Mark parallel workstreams with dependencies on a common ancestor | A single linear list that implies work was sequential when it was not |
| Distinguish blocked from pending | Leaving everything pending, which hides where the recovery actually stalled |
For compliance-driven reviews, the timeline is often the evidence that a control operated: that backups were verified before failover, that leadership was notified within the required window, that forensic images were captured before remediation destroyed them. Each of those is one dated, categorised event.
No. Events are held in your browser and saved to local storage on your own device. Exports are generated locally. Nothing is transmitted.
PDF and CSV. The PDF is a formatted report including the synopsis, a table of events and the closing summary; the CSV is the raw event data for spreadsheets and trackers.
Yes — CSV import is supported, so you can build the list in a spreadsheet or export it from a ticketing system and bring it in.
Yes. Events, synopsis and summary are persisted to local storage automatically. They are tied to that browser on that device, so they will not follow you to another machine — export to CSV if you need portability.
Each event shows what it depends on, which makes the ordering constraints explicit and lets you see where a branch runs in parallel. It is a documentation aid rather than a scheduling engine — it does not compute a critical path or shift dates automatically.
Yes. The milestone, task, deadline and meeting categories cover ordinary project work, and the table view with statuses works well as a lightweight plan for a migration or a rollout.
Record the start and the end as two events — typically a task for the start and a milestone for the completion — and link the second to the first. Our time duration calculator works out the elapsed time between them for the write-up.
Vertical classic for reports that will be read on screen, vertical compact when there are many events, and the horizontal infographic when the timeline goes into a slide or an executive summary.
Pair this with the time duration calculator for detection-to-containment metrics, the data breach cost calculator when the incident needs a financial impact estimate, and the risk matrix calculator for scoring the findings the review produces.
A timeline generator creates visual chronological representations of events, milestones, and phases. Timelines transform sequential data into clear visual narratives that are easier to understand, present, and analyze than raw lists of dates and events. They are essential for project management, incident documentation, historical analysis, and strategic planning.
This tool generates interactive timelines from your event data, supporting customizable date ranges, color coding, milestone markers, and export options for presentations and reports.
| Type | Structure | Best For |
|---|---|---|
| Linear | Single horizontal or vertical line | Simple event sequences, project milestones |
| Gantt chart | Horizontal bars showing duration | Project phases, task dependencies |
| Swimlane | Parallel lanes for different categories | Multi-team projects, parallel workflows |
| Interactive | Zoomable, scrollable, clickable | Large datasets, exploratory analysis |
| Milestone | Key events marked on a line | Executive summaries, roadmaps |
The tool includes three built-in templates: DR Test Schedule for planning recovery drills, Incident Response for security incident management, and Coordinated Recovery Plan with dependencies for complex multi-team scenarios. Each template pre-populates events with realistic timeframes and dependencies.
Dependencies allow you to link events so that one task must complete before another can begin. The timeline visually shows the critical path through your events and highlights which tasks are blocking others. Events can be marked as dependent on any existing event to create logical sequences.
Three view modes are available: Timeline view shows events in chronological order with visual indicators for status and dependencies. Table view provides a spreadsheet-like display with all event details. Board view organizes events into columns by status (Pending, In Progress, Completed, Blocked) for Kanban-style management.
You can export your timeline in multiple formats: Copy as text for quick sharing via email or chat, CSV for importing into spreadsheets or other tools, and PDF for formal documentation. Exports include the synopsis, all events with their details and dependencies, and the summary section.
Yes, all events, synopsis, and summary are automatically saved to your browser local storage. When you return to the tool, your timeline will be restored exactly as you left it. You can also import and export CSV files to backup your timelines or share them with team members.
Six categories help organize events: Task for general work items, Milestone for significant achievements, Deadline for time-critical requirements, Meeting for scheduled discussions, Incident for unplanned issues, and Recovery for restoration activities. Each category has distinct color coding for easy visual identification.
The critical path is the longest chain of dependent events in your timeline. Events on this path are highlighted because any delay in these tasks will delay the entire project. Understanding the critical path helps you prioritize resources and identify which tasks require the most attention.