Book a demo

Yearbook Tips · practical advice for a stronger book

The habits that make a yearbook good, not just done.

Yearbook Tips is the practical-advice side of running a school yearbook on the platform. Getting a book finished and getting a book right are two different jobs, and the difference is mostly habits: covering the whole school and not just the loudest twenty students, building a ladder and actually holding it, planning deadlines backward from the print date, and reaching the families who have not ordered before the window closes. Every tip here is grounded in a real, built part of the platform — it names the good habit and points at the tool that supports it. When you want advice on your own situation, there is a form that records your question and hands it to a person.

This is the best-practices hub. Mid-year how-to answers when you are stuck are at yearbook.support. Getting an adviser and staff set up is at yearbook.training. The sell-through reminder engine itself is at yearbook.marketing. The platform is free for the school; there is no live checkout on this page.

Four habits of a strong book

Most of what separates a good yearbook from a merely finished one comes down to four habits: cover everyone, hold the ladder, plan deadlines backward, and sell through to the families who have not ordered. Each one below names the habit and points at the built tool that supports it.

Coverage: the whole school, not the loudest twenty

The most common yearbook regret is a book that covers the same students on every spread. The habit that fixes it is checking coverage against the roster all year, not at the end. The coverage-gap report reads the roster against the photos tagged so far and shows which students and groups are not yet on a spread — while there is still time to send someone to shoot them. The report is built and production-ready. Built

The ladder: build it, then hold it

A ladder is the plan of every page — what goes where, who owns it, and whether it is done. Building one is easy; holding it is the discipline. The habit is treating the ladder as the single source of truth the whole staff reads, not a diagram drawn once and forgotten. The ladder lives in the editor and is the view an adviser reads all year. Built

Deadlines: plan backward from the print date

The print date is the one deadline that does not move, so every other deadline is set by working back from it: coverage complete, spreads drafted, copy edited, proofs approved, file pre-flighted and exported. The habit is writing that plan down in September. The proof gate and the automated pre-flight are the built checkpoints the plan runs through. Built

Sales: reach the families who have not ordered

A book sells better when the reminder goes to the families who have not ordered rather than the whole school again. The order rails resolve every price server-side, support scoped books (whole-school, grade, class, club) and deadline windows, and the sell-through reminder engine targets roster-minus-orders. The engines are built; the live sell checkout that charges a card is honest-off. Built · live checkout honest-off

Practical tips, in the order the year needs them

These are the small habits that add up to a book a school is proud of. Each is grounded in a built part of the platform.

  1. Start capturing coverage in September, not April. A book that photographs events all year has material to work with; a book that starts in spring reconstructs the year from memory. Tag photos to students off the roster as events happen, so the coverage-gap report has something to read while there is still time to fix a gap.
  2. Read the coverage-gap report every month. The report shows which students are not yet on a spread. Reading it monthly turns coverage from an end-of-year panic into a steady assignment — send a photographer to the students the report flags, and no one gets left out of their own yearbook.
  3. Assign every page on the ladder to a person. A page with no owner is a page that slips. Build the ladder as a staff and put a name on every spread, so the question is never “who was doing that?” the week before deadline.
  4. Lock the theme and the big decisions early. The decisions that are painful to change — the theme, the cover direction, the ladder’s shape — are cheapest to make in September. Locking them early is what keeps a redesign from eating March.
  5. Write the deadline plan backward from the print date. Set the print date first, then work back: proofs approved by here, spreads drafted by there, coverage complete before that. A plan on paper is the difference between a deadline and a scramble.
  6. Practise the proof gate before the real deadline. Walk the fail-closed approval and the read-only proof link on a spread or two early, so the workflow is familiar when it matters. Learning the gate under pressure is the hard way in.
  7. Sell to the families who have not ordered, not the whole school again. The sell-through reminder engine targets roster-minus-orders, so a reminder reaches only the families who still need to order. That is more effective and less annoying than mailing everyone twice.
  8. Use scoped books to reach more of the school. A family that will not buy a whole-school book might buy a single class book or a club book. The order rails support scoped book types and deadline pricing windows, so you can meet different families where they are.
  9. Pre-flight early, not the night before. Run the automated pre-flight check on spreads as they finish, so resolution, bleed, and colour problems surface as a checklist you fix over weeks — not a rejection from the lab the night before the deadline.
  10. Plan distribution day like an event. The check-in matches each book to a student off the roster, so plan the handout so the line moves and unclaimed copies are visible. The last day should be a celebration, not a scramble.

