Yearbook FYI · plain answers for a first-time adviser and a parent
Straight answers about running a yearbook, in plain language.
Most yearbook help reads like it was written for someone who has done this for a decade. Yearbook FYI is the plain version: what a deadline actually means, how a page ladder works, why the spine size depends on your page count, what to check before you send to the printer, and how the whole write-to-print process fits together. It is a reference, not a sales tour — the answers are the kind of thing an adviser looks up mid-task, and on the platform they sit right next to the page you are building, so you do not leave your work to go searching. The platform is free for the school to run; where a question touches money, the answer says so plainly.
This is the reference angle. What is new and how to start today is at yearbook.today. The umbrella overview of every stage is at yearbook.software. There is no checkout on this page.
The basics, in plain language
The vocabulary trips up a first-year adviser more than the work does. These are the terms that come up first, answered the way you would want a colleague to explain them — short, plain, and true to how the process actually runs.
What is a page ladder?
The ladder is the map of your whole book: every page, numbered, with what goes on it — portraits here, the fall play there, sports in the back, the index last. You plan the ladder first so the book has a shape before anyone designs a single spread, and it is how a staff spreads coverage evenly instead of discovering in March that three grades never got a page. On the platform the ladder is a live surface that plans every page.
What does a deadline actually mean?
A yearbook has staggered deadlines, not one due date. Each signature — a batch of pages — is due to the printer on its own date so the press can schedule the run. Missing one does not just delay that batch; it compresses every deadline after it. The practical rule is to treat the first deadline as the real one: a book that is on pace in the fall is a book that is calm in the spring.
Why does the spine size depend on page count?
The spine is the bound edge, and its width is a function of how many pages the book has and the paper weight. More pages means a thicker spine, which changes the cover art that wraps it. That is why the page count is a decision you make early and try not to change late — a book that grows by 16 pages in April changes the spine, and the cover has to be re-fit to match.
What is a spread?
A spread is the two facing pages a reader sees at once — a left page and a right page designed as one unit. Designers work in spreads, not single pages, because the eye reads across the gutter. On the platform the production editor is a spread surface with layers, masking, and typography, so a designer builds the left and right together the way it will be seen.
What is bleed, and why does pre-flight check it?
Bleed is the little bit of image that extends past the trim edge so that when the printer cuts the page, colour runs all the way to the edge with no white sliver. A photo that stops exactly at the trim line risks a white edge after cutting. The automated pre-flight check flags resolution, bleed, and colour problems before export, so they are a checklist to fix rather than a rejection from the lab a week later.
What is a proof, and who signs off?
A proof is the book as it will print, reviewed before it prints. The adviser reviews spread by spread, comments, locks a version, and approves through a fail-closed gate — nothing advances to print until it is genuinely signed off. A read-only proof link lets a principal or the print lab see the current state without emailing a giant file. The adviser is the final sign-off.
How the whole process fits together
A yearbook looks like a hundred small tasks, but they follow one arc. Seeing the arc is what keeps a first-year staff from feeling like the work is random. Here is the shape of it, start to finish.
- Plan the ladder. Before anyone designs, you map every page — what goes where — so the book has a shape and coverage is spread evenly across the school and the year.
- Set up the staff and the roster. Import the roster once so it becomes the spine of the year, and assign the student roles so the room becomes a staff with clear jobs.
- Report and write. Stories move through a lifecycle — pitched, assigned, reporting, drafting, edited, and reviewed — so nothing that goes on a page is unaccounted for.
- Photograph across the season. Portraits come in off the roster, and events are captured all year, so the book is not built from whatever photos happen to exist in April.
- Design in spreads. Build the facing pages together in the editor — layers, masking, typography — against the ladder you planned, so every page has a home.
- Proof and approve. Review spread by spread, lock versions, and approve through the fail-closed gate. A read-only link shares the current state without a giant file.
- Pre-flight and print. Run the automated file check, export a press-ready PDF, and send it to whichever print lab you choose. Delivery is tracked from proof to fulfillment.
- Distribute. At handout, the check-in matches each book to a student off the same roster the whole book ran on, so the right copy reaches the right hands.
Deadlines and coverage, answered plainly
The two things that sink a first book are falling behind on deadlines and leaving parts of the school uncovered. Both are avoidable with a plan, and both come up as questions constantly.
How do I keep from falling behind?
Work to the ladder and the earliest deadline, not the final one. Assign pages to people with dates, capture events as they happen instead of reconstructing them later, and treat each signature deadline as real. A book built across the whole year is calm; a book crammed into the spring is the one that goes wrong.
How do I make sure everyone is covered?
Coverage is a planning problem, not a luck problem. The ladder lets you see, page by page, who is represented, and a coverage view off the roster shows who has not appeared yet. Plan for every grade, team, and club up front so no group is discovered missing when the book is nearly done.
What do I check before sending to the printer?
Run the pre-flight file check — it flags resolution, bleed, and colour issues before export. Confirm the page count matches the spine, that every page on the ladder is filled, that the proof is approved through the gate, and that names are spelled right. Then export the press-ready PDF and send it to your lab.
Can I use my own print lab?
Yes. The platform exports a press-ready PDF you send to whichever print lab fits your budget and timeline — you are not locked to one printer. Delivery is then tracked from proof to print run to fulfillment, so you always know where the order stands.
Cost and privacy, answered honestly
What does the platform cost? The platform is free for the school to run — no subscription, no per-student fee, no setup charge. You only pay when you print, at a price the school sets. We do not publish a price table here, because the print price is the school’s decision. There is no live checkout on this page. The parts that would move a family’s money — the sell, giving, and print-order checkouts — are honest-off: built, but not enabled, so no card is charged today. This is a for-profit product and makes no tax claim of any kind.
What about student photos and data? Student and family data is owned by the school, never sold or shared, and minors’ data is never public. Facial recognition is off by default and is never used for auto-tagging without an explicit per-child opt-in. When you tag a photo to a student, that is a lookup against the school’s roster — matching a face to a name on a list — not a face match. One school’s students are never visible to another school, enforced below the screens in the data layer.
Do we sign a contract or wait on procurement? No multi-year contract and no territory rep to start. You import the roster and begin. That is the honest shape of it: free to run, you pay only to print, and the school stays in control of its own data and its own price.
More common questions
I am a first-year adviser and I have never done this. Where do I start?
Start with the ladder and the roster. Import the roster once so it becomes the spine of the year, then plan the ladder — the page-by-page map of the whole book. With those two in place you have a shape to build against and a staff to assign, and the rest of the arc (report, photograph, design, proof, print) follows the ladder. You do not have to know everything on day one; you have to have a plan.
How many pages should our book be?
That is a school decision driven by how much you are covering and what you can produce on time, not a number we set. What matters mechanically is that the page count sets the spine width and the cover fit, so decide it early and try not to change it late. A smaller book finished well beats a bigger book that misses deadlines.
What is the difference between a portrait and an event photo?
A portrait is the posed picture from picture day, matched to a student off the roster and laid out on the portrait pages automatically. An event photo is a candid from the season — a game, a play, a club meeting — captured across the year and placed on the spreads you design. Both feed the same book; the portrait flow handles the first, and event capture handles the second.
What if we miss a deadline?
A missed signature deadline compresses every deadline after it, because the press schedules the run. The fix is to protect the early deadlines: assign pages with dates, capture events as they happen, and keep the ladder full as you go. If you are behind, tighten scope rather than adding pages — a complete smaller signature beats an unfinished larger one.
Do parents get answers here too?
Yes. Parents often ask the same practical questions — when the book comes out, how photos are handled, whether their child’s data is private. The short version: the school owns and controls the data, minors’ data is never public, facial recognition is off by default, and photo tagging is a roster lookup, not a face match. For anything specific to a school’s calendar or price, ask that school — those are the school’s decisions.
Is any of this locked behind a paid plan or a course?
No. The guidance is part of the product, not a paid course, and the answers sit next to the page you are building rather than in a separate manual you buy. The platform is free for the school to run; you only pay when you print, at a price the school sets. There is no upsell on this reference.
How is this different from yearbook.today?
yearbook.today is the news view — what is shipping on the platform now and how to start a book the same day. Yearbook FYI is the reference: plain answers to the recurring questions about running a book, organized as a knowledge base you read when you are stuck. One is the what-is-new; this is the how-does-it-work.
Still stuck?
If your question is not answered here, it is not a failing on your part — yearbook advising has a steep learning curve, and asking for help is the right move, not an admission of being in over your head. There is a human wrap around the software: onboarding, training, and real help from former advisers who remember what the first year felt like. That lives at yearbook.services, and you can reach a person directly through the contact link below. We do not advertise a response time, because we would rather be plain than promise an operation we have not stood up — but a real person reads what you send.
Related surfaces
This reference sits alongside the news view, the umbrella overview, and the services wrap. These destinations go deeper on the platform the answers describe.
yearbook.software
The umbrella platform overview: write, design, photograph, proof, print, sell, give, and read, off one roster. The full arc these answers describe.
yearbook.today
The news view: what is shipping on the platform now and how to start a book the same day. Read this reference for the how; read Today for the what-is-new.
yearbook.services
The services around a program: onboarding that imports the roster once, training, adviser help from former advisers, proofing support, and print fulfillment. Where to go when a reference answer is not enough.
homeroom.software
The flagship platform brand home: the full product story behind the roster, the editor, and every surface the school runs on one platform.
What is built and what is honest-off
The answers here rest on real platform behaviour: one-roster import as the spine of the year, the page ladder that plans every page, the production editor with spread layout, layers, masking, and typography, the roster-driven portrait flow and season-long event capture, the fail-closed proof gate with a read-only no-file proof link, and print pre-flight and press-ready export with delivery tracking are all built and production-ready. The school picks its own print lab. Facial recognition is off by default and never auto-tags without a per-child opt-in; photo tagging is a roster lookup, not a face match. The parts that move a family’s money — the sell, giving, and print-order checkouts — are honest-off: built, but not enabled, and no card is charged. The platform is free for the school to run; you only pay when you print, at a price the school sets. 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 never public. No competitor brand names appear here.