IT Incident Management

Service outages are classified and signed off by the incident manager, resolved by the resolver group, analysed for root cause and formally closed (or reopened) by the service owner.

Sign in with your Edesy account; the setup wizard opens on this template.

Category

IT

Type

Business process

Steps

8

Roles

Incident manager, Resolver group, Problem manager, Service owner

Apps

Google Drive

Level

Intermediate, about 18 min to set up

How the workflow runs

An ITIL-style incident record for service disruptions. The reporter describes the affected service, impact and start time. The incident manager confirms the priority and signs the classification, which starts the clock. The resolver group restores service and records the fix; the problem manager then writes the root-cause analysis. The service owner reviews both and signs the closure, or reopens the incident, which sends it back to the resolver group. The post-incident review is saved to Google Drive and the reporter gets a closure e-mail.

Not an incidentAccept as incidentMark as doneMark as doneClose & signReopenFormForm: Incident ReportApprove & sign · Incident managerClassify & sign:{{trigger.body.service}}...E-mailE-mail: Your report about …E-mailE-mail: Incident open: …Task · Resolver groupRestore{{trigger.body.service}}Task · Problem managerRoot cause analysisApprove & sign · Service ownerSign incident closure:{{trigger.body.service}}App action · Google DriveGoogle Drive: post-incidentreviewE-mailE-mail: Resolved: …

Steps in order

  1. 1

    Form: Incident Report

    Starts the workflow

  2. 2

    Classify & sign: {{trigger.body.service}} incident

    Approve & sign · Incident manager

    Not an incident: E-mail: Your report about … · Accept as incident: E-mail: Incident open: …

  3. 3

    E-mail: Your report about …

    E-mail

  4. 4

    E-mail: Incident open: …

    E-mail

  5. 5

    Restore {{trigger.body.service}}

    Task · Resolver group

    Mark as done: Root cause analysis

  6. 6

    Root cause analysis

    Task · Problem manager

    Mark as done: Sign incident closure: {{trigger.body.service}}

  7. 7

    Sign incident closure: {{trigger.body.service}}

    Approve & sign · Service owner

    Close & sign: Google Drive: post-incident review · Reopen: Restore {{trigger.body.service}}

  8. 8

    Google Drive: post-incident review

    App action · Google Drive

  9. 9

    E-mail: Resolved: …

    E-mail

Forms

  • Incident Report

    Starts the workflow · 9 questions

  • Root Cause Analysis

    Task form · 4 questions

Who takes part

  • Incident manager
  • Resolver group
  • Problem manager
  • Service owner

Apps it connects

  • Google Drive

IT Incident Management: questions

You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.

Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.

Related templates