Yearbook Work · for student editors & advisers · free for schools

The desk where the spread actually gets made — and proofed until it’s right

Assignment is someone else’s screen. This is the chair you sit in to do the work: pull the spread, place the photos, pin the corrections, drive the open-note count to zero, and sign it off behind a gate that will not let an un-approved or un-proofed page reach the press. Then the pre-flight flags the resolution or colour problem before the file leaves for your lab — not after. Built for the people who have to get it right the first time.

Proof sheet
GateFail-closed sign-offNo spread reaches the press-ready export with an open note or an un-approved version — enforced at the engine.
ZeroOpen-note countProofing is a number, not a vibe. The loop is done when pinned corrections reach zero.
Pre flightCaught before the labResolution, colour space, fonts, bleed, margin, and overset flagged before export — pointing at the object.
FreeNo per-student feeFree for the school. Families who want a printed copy pay for it — that checkout is honest-off today.
01

The bench

A real production surface, not a template picker

A consumer photo-book wizard is built for a family making a holiday album. A school yearbook is several hundred portrait entries, a staff of twenty, an adviser who must approve every spread, a consent rule on every face, and a file a commercial lab has to print on schedule. Those are production problems, so the desk is a production surface.

The bench

The spread opens on a real production surface, not a template picker: independent layers with their own opacity and blend, object masking, spread-level undo, and a version history you can roll back to any saved state. Typography controls live at the spread, not a global theme switch, so a caption size fixed on one page does not silently re-flow forty others. The same bench lays out the yearbook, the newspaper, and the literary magazine — one editor the staff learns once. Built and production-ready.

Built · live

The proof loop

A proof is not a PDF someone emails around. A reviewer opens the spread and pins a note to the exact spot — a crooked portrait, a misspelled name, a caption that runs past the safety margin. Each note is a thread the staffer can reply to and mark resolved, and every spread carries an open-note count you can see at a glance. The loop is done when that count reaches zero. Built and production-ready.

Built · live
02

The proof loop

Corrections are pinned to the spot — and counted down to zero

A proof is not a PDF someone emails around and hopes gets read. A reviewer opens the spread on a read-only proof link — they can see the page and pin a note, but they cannot move an object or edit the file by accident. Each note lands on the exact spot that is wrong, becomes a thread the staffer can reply to, and gets marked resolved when it is fixed. Every spread carries an open-note count. The loop below is finished when that count hits zero — and the sign-off gate will not let it be approved before then.

The proof loop

A proof is not a PDF someone emails around. A reviewer opens the spread and pins a note to the exact spot — a crooked portrait, a misspelled name, a caption that runs past the safety margin. Each note is a thread the staffer can reply to and mark resolved, and every spread carries an open-note count you can see at a glance. The loop is done when that count reaches zero. Built and production-ready.

Built · live
03

The sign-off gate

Fail-closed approval, and version locking that holds it

Approval is enforced at the engine, not by a habit anyone can forget. A spread with any open note, or any version that has not been approved, physically cannot reach the press-ready export. When the adviser approves a spread, version locking pins that exact version — and if anyone edits it afterward, a new version opens and the spread returns to “needs approval.” What the adviser signed off is what goes to the lab.

The gate reads the open-note count and the approval state. Green only when both clear.

The sign-off gate

Approval is enforced at the engine, fail-closed: a spread with any open note, or any un-approved version, cannot reach the press-ready export — there is no honour-system checkbox to forget. When the adviser approves a spread, version locking pins that exact version; a later edit opens a new version and returns the spread to “needs approval,” so an approved page can never quietly change under the approval. Built and production-ready.

Built · live
04

Pre-flight & press-ready export

The lab’s rejection reasons, caught at the desk instead

The automated pre-flight check runs before the file leaves, not after the lab bounces it. It flags exactly the problems a school yearbook ships with, and each flag points at the specific spread and object so a student editor can fix it without a pre-press background:

  • A portrait whose effective resolution falls below the print threshold.
  • An image still in screen RGB instead of the print colour space (ICC).
  • A font that is not embedded and would substitute at the lab.
  • Missing bleed, or text and key objects inside the safety margin.
  • Overset text hidden in a box that would drop a caption.

