Give a brand its own social media calendar when it has its own approver, voice, timezone or confidentiality needs. Keep one shared layer on top for the dates that must line up everywhere, such as launches and holidays. It's how large brands keep teams and regions aligned: separate execution, shared dates.
TLDR: Run six tests (approver, voice, timezone, rhythm, confidentiality, volume). If three or more say "separate", split the calendar. Keep one master view for launch dates, blackouts and campaigns.
Six tests: split or keep together?
| Test | Keep one calendar if... | Split if... |
|---|---|---|
| Approver | The same person signs off everything | Each brand has its own approver |
| Voice and language | One voice, one language | Different tone or language per brand |
| Timezone | One audience timezone | Brands or regions run on different clocks |
| Posting rhythm | Similar frequency | One posts daily, another weekly |
| Confidentiality | Everything can be seen by all | Clients or markets must not see each other |
| Volume | Under about 15 posts a week in total | One calendar is too crowded to scan |
Count the splits. Three or more means separate calendars. With one or two, stay together and use filters.
What goes in the shared layer
Separate calendars shouldn't mean separate worlds. Keep one shared layer, owned by one person, and put in only what needs aligning:
- Launch dates and campaign start and end dates
- Bank holidays and blackout days (no promotional posts)
- Legal or compliance review deadlines
- Global posts that every region must run, with two weeks' notice
Everything else, the day-to-day posts, stays in each brand's own calendar. If a brand team has to ask permission to post on a Tuesday, you've built too much into the shared layer.
How to align regions without slowing them down
Large teams use a simple split: the centre decides what and when, the region decides how. Headquarters publishes the "must run" list. Regional teams adapt the copy, language and timing inside their own calendar and mark the shared posts as scheduled.
Set each region's timezone on its own calendar, so a 9 am local post isn't scheduled on headquarters' clock. If your regional work involves translation, localising a calendar without 10x the work covers it.
An example: one retailer, three regions
Picture a retailer with US, UK and German teams. Each has its own approver, language and clock, so all six tests say "split". Headquarters keeps a shared layer with just the seasonal sale dates, the two product launches and the public holiday blackouts.
The US team plans its own weekly posts, the UK team adapts the launch copy, and the German team translates and schedules in its own timezone. Headquarters doesn't review daily posts. It only checks that the shared dates appear on every regional calendar.
How this looks in Mydrop
Mydrop's workspaces give each brand or market its own calendar, timezone and roles, and brands keep profiles grouped under one account. For the shared layer, use campaign names consistently and filter the calendar by campaign, as described in how to filter the social media calendar by campaign. Calendar notes can carry blackout days and launch reminders right beside the posts they affect. Reminders and the social inbox can stay central even when the calendars are separate.
A 20-minute weekly alignment meeting
Hold it once a week, with one person per brand or region:
- Next two weeks of shared dates (5 minutes). Is anything changing?
- Conflicts (5 minutes). Are two brands running similar offers on the same day?
- Blockers (5 minutes). Late assets, approvals still waiting.
- Next week's must-run list (5 minutes). Confirm who owns each item.
If the meeting overruns, the shared layer has too much in it. Move anything that only affects one brand back into that brand's calendar, and save the meeting for dates that touch two or more.
Next step: run the six tests for your brands and write down the count. Then name an owner for the shared layer. To set up a workspace for each brand, start free with Mydrop.
Google review
Trustpilot review
Product Hunt comment