Coverage, in more depth

Coverage is the tip advisers ask about most, so it is worth going a little deeper. The goal is simple to say and hard to do: every student in the book, more than once if you can, across the real range of what the school did this year.

Count students, not photos

A spread can be full of photos and still show the same fifteen faces. The coverage-gap report counts students against the roster, not photos on a page, so it catches the quiet student who is technically in three group shots and never named. That is the count that matters for a book that belongs to the whole school.

Cover the whole year, not one season

Fall sports and the winter dance are easy to over-cover because they happen when energy is high. Tag events across the whole calendar off the roster, so spring clubs and late-year moments get the same attention. A book weighted to one season reads like a half-finished year.

Fix gaps while there is time

The value of reading the report monthly is that a gap in February is fixable — send a photographer, schedule a make-up, plan a spread. A gap found in April is a regret. The report exists to move the discovery earlier, where it can still change the book.

Tag by hand, keep recognition off

Photos are tagged to a student off the roster by a person. Facial recognition is off by default and never auto-tags a photo without a per-child opt-in from that child’s parent. Tagging by hand is a little more work and a lot more honest — and consent can be withdrawn at any time.

Selling the book without nagging the whole school

Selling a yearbook well is not about sending more reminders, it is about sending the right ones to the right families. The habit that works is targeting: reach the families who have not ordered, and leave the ones who already have alone.

The order rails resolve every unit price server-side, so what a family sees is what would bill — the buyer never types in an amount. A school can offer a whole-school book, a grade book, a single class book, or a club book, and run an early-bird-to-deadline price schedule, so different families can find the book that fits. The sell-through reminder engine targets roster-minus-orders, so a reminder reaches only the families who still need one. That is more effective than mailing the whole school again, and it respects the families who already bought.

The honest part: every one of those engines — the server-priced order rails, the scoped book types, the deadline windows, the four-way payout split, and the sell-through reminders — is built and production-ready, but the live sell checkout that charges a family’s card is honest-off. A family reserves a copy today; no card is charged. The platform is free for the school to run, and when live selling is enabled it is funded on the sale side, never by charging the school. The deep dive on the reminder engine itself is at yearbook.marketing.

Ask for advice on your situation

The tips above are general; your book is specific. If you want advice on a real situation — a coverage problem, a ladder that keeps slipping, a deadline plan you are unsure of, a sales window that is not moving — use the form. To be plain about what this is: it is a request intake, not a live chat and not a ticketing queue with a promised response time. When you send it, it records your request and a person gets back to you. There is no instant-answer bot behind it, and this page does not promise how fast the reply comes — a real person reads what you wrote and responds.

Tip requests are handled here. Support questions are best sent from yearbook.support, but either is fine.
Used only to reply to this request. Never sold or shared.

This form records a request and hands it to a person. It is not a live chat, and no response-time guarantee is made here. Contact information is used only to respond to this request; see the footer for the full privacy note.

Or email directly: [email protected].

Common questions

Is the advice form a live chat or a ticket with a response time?

No. The form on this page is a request intake: it records your question and hands it to a person who reads it and replies. It is not a live chat, and we do not advertise a response-time guarantee or a formal support tier here, because we would rather be honest about the help than promise an operation we have not stood up. A real person answers, not a bot.

How do I make sure the book covers the whole school?

