Five-Market Launch, Wrong Time Zone and Duplicate Posts
Wayfarer Travel is launching a winter fare sale in five markets: the US, UK, Germany, Japan and Australia. The team loaded 42 posts into Perch, intending each market to publish at 09:00 local time. On launch day, the US post went live at 02:00 local, the UK and Germany received duplicate posts from two planners, and a scheduled post promoted a beach destination while the airline was handling a weather-related cancellation crisis. Three approvers work in different time zones, and the final approval for Japan happened after the intended publish time. The team has no documented blackout process. The CMO wants a post-incident fix that does not add headcount and preserves the 09:00 local cadence.
1. Diagnose the time-zone and duplicate root causes and propose scheduling controls.
Read the worked answer
The symptoms point to three control gaps, not one mistake.
Time zone: The US post at 02:00 local strongly suggests the schedule was set in a default zone, probably UTC or the scheduler's home zone, rather than the market's local zone. The team may also have assumed that typing '09:00' means local time for every account. Fix: confirm the publishing time zone at the account or campaign level, display it next to every scheduled post, and run a one-post test in each market before launch. The calendar should show local time and the account label together.
Duplicates: Two planners scheduled the same content because there was no single owner or duplicate check. Fix: one market owner per market, a naming convention that includes market, date and sequence, and a daily duplicate review in the calendar. Lock approved posts so a second planner cannot reschedule them accidentally.
Japan approval: The approval cut-off was too close to publish time. Fix: require approval at least 24 hours before the local publish time, with an escalation path. These controls cost process discipline, not headcount.
2. Design an approval and blackout protocol for a five-market launch with three approvers.
Read the worked answer
I would define a simple RACI per market: one planner, one approver and one backup approver, with the global lead owning the calendar and the blackout decision. Three approvers can cover five markets if the split is by time zone, not by committee.
Protocol:
- Approval SLA: all launch content approved 24 hours before local publish; Japan's cut-off is the earliest in absolute time because of the time-zone gap.
- Escalation: if the named approver is unavailable, the backup decides within two hours; no silent auto-approval.
- Blackout trigger: a named crisis owner can pause all queues for a market or globally. The trigger list should include safety incidents, severe weather disruption, operational outages and legal holds.
- Crisis hold: when triggered, pause scheduled promotional content for 24 hours, review the next 72 hours, and replace with service messaging only after approval.
- Daily stand-up: 15 minutes across time zones to review the next 48 hours, duplicates and holds.
The beach post during the weather crisis shows the blackout trigger was missing, not that the planner was careless. A documented hold and a single pause authority fix that without adding staff.
3. The duplicate UK post has 40 comments and 3 customer complaints. Do you delete it, and what do you tell the market lead?
Read the worked answer
I would not automatically delete it. The decision depends on engagement and content. With 40 comments, the duplicate has become a conversation space; deleting it can remove customer questions, look evasive and fragment the record. If the two posts are identical and the second has little engagement, deleting the later one is reasonable. If both are active, I would keep one as the canonical post, pin a comment acknowledging the duplicate, and route complaints to the care team.
What I would tell the market lead:
- The cause was two planners scheduling the same content without a single owner, not a platform failure.
- The duplicate with active comments will remain for 24 hours with a pinned acknowledgment; the other will be removed if it has low engagement.
- Complaints are being logged and answered in Nest, not hidden.
- The fix is a market owner, a duplicate check and locked approved posts.
I would avoid a silent deletion because it creates a second trust problem. The goal is to reduce clutter while preserving customer voice and an auditable response.