Quick answer
A website change freeze checklist defines what is frozen and from when, who can approve exceptions and who recovers the site if something breaks. Before a major promotion, confirm a backup exists, require a reason and a test for every exception, and name who can restore it and how long that may take.
- Define the freeze scope by page, plugin and setting, with a start time, because a vague freeze is broken quickly.
- Give every exception a business need, a named approver, a test and an owner.
- Confirm a pre-freeze backup exists and agree who restores it, from which backup and how long it may take.
A promotion is about to launch and several teams still want website changes. A change-freeze checklist defines what is frozen, who can approve exceptions and who recovers if something breaks. This is for WordPress site owners and maintainers. It is written for wordpress site owners and maintainers and ends with the decision, owner and next step to record.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. A promotion is about to launch while several teams still request website changes.
What happens. A promotion launches on Monday. On Wednesday the team fixes the freeze scope, lists what is pending, approves two exceptions with a reason and a test, confirms a backup exists and names who can restore it if something breaks.
Freeze scope
Define the scope of the freeze: which pages, plugins and settings stop changing, and from when. Use the change and freeze status fields. Be specific, because a vague freeze will be broken within a day.
Approved exceptions
Decide what exceptions are allowed and who approves them. Use the business need and exception approver fields. Every exception needs a reason, a test and an owner.
Recovery ownership
Agree recovery before the freeze: who can restore, from which backup and how long it may take. Use the recovery action and verification fields. Confirm the backup exists first.
Promotion change-freeze checklist
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Change | Business need | Freeze status | Exception approver | Recovery action | Verification |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Change | Business need | Freeze status | Exception approver | Recovery action | Verification |
|---|---|---|---|---|---|
| Update homepage banner | Promotion launches Monday | Frozen from Friday | Marketing lead | Restore from pre-freeze backup if needed | Check homepage and form after the change |
Working through the completed row
The example freezes a homepage banner change from Friday for a Monday launch, names the marketing lead as exception approver, restores from the pre-freeze backup if needed and checks the homepage and form afterwards.
Common mistakes
- Leaving the freeze scope vague.
- Approving exceptions without a test.
- Having no tested backup.
Questions to settle before you rely on it
- Which changes are blocked and why?
- Who can approve an exception?
- What is the recovery plan?
How you know it is complete
The checklist is complete when each change has a need, status, approver, recovery action and verification. Record who reviewed it and the date.
Where you may not have the answer
A critical fix is needed during the freeze. The approver decides, and the change is tested and logged. The handoff, not a guess, is the correct next step.
Your next action
Write the freeze scope and exception approver before the next promotion.
Ask Web Design Davao to review this workflow and scope the website or marketing support required. Website maintenance & security arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Preventative website maintenance includes keeping plugins up to date and reviewing website code for known vulnerabilities. This reduces exposure to attack; it does not guarantee a site cannot be compromised. See website updates and uptime monitoring.
Frequently asked questions
What should a website change freeze cover?
Define which pages, plugins and settings stop changing and from when. Be specific, because a vague freeze will be broken within a day. List pending changes, and record each change’s business need and its freeze status.
Who should approve exceptions during a freeze?
Name an exception approver before the freeze starts, such as the marketing lead. Every exception needs a reason, a test and an owner. If a critical fix is needed, the approver decides, and the change is tested and logged.
What recovery plan do we need before a promotion?
Agree recovery before the freeze: confirm a backup exists, decide who can restore from it and how long that may take, and check key pages and forms after any change. A backup that has not been tested is a common mistake.