Flexible Yearbook · one book made personal for every family, with the adviser in control
The yearbook that flexes to every family.
A great school yearbook is one shared book — but the copy a child carries home can be theirs. That is the whole idea here: the book is made personal for each child, not assembled from modular building blocks — one shared book whose printed copy flexes to the family who holds it. Flexible Yearbook is that idea, built on a real engine: each printed copy can hold pages that belong to the child who holds it, while the adviser keeps master control of the whole book. Every family designs its own child’s personal pages, submits them for review, and the adviser locks them for print. For each child, the spreads that already feature them are gathered into that child’s copy by a deterministic curation — the same inputs always produce the same book, so a copy is reproducible, never a guess. Photos reach the right child by the roster, not a face scan. The order and giving engines are built, but checkout is honest-off — a family reserves a copy today, no card charged. We name what is on and what is not, plainly.
This is the personalized, parent-facing door to one real platform. The single-school, run-it-yourself product page is schoolyearbook.software, and the whole-platform overview is yearbook.software. The same engine runs behind all of them; this page describes the copy that flexes to each family.
What makes a copy flexible
Seven parts, one book. Five are built and running end to end — the per-copy compose, the deterministic curation, the family page maker, the adviser’s master control, and the consent and suppression wall. Two are marked honest-off: face-matching auto-fill is off by default, and the live payment rail is founder-gated, so a family reserves today.
Every copy flexes to the child
One school book, but the copy a child takes home can be theirs. Each printed copy is composed on its own — the shared spreads plus the pages that belong to that child — and merged into a single press-ready file per copy. This is not a reprint of the same book with a name swapped: a per-copy book prints individually, and because an offset run can only stamp one identical book, per-copy is refused on the offset lane by a fail-closed wall. The per-copy compose is built and running. Shipped
Personalized by a rule, not a guess
For each child, the spreads that already feature them are gathered into that child’s copy by a deterministic curation: given the same photos and the same roster tags, it always chooses the same pages, so a copy is reproducible and auditable rather than a random draw or a model’s hunch. The selection is a pure function with no clock, no randomness, and no guesswork — a family gets the same book whether it is built today or rebuilt next week. The curation engine is built and running. Shipped
Your pages, designed by your family
The part a family actually shapes is its own child’s personal pages — two to four pages that print ONLY in that child’s copy. A family designs them in a guided page maker, then submits them for review, which freezes the pages exactly as drawn. There is no picking-and-choosing which of the school’s spreads a child lands on; that is the adviser’s book. What a family owns is its own pages, and those are theirs to make. The family page maker and submit-to-review are built and running. Shipped
The adviser keeps the master
Personalization never takes the book away from the adviser. The adviser turns it on per book, reviews every family’s submitted pages, and locks each set for print — nothing a family submits reaches a copy until the adviser has locked it. Families see and touch only their own child’s pages; the whole-school book, the shared spreads, and the final lock stay with the adviser and the school. The flex is real, and it is bounded by the person responsible for the book. Adviser enable, review, and lock are built and running. Shipped
Consent decides who appears
A family’s choice about its child governs the whole book, not just its own copy. Publication consent is re-checked at the moment a family submits pages, and the curation drops any spread that depicts a child marked do-not-publish — so a child a family has held back never shows up in another child’s copy either. Minor child data is consent-gated and reversible, runs on private systems, and is never made public. The consent and suppression wall is built and enforced at the data layer. Shipped
Face-matching auto-fill — early access, off
There is an optional step that would use face-matching to auto-find a child’s photos across the book. It is off by default and not enabled here, so the book always uses the roster to decide who is on a spread — a photo reaches the right child because the roster says so, not because a face was scanned. If it is ever offered, it is operator-gated and opt-in, never switched on across a class by default. Today the whole product runs on roster tagging. Early access -- face-matching off
Reserve now — checkout is honest-off
The order rails resolve every price server-side, across scoped copy types and deadline windows, and a giving campaign can cover a copy for a family that cannot spend on one. Those engines are built. What is honest-off is the live payment rail: the charge to a family’s card is founder-gated and not enabled, so a family reserves a copy today rather than being charged. No copy has been sold here yet, and we say so. Early access -- live payment rails
How one book becomes every family’s copy
The shared book gets made the ordinary way — off one roster, in one editor, approved through a proof gate before anything prints. The flex is a layer on top: the adviser opens personalization, families add their own pages, and each copy is composed individually. Consent travels with every child from the first import, and the adviser holds the final lock the whole way through.
- Build the shared book. The school’s roster is imported once and carries the whole book — portraits, photo tags, the ladder, contents, cover. The staff lay out the shared spreads in the production editor, autosaving as they go, exactly as any yearbook is made. This is the book every copy starts from.
- The adviser turns on personalization. When the adviser is ready, they enable the personalized-copy plan for this book. It is the adviser’s switch, not a family’s — the whole-school book stays under the adviser’s control, and personalization is simply a layer they choose to open.
- Each copy is curated per child. For every child, the spreads that already feature them are gathered into that child’s copy by a deterministic rule — the same photos and roster tags always yield the same pages. Photos reach the right child through the roster, not a face scan; face-matching auto-fill stays off by default.
- Families design their own pages. Each family opens a guided page maker and designs its child’s two to four personal pages — the pages that will print only in that child’s copy. A family shapes its own pages; it does not reach into the school’s shared spreads or another child’s copy.
- Submit freezes the pages and checks consent. When a family submits its pages for review, the pages freeze exactly as drawn and publication consent is re-checked at that moment. A child a family has held back is dropped from the shared curation too, so no held-back child appears in anyone’s copy.
- The adviser reviews and locks. The adviser reviews each family’s submitted set and locks it for print. Nothing a family submitted reaches a copy until the adviser locks it, and a half-finished set cannot slip through — the proof gate is fail-closed.
- Compose the copy and reserve it. Each child’s copy is composed as one press-ready file — the shared spreads plus that family’s locked pages — on the per-copy print lane, refused on offset because offset cannot vary a copy. Families reserve a copy at a price resolved server-side; the live payment rail is honest-off, so no card is charged today.
What flexes, and what stays the adviser’s
A flexible book only works if the line between a family and the adviser is honest and clear. Here is exactly what a family shapes, and what stays the adviser’s call — no more, no less.
A family shapes its own pages
What a family designs is its own child’s two to four personal pages — the photos, the words, the layout on those pages — which print only in that child’s copy. That is the real, hands-on part for a family, and it is genuinely theirs. It is a page maker for your pages, not a control panel for the school’s book.
A family does not pick the school’s spreads
There is no dial where a parent chooses which of the yearbook’s sections or spreads their child appears in. The spreads that feature a child are gathered by a deterministic rule off the roster tags, not selected by a family. We would rather say this plainly than imply a control that does not exist: families make their own pages; the book’s spreads are curated automatically.
The adviser owns the book and the lock
The adviser turns personalization on, reviews every family’s pages, and locks each set for print. The shared spreads, the ladder, the cover, and the final approval stay with the adviser and the school. The book flexes to families, but it never leaves the hands of the person responsible for it.
The rule is the same for everyone
Because curation is deterministic, every child’s copy is built by the same rule from the same kind of inputs — no child gets a better copy because a parent knew which button to press. Fairness is a property of the engine, not a favour. A copy is reproducible, so the school can always see exactly why a page landed where it did.
Consent leads, and photos are matched by the roster
A personalized book means a child’s photos and pages travel into a specific copy, so consent has to lead rather than trail. Data that involves a minor child is consent-gated: a family opts in before a child’s image is used in a way that requires it, and that consent can be withdrawn at any time. When a family withdraws, it takes effect — it is a live setting the family controls, not a one-time checkbox. Minor child data runs on private systems and is never made public.
Publication consent is re-checked at the exact moment a family submits its pages, and the curation drops any spread that depicts a child marked do-not-publish. So a family that holds its child back is respected across the whole book: that child is dropped from the shared curation and never surfaces in another child’s copy either. Consent is a wall the engine enforces, not a note a person has to remember.
Photos reach the right child by roster lookup, not by scanning faces. Facial recognition is off by default and is never used to auto-tag a photo of a child. The optional face-matching auto-fill that could pre-find a child’s photos is early-access and not enabled here; if it is ever offered, it is operator-gated and turned on for an individual child only by that child’s own parent, one explicit opt-in at a time — never switched on across a class by default. The ordinary way a photo reaches the right page is the roster.
The school owns its children’s and families’ data. It is never sold to or shared with outside companies, advertisers, or third parties, and running a personalized book on this platform does not hand a child’s information to anyone. The school stays the custodian of its records from the first import to the last copy handed out, and consent for the youngest subjects in the book is the first thing the engine is built to get right.
Who a flexible book is for
The same book serves three people at once — the family that wants a copy that feels like their child’s, the adviser who has to keep one book coherent, and the school that has to keep it safe.
Families who want their child’s copy
A family that has ever wished the yearbook had more of their own child now has a real, bounded way to add it: two to four personal pages that print in their copy. It is warm and hands-on without asking a parent to learn design software — a guided page maker, a preview of the printed page, and a submit button. The copy that comes home holds the shared year and a few pages that are unmistakably theirs.
Advisers who still need one coherent book
An adviser gets the appeal of personalization without losing the book to a hundred families. Personalization is a layer the adviser opens, reviews, and locks; families touch only their own pages; the shared spreads and the final approval stay put. The flex adds copies families love without adding a hundred cooks to the shared book.
Schools that answer for the data
A school can offer a personalized book and still stand behind its privacy posture. Consent is gated and reversible, checked again at submit; a held-back child is dropped everywhere; minor child data is never made public; and photos are matched by roster, not a face scan. The school owns its data and stays the custodian of it. The premium experience does not cost the school its promises to families.
One platform behind all of it
The flexible copy is not a separate app bolted on; it is one capability of the same platform that runs the roster, the editor, the proof gate, and the press-ready export. Standing up a personalized book uses the same tools a school already knows, so the flex is an option to turn on, not a second system to run.
Common questions
What does “flexible” actually mean here?
It means one shared school book where the copy a child takes home can carry pages that are theirs. Each copy is composed individually — the shared spreads plus that family’s own personal pages — and each child’s copy is curated by a deterministic rule from the spreads that already feature them. The book flexes to the family; the adviser keeps master control of the whole thing.
Can I choose which yearbook sections or spreads my child appears in?
No, and we will not pretend otherwise. The spreads that feature a child are gathered automatically by a deterministic rule off the roster tags, not picked by a parent. What a family shapes is its own child’s two to four personal pages, which print only in that child’s copy. That is the real, hands-on part — a page maker for your pages, not a selector for the school’s book.
Does the platform scan my child’s face to find their photos?
No. Photos are matched to a child by roster lookup, not by a face scan. Facial recognition is off by default. There is an optional face-matching auto-fill that could pre-find a child’s photos, but it is early-access and not enabled here, so the book runs entirely on roster tagging. If it is ever offered, it is operator-gated and turned on for an individual child only by that child’s own parent, one explicit opt-in at a time.
How is a personalized copy actually different from a name printed on a book?
A personalized copy is composed on its own: the shared spreads plus the family’s own locked pages, merged into one press-ready file for that copy. It is not one identical book with a name swapped. Because an offset press can only stamp one identical book, per-copy books are refused on the offset lane by a fail-closed wall and printed on the per-copy lane instead.
How do I know two copies of the same child come out the same?
The curation is a pure function — given the same photos and the same roster tags, it always selects the same spreads, with no randomness and no clock. A copy is reproducible and auditable: the school can rebuild it and get a byte-identical result, and can see exactly why a page landed where it did. Fairness is a property of the engine, not of who pressed which button.
Who decides what actually prints?
The adviser. Personalization is enabled per book by the adviser, who reviews every family’s submitted pages and locks each set for print. Nothing a family submits reaches a copy until the adviser locks it, and a fail-closed proof gate keeps a half-finished set from slipping through. Families see and touch only their own child’s pages.
What happens to a child whose family does not want them published?
That choice is respected across the whole book. Publication consent is re-checked when a family submits pages, and the curation drops any spread that depicts a child marked do-not-publish — so a held-back child is removed from the shared curation and never appears in another child’s copy either. Minor child data is consent-gated, reversible, and never made public.
Can I buy my copy today? Is checkout live?
Not yet. The order rails — server-resolved pricing, scoped copy types, deadline windows — are built, but the live payment rail is honest-off: present in the platform, not enabled for live transactions. A family reserves a copy today rather than being charged. No copy has been sold here yet, and we say so plainly.
What if a family cannot afford the copy?
A giving campaign can cover a copy for a family that cannot spend on one: the school sets a goal and a per-copy amount, and every gift is tracked cent for cent with a no-skim ledger. The campaign substrate is built; the live giving checkout that moves a donor’s money is honest-off, so no donor is charged today.
Is this a different product from our regular yearbook?
No. It is one capability of the same platform that runs the roster, the editor, the proof gate, and the press-ready export. A school builds its shared book the ordinary way and turns personalization on as a layer. There is no second system to learn and no separate app for families beyond the guided page maker for their own pages.
Related surfaces
The flexible door connects to the general single-school product page, the whole-platform overview, and the studio-side photography home the photos flow from. These destinations cover the adjacent surfaces.
schoolyearbook.software
The single-school, run-it-yourself product page — the same program described for any school, with no rep and no contract. The flexible door leads on the per-copy, per-family angle; this is the general single-school view.
yearbook.software
The umbrella product overview: the whole yearbook arc — write, design, photograph, proof, print, sell, give, read — on one platform and one roster per school. The wide view of the platform this flexible copy is one capability of.
pholio.photos
The studio-side photography and proofing home. The portraits and event photos that land in a personalized copy flow from here, matched to the roster the book is built on.
homeroom.software
The flagship platform brand home: the full platform story behind the flexible copy a school runs. This page is part of the same family.
What is built and what is honest-off
The flexible-copy engine is built and running today: the per-copy compose that merges a child’s shared spreads with that family’s locked personal pages into one press-ready file on the per-copy print lane (refused on offset by a fail-closed offset-honesty wall, because offset cannot vary a copy); the deterministic curation that selects each child’s spreads by a pure rule, so a copy is reproducible byte for byte; the family page maker where each family designs its own child’s two to four personal pages and submits them for review; the adviser’s master control to enable personalization per book, review every family’s pages, and lock each set for print; and the consent and suppression wall that re-checks publication consent at submit and drops any spread depicting a do-not-publish child. Two things are honest-off. The face-matching auto-fill that could pre-find a child’s photos is off by default and not enabled, so the book runs on roster tagging — there is no live “the software finds your child’s photos” here, and photos are matched by the roster, not a face scan. The live payment rail — the charge to a family’s card and the move of a donor’s money — is founder-gated and not enabled, so a family reserves a copy today rather than being charged; no copy has been sold here yet. There is no parent dial to pick which of the school’s spreads a child appears in — a family shapes its own pages, and the spreads are curated automatically. Minor child data is consent-gated and reversible, runs on private systems, and is never made public; the school owns its data and it is never sold or shared. This is a for-profit product; no tax-deductible or charitable claim is made anywhere. No competitor brand names appear here. Pricing and checkout are not on this page.