The Production Management Stack for a Six-Person AI Vertical Drama Team

A six-person team can deliver 70 episodes of AI-native vertical drama at standard professional quality in eight weeks. This is not a theoretical capability. It is the operational reality of production companies that have built the correct infrastructure.

The infrastructure is the point. The same six people without the correct tool stack, communication structure, and workflow discipline produce the same 70 episodes in sixteen weeks with double the revision rate and half the delivery consistency. The people are constant. The stack is the variable.

This post covers the complete production management stack for a six-person AI vertical drama team: the six roles, the tools each role uses, the workflow handoffs between roles, and the communication structure that keeps the production moving at eight-week delivery pace without coordination failures.

The Six Roles

Role 1: Creative Director. Owns the brief, the arc map, the quality standard, and the delivery relationship with the commissioning party. Reviews and approves every arc map, generation sample, and delivery package. The creative director is the single accountable party for all production decisions. In a six-person team, the creative director also handles the commissioning party relationship and the platform acquisition relationship.

Role 2: Production Writer. Produces all 70 episode scripts from the approved arc map and the direction brief standard. In a six-person team, one production writer handles the full 70-episode script set across a two-week scripting window.

Role 3 and Role 4: Generation Operators (two operators). Produce the visual content for all 70 episodes using the approved character reference pack, the style guide, and the direction brief for each episode batch. Two generation operators working in parallel sessions produce the full 70-episode visual content across a four-week generation window.

Role 5: Post-Production Specialist. Handles audio post-production, colour grading, subtitle generation, and delivery package assembly. Receives approved generation outputs from the creative director's batch reviews and processes them through the post-production pipeline.

Role 6: Production Coordinator. Manages the production schedule, the generation log documentation, the delivery package tracking, and the communication between all other roles. The production coordinator is the operational backbone that prevents coordination failures from consuming creative director time.

The Tool Stack by Role

Creative Director tools:

Project management: Notion for the arc map document, the brief, and the quality review log. Notion's database structure allows the creative director to track each episode's status — scripted, generated, approved, in post, delivered — across the full 70-episode run without a dedicated production software subscription.

Quality review: Consumer phone for generation sample review and delivery quality validation. The creative director's quality review is always conducted on the delivery device, not on a production monitor.

Communication: Loom for async video review notes on generation samples and delivery packages. Loom allows the creative director to record a screen-share walkthrough of specific quality issues rather than writing text descriptions that generation operators must interpret.

Production Writer tools:

Script development: Google Docs for the 70-episode script set. The timestamp skeleton format — hook, escalation, spike, button cut positions — is enforced through a Google Docs template that the production writer completes for each episode.

Reference: The arc map document in Notion. The production writer has read-only access to the arc map and references it at every script revision to confirm structural compliance.

Generation Operator tools:

Primary generation: Seedance 2.5 API for dialogue close-up scenes. Kling 3.0 consumer interface for physical action and camera movement scenes. Veo 3.1 API for hero shots at the paywall episode and hook scene positions.

Character reference management: A shared cloud storage folder containing the approved character reference pack images organised by character and arc position. Every operator on the production accesses the same reference folder. No local reference storage.

Generation log: A shared Google Sheet with one row per generation output. Columns: episode number, scene type, tool used, model version, prompt hash, reference images used, quality criteria result for each of the five markers, revision count, approval status. The production coordinator owns the generation log structure. The generation operators populate it.

ComfyUI: For character reference pack build sessions and style guide verification outputs. Not used for primary dialogue close-up generation — Seedance 2.5 handles that — but used for the pre-production reference image build that feeds into the Seedance reference pack.

Post-Production Specialist tools:

Audio post-production: DaVinci Resolve for the audio mix. Phone speaker calibration as the evaluation standard for every final mix decision.

Colour grading: DaVinci Resolve colour panel. Phone display calibration check for every approved colour grade.

Subtitle generation: Subtitle Edit for SRT file production and timing verification. Phone display legibility check for every subtitle file.

Delivery package: A shared cloud storage folder with a defined file structure that the post-production specialist populates as episodes clear quality review. The production coordinator monitors the delivery folder population against the delivery timeline.

Production Coordinator tools:

Project tracking: Notion for the production schedule, role assignments, and delivery timeline. The production coordinator maintains the master production calendar and sends daily status updates to the creative director.

Generation log ownership: Google Sheets for the generation log that operators populate and the production coordinator audits for documentation gaps.

File management: Cloud storage (Google Drive or Dropbox) for the shared reference folder, the script set, the generation output folder, and the delivery package folder. The production coordinator sets up the folder structure at pre-production week one and maintains the access permissions throughout the production.

Communication coordination: Slack for team communication. One channel per production, with specific threads for generation batch submissions, quality review feedback, and delivery progress updates.

The Workflow Handoffs

The workflow handoffs are the points where one role's output becomes another role's input. Handoff failures are the most common source of production timeline extensions in AI vertical drama production. The production coordinator's primary function is preventing handoff failures by confirming that each handoff is complete before the receiving role begins work.

Handoff 1: Arc map to scripting.

The creative director completes and approves the arc map. The production coordinator creates a shared access link to the arc map document in Notion and confirms with the production writer that the arc map is accessible and complete. The production writer begins scripting only after this confirmation. Timeline: day 8 of week 2.

Handoff 2: Scripts to generation.

The production writer completes episode scripts in batches of 15. The production coordinator confirms each batch is in the script folder with the correct file naming convention before notifying the generation operators that the batch is ready. The generation operators begin generation for each batch only after the production coordinator's batch-ready notification. Timeline: first batch ready at the end of week 2, subsequent batches every three days through week 4.

Handoff 3: Generation outputs to creative director review.

