Skip to the article
Produce · Handoff

# Prepare the publishing packet

The Publishing tab gathers copy-ready metadata and checks the local production evidence. It helps you hand off confidently; it never uploads media or publishes to a platform.

## Build the packet

Open an episode and choose Publishing. Review the title, description, and comma-separated tags. Description edits save as you work; schedule, file links, render state, and external publication details are maintained in Episode Details.

- Planned release is the intended publication date and time.
- Published externally confirms that publication really happened.
- Published URL is the final complete web address.

Keep planned and actual publication separate. A schedule is not proof that the platform accepted or released the video.

## Use the authoritative readiness checks

Publishing readiness is informational: it does not change status or upload anything. It is the app’s most complete handoff check, and every item shown must be ready. Long-form episodes use seven checks; Shorts omit the separate thumbnail-file requirement:

1. Episode storage and folder are accessible. The configured role is online and the expected episode folder exists.
2. Final export is a readable regular file. A nonempty path string is not enough.
3. Thumbnail is a readable regular file. The file must resolve beneath the managed storage root.
4. Render is marked Complete. Render state is maintained manually in Episode Details.
5. Every required checklist item is complete. Optional checks do not block readiness.
6. Description is present. Review it for final platform formatting and links.
7. Planned release is set. This supplies the intended handoff time.

The Today summary is not the final assessment

Today can flag that a packet appears ready from status, checklist, and stored links. Before handoff, always open the episode’s full Publishing readiness card, which inspects storage and real files.

## Publish outside the app

1. Copy the final metadata. Transfer title, description, and tags to the target platform.
2. Upload the verified final export and thumbnail. Use Finder to reveal the real files when useful.
3. Complete the platform’s own checks. Visibility, audience, rights, captions, end screens, and policy acceptance remain platform responsibilities.
4. Return after publication. Record Published externally and the published URL, then save details.
5. Move to Published. Keep status, external confirmation, and the real platform state aligned.

## About uploads in the calendar

Existing upload records can appear as generated milestones, and an existing item’s title or schedule can be edited. The current pilot does not offer a complete user workflow for creating, deleting, or executing upload jobs. Treat the feature as planning context—not an upload engine.

## What readiness cannot guarantee

A green assessment proves the configured local evidence was present when checked. It cannot validate codec support, copyright claims, platform processing, network delivery, final public visibility, or policy compliance. Keep the platform confirmation step in the workflow.