About
We ran picture days before we wrote software for them
Homeroom Picture Day is part of Homeroom, built by Stanley Studios. It exists because the company was already running the hardest version of this problem, against rosters full of children whose data is not ours to be casual with. That is an unusual place to start, and it is the reason the product has the shape it does.
Who builds this
Stanley Studios. Homeroom is its platform for schools, and picture day is one of the operations that platform runs. The company’s starting point was the studio side of school photography: booking family sittings, dispatching a crew across several buildings, and routing a day, in the same week, against a school’s roster.
That order matters. Most software for picture day is written by people who have read about picture day. Starting from the operation means the awkward parts — the absence list, the retake that has to supersede cleanly, the family that asked in September and changed its mind in March — were the first problems rather than the ones deferred to a later release.
Why the product has this shape
Two decisions follow directly from running the operation, and both of them look conservative from the outside.
The first is that correctness rules live in the database rather than in application code. Application code is where the plausible-looking race condition lives, and where a privacy wall is a function somebody has to remember to call. A wall in the database is one a new feature inherits whether its author thought about it or not, which is the only kind of wall that survives a busy year.
The second is that the boring mechanism wins where a clever one is optional. Face matching exists and is off. The everyday match is a roster lookup, because the school already knows who was in the room and the clever version’s cost is a biometric template for every child in the building. When we run our own days on this, we are the ones holding that cost, which concentrates the mind.
What exists today, without the marketing tense
Software marketing has a habit of describing planned work in the present tense and letting the reader sort it out. This is the whole inventory in one place, and every page on this site is written to agree with it.
| Area | State today | What that means precisely |
|---|---|---|
| The picture-day cockpit | Built | Sessions, the roster they run against, and retake sessions |
| Roster matching | Built | A permission-checked lookup on a name and an id |
| The consent gate | Built | Per student, default closed, re-checked at the point of use |
| Face matching | Built, off by default | Off by default; face matching not wired |
| Family delivery | Built | A permission-checked read against the roster |
| The family store | Early access | Live payment is not turned on; no checkout and no price anywhere on this site |
There are no adoption numbers on this site, no customer logos, and no testimonials. A product this early that displays those has usually manufactured them. What is here instead is the list above.
What we will not do
We will not make a minor’s photograph public. Not indexed by a search engine, not on an open gallery link, not sold, and not handed to an outside company as a data set to be mined.
We will not turn face matching on for you. It is off until a parent turns it on, per parent, and it is not bundled into any other permission.
We will not tell you a compliance framework is satisfied. We describe mechanisms: where the wall is, what is re-checked, what defaults closed. Whether that satisfies a particular obligation is a question for the school and its counsel, and marketing copy has no business answering it.
We will not claim the piece we have not finished.
Questions about us rather than about the product
Are you a software company or a photography company?
Both, and in that order historically. Stanley Studios ran the studio side of school photography before it built the platform, which is why the picture-day module is the one with the most operational detail in it rather than the one with the most features. A company that had only ever written software would have built the easy parts first.
Do you still run picture days yourselves?
The operation is where the requirements come from, and the arrangement has a cost worth stating: our own operations break first when something is wrong. A scheduling or matching fault is not a support ticket from a stranger, it is a Saturday somebody is standing in the wrong building. That has made us conservative in specific ways, and the two biggest are on this page.
Why is there no customer list on this site?
Because a product at this stage that displays one has usually manufactured it. There are no logos, no “trusted by” band, no testimonials and no adoption figures anywhere on this site. What is here instead is the inventory table above, which says what is built and what is not in the same tense a school would use.
What is the business model, given the platform is free to the school?
The core platform is free to the school with no per-student fee, and the money is meant to come from the family store, above a cost floor enforced in code. That store is early access and live payment is not turned on, so today the honest answer is that the model is described rather than running. We would rather say that than describe a revenue line in the present tense.
Who do we talk to?
There is no form on this site, deliberately: nothing here collects anything. The platform’s own front door at homeroom.software is where a school gets in touch, and it is also where the whole-platform answer lives if picture day turns out not to be the thing you came for.
Why picture day has an address of its own
Several of the addresses this school platform owns point at one image library on purpose. A school looking for its picture-day operation and a school looking for the imagery its yearbook is built from are looking for two doors onto one shelf, not two products to buy.
This address is the picture-day door. It exists separately because picture day is the operation with its own calendar, its own failure modes and its own reader — a school office planning a day — and because burying that inside a general page about an image library is how a school ends up reading four paragraphs about publications to find out what time the day starts.
What it is not is a separate product with a separate bill, a separate roster, or a separate consent model. It is one operation on one platform, with a front door where the people who need it will look.
Where to go from here
The operational half of picture day is on the day, the matching mechanism is on matching, and the delivery side, including what is switched off, is on families.
Picture day is one collection in a larger library. The library itself is at homeroom.gallery, and the platform the whole thing sits in is at homeroom.software, which is also where a school gets in touch with us.