The photographer delivers 120 images per property in a folder called exports_final, and by the third price reduction there are three sets for the same house and no obvious way to tell which one is current.
The short answer
Listing photos are filed by address and then by shoot date, because a property is photographed more than once and the question is always which set is current. A photograph carries no address on its face, so the address comes from the upload rather than the file: one destination per property, and the Rename step names each image by the shoot date and a sequence number. The Move step files the set under that property, which keeps a re-shoot from silently mixing with the original.
Steps this uses
Before and after
As they arrive
After the workflow
Two shoots of one property and one of another, separated by the date each set was taken.
Setting it up
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When listing photos are uploaded for a property, rename each one by the shoot date and a sequence number, and file the set under that address in a folder for the shoot.
This is what supplies the address, since no photograph contains one. A delivery dropped into that destination belongs to that property, with no guessing involved.
A re-shoot after staging or a price change is a different set, and mixing it with the original is how a withdrawn image ends up back on a listing. The shoot date is the divider.
The Rename step writes the shoot date and a number. Naming by room requires somebody to decide what each image shows, and with 120 images per property that decision does not get made.
The full delivery and the subset that went to the MLS are different things. Keeping the selects distinct means the listing set can be reproduced exactly, which matters if a listing is questioned.
Every other document in a transaction states its address. A photograph states nothing, and tools that claim to sort images by content are inferring from pixels — which cannot distinguish two similar kitchens in the same neighbourhood. Routing by upload destination is less impressive and it is correct, and correctness is what matters when the alternative is a wrong property's photo on a listing.
Most photo mishaps are not lost files, they are stale ones: a staged image reused after the staging is gone, a summer exterior on a winter listing, a room that has since been renovated. Separating sets by shoot date makes the current set obvious and the superseded one still available, which is the combination that prevents both the stale image and the deleted-original problem.
It routes, names and files. It does not edit, select the best twenty, detect duplicates across shoots, or push images to an MLS. Choosing which photographs sell a house is judgement, and this is about making sure the right set is findable and the superseded one is not mistaken for it.
FAQ
By property address, then by shoot date, with each image named by the date and a sequence number. Photographs carry no address, so the property has to come from where the delivery was uploaded rather than from anything inside the file.
Because properties get photographed more than once — after staging, after a renovation, after a season changes. Mixing a re-shoot with the original set is how a withdrawn or outdated image ends up back on a listing, and the shoot date is the cleanest divider between them.
Not reliably enough to depend on. Inferring a room from pixels is a guess, and with 120 images per property a confident wrong guess creates work rather than saving it. Date and sequence require no judgement and never file an image under the wrong property.
Yes. They answer different questions: the delivery is everything the photographer produced, and the selects are what actually went on the listing. Keeping them distinct means the published set can be reproduced exactly if a listing is ever questioned.
Answered by the shoot date, not by which folder was opened last.
5 GB free · No credit card required