Skip to main content Scroll Top

Give December Website Changes a Smaller Approval Window

Photo: Estée Janssens / Unsplash

December can leave a website with fewer available reviewers and more time-sensitive messages. A smaller approval window helps the team finish necessary work without assuming someone will be available to check it later. The point is to reduce uncertainty, not to rush an incomplete change into production.

Make a short list of changes that must happen this month. Separate factual updates and reliability repairs from optional improvements. For each necessary item, name the person who supplies the facts, the person who publishes it and the person who checks the result. One person may hold several roles, but the responsibilities should still be explicit.

Advertisement

Set the review deadline before the publication deadline. Leave room to resolve contradictions in hours, offers or availability. Keep the proposed wording and visual in one place so reviewers do not approve different versions. If a required fact is still missing, explain that limitation and reduce the scope rather than filling the gap with a guess.

After publication, send the owner the actual public page and a short check result. Record any temporary wording that needs to change in January. This makes the approval process a completed loop: verified input, reviewed change, tested page and planned follow-up. A shorter queue can be more useful than a long list of festive improvements nobody has time to verify.

A practical review

A product demonstration and a decorative background loop should not be treated as the same component. A demonstration may justify a deliberate play action, controls and an accompanying explanation. The background loop should not be the only place a visitor learns an essential feature. Check the still fallback with the video fully disabled rather than merely paused. The page’s heading, explanation and action should still make sense. If a still image produces the same understanding, compare its actual visual quality with the video’s first frame. An intentional photograph often offers better composition than a frame chosen only because it happened to start the clip. Make the decision around the communication job instead of assuming movement automatically signals a more premium experience.

Before you finish

  • Separate necessary December updates from optional visual work.
  • Name the fact owner, publisher and final checker.
  • Allow time between approval and publication for factual corrections.
  • Record January follow-up for every temporary December change.

Quick check

How much did you catch? Tap a question to see the answer.

1. Which December changes should be separated from optional design work?

Answer: Separate necessary December updates from optional visual work.

Advertisement
2. Who should be named in the approval process?

Answer: Name the fact owner, publisher and final checker.

3. Why should approval happen before the publication deadline?

Answer: Allow time between approval and publication for factual corrections.

Setting Up the December Change Queue

A smaller approval window works best when the queue is visible to everyone involved and short enough to read in one glance. A simple process might look like this:

  1. List every December change on one page. Holiday hours, closure notices, shipping or booking cutoffs, year-end offers, and any repairs already scheduled.
  2. Sort into three groups. Must publish (factual or time-sensitive), should repair (reliability problems customers will notice) and can wait (everything else, including redesign ideas).
  3. Assign three roles to each must-publish item. The fact supplier, the publisher and the checker. Write the names in the queue.
  4. Set two dates per item. The review deadline and the publish date, with at least one working day between them where possible.
  5. Move “can wait” items to a January list. Taking them out of December’s queue protects the important work from distraction.

A worked example

A small bakery needs to publish holiday order deadlines, collection times and reduced opening hours. The owner supplies the dates, a part-time staff member updates the website and the manager checks the published pages. The review deadline is set for a Tuesday, the publish date for Thursday. On Tuesday, the manager notices that the order deadline on the draft differs from the one on the printed flyer. Because there is a gap before publishing, the owner has time to confirm which date is correct, and both the page and the flyer are corrected before customers see either.

Making Reviews Faster Without Making Them Weaker

  • Keep one source of truth. Put the proposed wording, any image and the target page link in a single document or ticket. Reviewers should never have to compare an email draft with a chat message.
  • Ask specific questions. Instead of “Does this look OK?”, ask “Are these dates correct?” and “Does this match what staff will tell customers on the phone?”
  • Approve in writing. A short “Approved” reply attached to the item is enough, and it removes any later doubt.
  • Batch similar changes. If hours appear on the contact page, the footer and a map listing, review them together so they stay consistent.
  • Schedule the follow-up now. Every temporary December message should have a January removal date before it is published.

Common December Pitfalls

  • Last-minute “small” improvements. A new banner style or homepage rearrangement introduced in the final week before a closure can break something nobody has time to fix.
  • Approvals given from memory. A reviewer who approves without opening the page may miss that the published version differs from the draft.
  • Single points of failure. If only one person can publish and they are away, the queue stops. Confirm a backup before the holidays.
  • Guessing at missing facts. If a delivery partner has not confirmed a cutoff, say that the date will be confirmed, or leave the line out until it is.

Questions to settle this week

  • Which changes genuinely must happen in December?
  • Who is unavailable, and when?
  • Who can publish and check if the usual person is away?
  • What will need to be undone in January, and who owns that task?

What this means for the rest of the month

A shorter, clearer queue usually means fewer changes, and that is the point. Each December update that does go live has confirmed facts behind it, a named reviewer and a planned exit. The improvements that were set aside are not lost; they sit on the January list with notes attached, ready for a time when reviewers have the attention to give them. Customers are better served by a few dependable updates than by many rushed ones that nobody had time to verify.

Fenway Web is coming to iPhone

Client news, portfolio work and the Fenway Journal in one app for iPhone, iPad and Apple Watch.

See Fenway Web

Latest stories

View all
Our clients