Yearbook Training · onboarding, role training, and deadline planning
Get the adviser and the staff ready to run the book.
Yearbook Training is the onboarding hub for running a school yearbook on the platform. A first-year adviser gets handed a binder, a deadline, and a room full of students — and the fastest way through that is not decoding a manual alone, it is a clear path: import the roster, set up the staff roles, build the ladder, and learn the tool each person actually uses. This page walks that path, trains each role on its part of the platform, and lays out a deadline plan for the year, so the class spends its time making the book instead of fighting the software. Everything trained here is a built part of the platform, described plainly.
This is the training-and-onboarding hub. Mid-year how-to answers when you are stuck are at yearbook.support. Practical best-practices advice is at yearbook.tips. Running the program as a graded class is at yearbook.education. The platform is free for the school; there is no live checkout on this page.
Training tracks by role
A yearbook staff is not one job, it is several. Training is organised by the role a person plays and the part of the platform that role actually touches. Each track below trains on a built surface, described plainly — not a certification, just the working knowledge to do the job.
The adviser, first
The adviser learns the shape of the whole program before the staff arrives: how the roster becomes the spine of the year, how the ladder plans every page, how the proof gate and version locking hold quality, and how the year ends at pre-flight, export, and distribution. The goal is an adviser who can answer a student’s question without stopping to look it up. The tools trained on are built and live. Training · on built tools
The editorial staff
Section editors, copy editors, and the editor-in-chief learn the newsroom workflow — a story moves from pitched to assigned to reporting to drafting to copy-edit to design to editor-in-chief sign-off to adviser review to published. Roles are scoped at the data layer, so a section editor cannot overwrite another section. Training is learning the lane you own and the handoff to the next one. The workflow is built and production-ready. Training · on built tools
The design staff
Designers learn the production editor: spread layout, layers, masking, typography, and the structural surfaces — the ladder, the table of contents, the endsheets, and the cover. They learn it on the resilient online workspace, where many editors work in parallel without overwriting each other and every change autosaves. The editor and workspace are built and live. Training · on built tools
The photo staff
Photo editors learn to bring photos in from every event and tag them to the right student off the roster, and to read the coverage-gap report that shows which students are not yet on a spread before the deadline. They learn the honest rule too: facial recognition is off by default and never auto-tags a photo without a per-child opt-in. Event capture, tagging, and the coverage-gap report are built. Training · on built tools
The onboarding path, step by step
Standing a program up follows the same order every year. Here is the path from an empty program to a staff that can build the book.
- Import the roster once. The school’s roster is imported a single time, in the format the student information system exports, and becomes the spine of the whole year. Every later stage keys off it — the portrait flow, event tagging, the class-book scope, sell-through, and the distribution check-in — so the first onboarding step is getting that one import right.
- Set up the staff and their roles. Assign the student roles off the roster: editor-in-chief, section editors, photo editors, copy editors. Roles are scoped at the data layer, so each person can work in their lane without overwriting another section. The room becomes a staff with a clear map instead of a blank editor and a hope.
- Build the ladder together. The ladder is the plan of every page — what goes where, who owns it, and whether it is done. Building it early, as a staff, is what turns a vague idea of the book into a concrete assignment for every person. It is also the single view the adviser reads all year to see what is finished and what is open.
- Learn the tool you own. Each role trains on its surface: editorial staff on the newsroom workflow, designers on the production editor, photo editors on tagging and the coverage-gap report. The point of role-based training is that nobody has to learn the whole platform — just the part they use well.
- Practise the proof gate before it matters. The adviser and the editor-in-chief walk the proof-approval gate on a spread or two early, so the fail-closed approval and the read-only proof link are familiar before the real deadline. Learning the gate under pressure is the hard way; learning it in September is the easy way.
- Set the deadline plan. With the ladder built and roles assigned, lay out the deadlines backward from the print date: coverage complete, spreads drafted, copy edited, proofs approved, file pre-flighted and exported. A plan on paper in September is what keeps March from becoming a scramble.
Planning the year backward from the print date
The one deadline that does not move is the print date. Every other deadline is set by working backward from it. Here is the shape of a plan a staff can adapt to its own calendar.
Early year: coverage and the ladder
The first stretch is about the plan and the photos, not finished spreads. Build the ladder, assign every page, and start capturing events off the roster so the coverage-gap report has something to read. A book that starts capturing in September is not reconstructing the year from memory in April.
Mid year: draft the spreads
With coverage flowing in, the staff drafts spreads in the production editor, and the newsroom workflow carries stories from reporting to copy-edit to design. The autosave and parallel editing on the online workspace mean many students build at once without a crashed lab computer losing a spread.
Late year: proof and approve
As spreads finish, the adviser reviews and approves through the fail-closed gate, and the coverage-gap report gets a final read so no student is left off. The proof link lets a principal see the current state without a giant file. This is the stretch the early practice pays off.
Deadline: pre-flight, export, deliver
At the print deadline the platform runs the automated pre-flight check and exports a press-ready PDF the school sends to the lab it chooses. Delivery is tracked from proof to print run to fulfillment, and the year ends with the distribution-day check-in matching each book to a student.
When training is not enough on its own
Some of the year is learning the tool, and some of it is judgement that no tool teaches: how much coverage is enough, which decisions to lock in September, how to read a room of students under a deadline. That is where a person who has advised a yearbook before is worth more than any walk-through.
Former advisers and production veterans help with exactly those calls — the ladder, spreading coverage across the year, the decisions to lock early, a theme that holds the book together, and the print-order numbers before you commit. It is a human service around the built platform, described plainly: not a chatbot and not a promise of instant answers at any hour, just people who remember what the first year felt like.
If a mid-year question comes up while you are working, the how-to help hub at yearbook.support takes the question and hands it to a person. Training gets you started; the help hub is there when you are already going.
Common questions
Is this a certification or a graded course?
No. Yearbook Training is a practical onboarding path, not a certification and not a graded course. There is no completion certificate to earn here. It is the working knowledge an adviser and a staff need to run the book — organised by role so nobody has to learn the whole platform, just the part they use. Running the program itself as a graded class is a separate thing, at yearbook.education.
Where should a brand-new adviser start?
With the onboarding path: import the roster once, set up the staff roles, build the ladder, and learn the proof gate before the deadline makes it urgent. The adviser learns the shape of the whole year first, then each student trains on the one surface their role uses. Starting with the path, not the manual, is the fastest way in.
How is training organised for the student staff?
By role. Editorial staff learn the newsroom workflow — a story moving from pitched to published — and the lane they own. Designers learn the production editor and the structural surfaces. Photo editors learn tagging off the roster and the coverage-gap report. Roles are scoped at the data layer, so training a student on their lane does not risk another section’s work.
What does the deadline plan look like?
It is built backward from the print date, the one deadline that does not move. Early year: build the ladder and start capturing coverage. Mid year: draft spreads and run stories through the newsroom workflow. Late year: proof and approve through the fail-closed gate and do a final coverage-gap read. Deadline: pre-flight, export a press-ready file, and deliver. A plan on paper in September is what keeps March calm.
Do students need to learn the whole platform?
No, and that is the point of role-based training. A photo editor does not need the production editor; a designer does not need the newsroom pitch flow. Each person learns the surface their role touches. The adviser is the one who learns the shape of the whole year, so they can answer a student without stopping to look it up.
How does the online workspace protect the staff’s work during training?
Every change autosaves as it happens, presence shows who is in which section, and a section assignment gate at the data layer stops two editors overwriting each other. Any saved state of a spread is recoverable, so a staff can experiment and roll back. That resilience is exactly what makes training on the real tool safe — a mistake during practice is recoverable, not fatal.
Is facial recognition part of photo training?
The honest rule is trained, not a shortcut. Facial recognition is off by default and is never used to auto-tag a photo without an explicit per-child opt-in from that child’s parent. Photo editors are trained to tag photos to a student off the roster by hand, and consent can be withdrawn at any time. Student and family data is owned by the school and never sold or shared.
Can we get help from someone who has advised before?
Yes. Former advisers and production veterans help with the judgement calls that no walk-through teaches — the ladder, coverage, the decisions to lock early, the theme, and the print-order numbers. It is a human service around the built platform, described plainly: not a chatbot and not a promise of instant answers, just people who have done it before.
Does training cost anything?
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. If you want to know what a specific human service around the software involves, get in touch and we will be plain about it.
What is the difference between this page and yearbook.support?
Yearbook Training is the onboarding path and role training — how a program stands up and how each person learns their part of the tool, before and at the start of the year. yearbook.support is the how-to help desk for the questions an adviser types when they are already mid-year and stuck, plus a way to reach a person. Training gets you started; support keeps you going.
Related surfaces
Training gets a staff started. The how-to help desk, the practical advice hub, 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. Where you go once you are already going.
yearbook.tips
The practical best-practices hub: how to spread coverage across the year, build a ladder, plan deadlines, and sell through. The advice side of running a strong book.
yearbook.education
Running the yearbook as a graded class: student roles with scoped access, coverage accountability, an adviser feedback loop, and a skills record a student can carry to a resume.
yearbook.software
The umbrella platform overview: write, design, photograph, proof, print, sell, give, and read, off one roster. The whole arc the training teaches.
What is built and what is honest-off
The platform this training teaches is real: the one-roster foundation, the scoped staff roles and the newsroom editorial workflow, the production editor and the ladder, the coverage-gap report, 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, and the resilient online workspace (autosave, parallel editing, the assignment gate, version recovery) are built and production-ready. The adviser help from former advisers is a genuine human service around the software, described honestly — not a certification, not a graded course, and no invented trainer roster. The parts that move a family’s or a donor’s money — the live sell checkout and the giving / print-order 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.