Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Change Freeze

A set period around a peak when changes that are hard to reverse are stopped while routine, reversible work continues through an agreed route.
StrategyprocessUpdated

Definition

A change freeze is a named period, set around a peak, in which changes that are hard to reverse or hard to diagnose are stopped while routine, reversible work continues. The tutorial on planning a change freeze around peak periods defines its parts: the period and why it matters, the kinds of change covered, what stays allowed, the dates, the exceptions route, the notice to everyone who can make changes, a queue for held requests and an ordered lift.

In software teams the same idea is often called a code freeze. A marketing freeze reaches further than code, because the systems that break at peak include tracking, email templates, journeys and ad account structure as well as the site.

What is frozen and what keeps moving

The dividing line is reversibility. What is costly or slow to undo during the peak is frozen: tags and tracking, site templates and pages near checkout, email templates and automated journeys, ad account and campaign structure, integrations between tools, and campaign naming. A change that would alter how results are measured is frozen by default, since it makes the peak's own numbers harder to read.

What keeps moving is routine work that can be undone: social posting, scheduled sends from approved templates, publishing in existing templates, community replies and budget moves within limits agreed in advance. The tutorial is blunt about why the list matters. A freeze that stops everything is ignored within days; a freeze that names nothing in particular invites argument about what counts.

The period is the business's own. It follows the Seasonality of its trade and its history of past peaks, so no general length applies.

In practice: dates, exceptions route and lifting in order

Dates. The start is early enough for changes made before it to be tested and settle; the end is late enough to cover the peak and the days after it, when orders, returns and reporting are still flowing. The peak season trading playbook places the freeze after the build window, so pages, feeds, campaigns and emails are finished first; the guide to seasonal and sale event pages has its page work done before the freeze begins. New work can be tested on a Staging Environment and is recorded before the start.

Exceptions. Some changes cannot wait: a broken checkout tag, a pricing error, a journey sending the wrong offer. The exceptions route asks the person raising it for what is broken, the fix, the test and how it will be reversed, and a named decision-maker, with a deputy, approves or declines. Approved changes are made, tested and dated in the Change Log, so a later movement in the figures can be traced.

Notice and lift. The freeze notice goes to everyone with publishing rights, including agencies and developers, since a freeze is most often broken by someone who never heard of it. Requests that arrive during the freeze wait in a queue and are released afterwards a few at a time, testing each. Affiliate programmes have their own reason to care: the guide to running promotions through affiliates asks for tracking to be left alone during the peak. The marketing governance hub sets the freeze beside approvals and access as one of the decisions about who may change what.

Illustrative example — not a real result

A toy shop finishes its template work before the December rush

Last year Skealdenny Toy Shop edited its product page template on 9 December to add a gift-wrap option. The edit removed the container the purchase tag relied on, and for three days the shop's reports showed almost no online sales while the till said otherwise. This year the owner set a freeze from 24 November to 3 January covering templates, tags, the email journeys and the feed. The gift-wrap change and two new templates went live on 17 November after testing. On 12 December the delivery cut-off banner showed the wrong date; the web freelancer described the fix and how to undo it, the owner approved it within the hour, and it was dated in the change log. Six held requests were released in the second week of January, two a day.

The Change Log is where every change before the freeze and every approved exception during it is dated. Seasonality decides when the peak falls and therefore when the freeze runs. A Staging Environment is a place to test the frozen kinds of change before the start, and queued ones before they are released.

Common confusions

  • A freeze stops all marketing. It stops changes that are hard to reverse; routine, reversible work continues through the normal route.
  • A freeze means nothing can be fixed. Real breaks go through the exceptions route, approved by a named person and recorded.
  • Only the in-house team needs to know. A notice that reaches agencies, freelancers or developers late is the commonest reason a freeze is broken.
  • The day the freeze ends, everything waiting can go live. Held changes are released in order and tested one at a time, so a new break has an obvious cause.
  • Last-minute work should be rushed in before the start. Changes made on the eve of a freeze are the ones most likely to break during it; unfinished work waits.

More terms to look up

Where this term is used

Related