Yearbook Management · run the whole program — ladder, deadlines, sales, proofing, and print
Run the program, not just the pages.
Yearbook Management is the yearbook platform seen from the angle of the person running the whole operation. A yearbook is a project with a moving-target deadline, a book that has to be planned page by page, coverage that has to reach every student, a sale that has to fund the print run, and a delivery that has to end with a book in every buyer’s hands. This page is about the tools that manage that program: the ladder that plans every page, coverage tracking off the roster, the deadline and proof-approval control, the server-priced sales rails, the sell-through reminder engine, and print-and-delivery tracking from proof to distribution — all on the one school roster. The money that moves is honest-off; a family reserves rather than pays today.
This is the run-the-program product page. The staff-and-roles collaboration angle is at yearbook.team. The umbrella overview of every stage is at yearbook.software. The platform is free for the school; the live sell checkout is honest-off.
Six things a program runs on — what is built and what is honest-off
Every engine below is built and production-ready. The parts that move a family’s money — the live sell checkout and the print-order checkout — are honest-off: present in the platform, not enabled for live transactions. Each is marked plainly.
The ladder: a plan for every page
The ladder is the map of the whole book — every page, its section, its assigned staff, and its status. A program is managed on the ladder: the table of contents, the endsheets, and the cover are structural surfaces the ladder plans alongside the content spreads. An adviser can see at a glance which pages are planned, in progress, in review, and done, instead of guessing how far along the book really is. The ladder and the structural surfaces are built and production-ready. Shipped
Coverage tracking off the roster
The hardest program-level question is who is missing. Coverage tracking shows, before deadline, which students and which groups — clubs, teams, classes — are already on a spread and which are not yet covered, computed against the school roster. It turns an abstract deadline into a checkable standard: the book is done when the coverage is complete, not when it looks full. The coverage-gap report is built and production-ready. Shipped
Deadlines and the proof-approval gate
Deadlines are the spine of a yearbook program. The adviser reviews the book spread by spread, comments, locks a version, and approves through a fail-closed approval gate — nothing advances to print until it is genuinely signed off. A read-only proof link reaches the principal or the print lab without generating and emailing a giant file. The proof-approval workflow, version locking, and the no-file proof link are built and production-ready. Shipped
Server-priced sales, scoped by book type
When it is time to sell, the order rails resolve every unit price server-side from the school’s catalog — the buyer never types in the amount, so what a family sees is what would bill. A program can offer a whole-school book, a grade book, a single class book, or a club book, run an early-bird-to-deadline price schedule, and split every sale four ways (studio, photographer, school, platform) with an optional fundraiser cut from the school’s own share. The order, pricing-window, scoped-book, and payout engines are built; the live payment rail is honest-off — a family reserves a copy today. Built · live checkout honest-off
Sell-through: reach only who has not ordered
Managing a sale means knowing who has bought and who has not. The sell-through reminder engine targets the families who have not yet ordered — roster minus orders — instead of blasting everyone again, and a print-run thermometer shows how close the program is to the quantity it needs to commit. An adviser can make an informed print-run decision instead of a guess. The sell-through targeting and the run thermometer are built and production-ready. Shipped
Print and distribution tracking
At deadline the platform runs an automated pre-flight file check — resolution, bleed, colour — and exports a press-ready PDF the school sends to whichever print lab it uses. Delivery status is tracked from proof to print run to fulfillment, and a distribution-day check-in matches each book to a student at handout so no copy goes to the wrong hands. The pre-flight, press-ready export, delivery tracking, and check-in engines are built; the print-order checkout that takes a family’s payment is honest-off. Built · print checkout honest-off
A yearbook program, from ladder to distribution
Running the program is a sequence: plan the book, cover the school, hold the deadlines, sell the copies, print the run, and hand out the book. The platform gives each step a real tool on the one roster.
- Import the roster once and build the ladder. The school’s roster is imported a single time and becomes the spine of the year. The ladder is built on top of it: every page planned, sectioned, and assigned, with the table of contents, endsheets, and cover as structural surfaces alongside the content spreads.
- Assign coverage and watch the gaps. Coverage is planned against the roster. The coverage-gap report shows which students and groups are not yet on a spread, so the program chases what is missing before the book closes — not after it prints.
- Hold the deadlines through the proof gate. As spreads finish, the adviser reviews and approves through the fail-closed gate. An approved spread locks; a read-only proof link lets the principal or the print lab see the current state without a giant file. The deadline is enforced by what has been approved, not by a wall calendar alone.
- Open the sale at a server-resolved price. The storefront resolves every price server-side, so a family sees exactly what would bill. The program picks its book types — whole-school, grade, class, or club — and its price schedule. Every sale splits four ways with an optional fundraiser cut from the school’s own share. The live payment rail is honest-off; a family reserves a copy today.
- Drive sell-through without over-mailing. The reminder engine targets only the families who have not yet ordered, and the print-run thermometer shows how close the program is to the quantity it needs. The adviser commits a print run from real numbers instead of a guess.
- Pre-flight and export press-ready. At deadline the platform runs the automated pre-flight file check and exports a press-ready PDF the school sends to whichever print lab it chooses. The book does not have to be adjusted to survive a consumer export.
- Track delivery and check in at distribution. Delivery status is tracked from proof to print run to fulfillment. On distribution day, the check-in matches each book to a student at handout, so the right copy reaches the right hands and unclaimed copies are visible rather than a pile in the office.
The ladder is the program’s map
Every yearbook program lives or dies on knowing how far along the book actually is. The ladder is where that lives — the plan of every page, its status, and who owns it.
Every page, planned
The ladder lays out the whole book page by page: the section a page belongs to, the content planned for it, and the staff assigned to build it. A program manager sees the shape of the book before it exists, and can spot the section that is thin or the spread that has no owner while there is still time to fix it.
Status at a glance
Each page carries a status — planned, in progress, in review, approved. The ladder rolls those up so the adviser can answer the question every principal asks, “how close are we,” with a real number instead of a hopeful guess. The deadline stops being a surprise.
The structural surfaces too
A yearbook is more than content spreads: the table of contents, the endsheets, and the cover are real surfaces the ladder plans alongside the pages. They are part of the program plan, not an afterthought discovered the week the book is due.
Coverage plugs into the plan
The ladder and the coverage-gap report work together: the plan says which pages exist, and coverage says which students and groups are on them. A program manager can see both the pages that are unfinished and the people who are not yet in the book — the two questions that actually decide whether a yearbook is done.
Selling the book without guessing
The sale is the part of a yearbook program with real money and real risk: order too few books and families go without; order too many and the office has a pile of unclaimed copies and a bill. The platform is built to take the guessing out of that decision.
Every price is resolved server-side from the school’s catalog, so a family never types in an amount and what they see is what would bill. A program can scope the sale to a whole-school book, a grade book, a single class book, or a club book, and run an early-bird-to-deadline price schedule. Every sale splits four ways — studio, photographer, school, and platform — with an optional fundraiser cut taken from the school’s own share, so a program can raise money on top of the book without a separate tool.
Once the sale is open, the sell-through reminder engine targets only the families who have not yet ordered — the roster minus the orders — so a program reminds the people who need reminding instead of mailing everyone again. The print-run thermometer shows how close the program is to the quantity it needs to commit, so the adviser makes the print-run call from a real number.
The order, pricing-window, scoped-book, payout-split, sell-through, and thermometer engines are built and production-ready. The one thing that is not enabled is the live payment rail: the live sell checkout that charges a family’s card is honest-off. Today a family reserves a copy; no card is charged. We name that plainly rather than imply a live sale. Mission-giving, where a program also underwrites books for students who cannot afford one, goes deep at yearbook.fund; its live giving checkout is honest-off as well.
From proof to print to hands
The last stretch of a program is where a well-built book can still go wrong: a file the printer rejects, a delivery nobody tracked, a distribution day of chaos. The platform tracks the whole tail.
Automated pre-flight
At deadline the platform runs an automated pre-flight file check — resolution, bleed, colour — before anything goes to the printer. Problems surface as a checklist to fix, not as a rejection email from the lab a week later. The book does not have to be adjusted to survive a consumer export.
Press-ready export, your own lab
The platform exports a press-ready PDF the school sends to whichever print lab it uses. The program is not locked to one printer — it picks the lab that fits its budget and timeline, and sends a file built to a press standard.
Delivery tracking
Delivery status is tracked from proof to print run to fulfillment, so a program manager knows where the order stands instead of calling the printer to ask. The status is visible in the same place the book was built.
Distribution-day check-in
On distribution day the check-in matches each book to a student at handout, off the same roster the whole program ran on. The right copy reaches the right hands, unclaimed copies are visible rather than a mystery pile, and the last day of the program is orderly instead of frantic. The print-order checkout that takes a family’s payment is honest-off.
Common questions
How is this different from yearbook.team and yearbook.software?
yearbook.team is about the people building the book — the staff roles, permissions, and collaboration. yearbook.software is the umbrella overview of the whole write-to-read arc. Yearbook Management is the operations view: the ladder and page tracking, deadlines, coverage, selling the book, and getting it printed and distributed. If you are the adviser or administrator running the program as a project, this is the angle for you.
What is the ladder and why does it matter?
The ladder is the plan of every page in the book: its section, its assigned staff, and its status — planned, in progress, in review, approved. It is how a program manager knows how far along the book actually is, spots the thin section or the unowned spread early, and answers “how close are we” with a real number. The table of contents, endsheets, and cover are structural surfaces the ladder plans alongside the content spreads.
How does coverage tracking work?
Coverage tracking runs against the school roster and shows which students and which groups — clubs, teams, classes — are already on a spread and which are not yet covered. It turns the deadline into a checkable standard: the book is done when coverage is complete, not when it merely looks full. A program manager can turn the gap list into assignments before the book closes.
Can a family buy a book here today? Is checkout live?
Not yet. The order rails — server-side pricing, scoped book types, deadline windows, the four-way payout split, sell-through targeting, and the print-run thermometer — are all built and production-ready. The live payment rail is honest-off: present in the platform but not enabled for live transactions. Today a family reserves a copy; no card is charged. We say so plainly rather than imply a live sale.
How does the sales split work?
Every sale splits four ways — studio, photographer, school, and platform — with an optional fundraiser cut taken from the school’s own share, so a program can raise money on top of the book. Every unit price is resolved server-side from the school’s catalog, so the buyer never types the amount and what a family sees is what would bill. The split and pricing engines are built; the live checkout is honest-off.
How do we decide how many books to print?
From the numbers, not a guess. The sell-through reminder engine targets only the families who have not yet ordered, so a program keeps working the actual holdouts. The print-run thermometer shows how close the program is to the quantity it needs to commit. Together they let an adviser commit a print run from real demand instead of over-ordering to be safe.
Can we use our own print lab?
Yes. The platform runs an automated pre-flight file check and exports a press-ready PDF the school sends to whichever print lab it uses. The program is not locked to one printer — it picks the lab that fits its budget and timeline. Delivery status is then tracked from proof to print run to fulfillment.
What happens on distribution day?
The distribution-day check-in matches each book to a student at handout, off the same roster the whole program ran on. The right copy reaches the right hands, unclaimed copies are visible instead of a mystery pile, and the last day of the program is orderly. It is the same one-roster spine that drove the ladder, the coverage, and the sale.
What does the platform cost a school?
The platform is free for the school to run — no subscription, no per-student fee, no setup charge. There is no live checkout on this page. When live selling is enabled, the platform is funded on the sale side — a small per-sale share of a printed-copy purchase — never by charging the school to use the software. This is a for-profit product and makes no tax claim of any kind.
How is student and family data handled?
Student and family data is owned by the school and is never sold to or shared with outside companies. Data involving minor students is consent-gated and never made public. Photos are tagged to students off the roster; facial recognition is off by default and never auto-tags a child’s photo without an explicit per-child opt-in from that child’s parent.
Related surfaces
Managing the program is one angle on a platform that also covers the staff, the whole write-to-read arc, and the studio side. These destinations cover the rest.
schoolyearbook.software
The all-in-one yearbook front door: design, staff roles, picture-day photos, sales, and print in one place — no contract, no vendor rep. Running the program is the operational view of that whole.
yearbook.software
The umbrella platform overview: write, design, photograph, proof, print, sell, give, and read, off one roster. It summarises every stage; this page goes deep on managing the program.
pholio.photos
The studio and photographer side: picture day and portraits. The portrait flow feeds the book’s coverage, and the photographer is one share of the sale’s four-way payout split.
homeroom.software
The flagship platform brand home: the full product story behind the roster, the sales rails, and every other surface the school runs on one platform.
What is built and what is honest-off
The ladder and page tracking, the table of contents, endsheets, and cover surfaces, and the coverage-gap report off the roster are built and production-ready. The deadline and proof-approval control — the fail-closed approval gate, version locking, and the read-only no-file proof link — is built and production-ready. The server-priced sales rails — scoped book types, deadline pricing windows, and the four-way payout split with an optional fundraiser cut — are built, and the sell-through reminder engine and print-run thermometer are built and production-ready. Automated pre-flight, press-ready PDF export, delivery tracking, and the distribution-day check-in are built and production-ready; the school picks its own print lab. The parts that move a family’s money — the live sell checkout and the print-order checkout — are honest-off: present but not enabled, and no card is charged. A family reserves a copy today. Mission-giving’s live checkout is honest-off as well. The platform is free for the school to run. This is a for-profit product and makes no tax claim of any kind. Student and family data is owned by the school, never sold or shared; minors’ data is consent-gated and never public; facial recognition is off by default. No competitor brand names appear here.