The generation operators submit each generation session's outputs by updating the generation log with the output files and quality criteria results. The production coordinator confirms the log is complete for the session before notifying the creative director that a review batch is ready. The creative director reviews the batch and records revision notes in the log or approves each output. Timeline: every two days from week 3 through week 6.

Handoff 4: Approved generation to post-production.

The creative director's approval in the generation log triggers the production coordinator's notification to the post-production specialist that an episode batch is approved and ready for post-production processing. The post-production specialist processes each approved batch in sequence. Timeline: beginning week 4, running through week 7.

Handoff 5: Post-production outputs to delivery folder.

The post-production specialist completes each episode's audio, colour grade, and subtitle processing and moves the complete episode files to the delivery folder with the correct naming convention. The production coordinator audits the delivery folder daily against the expected episode count and notifies the creative director of any episodes that have not cleared post-production on schedule. Timeline: week 5 through week 8.

The Communication Structure

The communication structure prevents the six-person team from losing coordination time to status uncertainty — not knowing where a production element is in the workflow without having to ask.

The daily status update. The production coordinator sends a daily Slack message in the production channel at the start of each production day. Format: production day number, scripts completed versus total, generation outputs submitted versus total, generation outputs approved versus total, episodes in post-production versus total, episodes in delivery folder versus total, and any blockers. The daily status update takes five minutes to write and prevents the creative director from spending time on status inquiries throughout the day.

The batch-ready notification. The production coordinator sends a batch-ready notification in Slack whenever a handoff has been completed. Format: the handoff type, the episode batch numbers, and the action the receiving role needs to take. No ambiguity about what is ready, who needs to act, and what they need to do.

The revision log thread. For every creative director revision note, the production coordinator creates a Slack thread in the generation log channel with the revision instruction, the episode number, and the generation operator assigned to execute it. The generation operator confirms receipt and posts the revised output in the same thread. The creative director approves or sends further notes in the thread. Every revision has a complete record in a single thread.

The weekly production meeting. A 30-minute Zoom call every Monday morning covering the week's planned generation batches, any quality issues from the prior week's batch reviews, and any delivery timeline risks the production coordinator has identified. The creative director, production coordinator, and both generation operators attend. The production writer and post-production specialist are notified of relevant decisions by the production coordinator in the production channel.

What Goes Wrong Without the Stack

The six-person team without this tool stack and communication structure produces the same 70 episodes at a higher revision rate, a longer timeline, and lower character consistency, because:

Generation log gaps mean the creative director cannot track which outputs have been reviewed and which have not. The review process becomes reactive rather than systematic.

Reference folder access without version control means generation operators in different sessions may use different reference images for the same character, producing visible drift between session one and session eight.

Handoffs without production coordinator confirmation mean the receiving role sometimes begins work before the preceding handoff is complete, producing downstream quality issues that require backtracking.

Communication without batch-ready notifications means the receiving role does not know when to begin work, which creates idle time that extends the production timeline without any production activity in the gap.

The tool stack and communication structure are the production management decisions that determine whether an eight-week delivery commitment is achievable or aspirational.

Axis AI Studios Perspective

The production management stack described in this post is the operational infrastructure that makes Axis AI Studios' eight-week delivery commitment reliable rather than exceptional. The tools are standard. The discipline is the investment. Every production coordinator notification, every generation log entry, and every batch-ready handoff is five minutes of administrative discipline that prevents two hours of revision, backtracking, or timeline extension.

For generators, editors, and production coordinators who want to work in AI vertical drama production at this operational standard, the role descriptions and tool requirements in this post are the starting point for understanding what professional production operations look like from the inside.

For businesses commissioning AI-native vertical drama who want to confirm their production partner operates with documented production management infrastructure, the due diligence checklist covers this question directly: can the production partner describe their production schedule tracking, generation log documentation, and handoff confirmation process?

Reach out at business@axisaistudios.com for commissioning conversations or production team applications.

FAQ

Does a Six-Person Team Scale to Multiple Simultaneous Productions?

A six-person team can manage two simultaneous productions if the generation operators work on separate productions in separate sessions and the production coordinator maintains separate project tracking channels for each production. The creative director is typically the bottleneck at two simultaneous productions — the batch review and quality approval work for two 70-episode productions running simultaneously requires more review time than most creative directors can manage without quality degradation. The correct scaling approach is adding a second creative director rather than a second set of operators.

What Happens When a Team Member Is Unavailable Mid-Production?

The generation log documentation and the reference folder version control are the tools that enable another operator to continue any production session from exactly the point a prior operator left off. If a generation operator becomes unavailable, the production coordinator locates the most recent session's generation log and the approved reference frame, and a replacement operator loads the documented configuration and continues from the prior session. Without the generation log documentation, this handoff requires a session-open consistency check and likely produces character drift in the replacement operator's first batch.

Can the Stack Be Simplified for a Smaller Team?

Yes, with trade-offs. A four-person team — creative director, production writer, one generation operator, and production coordinator — can produce a 70-episode series in twelve weeks rather than eight by extending the generation window. The post-production role is covered by either the creative director or the production coordinator at reduced efficiency. The two-operator generation window that produces eight-week delivery becomes a one-operator window that extends to twelve. The stack simplifies. The timeline extends proportionately.

Further Reading

For the agentic AI workflows that automate portions of the production management described in this post, the guide to agentic AI workflows for vertical drama covers the orchestrator-worker architecture that automates scene routing, quality review flagging, and session scheduling.

For the generation log discipline that the production coordinator oversees in this post, the guide to the generation operator's role in AI-native vertical drama covers the documentation requirements and quality review process that the generation log captures.

For the eight-week production timeline that the stack in this post supports, the guide to how to commission your first AI micro-drama series in 8 weeks covers the week-by-week production calendar and approval gate structure.