When the book is approved and pre-flight is clean, the export writes a single press-ready PDF with printer marks — crop marks, bleed, and registration — in the print colour space, fonts embedded. You take that file to whichever commercial lab you already use; the book is not locked to one printer.

Pre-flight

The automated pre-flight check runs before the file leaves the desk, not after the lab rejects it. It flags the problems a school yearbook actually ships with: a portrait whose effective resolution falls below the print threshold, an image still in screen RGB instead of the print colour space, a font that is not embedded, missing bleed, text or a key object inside the safety margin, and overset text hidden in a box. Each flag points at the spread and the object, so a student editor can fix it without a pre-press degree. Built and production-ready.

Built · live

Press-ready export

When the book is approved and pre-flight is clean, the export writes a single press-ready PDF with printer marks — crop marks, bleed, and registration — in the print colour space, with fonts embedded. The school is free to take that file to whichever commercial print lab it uses; the platform does not lock the book to one printer. The file is built to press standard from the start, so it does not need to be “adjusted to survive” a consumer export. Built and production-ready.

Built · live
05

Portraits & consent

Matched by roster and filename — never by comparing faces

Portrait slots populate from the school roster, imported once at the start of the year. A portrait is matched to a name by roster and filename — not by a face comparison; no facial recognition runs in the portrait pipeline. Consent is checked at the data layer: a student whose family has not consented to publication is withheld from shared spreads automatically, so a staffer does not have to remember, and consent can be withdrawn at any time.

06

A desk session

One spread, from “laid out” to “press-ready and approved”

This is the loop you run at the chair, once per spread, many times a week. It is not a year-long calendar — that belongs to the program board. It is the five moves that take a single spread the last mile.

  1. Place

    Pull the assigned spread. Portrait slots are already sitting on the page from the roster; drop in the candids, size them on the grid, write the captions. The layers, masking, and typography controls are the bench you already know.

  2. Send to proof

    Mark the spread ready for review. It joins the proof queue with an open-note count of zero and a read-only proof link — a reviewer sees the spread, not the editable file, and cannot move anything by accident.

  3. Work the redlines

    The reviewer pins notes to the exact spots that are wrong. Back at the desk you fix each one and mark it resolved; the open-note count ticks down. The loop is not “I think it’s fine” — it is a number, and the number has to reach zero.

  4. Sign off

    With zero open notes, the adviser approves the spread. Version locking pins that exact version. If anyone edits it afterward, a new version opens and the spread returns to “needs approval” — the gate never lets an approved page change under the approval.

  5. Pre-flight & export

    Before the book leaves, the automated pre-flight check flags any resolution, colour-space, font, bleed, margin, or overset problem, pointing at the spread and object. Clean the flags, and the press-ready PDF exports with printer marks for whichever lab the school uses.

07

Two chairs at the desk

The student editor makes it; the adviser signs it

Student editorDoing the pages

You get a scoped canvas — your section, your spreads — on a bench you learn once and reuse for the newspaper and the lit mag. You place, caption, and clean up the pre-flight flags, and you watch your open-note count fall to zero. You cannot ship an un-approved page, and nobody can quietly change one you finished.

AdviserHolding the gate

You hold approval authority, and the fail-closed gate enforces it — nothing reaches the export without your sign-off. You can grant a section editor or editor-in-chief approval for their own section, and version locking guarantees that what you approved is what prints. The consent rule runs at the data layer, so a non-consented student never lands on a shared spread by mistake.

08

What is honest-off today

The rails we have not wired — said plainly, not dressed up as “coming soon”

Two capabilities a yearbook desk might expect are deliberately not wired from this product today. We would rather name them here than show a button that cannot do the thing.

Honest-off

Print-order checkout

The interface where a family pays for a printed copy is not wired — the money rail is founder-gated. The yearbook is free for the school; revenue from printed copies is described plainly, with no live checkout on this page.

