Short answer: a social SOP for a SaaS team writes down who picks topics, who films and edits, who approves, who posts and who checks results, plus the rules for account access, rights and failures. Keep it to one page, review it quarterly, and make the approval step and the "did it actually go live" check non-negotiable.
Roles
| Role | Owns | Typical person |
|---|---|---|
| Social lead | Calendar, final approval, account list | Marketing manager |
| Creator | Scripts, recording | Marketer, founder, product person |
| Editor | Cuts, captions, exports | Editor or marketer |
| Reviewer | Accuracy of product claims | Product manager |
| Poster/operator | Scheduling and confirming posts | Social lead or ops |
| Responder | Comments and DMs | Support or community |
In a small team one person holds several roles. Write the names anyway.
Weekly cadence
| When | Step | Done when |
|---|---|---|
| Monday | Topics chosen from support and sales notes | 5–7 topics in the calendar |
| Monday–Tuesday | Recording | Raw files in the shared folder |
| Wednesday | Editing and captions | Exports named by convention |
| Wednesday | Product review | Reviewer signs off each claim |
| Thursday | Scheduling | Each post has account, time, caption, link |
| Daily | Confirm posts went live | Status set to posted or uncertain |
| Daily | Comments, 15 minutes | Replies sent or escalated |
| Friday | Numbers and notes | Report row filled |
The times are assumptions; the sequence is what matters. The calendar itself is covered in the content calendar template.
Rules to write into the SOP
- Rights. Only post content we own or have written permission to use. Customers and guests sign off before they appear; see customer story shorts.
- Claims. No numbers without a source. No promised results.
- Disclosure. Company-run accounts say so in the bio.
- Honesty. No fake engagement, no bought followers, no replies posing as customers.
- File naming.
date_topic_format_account.mp4. - Links. Only tagged links from the shared sheet; see UTM links.
- One post, one account. Never post the same clip twice to one account.
Account access
- Accounts are owned by company email addresses, with two-factor authentication on.
- A written list of every account: handle, platform, owner, recovery email, device it lives on.
- Remove access the day someone leaves.
- Founder personal accounts: the founder owns the login and agrees what the team may post.
When a post fails or is uncertain
| Situation | Action |
|---|---|
| Post did not publish | Reschedule for the next slot, note the reason |
| Unsure whether it published | Check the profile by hand before reposting |
| Posted to the wrong account | Delete, note it, review the account check |
| Comment storm or complaint | Escalate to social lead; do not argue in public |
Checking before reposting avoids duplicates, which look careless.
Quarterly review
Once a quarter, walk through the SOP as a team. Check that every account on the list still exists and has a named owner, that ex-staff no longer have access, that the link sheet matches the live profile links, and that platform changes (lengths, link rules, features) have not made a step out of date. Record what changed and when, at the bottom of the SOP.
Where Farmero fits in the SOP
If posting runs from iPhones with Farmero, the "confirm posts went live" step is built in: it checks the profile for each new post, labels what it could not confirm as uncertain, never retries those automatically, and stops with saved evidence when it cannot identify a screen. It reports what posted, what did not and what was refused. See troubleshooting and what Farmero never does.
FAQ
How long should a social SOP be?
One or two pages. Link out to the calendar and the link sheet.
Who should approve product claims?
Someone who knows the product well, usually a product manager.
How often should we update the SOP?
Quarterly, or whenever a platform changes something that affects the steps.
Should the SOP cover paid ads?
Keep ads in a separate SOP; the approvals and budgets differ.