Scripts That Depend on Consistent Names

Render queues, watch folders, batch exports and small scripts all read file names to decide what to do. A script can't ask what you meant. If the name doesn't follow the pattern, the file gets skipped, misfiled or overwritten. The fix is less about the script and more about how the studio runs around it: who owns the pattern, where files go in and come out, and how people check things each week. The examples use a fictional client, ACM.

Who owns what

• Naming lead: owns the written naming pattern. Any change to the pattern goes through them, because it can break scripts.

• Script owner: the person who wrote or maintains each script. Keeps a one-line description of what it reads, what it does and where it writes.

• Project owner: sets up the project folder from the template and makes sure files going into watch folders are ready.

• Everyone else: names files when they save them and doesn't drop files into watch folders by hand unless that's the agreed step.

Keep a short list of scripts in one place, with each one's owner, input folder and output folder.

Folder and role names are examples; adapt them to your team.

From intake to delivery

1. Intake. Client files land in 00_In/. People rename copies into the studio pattern before a script touches them, and keep the originals as they arrived.

2. Work. Working files are named with the pattern from the first save, so later steps can read them.

3. Queue. When a file is ready, a person moves it into the script's input folder, for example _queue/render/. Only ready files go there.

4. Process. The script reads the name, does its job and writes results to its output folder, such as 03_Renders/. It doesn't write into the source folder.

5. Check. A person looks at the output and the script's log before anything goes further.

6. Deliver. Approved results go into 04_Out/, renamed to the client's spec if there is one.

Handoff steps

When a script or its folders change hands:

1. Write down what the script expects: the name pattern, the input folder and the output folder.

2. Run it once on a copy of a real project with the new owner watching.

3. Show where the log lives and how to undo a run.

4. Update the script list with the new owner.

One example of why the pattern matters:

Weekly hygiene routine

A short weekly check, done by the project or script owner:

• Look at each input folder. Anything sitting there for days probably failed or wasn't ready.

• Read the script logs for skipped files, and fix their names.

• Look for download duplicates like (1) and mixed versions like v3 next to v03.

• Confirm outputs went to the output folder, not next to the sources.

• Note any pattern changes people asked for, and send them to the naming lead before anyone edits a script.

Checklists

Before you rely on a script

• Naming pattern written down

• Owner, input folder and output folder listed

• Tested on a copy of one project

• Log of old and new names kept

• Skips names it can't read instead of guessing

Before changing the naming pattern

• Naming lead approved it

• Each script that reads names checked

• Tested on a copy before real work

Before a delivery

• Output checked by a person

• Names match the client's spec or your pattern

• Only approved files in the delivery folder

Check your names

Prisma: file-naming and folder-structure tools for creative studios. Paste a few of your current names or folder paths into Prisma Scanner. It's free, needs no signup, and gives a score plus recommendations on where names break good practice. When you're ready to fix them, Prisma Hub, the Prisma app for Mac, suggests names based on your own rules. It's designed to fit into creative pipelines.

Open Prisma Scanner