Why sets are more informative than singles
Photographs taken by one person, on one device, in one session, share a processing history. They were compressed the same way, denoised by the same software and exported by the same app, so they land in a similar range.
That gives you a baseline for free. You are no longer asking whether 58 is high, which depends on the camera and the compression. You are asking why one image scored 58 when its eleven neighbours scored between 18 and 26.
The comparison removes most of what makes a single score hard to read. Device processing, platform recompression and lighting affect the whole set together, so they cancel out and what remains is genuinely about that one picture.
The batch workflow
-
Collect originals, not forwards
Ask for files from the device rather than images pasted into an email. A set where some images have been recompressed and others have not will scatter for reasons that have nothing to do with manipulation.
-
Run the whole set at once
Up to twenty-five per batch. Running them together is what gives you the comparison; running them one at a time throws it away.
-
Read the summary before opening anything
The batch view shows the spread and how many landed in each band. That tells you whether you are looking at a clean set, a degraded set, or a set with one problem in it.
-
Open the outlier first
Not the highest score. The one furthest from its neighbours, which is not always the same image.
-
Check the region map on anything you open
Whether the whole frame is hot or one tile is decides what kind of finding you have and what to ask for next.
-
Export the batch report
One PDF summarising every image, and a combined JSON with the full result for each. That is the artefact that goes in the file.
What the shape of a set tells you
| Pattern across the set | Usually means | What to do |
|---|---|---|
| All low, tightly grouped | A clean set from one device | Nothing further |
| All middling, tightly grouped | Heavy processing or platform recompression | Ask for originals before concluding anything |
| Mostly low, one clear outlier | One image from a different source | Open the outlier and read its region map |
| Widely scattered with no cluster | Mixed sources or mixed compression | The set cannot be compared. Treat each separately |
| All high, tightly grouped | Either wholly generated, or a heavily filtered set | Check one image closely to tell which |
The fourth row is worth dwelling on. A scattered set is not a set at all for comparison purposes, and the useful response is to find out why the images differ before reading any of the numbers.
Where the limits are
Twenty-five per batch is a browser memory limit rather than a commercial one. Each image is decoded and scored in the tab, and a larger batch on a modest device runs out of room rather than slowing down gracefully.
For a set of two hundred, split it into groups that make sense: by day, by device, by source. That is better practice anyway, because comparing images from different sessions reintroduces exactly the variation the batch approach removes.
Who this workflow suits
- Claims handlers. A claim arrives as a set, and the outlier is the standard finding.
- Moderation teams. Ordering a review queue rather than judging items individually.
- Agencies. Checking a delivered batch of assets before it goes to a client.
- Finance teams. A single expense claim with twenty receipts photographed in one session.
- Researchers. Scoring a sample and looking at the distribution rather than any single result.
Building a baseline for a source you see often
Teams that review images from the same places repeatedly can go further than comparing within one set. Recording where a source normally lands turns every future batch into a comparison against history rather than against itself.
A particular claims portal that recompresses heavily might produce scores clustering around 45. That is not suspicious, it is that portal. Knowing the number means a set arriving at 45 raises nothing and a set arriving at 70 raises a question immediately.
Build it from images you have already resolved rather than from a sample you have not checked. Twenty known-good sets per source is enough to see the range, and the exercise usually surfaces a processing quirk somebody had been misreading as a signal for months.
Keep the note somewhere the whole team can read it. A baseline held in one person’s head stops being a baseline the week they are on leave.