Shoot Ingest and Backup

Turn a pile of memory cards into two verified copies of every file before anyone starts editing.

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

When a card is offloaded to the working folder, check each file against the card listing, post the count per card, and list anything that did not copy whole.

## Check every card
CheckIf it fails
File count matches the cardList the missing files
Every file opensFlag the broken ones
A second copy existsDon't mark the card safe
-Never format or delete a card — only report.
Ready-made: Offload Checksum Verify

The job, and what good looks like.

### What breaks Cards get formatted while the only copy is still sitting on one laptop, and a file that failed to copy looks exactly like one that did. The gap is found on Monday, when the cut is already booked. ### What the workflow does - Copy each card to the working folder without renaming anything yet. - Recalculate a checksum for every file and compare it with the card listing. - Copy the same folder to one offsite location and wait for the counts to match. - Write the frame count per card next to the shoot name. - Add the card to the format list only after both copies check out. ### What a human still approves The second person on the shoot confirms the frame count per card before anything is formatted, and names which offsite copy counts as the backup. Checksums catch silent truncation; they do not catch a card that was never read at all.

When it is handled

  • Two verified copies before a card is formatted
  • Frame count logged per card
  • Truncated files named, not discovered later
  • Same-day handoff note to the producer

Works with tools like

  • Adobe Lightroom
  • Capture One
  • Photo Structure
  • Bunny.net

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.

Catalog Gap List

When the catalog index finishes a shoot, compare it against the frame list for each card, post the gaps, and keep the shoot out of the archive folder until they close.

When the catalog index finishes a shoot

Offload Checksum Verify

When a card is offloaded to the working folder, check each file against the card listing, post the count per card, and list anything that did not copy whole.

When a card is offloaded to the working folder

Two-Copy Backup Check

At the end of each shoot day, confirm the files are in the working folder and on the offsite copy, then email me both counts before any card goes on the format list.

At the end of every shoot day

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.

Offload Checksum Verify

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.

Related workflows.

Bulk Rename and Folder Structure

Put a shoot into one predictable folder and file-name shape so search, backup, and handoff all agree.

3 automations

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.

2 automations

Video transcoding

Render every delivery version of a finished video from one master and play-test each one, so a broken file is found before the client opens the link.

1 automation

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