RAW to Delivery Color
Apply one agreed look across a shoot and export delivery files that match the proof the client approved.
When a set is marked ready, check each file in the delivery folder against the agreed size, color space, and file type, then email me the mismatch list before anything is packed.
The job, and what good looks like.
### What breaks Every retoucher reads the brief differently, so 200 product shots arrive in six different whites. Proofs look right on a bright laptop and wrong in print, and the correction gets made twice. ### What the workflow does - Fix one working color space and one export recipe per job, and write them into the file. - Photograph a ColorChecker card in the first frame of the set and keep it with the shoot. - Pick the frame closest to the target white and use it as the reference. - Match the rest of the set to that frame rather than to each frame's own white balance. - Export from the same settings every time, including the embedded profile. ### What a human still approves The colorist chooses the reference frame and signs off on the first export before the batch runs. The workflow removes the re-grade on the retouch pass; it does not decide what the product should look like.
When it is handled
- One working color space per job
- Reference frame attached to the shoot
- Exports match the approved proof
- No re-grade on the retouch pass
Works with tools like
- Capture One
- Adobe Lightroom
- Adobe Photoshop
- ColorChecker
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.
Export Settings Check
When a set is marked ready, check each file in the delivery folder against the agreed size, color space, and file type, then email me the mismatch list before anything is packed.
When a set is marked ready to export
Reference Frame Pick
When a product set is imported, find the frame holding the ColorChecker card closest to the target, set it as the reference, and post the file name so the rest of the set follows it.
When a product set is imported
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.
Export Settings Check
Approve before it sends the email?
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.
Culling and Retouch Queue
Turn a finished shoot into one ordered list of the frames worth retouching, with the rest set aside on purpose.
3 automations
Client Delivery Packaging
Build a download package that names every file, states the usage terms, and stops at a size the client can actually receive.
3 automations
Photo tagging
Puts reviewed keywords on a shoot as it lands, so a decade-old library is findable by the words a client actually says out loud.
2 automations
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 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.