Prepare the board before the meeting.
Give the team a current view of the next seven days before the meeting starts. Pull scheduled posts, drafts waiting on review, open ideas, publishing blockers, and inbox items that may need a response or follow-up post.
This preparation keeps the meeting focused on choices. The team can see what already exists, what is blocked, and where the week needs stronger coverage.
- Scheduled posts by platform
- Drafts waiting on approval
- Open calendar slots
- Inbox items that need follow-up
- Publishing or account connection blockers
Begin with coverage.
Look at the week by brand, platform, campaign, pillar, and timezone. Mark empty slots, overloaded days, missing platform coverage, and content that depends on an approval deadline.
Coverage tells the team where attention belongs. A launch week may need more proof posts and support replies. A quiet week may need evergreen posts, founder updates, or community prompts.
- Empty days
- Overloaded days
- Campaign gaps
- Pillar gaps
- Review bottlenecks
Pull intake from Slack.
Review saved messages, bot DMs, links, campaign notes, customer comments, and threads the team marked during the week. Slack is where many usable ideas appear, so planning should start from that source material.
Turn each useful input into one of three outcomes: draft it, park it in the content library, or close it with a reason. An idea that sits in the channel with no owner will disappear by the next planning cycle.
- Customer proof
- Product updates
- Launch notes
- Support themes
- Founder commentary
- Competitive observations
Commit each accepted idea to a next action.
For each accepted idea, assign an owner, platform target, campaign or pillar, and review deadline. If the team cannot name those details, keep the idea in the library until it has enough shape to become work.
Use the meeting to make ownership visible. A planned post should leave the room with one person responsible for the next step and one date when the draft needs a decision.
- Draft owner
- Platform target
- Campaign or pillar
- Approval route
- Review deadline
Finish with risks and owners.
End by checking account health, publishing blockers, aging inbox items, and posts waiting on approval. The meeting should reduce the number of blocked items before the team leaves.
Give each risk an owner. A blocked account connection needs one person to reconnect it. A delayed approval needs one person to chase the decision. A late inbox thread needs one person to answer or escalate it.
Where this fits in Slash Social
Use the product workflow that matches this resource: approvals, planning, inbox, analytics, or multi-brand operations.