Use casesIT change calendar

Build your IT change calendar.

Plan IT changes around service windows, dependencies and rollback references.

How to build your it change calendar

  1. Describe the job

    Plan IT changes around service windows, dependencies and rollback references.

  2. Review the first version

    Choose how the it administrator records the change and how the system owner reviews the next step.

  3. Refine the views

    Ask First to adjust the fields and views for the people who will use the app.

  4. Test before sharing

    Walk through the process with a sample record and check who owns the next action.

An IT change calendar example

Two noncritical changes require the same reviewer during one window.

Illustrative workflowIT change calendar

IT change calendar example

Record
IT change calendar · 01
Owner
IT administrator

Current stage · IT administrator

Open the change

Two noncritical changes require the same reviewer during one window.

Read the full walkthrough
  1. Open the change

    Two noncritical changes require the same reviewer during one window.

    Record:
    IT change calendar · 01
    Owner:
    IT administrator
  2. Review the rollback reference

    Expose the conflict and keep the second window proposed until its owner agrees.

    Stage:
    Awaiting system owner review
    Owner:
    System owner
  3. Keep a conflicting change unconfirmed

    Keep a conflicting change unconfirmed until the service owners agree a window.

    Next action:
    Keep a conflicting change unconfirmed until the service owners agree a window.
    Owner:
    IT service manager

What to include in your it change calendar

  • Keep the change in context

    Keep change, service, window, dependency, approval and rollback reference together so the next person can understand the request or record.

  • When the next step needs a decision

    Two noncritical changes require the same reviewer during one window. Expose the conflict and keep the second window proposed until its owner agrees.

  • Keep rollback reference visible

    Keep a conflicting change unconfirmed until the service owners agree a window.

  • Choose what each person needs

    Give the it administrator a working view and the system owner a review view. Keep change and service attached to the decision as the work moves between them.

Questions about IT change calendar

Start with change, service, window, dependency, approval and rollback reference. Describe who enters the information and who reviews the next step.

Build your IT change calendar.

Start with your workflow and make it yours.

Get started