Build the workflow that turns an approved episode into the supporting assets you actually need. Nothing is default. The user chooses the platform, angle, purpose, and recipient before generating content.
A finished episode can become a YouTube package, a LinkedIn post, a community-building email, a guest share kit, a sponsor recap, a blog post, a clip caption, or a task list. It should not automatically become all of those things every time.
This playbook teaches members to build a selection layer. The system asks what asset they want, what platform it is for, what angle it should take, and whether it is for the audience, the guest, the sponsor, or the internal team.
The goal is to turn one approved episode into a clean distribution package without burying the team in unused drafts.
Asset creation and distribution owns the publishing package. YouTube details, social drafts, publishing tasks, comments, guest courtesy assets, and sponsor-friendly copy live here.
Short clips are not created here. Playbook 02 creates and approves the clip files. This stage decides where those finished clips go and what copy supports them.
Approved episode, transcript, YouTube-ready file, final clips, quotes, CTA, and sponsor notes.
Select platform, asset type, purpose, angle, audience, and recipient.
Generate only the assets needed, then review and edit them.
Publish, schedule, assign, or send a courtesy kit to the guest or sponsor.
If you already have a YouTube or episode table, use that as the asset source. The fields below match what is already available in the current YouTube workflow and can feed the rest of the distribution process.
Working or final episode title. This can feed YouTube, emails, social posts, and guest-share copy.
The source material for descriptions, chapters, key takeaways, quotes, captions, and platform-specific drafts.
The system should know why the asset exists before writing anything. A LinkedIn authority post and a community-building email should not sound the same.
Generated summary material that can become the base for longer publishing assets.
Short internal recap for the team, useful when assigning tasks or explaining why an asset matters.
Keep the record from floating forever as a draft. Use status and publish date to move assets toward done.
The current schema already supports YouTube outputs, social posts, tasks, and comments. Email, image requests, and guest/sponsor delivery can be added as a later table or handled as tasks until that layer is built.
The YouTube table already has the fields needed for a strong publishing package. The playbook should teach members to generate and review these fields from the approved episode and transcript.
Episode description with clear context, guest or sponsor mention when relevant, resources, and CTA.
Timestamped chapter list generated from the transcript and final media.
Stored in title, key points, or source notes depending on your build. Teach users to request different title angles instead of one generic title.
Short headline options for YouTube thumbnail design.
Pinned comment that invites engagement, points to a resource, or highlights a CTA.
Takeaways already exist. Pull quotes can live in source notes until a dedicated quote field or share kit table is added.
Tags are built in. Mentioned resources and CTA can live inside description, source notes, or comments until separate fields are added.
The guest or sponsor does not need to approve the episode here. This is a courtesy delivery workflow: give them the best quotes, links, clips, and platform-specific copy they can use to promote the episode.
YouTube link, podcast link, blog link, or any published URL they can share.
3 to 7 strong quotes from the guest, sponsor, or host that are easy to reuse.
Optional copy for LinkedIn, Instagram, email, newsletter, or community based on where they are active.
Finished clips from Playbook 02 that the guest or sponsor is allowed to share.
Sponsor-approved message, CTA, promo code, or landing page link.
Until there is a dedicated delivery table, create a task called "Send guest/sponsor share kit" and attach the copy in task details or comments.
Send: "Your episode is live. Here are the links, best quotes, clips, and platform-specific captions you can use if you want to share it." Keep it helpful, not demanding.
Distribution breaks when assets are generated but no one knows who is publishing, reviewing, designing, or sending them. Use tasks for ownership and comments for discussion.
This is also where "coming soon" assets can live until dedicated tables exist. An image request or guest delivery can be a task before it becomes its own module.
The tasks table already supports status, priority, task details, deadline, parent ID, parent type, assignee, and workspace. Comments already support content type and content ID.
Publish YouTube episode, schedule LinkedIn post, create thumbnail, send guest kit, or upload short clip.
Connect the task back to the YouTube video, social post, podcast episode, or guest delivery record.
Make the next action owned by a person and a date.
Store the asset instructions, final copy, links, and notes.
Use comments for review notes, approval notes, guest kit edits, and internal discussion.
These prompts should run after the user selects the asset type, platform, angle, and recipient. All prompts stay collapsed by default.
Create a supporting asset from this approved podcast episode.
Episode title: [TITLE]
Transcript or summary: [TRANSCRIPT OR SUMMARY]
Final episode link: [LINK]
Selected platform: [PLATFORM]
Selected asset type: [ASSET TYPE]
Selected purpose: [PURPOSE]
Selected angle: [ANGLE]
Recipient: [AUDIENCE, GUEST, SPONSOR, PARTNER, OR INTERNAL]
Brand voice or style notes: [STYLE NOTES]
CTA or resource links: [CTA OR LINKS]
Create only the requested asset. Do not create a full distribution campaign unless asked.
Return:
- Final draft
- Suggested status
- Any image or clip notes
- Any task that should be created
- Any uncertainty that needs review before publishingCreate a YouTube publishing package from this approved episode.
Episode title: [TITLE]
Transcript: [TRANSCRIPT]
Guest, sponsor, or CTA notes: [NOTES]
Resources mentioned: [RESOURCES]
Audience: [AUDIENCE]
Angle to emphasize: [ANGLE]
Return:
- 10 title ideas in different angles
- YouTube description
- Chapter timestamps
- First comment
- Key takeaways
- Thumbnail title options
- Tags
- Pull quotes
- Internal summary
Keep the package useful and specific to this episode. Avoid generic creator language.Create a courtesy share kit for this podcast guest, sponsor, or partner.
Episode title: [TITLE]
Published links: [LINKS]
Guest or sponsor name: [NAME]
Best transcript moments or quotes: [QUOTES OR TRANSCRIPT]
Approved clip links: [CLIP LINKS]
Platforms they may use: [PLATFORMS]
Sponsor message or required links: [SPONSOR DETAILS]
Return:
- Friendly email letting them know the episode is live
- Best quotes they can reuse
- Platform-specific captions they can copy
- Suggested post copy for each selected platform
- Clip/link list
- Any sponsor-specific wording or link notes
Do not ask them for approval. This is a helpful courtesy package.Create the distribution tasks for these selected podcast assets.
Episode: [EPISODE]
Selected assets: [ASSET LIST]
Publish dates or deadlines: [DATES]
Team members: [TEAM]
Required links or files: [LINKS]
Return one task per action with:
- Task name
- Parent content type
- Owner
- Deadline
- Priority
- Task details
- Done criteria
Only create tasks for the assets selected. Do not invent platforms or extra campaign pieces.Click each item as you confirm it. The goal is a distribution system that creates the right assets, not the most assets.
Final episode and finished clips from Playbook 02 are linked before asset generation
User can choose platform, asset type, purpose, angle, and recipient before generating
YouTube fields store description, chapters, first comment, takeaways, tags, and thumbnail titles
Social post records link back to the episode and store channel, style, final content, status, and publish date
Guest or sponsor share kit is treated as a courtesy delivery, not an approval workflow
Tasks and comments are connected to the asset records so review and publishing work is visible
The social_posts table already supports platform, post type, style, final content, scripts for Reels, image notes, status, publish dates, and parent links back to YouTube or podcast content.
Use one social post record per selected asset. If the user wants LinkedIn from a contrarian angle and an email for community building, those should be two separate assets with different instructions.
A finished episode does not automatically need LinkedIn, Instagram, TikTok, Facebook, and email. The system should generate only what the user asks for.
Use parent_content_type, youtube_id, podcast_id, or another parent field so every social draft links back to the episode.
LinkedIn, Instagram, TikTok, Facebook, X, YouTube Short, newsletter, community, or another selected destination.
Use this for the requested format and angle: community-building, teaching, story, authority, contrarian, recap, clip support, or sponsor-friendly.
The actual post, caption, or email-style draft after review.
Use when distributing a finished short clip and the post needs a voiceover, intro, or scripted caption support.
Use for thumbnail, carousel, quote graphic, or platform-specific visual requests.
Draft, approved, scheduled, published, or sent. Keep distribution visible.