Read the coverage-gap report monthly, not at the end. It counts students against the roster and shows which ones are not yet on a spread — while there is still time to send a photographer. Count students, not photos: a spread can be full of images and still show the same fifteen faces. The report is built and production-ready.

What is a ladder and why does it matter?

A ladder is the plan of every page — what goes where, who owns it, and whether it is done. It matters because a page with no owner slips, and a book with no plan drifts. Build it as a staff, put a name on every spread, and treat it as the single source of truth the whole staff reads. The ladder lives in the editor.

How should I plan deadlines?

Backward from the print date, the one deadline that does not move. Set the print date, then work back: proofs approved by here, spreads drafted by there, coverage complete before that. Write it down in September. The proof gate and the automated pre-flight are the built checkpoints the plan runs through.

How do I sell more books without nagging everyone?

Target the families who have not ordered. The sell-through reminder engine works off roster-minus-orders, so a reminder reaches only the families who still need one — more effective and less annoying than mailing the whole school again. Scoped books (grade, class, club) and deadline pricing windows help different families find a book that fits. The engines are built; the live sell checkout is honest-off.

Can a family buy a book from these tips?

Not from this page. The order rails, scoped books, deadline windows, and the reminder engine are built, but the live sell checkout that charges a card is honest-off, and there is no live checkout here. A family reserves a copy; no card is charged. The platform is free for the school to run.

When should we run pre-flight?

Early and often, not the night before. Run the automated pre-flight check on spreads as they finish, so resolution, bleed, and colour problems surface as a checklist you work over weeks. Catching a file problem in February is a fix; catching it the night before the deadline is a crisis.

Is facial recognition a shortcut for coverage?

No, and we would not recommend it as one even if it were on. Facial recognition is off by default and never auto-tags a photo without a per-child opt-in from that child’s parent. Photos are tagged to a student off the roster by hand. It is a little more work and a lot more honest, and consent can be withdrawn at any time. Student and family data is owned by the school and never sold or shared.

Where do I go for step-by-step help versus onboarding?

Mid-year, when you are stuck on a specific how-to, the help desk at yearbook.support takes the question and hands it to a person. Getting an adviser and a staff set up in the first place is the onboarding-and-training hub at yearbook.training. This page is the practical advice: the habits of a strong book, plus a way to ask for advice on your own situation.

Does any of this cost the 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. This is a for-profit product and makes no tax claim of any kind. When live selling is enabled on the wider platform, it is funded on the sale side, never by charging the school for the software.

Related surfaces

The tips are the advice side of a strong book. The help desk, the onboarding path, and the full platform each have their own home. These destinations cover the rest.

yearbook.support

The mid-year how-to help hub: plain answers to the questions an adviser types when stuck, plus a request-intake form that hands the question to a person.

yearbook.training

The onboarding-and-training hub: getting an adviser and the student staff up to speed, the onboarding path, role training, and deadline planning.

yearbook.marketing

The sell-through reminder engine: roster-minus-orders targeting and the print-run thermometer. The deep dive on reaching the families who have not ordered.

yearbook.software

The umbrella platform overview: write, design, photograph, proof, print, sell, give, and read, off one roster. The whole arc the tips lean on.

What is built and what is honest-off

The platform these tips lean on is real: the one-roster foundation, the production editor and the ladder, the coverage-gap report, the newsroom editorial workflow, the proof-approval gate with version locking and the read-only no-file proof link, automated pre-flight and press-ready PDF export with delivery tracking, the distribution-day check-in, the server-priced order rails (scoped book types, deadline windows, a four-way payout split), and the sell-through reminder engine (roster-minus-orders targeting) are built and production-ready. The request-intake form on this page records a question and hands it to a person — it is not a live chat, not a ticketing queue, and no response-time guarantee is made. The parts that move a family’s or a donor’s money — the live sell checkout and the live giving checkout — are honest-off: present but not enabled, and no card is charged. 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.