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
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
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.
Form: Incident Report
Starts the workflow
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: …
E-mail: Your report about …
E-mail: Incident open: …
Restore {{trigger.body.service}}
Task · Resolver group
Mark as done: Root cause analysis
Root cause analysis
Task · Problem manager
Mark as done: Sign incident closure: {{trigger.body.service}}
Sign incident closure: {{trigger.body.service}}
Approve & sign · Service owner
Close & sign: Google Drive: post-incident review · Reopen: Restore {{trigger.body.service}}
Google Drive: post-incident review
App action · Google Drive
E-mail: Resolved: …
Incident Report
Starts the workflow · 9 questions
Root Cause Analysis
Task form · 4 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.
Requests for administrator or privileged accounts are approved and signed by the system owner; the IT administrator then records exactly what was granted and until when, and the record is filed in Drive.
7 steps · 3 rolesEquipment Purchase RequestTeams request new laptops, phones, instruments or tools; the department manager approves and signs, and procurement orders the items and tells the requester the PO and delivery date.
4 steps · 2 rolesHelp Desk Ticket ApprovalHelp desk tickets that need a sign-off are routed by type: purchases to the budget holder, access to the system owner, and every ticket is then approved and signed by the IT support lead.
10 steps · 5 rolesInformation Request ApprovalStaff request a data extract or report; the data owner approves sharing it, a data analyst prepares it with escalation if it stalls, and the data protection officer gets a report.
6 steps · 4 rolesIT Change RequestIT changes are routed by type: standard changes go straight to scheduling, normal changes need the CAB chair's signature and emergency changes the emergency approver's, before the window is booked and implemented.
12 steps · 4 rolesIT Service ManagementUsers describe an IT problem in their own words; AI sorts it into network, hardware, software or accounts and hands it to the right support team, with a Drive log of every ticket.
9 steps · 5 roles