Workflow
The Content Production Workflow: Shipping 60 Videos a Month Without Chaos
22 July 2026 · 12 min read
Volume is not a talent problem. Every brand that publishes sixty assets a month is running a boring, well-documented system; every brand stuck at six is running on goodwill and last-minute panic.
This is the production workflow we use, stage by stage. It works whether you are a two-person team or an agency serving twenty clients, and its main purpose is to make output independent of anyone's motivation on a given Tuesday.
Stage 1 — Plan in cycles, not in posts
Plan a month at a time in one session. Decide pillars, formats and ratio, then fill the calendar with slots rather than finished ideas. A slot says "Tuesday: proof pillar, talking-head, 45 seconds". That is enough for production to proceed and vague enough to stay reactive.
Leave 20% of the month deliberately empty. Reactive content consistently outperforms scheduled content, and a full calendar has nowhere to put it.
Stage 2 — Batch capture
- One filming block per month, two to four hours, covering 60–80% of the month's talking-head content.
- A fixed set-up: same lighting, same framing marks, same audio chain, documented with a photo so it is reproducible.
- Two outfit changes so a month of clips does not look like one day.
- A run sheet ordered by energy: hardest topics first, quick reactive clips last.
- Everything filmed in 4K where possible so vertical reframing does not cost resolution.
- A standing b-roll list captured in the same block — hands, product, workspace, walking shots.
Stage 3 — Intake and file discipline
Most delays are logistics, not editing. Adopt one naming convention and never break it: date, client or brand, format, topic, version. Files land in a single intake folder per shoot with the run sheet attached.
Give every editor a brand kit folder containing fonts, logo variants, caption style presets, colour codes, LUTs, music licences and the graphics template project. If an editor has to ask where the font is, the system has already failed.
Stage 4 — Brief and edit
Every asset gets a one-screen brief: the single idea, the platform, the hook direction, must-keep timestamps, the call to action, and a reference. Anything longer gets skimmed.
Edits move through two states only. Assembly cut is reviewed for structure — is the point clear, is the hook right, does the pacing hold. Fine cut adds captions, graphics, sound design and colour, and is reviewed for detail. Mixing the two states is the most common cause of endless revision loops.
Stage 5 — Review rules that stop the ping-pong
- One reviewer, consolidating everyone's notes. Two reviewers with direct access doubles the rounds.
- Notes are timestamped and specific: "0:14 caption overlaps the logo", never "make it punchier".
- Two rounds included, a third billed. Scarcity produces better notes.
- A 48-hour approval SLA on the client side — an unapproved edit blocks the whole queue.
- Structural notes are inadmissible at fine cut; that decision was made at assembly.
Stage 6 — Publish, and treat the caption as part of the asset
Schedule natively or through one scheduler, with platform-specific copy rather than one caption pasted five times. Post first-comment links where the platform penalises outbound links in the body, add alt text, and keep a consistent posting time so the audience learns your rhythm.
Keep a published-asset log with the hook used, the format, the pillar and the publish date. Without that log, the monthly review has nothing to analyse.
Stage 7 — The monthly review that kills weak formats
Once a month, sit with the log and the analytics and answer four questions. Which formats beat the account average on three-second retention? Which produced saves and shares rather than passive views? Which hooks recurred in the top five? What should we stop making?
Promote winners to templates, retire losers immediately, and change only one variable at a time. Teams that rewrite the whole strategy every month never accumulate enough signal to learn anything; teams that change one variable compound.
The five bottlenecks that break high-volume content
- Approval delay — fix with an SLA and a single decision-maker.
- Missing raw footage — fix with monthly batch capture, not per-post filming.
- Undocumented brand style — fix with a brand kit and template project.
- Reinventing graphics — fix with a component library.
- No measurement loop — fix with a published-asset log and a monthly review.
Frequently asked questions
- How often should we batch film?
- Monthly works for most teams: enough footage for four weeks of publishing without content that feels stale. Weekly filming is usually a symptom of no run sheet rather than a genuine need.
- How many revision rounds are reasonable?
- Two — one on the assembly cut for structure, one on the fine cut for detail. Unlimited rounds are a scoping problem, not a generosity feature.
- How many videos a month does a brand need?
- Consistency matters more than volume, but below roughly eight to twelve assets a month there is rarely enough data to learn what works. Start at a volume you can sustain for a year.
- What tools does this workflow need?
- Very few: shared cloud storage with a naming convention, one project tracker, one scheduler, and a brand kit folder. Systems fail from missing rules, not missing software.