Incident Reports
100%

Incident Response · Lesson 6

Incident Reports

Learn to write a concise incident update grounded in observed evidence and open questions.

A short incident report helps another person take over without reconstructing the whole investigation. Include the affected service, a few timestamped observations, and the next action.

Reporting Observations

Here are three simulated records from the service incident.

09:17 UTC  Deployment record: version 3 reached production
09:22 UTC  Visitor-path check: homepage returned 503
09:31 UTC  After rollback: version 2, homepage returned 200

These records describe a change, a failure, and a successful check after recovery. Include the affected path and time. Keep the specifics of what was tested.

Which statement can you make directly from the records?

Simulated incident evidence showing a production change, a 503, and a successful recovery check

Explaining Uncertainty

A rollback followed by a successful request can make the deployment worth investigating. Keep the cause open until evidence supports it. For example, a maintainer can compare the two versions' service logs during the failed request window.

Which sentence belongs under an open question?

Giving the Next Reviewer a Task

Name who can take the next action, which records to look for, and what result would answer the open question. Keep secrets and personal details out of broad updates. A short report can link to protected evidence for approved reviewers.

Which next action best follows from this case?

Recording the Scope of Recovery

A report may need both a recovery observation and an unresolved impact estimate. A successful homepage check after rollback supports recovery for the tested path. To estimate affected visitors, a reviewer still needs request counts or other suitable observations from the failure window.

Which handoff accurately describes both kinds of evidence?

Lesson complete

You finished Incident Reports

You can now hand off an incident using facts, uncertainty, and a next action.

  • State the affected path and observed timeline.

  • Separate a suspected cause from confirmed evidence.

  • Assign a follow-up grounded in a source and time window.

Keep your learning progress

Create a free account to save this lesson and continue learning on any device.

Create a free account
Back to Incident Response