IngestNaming

Photo organization

Hold the library to one folder shape, with no duplicate or undated shoot left behind, so a job is never hunted for twice.

Tools

Photo Structure, Adobe Lightroom, Bunny.net, SmugMug

Outcomes

One folder shape across the library • Duplicates and undated shoots listed weekly • Frame counts recorded per card • No delivery built from the wrong folder

Documentation

Instruction-ready detail below

A library grows by accident: one shoot in a folder named for the client, another named for the month, and a third on somebody's desktop. Three weeks later nobody can say which folder holds the frames the client picked, and the answer has to be found by asking three people. This workflow reads the library and reports every folder that does not match the agreed shape, with the shoot date, the file count, and the folder it belongs in. It lists shoots that have a folder but no delivery or archive date, finds two shoots whose names differ only by a typo, and compares each card's frame count against what the catalog recorded. Renames are proposed, never applied quietly. The photographer still decides what a shoot is called, which duplicate is the keeper, and when an old year comes off the drive.

Automations

Choose the setup that matches your tools.

Problem this workflow solves

A shoot turns up in three folders because each assistant named it differently, and the frame list that should say what is on every card never gets written. The producer is the one who chases it, calling three people to work out whether Saturday's 400 frames were delivered or are still on a card. The result is a billed retake, or a job that ships without the family group shots, because nobody could find the folder in time.

Download

Start with one instruction file.

Download the app and begin with drafts and checklists before you write anything back.

  • •Plain-language instructions
  • •Runs on your machine
  • •Works with your existing setup
  • •Reviewable activity history
Download