Two shows can turn into twice the chaos. A weekly interview series, a short news brief, and a monthly deep dive soon mean scattered scripts, uncertain voice assignments, mismatched export settings, and too much information held in your head.
Vois gives each show a project where its scripts, speaker assignments, generated takes, timeline edits, mastering choices, and exports remain connected. That does not make a network automatic, but it does give production decisions an address.
When every show is a flat list of files, you end up reconstructing the organization yourself in folders and spreadsheets. A Vois project keeps a show's working material in one place, so a script or voice revision can be reviewed in the same context as the episode it changes.
One Project Per Show
The starting rule is simple: give each show its own project.
Your interview series can have one project. Your daily news brief can have another. Each project keeps the scripts, speaker assignments, timeline work, mastering choice, and export history for that particular show.
When you open a project, you see the decisions that belong to that series. Create a new show only when you are ready to establish its own cast, editorial workflow, and release process.
Set the recurring cast before the next episode
Every podcast has recurring roles. Define the host, narrator, and any repeat contributors inside the show project, then assign each role an approved voice. That gives the script editor a stable cast for every new episode.
For an interview show:
- Create the project, for example, "The Builder's Corner."
- Add a Host speaker and audition a warm, conversational voice from the voice library.
- Add a Guest speaker and choose a contrasting voice when the show uses scripted guest dialogue.
- Generate a short exchange and approve the pair before you make it part of the series.
In each script, insert the Host and Guest speaker pills and keep the voice choices attached to those roles. If a project uses a cloned voice, use it only with the speaker's permission and store the approval with the production record.
Episodes as Scripts: Keep It Organized
Inside each project, individual episodes are stored as scripts. Name them so another editor can identify the episode and its status, such as "EP001: Interview with Sarah Chen" or "EP002: The State of Podcasting." The project becomes the place to see what is drafted, ready for review, approved, and exported.
Keep a season together while it is useful, and start a new project when the show needs a new cast, new delivery requirements, or a cleaner editorial boundary. The goal is not a perfect folder taxonomy. It is a clear history for the work you will revisit.
Consistent Mastering Per Show
Choose the mastering and export preset that fits the destination for each project, then confirm the distributor's current delivery requirements before release. An Apple Podcasts show and a Spotify-first show may need different loudness targets, so keeping the intended preset with the project reduces a common last-minute mistake. See the export presets guide for the workflow.
Batch the preparation, not the approval
Batching works well when it removes repeated setup without lowering the quality bar:
Write. Draft related episodes together while the editorial context is fresh.
Generate. Use the project's approved speaker assignments to create first takes for the batch.
Edit. Review each episode on the Vois timeline. Check dialogue, trim unwanted space, set intentional crossfades, and regenerate any line that does not match the script or voice standard.
Export. Apply the project's delivery preset only after the episode has cleared its editorial and audio review. Listen to the exported file before it leaves the project.
This keeps the efficient part of a batch workflow, while preserving a release decision for every episode.
Why the project is the production record
Switching between tools can make it difficult to answer basic questions: Which voice did this show approve? Which script produced this file? Was this export mastered for the intended platform?
In Vois, the project holds the script, cast, generated clips, timeline review, mastering choice, and export together. A flat subscription also means a necessary regeneration does not require a separate character-cost calculation. The production decision can stay creative rather than financial.
As the network grows, use a clear project name such as "ClientName: ShowName." Keep client permissions, speaker approvals, and release notes with the project. Local processing also means scripts stay on the machine where the work is being done.
A Complete Multi-Show Setup Walkthrough
Say you are launching two shows this quarter:
"Product Thinking," weekly interviews. Create a project. Add the recurring host and guest roles, audition the pair in a short dialogue, and set the destination-specific mastering choice after you confirm the distributor requirements. Draft the first few episode scripts in the same project.
"Five-Minute Founder," short founder briefings. Create a separate project. Assign an energetic narrator role, test the intro against a real briefing, and set the approved export choice for that show.
Then work in a measured batch: draft the scripts, generate the first takes, review each episode on the timeline, and export only the approved versions. The project system makes the repeatable parts easier without pretending that every episode needs the same editorial attention.
The Compound Effect of Good Organization
The real payoff is not one episode. It is the tenth or fiftieth, when an editor can still find the approved cast, script, pacing decision, and delivery choice without reconstructing the show from memory.
Vois keeps those production decisions close to the creative work. Set up a dedicated show project, build the first episode with the podcasting workflow, and Get started when you are ready to give the next show the same clarity.
The Vois Team