SOP-001

Unified Naming Conventions

Moon Street Films — Post-Production Operations

1. Purpose & Scope

This SOP defines naming conventions for every file, folder, sequence, and export in Moon Street Films post-production projects. The rules apply to everyone on every project with no exceptions.

Consistent naming eliminates the need to ask what anything means. Any editor — new or returning — should be able to navigate a drive without context. It also makes search reliable, archives clean, and handoffs to color, sound, VFX, and clients unambiguous.

Companion documents: Client Code Registry and Context Code Registry are referenced throughout. They must be updated whenever a new code is introduced.

2. Core Rules

These apply to every filename and folder name without exception.

1. No spaces. Ever. In any filename, folder name, or sequence name.
2. _ is the only separator. It separates every token in a name. No dashes, no dots, no slashes in names.
3. No special characters. Only alphanumeric characters and _ are permitted.
4. No status suffixes in filenames. Words like FINAL, FINAL_FINAL, APPROVED, or LOCKED are prohibited. Version status lives in project management software.
5. Never delete. Move unwanted items to zTRASH instead. See Section 6.
6. Dates always use YYMMDD format. Never MMDD, YYYY-MM-DD, or any other format.
7. Version numbers are always two digits: v01, v02 — not v1 or V01.
8. Codes must match the registry. Confirm a code exists before using it. Add it first if it doesn't.

3. Casing Hierarchy

Casing communicates hierarchy — it tells you where in the system you are at a glance.

4. Naming Formulas

Tokens in brackets are required. Tokens marked [Token?] are conditional. The order is fixed — do not rearrange.

4.1   Folders

Top-level (project root)

Sub-level

4.2   Editorial Cut Sequences

DelivVersion is only included when the project has more than one distinct deliverable version.

4.3   Dailies Sequences

4.4   Stringout Sequences

Context is descriptive PascalCase. Use underscores to separate multiple words within the context token.

4.5   Turnover Sequences

Context uses ALL CAPS if it refers to a cut code (e.g., QT), or PascalCase if it is a descriptive label.

4.6   Delivery Sequences

Codec and resolution are part of the sequence name since this sequence is the direct source for master exports.

4.7   Episodic Sequences

For long-form or series work. The EP token sits immediately after the project code, before the cut type.

4.8   Exported Files

An exported file always shares its name with the source sequence. When exporting multiple formats from the same sequence, codec and resolution are appended.

4.9   Shoot Day Folders

4.10   VFX / GFX Files

Include shot ID, short description, and version number. Version number is always present, starting at v01.

4.11   Documents & Reports

5. Code Component Definitions

5.1   Client Code   [CLIENTCODE]

• 3–4 uppercase characters only. No numbers or underscores.
• Abbreviated from the client name in a way that is logical and unambiguous.
• Once assigned, a code is permanent. It does not change if the client rebrands.
• All codes must exist in the Client Code Registry (REF-001) before use.

5.2   Project Code   [ProjectCode]

• PascalCase, descriptive, no spaces.
• Commercial: short descriptive title of the campaign or spot series (e.g., BrevillePlus, GreenSauce).
• Long-form / series: show or series title (e.g., DocSeries, BrandFilm).
• The project code does not change across the life of the project, even as deliverable versions multiply.

5.3   Deliverable Version   [DelivVersion]

Only used when a project produces multiple distinct output versions. Omit if there is only one deliverable.

Additional codes are maintained in the Context Code Registry (REF-002).

5.4   Cut Type Codes   [CutCode]

ALL CAPS + two-digit number. Increments with each new cut of that type within a project. Resets to 01 on a new project.

5.5   Turnover Department Codes   [ToDEPT / FromDEPT]

5.6   Initials   [Initials]

• 2–3 uppercase letters. Always the editor’s or AE’s initials.
• If two people share the same two-letter initials, both add a third letter to differentiate (e.g., JJA vs. JJO).

5.7   Date Format   [YYMMDD]

• Always YYMMDD. No dashes, no slashes, no other format.
• February 11, 2026 = 260211    March 28, 2026 = 260328
• This format sorts chronologically in any file browser without special tools.

5.8   Version Numbers   [v##]

• Always v + two digits: v01, v02, v03.
• Never: v1, V01, FINAL, APPROVED.
• Applies to VFX/GFX files and versioned documents. Sequence cuts use cut type codes (DC01, DC02), not v##.

5.9   Codec & Resolution

6. The zTRASH Convention

Nothing gets deleted. Everything unwanted moves to zTRASH. The z prefix sorts these folders to the bottom of any directory listing automatically.

7. When In Doubt

1. If a client code doesn’t exist in REF-001, create it and add it before using it.
2. If a context code doesn’t exist in REF-002, create it and add it before using it.
3. If unsure about casing: project-root level = ALL CAPS, everything below = PascalCase.
4. If you inherit a non-compliant project, do not rename mid-project. Document the deviation and standardize on the next project.
5. Never use spaces as a placeholder while figuring out the name.
6. If a sequence and its export file don’t share the same name, something went wrong. Fix it before delivery.

8. Quick Reference

Moon Street Films — Post-Production Operations — SOP-001