IT 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.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
12
Roles
CAB chair, Emergency change approver, Change implementer, Change manager
Apps
Google Calendar
Level
Advanced, about 16 min to set up
Changes to production systems cause most outages, so each kind gets the right level of control. The engineer describes the change, the systems affected, the risk and the rollback plan. Pre-approved standard changes go straight to scheduling. Normal changes need a signed approval from the change advisory board chair, and emergency changes need a signed approval from the emergency change approver. The change window is added to Google Calendar, the implementer carries it out and records whether it succeeded or was rolled back, and the change manager gets a flow report.
Form: IT Change Request
Starts the workflow
E-mail: Change logged: …
Route by change type
Conditional branch
Normal: CAB: approve & sign {{trigger.body.summary}} · Emergency: Emergency change: approve & sign · Otherwise: Google Calendar: change window
CAB: approve & sign {{trigger.body.summary}}
Approve & sign · CAB chair
Deny: E-mail: Change rejected by CAB · Approve: Google Calendar: change window
Emergency change: approve & sign
Approve & sign · Emergency change approver
Deny: E-mail: Emergency change not approved · Approve: Google Calendar: change window
E-mail: Change rejected by CAB
E-mail: Emergency change not approved
Google Calendar: change window
App action · Google Calendar
Implement: {{trigger.body.summary}}
Task · Change implementer
Rolled back: E-mail: Change rolled back: … · Implemented: E-mail: Change completed: …
E-mail: Change rolled back: …
E-mail: Change completed: …
Flow report
Flow report
Flow report
Flow report
IT Change Request
Starts the workflow · 12 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 Incident ManagementService 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.
8 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