Content calendar: leaving the spreadsheet without losing control
The spreadsheet works until the third client. How to build a content calendar the whole team actually uses — and how to switch in a week.
Almost every social media team starts in a spreadsheet. It makes sense: it's free, everybody knows it, and a post fits on one row. The trouble shows up slowly, with the third or fourth client.
Where the spreadsheet starts to fail
- The files live somewhere else. The row says "launch Reel", but the video is in a Drive folder, version 2 is on WhatsApp and the final caption is in a separate document.
- Nobody knows where things stand. "Editing" was typed on Monday; the editor finished on Wednesday and never changed the cell.
- Approval happens outside it. The client says "go ahead" in the middle of another conversation, and a week later nobody remembers whether it was the right version.
- Each client has a tab, and seeing the whole team's week means opening ten of them.
None of this is a lack of discipline. It's the tool asking people to remember what it doesn't keep.
What a calendar needs
A good content calendar answers seven questions for every post, without anybody having to ask:
- When it goes out — day and time.
- What it is — the format: image, Reel, carousel.
- Where it goes — the networks.
- Where it stands — a status everyone updates: not started, shooting, editing, finished, scheduled, published.
- Who owns it — one person, not "the team".
- What it says — script and caption, on the post itself.
- What it's made of — the files, with their versions and the client's decision on each.
If any of those answers lives outside the calendar, that's where the work gets lost.
A weekly routine that works
- Monday: plan the following week. Whoever plans puts the posts on their days, with format, network and owner. The script can stay blank, but its place already exists.
- During the week: change the status on the post itself. Shot it — "shooting". Edited it — "editing". That's what keeps next Monday short.
- Wednesday: send to the client for approval whatever will be ready by Friday, through one link instead of five messages.
- Friday: look at what's late. A post still "editing" the day before it goes out is the conversation that has to happen today, not tomorrow.
How to switch in a week
Don't migrate the history. Start with what's still ahead:
- Day 1: create one team per client and invite the people who work on it.
- Day 2: put in the next two weeks of posts, with just the day, format and owner.
- Days 3 and 4: whoever produces uploads files to the post and changes the status there, not in the group chat.
- Day 5: send the first approval to the client from the calendar.
The spreadsheet stays as an archive of the past. In two weeks, nobody opens it anymore.
Want to see how this works in Tucan? The steps are in Create posts and tasks and Invite your team.