Honest-off

Outbound proof email

No email is sent from this product today. What the staff see is the desk itself — the proof queue, the read-only proof link, and the open-note count on each spread — not a message we cannot actually send.

Start your book

Bring your roster and a pile of photos — we’ll set up the desk

Yearbook Work is free for the school. Tell us about your program and we will walk you through the bench, the proof loop, and the sign-off gate on your own book — no per-student fee and no annual contract to start.

FAQ

Common questions

The questions a staff actually asks

Is this the same thing as the deadline board?

No, and it is deliberately separate. The board — who is assigned to which spread, which pages are behind, the coverage report — lives at yearbook.management. Yearbook Work is the desk where the person already assigned does the making and the proofing: place the photos, work the redlines to zero, sign off, pre-flight, export. This page tracks a spread’s state, not a staffer’s punctuality.

What does “fail-closed” approval actually mean here?

It means the gate is enforced at the engine, not by a habit. A spread with any open proofing note, or any version that has not been approved, physically cannot reach the press-ready export. There is no checkbox an editor can tick to skip it and no build step that quietly proceeds anyway. The safe failure direction is “not exported yet,” never “shipped un-approved.”

If I edit a spread after it’s approved, does the approval still stand?

No. Approval uses version locking: the approval is pinned to the exact version that was approved. The moment someone edits that spread, a new version opens and the spread returns to “needs approval.” An approved page can never change under its own approval, so what the adviser signed off is what goes to the lab.

What does the pre-flight check catch?

The problems a school yearbook actually ships with: a portrait whose effective resolution is below the print threshold, an image still in screen RGB instead of the print colour space, a font that is not embedded, missing bleed, text or a key object inside the safety margin, and overset text hidden in a box. Each flag points at the specific spread and object so a student editor can fix it without a pre-press background.

What is a press-ready PDF, and can we use our own printer?

A press-ready PDF is a single file in the print colour space with fonts embedded and printer marks — crop marks, bleed, and registration — that a commercial lab can print without re-work. Yes, you use your own printer: the platform exports the file and the school submits it to whichever lab it already works with. The book is not locked to one printer.

How are portraits placed — do you scan faces?

No face scanning. Portraits are matched to names by the school roster and the filename, not by comparing faces. No facial recognition runs in the portrait pipeline. The roster is imported once and drives which slots exist on which spreads.

What happens to a student whose family didn’t consent?

They are withheld from shared spreads automatically, at the data layer — a staffer does not have to remember. Consent is checked when portraits populate, and it can be withdrawn at any time, which removes the student from shared spreads going forward. Student portrait and student data is never sold or shared with outside companies.

Can a reviewer break the layout while proofing?

No. A proof link is read-only: the reviewer sees the rendered spread and can pin notes, but cannot move objects, change type, or edit the file. Only the staffer at the editable bench makes changes, and only in response to the resolved notes.

Does the family pay for a printed copy through this page?

Not today. The print-order checkout — where a family would pay for a printed book — is honest-off: the money rail is founder-gated and is not wired. We will not show a paid checkout that cannot take a payment. The yearbook is free for the school; revenue from printed copies is described plainly, with no live checkout.

Does Yearbook Work email proofs and reminders to staff?

No outbound email is sent from this product today — that rail is honest-off. What the staff see is the desk itself: the proof queue, the read-only proof link, and the open-note count on each spread. We would rather show you the real state on the page than claim an inbox we do not send from.

Who has final approval on the book?

The adviser account holds approval authority, and the fail-closed gate enforces it. An adviser can grant a section editor or a student editor-in-chief approval authority for their own section, but the gate enforces whoever holds the approval role — not an honour system, and not a build step that ships whatever is there.

Is this a different tool from the newspaper and the lit mag?

No — it is the same bench. The multi-surface editor lays out the yearbook, the newspaper, and the literary magazine on one production surface the staff already knows, so a student editor does not learn three tools. One editor, one proof loop, one export.