--- title: "Every Change, Release and Freeze Window on One Year" description: "Changes, releases, freeze windows and vendor maintenance feeds in one Microsoft 365 year view, so the CIO sees a release inside a freeze before it is approved." url: https://www.virtosoftware.com/use-cases/cio-change-freeze-calendar/ language: en-US last_modified: 2026-10-22T00:00:00+02:00 translations: de: https://www.virtosoftware.com/de/use-cases/cio-change-freeze-calendar/index.md --- # Every Change, Release and Freeze Window on One Year Overlay approved change records, release milestones, freeze windows and vendor maintenance feeds in one Microsoft 365 year view, so the CIO sees a release inside a freeze before it is approved. Available at: SharePoint Microsoft Teams Microsoft Azure Illustrative December in a calendar: a release falls inside the year-end change freeze, and the overlap is marked. Trusted by Industry Leaders Warner Bros. Disney Sony UC Berkeley Motorola Teck Resources US Treasury University of Pittsburgh NASA Stockholms Stad FedEx Zespri and over 8,000 businesses worldwide ## A Year of Technical Change Against the Business Plan Overlay the change records, release milestones and freeze windows your teams already keep — in SharePoint, Planner, Microsoft 365 Groups and vendor feeds — without a second change register. Year ### Every change and release of the year, by domain #### Changes by risk tier and domain Approved change records from the SharePoint change list carry their domain — application, cloud platform, database, infrastructure, network, security — as a category, so a year of technical activity is read by what it touches, not by who filed it. #### Three sources, three colours The change list, the delivery milestones from Planner and the vendor maintenance feed each keep their own colour, so the CIO sees at a glance whether a crowded month is internal change, delivery pressure or a vendor's schedule. #### Vendor maintenance where a feed exists Where a vendor publishes an authoritative maintenance calendar, it can be added as a read-only feed and drawn next to internal changes. The calendar shows the window; it does not confirm the vendor's plan. ![Year view of a CIO change and release calendar for 2026: infrastructure, application, security, database and cloud platform changes, vendor maintenance windows and delivery milestones month by month, with the category list open showing Application, Cloud Platform, Database, Infrastructure, Network and Security](https://www.virtosoftware.com/images/use-cases/cio-change-freeze-calendar/year.webp) Year — 2026 month by month: changes by domain, vendor maintenance windows and delivery milestones, with the category list open. Quarter ### A quarter of change, with a vendor's own entry open #### What the feed says, unchanged A vendor's maintenance entry keeps the description it was published with — the change reference, the owning team, the expected impact — because the calendar reads the feed rather than re-entering it. #### Emergency changes next to planned ones An emergency hotfix on the network firewall is drawn in the same August as the planned migrations around it, so the quarter shows what was planned and what was not. #### Quarter for the review, Year for the plan Year Quarter is the scale for a quarterly risk review; Year and Flat Year hold the whole plan. The sources, colours and permissions stay the same at every scale. ![Year Quarter view, Q3 2026: application, security and database changes, delivery milestones and vendor maintenance for July, August and September, with a Salesforce release deployment entry open showing its description, change reference and owning team](https://www.virtosoftware.com/images/use-cases/cio-change-freeze-calendar/year-quarter.webp) Year Quarter — Q3 2026: the open entry is a vendor release as it arrives from the maintenance feed, with its change reference and owning team in the description. Week ### Delivery milestones over the week's changes #### Milestones from Planner, not re-typed Selected Planner tasks — the delivery milestones a programme reports on — appear as all-day bars in the week they are due, read directly from the plan. #### Freeze windows as bars, not footnotes A freeze declared for a peak period or a year-end close is drawn across the days it covers, so a change scheduled into it is read against the freeze, not discovered afterwards. #### Read-only, by design Change records stay in the SharePoint list, milestones in Planner, vendor windows in the feed. The calendar reads them through the permissions each reader already has and becomes nobody's second change register. ![Week view, 21 to 27 June 2026: five delivery milestones from Planner — benefits configuration review, penetration test findings review, beta tester feedback review, analytics dashboard prototype and integration testing cycle 1 — drawn as all-day bars across the week, with an infrastructure config change to the analytics pipeline and an application upgrade of the e-commerce front end below them, and the integration testing cycle task open showing its dates, bucket ERP Consolidation, progress and priority](https://www.virtosoftware.com/images/use-cases/cio-change-freeze-calendar/week.webp) Week — 21–27 June: Planner's delivery milestones above the week's changes, with one milestone open to show its bucket, progress and priority as Planner holds them. ## Key benefits ### The year of change on one screen Changes, releases, freeze windows and vendor maintenance from every source in one Microsoft 365 view — Year for the plan, Year Quarter for the review. ### Collisions before approval A release inside a freeze, or two migrations on the same system in the same month, is visible while the change board can still move one of them. ### Domain and risk tier as categories Application, infrastructure, security, database, network and cloud platform changes keep their category, so a leader reads the year by what is being touched. ### Vendor windows, conditionally An authoritative vendor maintenance feed can be overlaid read-only. Where no such feed exists, nothing is invented. ### No second change register Records, approvals and the CAB workflow stay in the ITSM tool or the SharePoint list that owns them. The calendar only shows when. ### Permissions from the source Each reader sees the change lists and calendars they already have access to — the executive view is not a broadcast. ## When Virto Calendar App fits — and when it does not | Real-life scenario | Best fit | Why it works | | --- | --- | --- | | A release lands inside a financial close freeze — You approve the annual plan, but change and close calendars live in different systems. | Virto Calendar App M365 | Changes, releases and freeze periods are drawn on the same year as close cycles and board dates, so the collision is visible while the date can still move. Use the same app in Microsoft 365 or Microsoft Teams. | | Two migrations and a vendor upgrade in the same month — The change list, Planner and the vendor's calendar each show one of them. | Virto Calendar App M365 | All three are drawn in the same month with their own colours, so the CIO sees the crowded window before the change board approves the last one. | | Change records, approvals and the CAB workflow | An IT service management system | Virto Calendar App shows when a change happens. Records, risk assessment, approvals and the CAB workflow stay in the ITSM tool or the SharePoint list that owns them. | ## Related products Explore how our set of productivity tools can transform your task management - [Virto Calendar App M365](https://www.virtosoftware.com/microsoft-365/virto-calendar-overlay-app/): Consolidate events from SharePoint, Exchange, Google, and more into one calendar view for simplified planning. - [Virto Calendar App](https://www.virtosoftware.com/microsoft-teams/virto-calendar-app/): The same change, release and freeze calendar inside Microsoft Teams, where the CIO's staff and service owners already work. - [Virto Calendar On-Premises](https://www.virtosoftware.com/sharepoint/sp-calendar-web-part/): Overlay SharePoint change lists and other calendar sources for the same year view in SharePoint On-Premises. ## Related use cases Discover our range of use cases to take your planning and coordination to another level ![Executive Annual Calendar](https://www.virtosoftware.com/images/use-cases/executive-annual-calendar.webp) ### Executive Annual Calendar Overlay approved strategic milestones, launches, board and QBR dates and annual targets by theme in one live annual calendar for the CEO and COO. ![IT Change & Release Calendar](https://www.virtosoftware.com/images/use-cases/it-change-release-calendar.webp) ### IT Change & Release Calendar Overlay change, release and maintenance lists from every business unit in one Microsoft 365 calendar, so IT sees colliding windows before they open. ![CFO Close, Reporting & Governance Calendar](https://www.virtosoftware.com/images/use-cases/cfo-close-reporting-calendar.webp) ### CFO Close, Reporting & Governance Calendar Overlay finance registers, board and audit calendars and statutory feeds in one Microsoft 365 year view, so the CFO sees close windows, filing deadlines and board dates in sequence.