FARMBuild a TikTok content calendar across accounts
Plan a six-video TikTok batch across two accounts, assign hooks and production roles, budget time and hand approved videos to the PhoneFarm publisher.
Build the calendar around a production batch and a decision, not a grid of unrelated posting ideas. Choose the format, assign its variants, reserve time to make them, and schedule the review that determines the next batch.
This hypothetical week markets Example Speaking, a recording-and-replay app. It uses two existing accounts: one teaches interview practice and the other teaches everyday spoken English. Six videos test three opening approaches, with a distinct demonstration for each account. The times and workload are planning choices, not platform requirements.
Start with content pillars that answer different questions
Choose recurring subjects that can generate usable scripts:
| Account | Customer problem | Repeatable content pillar | First demonstration |
|---|---|---|---|
| ACC-SPK-01, interview practice | A written answer sounds unnatural aloud | One answer, one improvement | Shorten “Tell me about yourself” |
| ACC-SPK-02, everyday speaking | A simple request becomes a long explanation | Say it more clearly | Ask to change an appointment |
Both use first attempt → replay → shorter sentence → retry. That common structure reduces production work while each account keeps a relevant purpose. Add accounts when you have a clear audience and enough production capacity to serve it.
Build an idea backlog before choosing dates
Start with the campaign brief. The first batch holds the demonstration and offer steady within each account while testing the opening.
| Hook | Interview account opening | Everyday-speaking opening |
|---|---|---|
| A: recognize the problem | “Your interview answer sounds better in your head.” | “That simple request sounded simpler in your head.” |
| B: challenge the approach | “Stop rehearsing the whole interview. Fix one answer first.” | “Stop explaining everything. Practice the request first.” |
| C: show the contrast | “Read it. Say it. Different answer?” | “A paragraph—or one clear request?” |
Keep later ideas in the backlog: another interview question, a pronunciation close-up, a genuine comment response and a slideshow version. Mixing all four into the opening test would make the batch harder to interpret.
Batch by production task, then publish by audience need
Use one small production packet:
- Creative lead: selects the two customer problems, approves the three hooks and supplies the exact ending.
- Presenter/editor: records two demonstrations and six openings; exports the assigned versions using one visual template.
- Publisher: receives approved files, captions, phone assignments and target times; returns verified post links.
The packet contains the script, original footage, app screen recording, text style, caption, destination and an accepted example. Lock the body during the hook test. Collect proposed improvements for the next batch instead of letting every editor change the experiment independently.
Calculate capacity before setting a posting cadence
Here is a completed estimate for the six-video batch:
| Work | Planned time |
|---|---|
| Research and approve the brief | 40 minutes |
| Script two bodies and six openings | 40 minutes |
| Record demonstrations, screen captures and openings | 60 minutes |
| Edit two masters and six exports | 90 minutes |
| Review the six exports and captions | 30 minutes |
| Publish, verify and log six posts | 60 minutes |
| Read responses and review results | 40 minutes |
| Total | 360 minutes: six hours |
Reserve another hour for revisions or an operational problem. These are estimates to replace with your first batch's actual times. If editing takes twice as long, simplify the template or reduce the batch before adding phones. If finished work waits for device time, investigate publishing capacity.
A worked first-week calendar
All publishing targets below use America/New_York. Both accounts receive each opening style in a different order. This reduces one obvious ordering bias; interpret results within each account before comparing their different audiences.
| Day | Production or publishing task | Account and asset | Follow-up |
|---|---|---|---|
| Monday | Research, script and record the batch | Two demonstration masters, six openings | Approve footage before editing |
| Tuesday | Edit, review and upload all six exports | SPK-01 interview; SPK-02 everyday | Match each filename to its caption and phone |
| Wednesday, 12:00 | Publish first variants | ACC-SPK-01: SPK-01_hook-a_v1; ACC-SPK-02: SPK-02_hook-c_v1 | Verify each post; review genuine questions later that day |
| Thursday, 12:00 | Publish second variants | ACC-SPK-01: SPK-01_hook-b_v1; ACC-SPK-02: SPK-02_hook-a_v1 | Verify and log; capture Wednesday's first-day metrics |
| Friday, 12:00 | Publish third variants | ACC-SPK-01: SPK-01_hook-c_v1; ACC-SPK-02: SPK-02_hook-b_v1 | Verify and log; collect each post's 48-hour result when due |
| Following Monday | Review the completed comparison | All six posts at their recorded 48-hour age | Choose next interview and everyday-speaking batches |
Arrange Friday, Saturday and Sunday measurement checks, or use your reporting system's available history to collect the same age reliably. If a check occurs late, record the actual age. The calendar is a manual production plan; PhoneFarm's Run now flow starts work when the operator submits it.
Hand the finished work to the PhoneFarm publisher
A complete handoff row looks like this:
| Field | Completed example |
|---|---|
| Asset | SPK-01_hook-b_v1.mp4, reviewed in Videos |
| Phone and account | PF-SPK-01 → ACC-SPK-01; confirm the actual TikTok handle |
| Caption | “One question. One recording. One sentence to improve. Practice it in Example Speaking.” |
| Product route | Approved app/profile destination matching the video |
| Timing | Thursday, 12:00 America/New_York; operator uses Run now |
| Settings | Approved visibility and applicable disclosure choices |
| Return record | Actual publication time, post link, job reference and any exception |
Follow the verified first-post workflow:
- Open the intended phone in live control and confirm the account.
- In Videos, preview and select the approved export.
- Choose TikTok, Run now, the final caption and intended phone; inspect readiness and assignments.
- Submit once, then follow Publish jobs and Proof reports.
- Open the actual profile and confirm the post before marking the row published.
For multiple selections, inspect the displayed video-to-phone mapping. Selecting several videos and phones does not mean every file is sent to every account. Resolve an uncertain result before retrying.
Review the calendar as a learning system
Finish with a production decision: repeat a promising opening on a new question, improve an unclear demonstration, make a real comment response or stop an unproductive execution. Keep one slot available for a useful audience question instead of filling every future date in advance.
Compare available watch measures and product interest alongside production time using the experiment guide. Retain the original master, then update the next brief from what the batch taught you. The downloadable calendar contains this six-post example and blank rows for your next batch.