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.

macOS — coming soonSee the 2 automations
Media / AUTOMATE.md

Every Friday at 4:00pm, list the folders under the photo library that do not match our shape, and post the folder name, the file count, and the pattern you suggest.

Ready-made: Folder Structure Audit

The job, and what good looks like.

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.

When it is handled

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

Works with tools like

  • Photo Structure
  • Adobe Lightroom
  • Bunny.net
  • SmugMug

Ready-made automations. Pick the one that fits.

Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.

Folder Structure Audit

Every Friday at 4:00pm, list the folders under the photo library that do not match our shape, and post the folder name, the file count, and the pattern you suggest.

Every Friday at 4:00pm

Library Size Report

On the first working day of each month, total up the photo library by month, list the shoots with no delivery or archive date, and email me both numbers.

On the first working day of each month

You stay in charge.
At every step.

It checks and files. Every creative call stays yours.

  • It never deletes on its own

    It checks, lists and files. Deleting or formatting anything waits for your OK.

  • Undo a move you don't want

    Every step is recorded, and files it moved or renamed can be put back.

  • Your drives stay yours

    It works on the folders you point it at, on your computer. Nothing is uploaded to a new library.

Folder Structure Audit

Approve before it posts in Slack?

ReviewApprove

Before you download.

Where does it run?
On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
How does it connect to our CRM and other tools?
Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
Does it run when my computer is asleep?
It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
How does my team use it?
Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
Do I need anyone technical to set it up?
No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.

Already have tools for this? Here is the difference.

Presets and actions in your editor

Repeating the same edit across many files.

They can't check a delivery against an approval or tell you a card didn't copy.

Flowchart automation tools

Moving data between cloud apps.

They rarely reach local drives, and every exception becomes another branch.

Doing it by hand

Knowing exactly what happened.

It is the part of the job that waits until midnight.

AUTOMATE.md

Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 3

    Try it, then turn it on

    Run it once and check the result. It only runs on its own once you switch it on.

macOS — coming soon