A ready-to-use conversational form

Software incident report form template

Log software incidents in one consistent shape: affected service, severity, start time, impact, what was tried and evidence. Critical ones ask for a callback number.

13 questionsAbout 4 min6 branchesRead the template guide
Use this template

Free to customize. No code needed.

The real thing. Go ahead, try it.

Use this template

Software incident report

0% complete
Who is reporting this?

Something not working? Tell us what you're seeing and we'll get the right person on it.

Who is reporting this?

A live preview of this template. Answer the first question to begin.

What's inside

Every question, and where it leads

  • Contact info
  • Short text
  • Single select
  • Date
  • Phone
  • Yes / No
  • Long text
  • Multi select
  • File upload

The conversation

What a respondent is asked, in order.

Something not working? Tell us what you're seeing and we'll get the right person on it.

1

Who is reporting this?

Contact inforequired
2

Which system, app or service is affected?

Short textrequired
3

Where is it happening?

Single selectrequired
4

When did it start, as best you know?

Daterequired
5

How bad is it right now?

Single selectrequiredsplits the flow
6

What number can the on-call engineer reach you on right now?

Phonerequiredif severity is Critical: it's down or data is at risk
7

Is it still happening?

Yes / Norequiredsometimes askedsplits the flow
8

What made it stop, and roughly when?

Long textoptionalif ongoing is No
9

What exactly are you seeing?

Long textrequiredif ongoing is Yes
10

Who is affected?

Single selectrequired
11

What is it getting in the way of?

Multi selectoptional
12

What have you or anyone else already tried?

Long textoptional
13

Add a screenshot, recording or log file if you have one.

File uploadoptional

Ends with

Incident logged ๐Ÿ› ๏ธ

The flow

Where each answer leads. Every route here is editable once the form is yours.

A labelled route is taken only by answers matching the label

A little guidance

Make the most of your next ask.

Questions to consider for your software incident report form

  • What counts as critical for your service, and does the wording of the severity options match your incident policy?
  • Is there an urgent channel, like an on-call phone line, that people should use instead of the form for outages?
  • Which systems do people most often report? A dropdown of them may beat a free-text answer.
  • Who reads new reports, and during which hours?

How to use the responses

Triage from the severity and who-is-affected answers first, then assign an owner. Critical reports carry a phone number, so ring back rather than replying by email. Keep the start time and the resolution answer for the incident timeline, and export the reports to CSV each month to see which services break most and whether the same impact keeps coming up.

How to customize and share this template

  1. 1Rename the severity levels to match your incident process, keeping the critical option first so it routes to the callback question.
  2. 2Replace the impact options with the parts of your product people depend on most.
  3. 3Share the link in your help desk, status page and internal chat so reports land in one place, and review them in the dashboard.

Frequently asked questions

What should a software incident report include?

The affected service, when it started, how severe it is, who is affected, what the person saw and what has been tried. A screenshot or error message makes it much faster to diagnose.

Is an incident report the same as a bug report?

Not quite. An incident report records a disruption to a running service, while a bug report describes a defect that may never have caused an outage.

How do I handle critical incidents reported through a form?

Make sure someone is watching for them. This form asks critical reporters for a phone number so the on-call engineer can call straight back.

Can non-technical staff use this form?

Yes. The questions are in plain language, and in the chat an AI follow-up asks for more detail when a description is too vague to act on.

A few more possibilities

Keep the ideas coming.

Explore all forms

There is a good answer on the other side

Make a formnobody minds filling in.

Start for free

Free forever. No credit card. Unlimited submissions.