A reliable Descript project organization system makes episodes, clips, transcripts, assets, and revisions easier to find—and makes every team handoff safer. This guide gives you a reusable folder structure, naming convention, status system, and setup checklist for podcasts, video channels, and short-form workflows.
Overview
Descript projects can accumulate quickly. A single episode may produce a recording, transcript, edited master, social clips, captions, thumbnails, show notes, review versions, and exports for several platforms. Without a consistent structure, editors spend time searching for files, collaborators edit the wrong version, and finished assets become difficult to reuse.
The goal is not to create the most elaborate folder system. It is to create a predictable one that answers four questions at a glance:
- What show, series, or client does this project belong to?
- What stage is the work in?
- Which version is current?
- What does the next person need to know?
Use Descript’s current workspace, project, folder, sharing, and permission options as the foundation, but treat the labels and workflow below as your operating system. Interface names and plan capabilities can change, so confirm the available collaboration controls in your workspace before onboarding a team.
A practical top-level structure
For a recurring show or channel, organize projects by series first and production stage second:
SHOW_NAME/
00_Admin_and_Templates/
01_Inbox_Raw_Recordings/
02_In_Progress/
03_Review/
04_Approved_Masters/
05_Social_Clips/
06_Published_Archive/
07_Assets_and_Brand/
If Descript does not support exactly this hierarchy in your workspace, reproduce the logic with the closest available folders, projects, or naming prefixes. The important distinction is between working material, review material, approved masters, and archived outputs.
Use one project as the source of truth
For each episode or long-form video, designate one primary project as the editorial source of truth. Keep the transcript, timeline, scenes, speaker labels, notes, and principal edit there. Create separate projects for social clips or platform-specific versions only when that separation makes review or publishing safer.
Avoid treating exported files as the main record of an edit. An MP4 or WAV file shows the result, but it does not preserve the decisions and context that made the result editable. Link each derivative project or export back to its source project in a handoff note.
Checklist by scenario
Starting a new episode or video
- Create the project from a consistent template. Include recurring scenes, intro and outro placeholders, speaker labels, standard notes, and any regular export reminders.
- Use a stable project name. Add the episode number or publication date, short title, and status. For example:
SHOW_E042_topic-keywords_EDITING. - Add the raw recording before editing. If there are multiple cameras, microphones, or remote guests, label each source clearly.
- Record the editorial brief. Put the working title, target audience, key message, required sections, planned deliverables, and deadline in the project notes or an agreed handoff document.
- Confirm transcript details. Check speaker names, unusual terms, names, products, and technical vocabulary before relying on the transcript for editing or repurposing.
- Move the project to the active-work area. Do not leave production projects mixed with templates, old exports, or unreviewed recordings.
Editing a podcast or video episode
- Keep the main edit in one clearly named project.
- Use scene names or markers for major sections, such as
Cold Open,Interview,Sponsor,Outro, andClip Candidate. - Use comments or notes for decisions that another editor may need to understand.
- Separate editorial notes from final copy. Mark uncertain sections with labels such as
QUESTION,VERIFY, orNEEDS_APPROVAL. - Review the transcript and audio together. Text-based editing is efficient, but the finished cut still needs an audio and visual pass.
- When the edit is ready, duplicate or label the review version rather than overwriting the approved master.
For a deeper audio process, use a dedicated Descript podcast editing and cleanup workflow. If your production includes multiple cameras, keep camera roles and sync decisions documented; the multicam editing workflow is a useful companion.
Creating clips for Shorts, TikTok, or Reels
- Keep the long-form source project name in every clip project or export name.
- Use a clip identifier, such as
C01,C02, or a descriptive hook. - Record the intended format, for example
9x16, and the destination platform only when it affects the edit. - Preserve the original quote or time range in the clip notes so the selection can be traced back to the source.
- Track caption, framing, music, and branding changes as versioned edits rather than replacing files without explanation.
For a repeatable repurposing process, see how to turn long-form recordings into social clips. Keep captions and export settings documented separately so the same clip can be adapted without rebuilding it from scratch.
Handing a project to a collaborator
Before sharing a project, prepare a short handoff note. It should include:
- Project: exact project name and location.
- Current status: editing, internal review, client review, approved, or archived.
- What is complete: for example, transcript cleanup and rough cut.
- What remains: such as audio review, fact-checking, captions, or exports.
- Known issues: missing media, uncertain wording, visual replacement, or approval questions.
- Decision owner: the person who resolves editorial or publishing questions.
- Deliverables: required aspect ratios, file types, captions, thumbnails, or publishing destinations.
- Deadline and priority: include the time zone when collaborators work remotely.
Give collaborators the minimum access needed for their role, then test the share before the deadline. A permission setting is only useful if the recipient can open the project and perform the required task without receiving unnecessary access to unrelated work.
What to double-check
Use a naming convention that sorts naturally
Choose one convention and document it in your template folder. A useful pattern is:
[SHOW]_[EPISODE]_[SHORT-TITLE]_[ASSET]_[VERSION]_[STATUS]
Example:
FIELDNOTES_E042_remote-work_FULL-EDIT_v03_REVIEWFIELDNOTES_E042_remote-work_CLIP-C02_v02_APPROVED
Keep titles short enough to scan. Use leading zeroes for episode numbers if you want them to sort correctly. Avoid vague labels such as final, new, or latest. If you use “final,” pair it with a version and status, such as v04_APPROVED.
Separate version from status
Version answers “which revision is this?” Status answers “what can happen next?” They are different fields. A project can be v03_REVIEW, then v03_CHANGES-REQUESTED, and later v04_APPROVED.
| Status | Meaning | Next action |
|---|---|---|
| INBOX | Received but not assessed | Check media and brief |
| EDITING | Active editorial work | Complete the assigned pass |
| REVIEW | Ready for a defined reviewer | Collect decisions in one place |
| CHANGES-REQUESTED | Review produced actionable revisions | Resolve notes and increment version |
| APPROVED | Ready for export or publishing | Run the delivery checklist |
| ARCHIVED | Complete and retained for reference | Restrict routine editing |
Double-check the handoff boundary
Before moving a project between folders or statuses, confirm that the next owner has the context needed to continue. Check the source media, transcript, brand assets, notes, review comments, and required deliverables. If an asset lives outside Descript, include its location and access instructions rather than assuming the collaborator can find it.
Common mistakes
- Putting every asset in one folder. A single crowded location makes active work and archives difficult to distinguish.
- Creating a new project for every tiny correction. Use clear versions and notes for routine changes; create a separate project when the edit has a different purpose or approval path.
- Using “final” repeatedly. Replace ambiguous labels with numbered versions and explicit statuses.
- Leaving review feedback in scattered channels. Consolidate decisions in the project comments, notes, or one designated review document.
- Renaming projects without recording the change. If a title changes after handoff, update the handoff note and related clip names.
- Mixing source files with exports. Keep masters and delivery files identifiable so an editor does not accidentally revise a compressed platform export.
- Archiving without a retrieval note. Record the episode title, publication date, source project, approved master, and important derivative assets.
- Assuming permissions stay appropriate forever. Review access when collaborators change roles or a project moves from production to archive.
When to revisit
Review your Descript project organization at least twice a year and whenever the workflow changes. A short audit before a new season, channel launch, or major production cycle can prevent months of accumulation.
Revisit the system when you add a collaborator, introduce video to an audio-only show, increase short-form output, change publishing platforms, or begin using new recording, transcription, caption, or AI voice tools. Also check it after Descript changes its workspace, folder, collaboration, permission, or project-sharing options. Confirm that your documented steps still match the controls available on your plan and in your workspace.
Reusable project-setup checklist
- Choose the correct show or channel folder.
- Create the project from the current template.
- Apply the agreed naming convention.
- Add raw recordings and label sources.
- Confirm speakers, transcript terms, and required assets.
- Add the editorial brief and delivery requirements.
- Set the initial status to
INBOXorEDITING. - Record the owner, reviewer, and deadline.
- Link any related clip, thumbnail, caption, or publishing work.
- Before handoff, list completed work, open questions, and next actions.
- After approval, label the master clearly and move it to the approved area.
- After publishing, archive the project with a retrieval note.
Save this checklist in your team template area and test it on the next episode. After one production cycle, remove steps nobody uses, add the questions people repeatedly ask, and keep the structure simple enough that every contributor will follow it.