Short answer: a clipping team SOP names each role, the handoff between them and the checks at each step. A typical flow is sourcing, editing, QA, posting and reporting, with one shared tracker. Write the rules down once: permission, originality, disclosure and no fake engagement. Then every clip passes the same checklist before it goes live.
Roles
| Role | Owns | Hands off |
|---|---|---|
| Lead | Campaigns, niches, accounts, rules | Briefs to sourcer |
| Sourcer | Finding moments in permitted sources | Moment list with timestamps |
| Editor | Cuts, layout, captions, export | Finished files |
| QA | Checks against brief and rules | Approved files |
| Poster | Scheduling, captions per account, confirming live | Live links |
| Reporter | Views, proof, submissions | Weekly report |
On a small team one person holds several roles, but keep QA separate from editing where you can.
The flow
- Brief. Lead adds the campaign or niche to the tracker with its rules. See clipping campaigns at scale.
- Source. Sourcer logs moments from permitted material only.
- Edit. Editor works in passes. See batch editing.
- QA. Checklist below. Rejected clips go back with a note.
- Post. Poster assigns each clip to one page per platform and schedules.
- Confirm. Poster records the live link.
- Report. Reporter captures views and submits proof. See proving views.
QA checklist
| Check | Pass condition |
|---|---|
| Permission | Source is on the approved list |
| Brief | Length, tags, platforms match |
| Hook | On screen, matches the clip |
| Captions | Proofread, names and numbers correct |
| Placement | Text clear of app UI areas |
| Disclosure | In the video when paid |
| Audio | No uncleared music |
| AI | Labeled if realistic synthetic content |
| Duplicates | Not already queued to another page on the same platform |
| File | Named correctly, export preset used |
Team rules
- Use only content we own or have permission to use. See clipping and copyright.
- No bought views, likes or follows; no engagement groups or comment bots.
- No buying, selling or sharing accounts outside the team's agreed setup.
- No impersonating creators or brands.
- Label realistic AI content. See AI disclosure.
- Report mistakes fast; delete a wrong post rather than hoping nobody notices.
Access and accounts
Keep an account register: handle, platform, niche, which phone it is on, who may post. Share logins through a team password manager, keep 2FA with the lead, and remove access when someone leaves.
Onboarding a new team member
- Share the written SOP and rules; get a written acknowledgment.
- Give access only to the tools and accounts their role needs.
- Pair them with an experienced member for their first batch.
- Review their first ten clips against the QA checklist together.
- Widen access once their work passes consistently.
Review the SOP itself every month or two. When a mistake happens, fix the process in the document, not just the clip.
Running the posting step with Farmero
Farmero gives the poster one place to work: a web hub for fleet, accounts, content and schedule, and a Mac app that posts through the real apps on the team's iPhones. Each post is confirmed on the profile before it is marked posted; anything unconfirmed is "uncertain" and never auto-retried, and it stops and saves evidence rather than tapping blind when a screen is unexpected. Reports can go to Telegram or ntfy so the whole team sees them. See plans and limits.
FAQ
What roles does a clipping team need?
Sourcing, editing, QA, posting and reporting, with a lead who owns rules and accounts. One person can cover several roles.
Who should do QA on clips?
Ideally someone other than the editor, working from a written checklist.
How should a team share account logins?
Through a team password manager, with 2FA controlled by the lead and access removed when someone leaves.
What should be in a clipping SOP?
Roles, the step-by-step flow, a QA checklist, team rules and an account register.