As y'all know, I've been working with the QR codes extensively of late, and I believe a good solution for making the QR codes work well is to use a tablet at the shooting station to scan QR codes generated by Stratus. This would solve the resolution issue (as well as toner issue if printing yourself) of needing to print QRs large enough to be read by software at 50mm from ~10' so you can fill frame with the largest Hi-Lite background made (like y'all saw from my most recent shoot): people can just walk to the photographer's station to have their code scanned; an assistant could do it; or you could set up a kiosk of sorts (probably asking for trouble, but could be done).

You'd read in the timestamps, so now they're known. Photographer could sign in to the app, so you know what station goes with what set of time stamps (this is a major, major concern - consider time brackets from multiple sets... how do you know whose image it is if three kids are all getting photographed within seconds and several codes have been stamped?). I'd suggest making it a process where the photographer has to photograph the device itself open in a Web browser to time.is using program mode on the camera (to solve for lighting issues - camera will otherwise be ultra dark). You could even make an option to force photographer to ingest the time.is image so that the software could verify that it read the time. We use time.is shots at the start of all shoots (I learned this working for a large wire service who is very particular about accurate timestamps) to make sure that cameras are synced from multiple views from multiple cameras.

With a time.is reference, you could 1) Verify the time.is can be read; 2) Link a camera serial number in metadata to a mobile device that read the codes so that you can then have time brackets for identifying session client photographed per camera; 3) Either harvest the time from time.is and create a delta from the camera time to fix the time brackets automatically or force the photographer to fix time on camera before proceeding if the scanned time doesn't match the time.is capture time as recorded by the camera; 4) Use the QR scan to check off a student from class list you're working on so photographers know whose been photographed or is missing... could even do some simple stats like "12 students left to photograph" whatever.

The Entagged App uses the checkoff with list mode. I could write a book about what Stratus could do with all the data it has (chapters might include "Shoot List Tree Structures using Organization/Client Data for Elementary Schools" or "Live Database Updates and Temp Client Records for Athletes Added to Rosters Late to Picture Day") that could more than replicate existing Entagged functionality short of actually writing metadata to files in-camera using their proprietary dongle. I have always loved Entagged and was a very early adopter, but I don't like how the codes don't always sync (you may have to tap a person's name several times before it takes) or that the list is a paid service now. With a robust timestamp feature - I would absolutely enforce time.is - this would be a home run.