IT Change Request

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

IT

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

How the workflow runs

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.

NormalDenyEmergencyDenyApproveApproveOtherwiseRolled backImplementedFormForm: IT Change RequestE-mailE-mail: Change logged: …Conditional branchRoute by change typeApprove & sign · CAB chairCAB: approve & sign{{trigger.body.summary}}Approve & sign · Emergency change Emergency change: approve &signE-mailE-mail: Change rejected by CABE-mailE-mail: Emergency change notapprovedApp action · Google CalendarGoogle Calendar: change windowTask · Change implementerImplement:{{trigger.body.summary}}E-mailE-mail: Change rolled back: …E-mailE-mail: Change completed: …Flow reportFlow reportFlow reportFlow report

Steps in order

  1. 1

    Form: IT Change Request

    Starts the workflow

  2. 2

    E-mail: Change logged: …

    E-mail

  3. 3

    Route by change type

    Conditional branch

    Normal: CAB: approve & sign {{trigger.body.summary}} · Emergency: Emergency change: approve & sign · Otherwise: Google Calendar: change window

  4. 4

    CAB: approve & sign {{trigger.body.summary}}

    Approve & sign · CAB chair

    Deny: E-mail: Change rejected by CAB · Approve: Google Calendar: change window

  5. 5

    Emergency change: approve & sign

    Approve & sign · Emergency change approver

    Deny: E-mail: Emergency change not approved · Approve: Google Calendar: change window

  6. 6

    E-mail: Change rejected by CAB

    E-mail

  7. 7

    E-mail: Emergency change not approved

    E-mail

  8. 8

    Google Calendar: change window

    App action · Google Calendar

  9. 9

    Implement: {{trigger.body.summary}}

    Task · Change implementer

    Rolled back: E-mail: Change rolled back: … · Implemented: E-mail: Change completed: …

  10. 10

    E-mail: Change rolled back: …

    E-mail

  11. 11

    E-mail: Change completed: …

    E-mail

  12. 12

    Flow report

    Flow report

  13. 13

    Flow report

    Flow report

Forms

  • IT Change Request

    Starts the workflow · 12 questions

Who takes part

  • CAB chair
  • Emergency change approver
  • Change implementer
  • Change manager

Apps it connects

  • Google Calendar

IT Change Request: 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