Homeroom Picture Day · homeroom.pics
Picture day is an operation, not a photo shoot
It is the one day of the year when a school hands a stranger a list of every child in the building. Almost everything that goes wrong afterwards goes wrong because that list and those images ended up in two different systems. Homeroom runs the day on the school’s own roster, so the list and the images are the same thing.
Four things at once, and they are not the same job
Picture day gets discussed as though it were one activity. It is four, they have different failure modes, and a product that is strong at one of them is usually silent about the other three. Here is each one, with what is built beside it rather than in a chart somewhere else.
A schedule
Built
A day with a shape, agreed before anyone arrives
Picture day is a timetable before it is a camera. Which classes come when, how long a station holds a student, where the line forms, which specialists get pulled out of a lesson and when they go back. A day planned as “we will work through the school” is a day that runs an hour long by second period and takes the last two classes after lunch, which is how the retake list gets written.
The picture-day cockpit covers the session and the day’s shape
A roster
Built
The list is the school’s own, not a spreadsheet emailed out
The day runs against the roster the school already keeps, in the system where that roster is maintained. That is the difference between a picture day and a photo shoot: at the end of it there has to be an answer to “who was not photographed”, and the only way to have that answer is to have started from a list the school recognises.
Roster-backed sessions built
A match
Built
Every frame has to land against the right student record
The match is a permission-checked roster lookup on a name and an id — the school’s own list. No face scanning is involved in the ordinary path, because the school already knows who was in the session. This is the single most under-discussed part of picture day and the part most likely to be handled, elsewhere, by a paper envelope and somebody’s handwriting.
Face matching is not wired in the shipping product and cannot be switched on from it: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead.
A delivery
Early access
Getting images to the families entitled to them, and nobody else
Delivery is a permission-checked read against the roster: a family sees the students attached to that family, and nothing else. There is no public gallery link that works for anyone who has it, because a link that works for anyone who has it is not a permission model. The buying side of delivery is a separate question, and it is switched off.
Delivery built · the family store is early access, live payment not turned on
The order of the day, and where the gate sits
Six stages, and the load-bearing detail is the fifth. The consent gate sits between the match and the delivery, not after it. A gate consulted after people have been served is a report, and a report cannot un-send anything.
Each stage below is a thing that already exists rather than a diagram of an intention. Nothing in it depends on anyone remembering a decision made in September.
What actually goes wrong on picture day
These are the five that recur. None of them is about photography, and that is the whole argument for treating picture day as a records operation that happens to involve a camera.
Nobody can say who was missed
This is the failure that produces every other one. If the day did not start from the school's roster, the absence list at the end is a subtraction between two things that were never the same list. Running against the roster the school maintains means the missed list is a query rather than a reconciliation.
A portrait is attached to the wrong student
A misattached portrait is not a cosmetic problem: it is a student record with someone else's face in it, and it travels into the yearbook, the identification card and the family's delivery all at once. Matching on a name and an id against the school's own list is deliberately boring, because the interesting version of this is where the mistakes come from.
A family's decision does not reach the print run
A publication permission enforced in one system and an image sitting in another that has never heard of it is the ordinary arrangement, and it is why a withdrawn consent so often reaches a person's memory rather than a print job. Holding the images on the same roster as the permission is what closes that gap.
The retake list is written on paper
Retake day exists because picture day has absences, blinks and uniform problems. Where the retake list lives outside the system, the retake session cannot be run against it, the second image cannot supersede the first cleanly, and the yearbook gets whichever one somebody happened to file.
The images end up in three places
A drive for the raw take, a service for the family gallery, and a folder somebody made for the yearbook staff. Three copies is three consent models, and the one that matters is whichever one the print run happened to read. This is the argument for one library rather than a preference for tidiness.
What is built, counted honestly
These bars are counted from this page’s own lists at render time, so they cannot drift away from the descriptions above them. They measure build state, not customers — there is no adoption number anywhere on this site.
How money works here, and what is switched off
The core platform is free to the school. There is no per-student fee and no seat licence for running picture day on it, so nothing about a school’s own photographs sits behind a payment.
The family store is early access and live payment is not turned on. This site runs no checkout, quotes no price, and has nothing on it that takes money. We are describing what this product does when the family store is live, not something a family can use this afternoon.
The mechanism the family store runs on — not a promise of when — is written out on the families page.
Questions a school asks first
Do we have to change photographers to use this?
No. This is the school's side of picture day -- the roster the day runs against, the match back to the student record, the consent state, and the delivery. Who stands behind the camera is a separate decision, and a school that already has a photographer it likes has no reason to change one to fix the other.
Is facial recognition used to sort the photos?
Not by default, and not unless a parent opts in. The everyday way a photo is attached to a student is a permission-checked roster lookup on a name and an id. Face matching is not wired in the shipping product and cannot be switched on from it: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead.
What does this cost a school?
The core platform is free to the school. There is no per-student fee and no seat licence for running picture day on it, so nothing about a school's own photographs sits behind a payment. The family store is a separate thing and it is early access with live payment not turned on.
What happens to the images if the school leaves?
They come with them. Because the images live in the same system as the records rather than with a separate vendor, leaving is an export and a wipe rather than one negotiation per vendor. That is the other side of a single home: easier to hold, and easier to hand back.
The matching answer above is the short version. The long one, including what happens when a parent does opt in and the one piece of it we have not finished proving, is on matching. Who builds this and why it has this shape is on about.