File names such as final-new and final-really-new become confusing as soon as two people edit the same episode. A useful version name should help someone choose the right file without listening to every export.
Use a stable episode identifier
Keep one episode identifier across the project, review files and notes. Add a version number or date in a consistent format. Then add a short purpose label, such as structure-review, voice-balance or delivery-approved.
For example, episode-014-v03-structure-review tells a recipient more than interview-final-2. The words do not need to describe every individual cut. Put those details in the review note or project history.
Keep the original source names separate from versioned exports. Renaming every source after each editing pass can make project references harder to follow.
Mark approval clearly
Choose one place where the approved delivery version is recorded. It may be a short text note, a project status or an agreed review message. Do not treat the newest file in a folder as automatically approved.
If an urgent correction creates a new delivery file, record what it replaces and why. Keep the previous approved version long enough to compare the correction, according to the project's retention needs.
Before publishing, check the selected file name, duration and opening against the approval note. This is especially useful when a folder contains both a shorter review sample and the full episode.
A small naming scheme works best when everyone uses it. Start with the few labels your team actually needs, test them on one handoff and remove fields that never help anyone make a decision.