Workspace Setup: File Organization & Naming Conventions

Why File Organization Matters in a Professional Workflow

In a graphic and digital media studio, the files you create are deliverables that belong to a client and must be handed off to teammates, vendors, or future contractors. A folder structure built at random—or a file named "final_FINAL_v3_USE THIS ONE.psd"—creates confusion, delays, and costly errors. Professional agencies enforce strict organization rules so that any team member can open a project cold and find exactly what they need in under a minute. This lesson teaches you to build that discipline from day one.

The Standard Folder Hierarchy

A reliable agency folder structure follows a logical drill-down from broad to specific. The most common five-level model is:

```

Client

└── Campaign

└── Platform

└── Format

└── Version

```

Example:

```

AcmeCo

└── SummerSale2025

└── Instagram

└── Story_1080x1920

└── v01

```

Each level answers one question: Who? (Client), What project? (Campaign), Where does it run? (Platform), What size or type? (Format), How far along is it? (Version).

Subfolders within the version level typically include:

• WIP (work in progress) — editable source files (.ai, .psd, .indd)
• Exports — flattened or compressed output files (.jpg, .png, .mp4)
• Assets — raw images, fonts, logos, and supplied client material
• Links — any placed files that must travel with the source document

Never mix source files with exports. A client approves a JPEG; the editor needs the PSD. Keeping them separate eliminates accidental overwrites.

The Standard Naming Convention

A filename must be readable by a human and sortable by a computer. The class convention for this program is:

```

YYYYMMDD_ClientCode_Platform_Format_v##

```

Field-by-field breakdown:

| Field | Rule | Example |

|---|---|---|

| YYYYMMDD | ISO 8601 date — creation or delivery date | 20250615 |

| ClientCode | 4–6 uppercase letters, no spaces | ACMCO |

| Platform | Abbreviated platform name | IG, FB, TT, LI, YT |

| Format | Abbreviated size or asset type | Story, Feed, Banner, Thumb |

| v## | Two-digit zero-padded version number | v01, v02, v10 |

Full example: `20250615_ACMCO_IG_Story_v01.psd`

Rules to follow every time:

• Use underscores (`_`) as separators, never spaces or hyphens as primary separators.
• Keep all characters lowercase except the ClientCode, which is uppercase.
• Never use special characters: no `/ \ : * ? " < > |`.
• Extensions are lowercase and never altered manually (`.psd`, not `.PSD`).

Consistency is non-negotiable. One mis-capitalized field breaks alphabetical sorting and can cause automated scripts to fail.

Using Adobe Bridge for File Management

Adobe Bridge (included with Creative Cloud) is a dedicated media browser that lets you view, rename, sort, and batch-process files without leaving the Adobe ecosystem. Key features for this workflow:

• Batch Rename (Tools › Batch Rename): rename dozens of files at once using string substitution, date fields, and sequence numbers. Saves hours compared to renaming one file at a time.
• Metadata panel: view EXIF data, add keywords, and track copyright—useful when logging received client assets.
• Filter panel: sort by file type, date, rating, or label so you can isolate all v01 PSDs instantly.
• Collections: create virtual groups of files from multiple folders without moving originals.

Practice the Batch Rename tool during the activity portion of this lesson. Always run a test rename on a copy of your files first, then verify the result before touching originals.

Writing an Asset Library SOP

A Standard Operating Procedure (SOP) documents a repeatable process in plain language so that a new hire can follow it without additional explanation. A one-page Asset Library SOP should cover:

1. Purpose — why this system exists and who it applies to.

2. Folder structure diagram — a visual or text tree showing every level.

3. Naming convention table — fields, rules, and an annotated example.

4. Version control rules — when to increment the version number and who approves the change.

5. Archiving policy — when a project is complete, where it goes and who has access.

Write for a reader who knows design software but has never seen your specific system. Avoid jargon, define abbreviations on first use, and include at least one worked example filename.

Workspace Safety and Data Integrity

File organization is a form of data safety. Follow these practices:

• Never rename or move files while they are open in Illustrator, Photoshop, or InDesign. Doing so breaks live links and can corrupt placed files.
• Back up before batch renaming. Copy the source folder to a backup location first. Bridge's Batch Rename cannot be undone with Ctrl+Z once applied.
• Do not store working files only on a local drive. Use a network share or cloud backup (Creative Cloud Libraries, Google Drive, or equivalent) so work is not lost if hardware fails.
• Verify write permissions before placing a new folder on a shared server. Creating folders in the wrong directory can overwrite another team's work.
• Log in as yourself, not a shared account, so file metadata records the correct creator.

These habits protect both your work and your client's assets.