You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree ยท Change it any time

    • NecessaryAlways on
    • AnalyticsOpt-in
    • MarketingOpt-in
    • PreferencesOpt-in
    Still loading. Try again in a moment.Still loading. Try again in a moment.Still loading. Try again in a moment.
    Atlas
    • All-in-one
    • Solutions
    • Compare
    • Pricing
    PricingGet started
    1. Templates
    2. Change Freeze Plan Template

    Moratorium template

    Free Change Freeze Plan Template

    A change freeze plan built on the moratorium presets in Atlas: a yearly holiday freeze, a sale-season block on releases, and a weekly weekend block on deployments, each at the enforcement level it needs.

    Use this template in AtlasStart free
    • Release template
    • Free to use
    • Set up in Atlas

    Overview

    About the change freeze plan template

    A change freeze, also called a moratorium or blackout window, is a period when a team deliberately does not ship. Holidays leave nobody to watch production, a sale makes any change too risky, and some windows are set by compliance.

    In Atlas a moratorium is a window in the workspace time zone, optionally repeating every year or every week, scoped to projects and environments, with one of four enforcement levels. Three presets give a starting point: Christmas and New Year, Black Friday and Cyber Monday, and Every weekend.

    A freeze is only useful when it is enforced. Atlas checks moratoriums when a release is created, when it is moved to Released, and when a deployment is recorded, and an allowed release type or an approved exception turns a block into a warning.

    What is included

    What is in the template

    • Christmas and New Year

      From 24 December to 2 January, repeating every year, for the holiday reason, at Freeze all: no new release, no release, and no deployment.

    • Black Friday and Cyber Monday

      From the Friday after the fourth Thursday of November for four days, for the sale reason, at Block releases: no release may ship or deploy.

    • Every weekend

      From Saturday to Monday, repeating every week, for the staffing reason, at Block deployments: no deployment may be recorded.

    • Four enforcement levels

      Warn blocks nothing and is shown everywhere. Block deployments refuses deployments. Block releases also refuses moving a release to Released. Freeze all also refuses creating a release.

    • A way through

      Name release types that are let through, such as Hotfix, and let a release ask for an exception that a workspace owner or administrator approves.

    How to use it

    How to use the change freeze plan template in Atlas

    1. 1

      Open the moratoriums screen

      Go to /releases/moratoriums. Creating and editing moratoriums is for workspace owners and administrators.

    2. 2

      Start from a preset

      Choose a preset, then adjust its dates, time zone, environments, projects, and enforcement level to fit your calendar.

    3. 3

      Let the urgent work through

      Name the release types allowed during the freeze, for example Hotfix, so a live problem can still be fixed.

    4. 4

      Review exceptions

      When a release asks to ship during a freeze, approve or reject the request from the exceptions queue.

    Related reading

    • Change freeze periods
    • IT change management guide
    • The hotfix release process
    • Release management: a complete guide
    • Release Management in Atlas
    • All free templates

    FAQ

    Questions, answered.

    What is the difference between the four enforcement levels?
    Warn is shown everywhere and blocks nothing. Block deployments refuses recording a deployment. Block releases refuses deployments and moving a release to Released. Freeze all also refuses creating a new release.
    Can a freeze apply to only one environment?
    Yes. A moratorium can name environments, and then it applies to deployments to those environments only. An empty list means every environment. It can be scoped to projects in the same way.
    How does an urgent fix get through a freeze?
    Either the moratorium names the release type as allowed, which turns the block into a warning for that type, or the release asks for an exception and a workspace owner or administrator approves it. A new release cannot be created during Freeze all, because an exception belongs to a release that already exists.

    Ready when you are

    Put the change freeze plan template to work in Atlas.

    Atlas is the all-in-one work OS: tasks, projects, CRM, contracts, HR, and automation on one shared record, with a governed AI assistant. Start free.

    Get started freeSee pricing
    AtlasWork, planned itself.

    The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    Product

    • Overview
    • PDF tools
    • Diagram tools
    • People & HR
    • Integrations
    • Marketplace
    • Pricing

    Resources

    • Guides
    • Glossary
    • Compare
    • Docs
    • API reference
    • Support
    • Changelog
    • Status

    Company

    • About
    • Careers
    • Press
    • Contact

    Legal & trust

    • Trust center
    • Security
    • Privacy
    • Terms
    • DPA
    • GDPR
    • SLA
    • Refunds
    • Google API data
    Atlas, a product by wrxstack.comยทยฉ 2026 wrxstackยทAll rights reserved
    PrivacyTermsSecurityStatus