Service Incident Timeline
Build a relative incident timeline, measure response milestones and calculate user-impact minutes from affected-user segments.
- 1Explore the example
- 2Edit your assumptions
- 3Compare & export
Loading the worked example…
Your working data
Edit cells directly or import a CSV. Download “Input CSV” for the required column names. Up to 200 rows; scroll the table sideways for additional fields.
Detailed analysis
Exports include all results, regardless of the search filter. The HTML report includes assumptions and source data; use your browser’s Print command for PDF.
Chart shows the first 20 rows; negative values use a warm color. Click table headers to sort.
Compare up to four scenarios
Capture the current inputs, change assumptions and capture again. Scenarios are included in downloaded projects.
What this model includes
Relative minutes, not time zones. Each row replaces the affected-user count until the next event. User-impact minutes are not unique affected users.
Import and save safely
CSV imports use your current assumptions. Project files restore assumptions, rows and saved scenarios. No automatic saving: download a project before closing this page. Imports are limited to 10 MiB and 200 rows. Calculations run in your browser; the site’s advertising and analytics follow its privacy policy.
Using Service Incident Timeline
Build a relative incident timeline, measure response milestones and calculate user-impact minutes from affected-user segments.
- Review the preloaded example and the model limits before entering real data.
- Adjust observation ends at minute.
- Edit the event rows or import a CSV using the Input CSV column template.
- Open Results & chart to inspect details, sort columns and filter rows.
- Capture alternative scenarios, then download a project, result CSV or printable report.
Example
The worked example includes Outage begins, Alert, On call responds, Partial recovery, Service restored. Change the first observation ends at minute setting and compare the result with a saved baseline.
Questions & answers
What does Service Incident Timeline calculate?
Build a relative incident timeline, measure response milestones and calculate user-impact minutes from affected-user segments.
What are the important limitations?
Relative minutes, not time zones. Each row replaces the affected-user count until the next event. User-impact minutes are not unique affected users.
Can I continue my work later?
Yes. Save a project JSON file and reopen it with Import CSV / project. It contains the working data, assumptions and up to four scenarios. Nothing is saved automatically.
What CSV columns do I need?
event, minute, kind, affected, notes. Download Input CSV for a compatible example. CSV imports keep your current assumptions.
Are these example figures current industry benchmarks?
No. They are illustrative values to demonstrate the model. Replace them with figures appropriate to your situation.
Related tools
A useful next step for your task.
Everyday CalculatorsProject Risk RegisterRank project risks, compare initial and residual exposure, and highlight overdue mitigation actions.
Everyday CalculatorsFMEA Risk AnalyzerCompare failure modes using severity, occurrence and detection scores, then review planned residual scores.
Everyday CalculatorsResource Capacity PlannerCompare team members’ workable hours with planned work, leave and recurring overhead; expose overload by role.
Everyday CalculatorsBackup Retention PlannerEstimate retained backup storage and transfer windows across datasets with full and incremental schedules.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.