Short answer: nothing gets posted until the model has approved the clip, the caption and the accounts it goes to. Keep separate folders for raw, edited, approved and posted files, record every approval with a name and date, and let only the operator move files into the posting queue. It protects the creator's control over their own image and gives the agency a record if anything is questioned.
The workflow
| Stage | Who | Output | Moves to |
|---|---|---|---|
| Brief | Content lead | One-line idea, platform, account | Creator |
| Film | Creator | Raw clips | Editor |
| Edit | Editor | Platform versions, draft captions | Review |
| Compliance review | Compliance owner | SFW check, AI label check, rights check | Creator |
| Approval | Creator | Approved or change requested | Operator |
| Queue | Operator | Scheduled posts | Posted |
| Record | Operator | Post status per account | Archive |
The compliance review sits before the creator sees the edit so the creator is never asked to approve something that would break platform rules. What to check is in suggestive-content restrictions and AI content disclosure.
Folder structure
/Models
/Model-A
/01-raw
/02-edited
/03-approved
/2026-W38
/04-posted
/approvals.csv
Rules that keep it clean:
- Only approved files live in
03-approved, grouped by week. - The operator queues only from
03-approved. - After posting, files move to
04-posted, never back. - File names carry the clip ID, platform and account:
A-0412_tt-main.mp4.
The approval record
| Clip ID | Accounts | Caption (final) | AI used | Approved by | Date | Notes |
|---|---|---|---|---|---|---|
| A-0412 | tt-main, ig, yt | "Morning routine, part 2" | No | Model A | 2026-09-15 | — |
| A-0413 | tt-fit | "Three warm-up drills" | Captions only | Model A | 2026-09-15 | — |
Keep it as a shared sheet or a CSV next to the folders. Approval by message is fine if it is copied into the record.
Who posts what
- One operator per model or per phone, named in the phone setup sheet.
- Captions are final at approval. Operators do not rewrite them.
- Withdrawals win. If the creator withdraws approval, the post comes out of the queue, or down if it is live.
- Rights. Only content the creator owns or has permission to use, including anyone else who appears in it.
The approval step also feeds the weekly plan in the content calendar.
Approvals also need a way to say no. Give the creator a simple way to reject a clip or ask for changes, and record the reason. Over time those notes show what the creator is and is not comfortable with, which makes briefs better and saves filming time. Treat a rejected clip as closed: it does not come back into the queue unless the creator approves a new version. Keep old approval records for as long as the posts they cover are live, and hand them over if the creator leaves.
Approval and Farmero
Farmero only posts what is in its queue, and publishing is gated by the user's switch, including posts queued through its MCP server. Each account's post is its own editable card, so a caption change for one account does not touch the others, and per-post settings like who can view and comments are applied on the phone and read back. See posting.
FAQ
Does the model need to approve every single post?
That is the safest default. Some creators pre-approve a format; if so, write that down and review it regularly.
What if the model wants a change after posting?
Edit or remove the post on the account and log it. Honor removal requests promptly.
Who should hold the approval record?
The agency and the creator both should be able to see it.
Can an AI assistant queue posts?
It can queue them through an MCP server, but a person should still approve the content and control publishing.