A school year, made into something lasting
The yearbook platform
Plan / Make / Review / Keep
The names, the photographs, the stories people will read years from now. Yearbook.software brings the work of making that book into one platform, from the first page plan to the files and records that close the project.
Give your staff a structure, your design a consistent direction and every production decision a result someone can review. Explore the engines in detail, including what they calculate, what they save and where they refuse an action.
01 The whole platform
The work moves between people and disciplines. These eight stages provide a useful route through the platform; each has its own inputs, decisions and finished result.
Move a story through defined editorial stages, review its checklist and retain an approval record. A finished draft still needs the appropriate sign-off before it can move forward.
Save the book's color and font policy, organize its sections and distinguish required material from optional composition choices. A saved design rule and a checked finished page are different results.
Review the student references and coverage records behind the book. Use the worklist to plan follow-up reporting and photography, then verify names and the intended use of each image.
Identify the content being approved, inspect unresolved findings and distinguish editorial acceptance from a production file. A proof decision should have a clear version and an accountable reviewer.
Inspect the cover and interior outputs, their preflight results and the recorded state of each signature. Marking a signature submitted does not itself transmit a file to a printer.
Review pages, binding, quantity, price and the basis of a cost estimate. Keep an economics calculation, a contract record and a payment outcome separate when evaluating the financial workflow.
Define the books or students the program intends to support and inspect the actual records behind any commitment. A funded count or pending order does not establish that a donation or payment was collected.
Distinguish the working book from a generated PDF, a digital flipbook and a structured manifest. Review the artifact that was actually produced and the audience authorized to receive it.
The examples in this guide are illustrative. Feature descriptions identify specific workflows and conditions, not a claim that every connected service is active for every school.
02 Plan the year
The setup wizard turns a set of book choices into a section ladder, a portrait budget and signature-aware page math. Staff can see the planning assumptions before they begin treating a target page count as a finished production specification.
The plan can follow class and grade, traditional sections, chronological coverage, a theme or a blended approach. Class-and-grade organization creates grade portrait blocks alongside school events and recognition material. Chronological organization can use seasons, months or week groups, with a separate People block. The organizing choice gives coverage a destination.
Education level and theme intensity also shape the plan. A lighter treatment changes the division and opening material. The planning engine identifies components such as the cover, title page, contents, divisions and index according to the chosen structure. The returned list explains what staff need to work on.
Enrollment, homeroom count and the selected portrait grid inform the portrait estimate. Grouping students by homeroom can use more space than one continuous flow because groups begin separately. The content floor combines that portrait allowance with space for the required components.
The requested extent is raised to at least the content floor, then rounded to a full 16-page signature. A target that does not fit that unit produces a warning; a target below the content floor produces another. The wizard saves the book, section records and locked component spread records, and returns its validation report. Staff still supply the authored pages.
Step 1
Establish the source of student names and the scope of the publication. In book setup, choose the school year, education level and organizing style. Supply enrollment and homeroom counts for the portrait estimate, then examine the returned ladder and page budget. A plan gives staff a place to start; it does not replace their reporting or populate finished stories.
Step 2
Assign the reporting, set the design policy and decide which sections belong in every copy. Review the content floor before fixing a target extent. A chronological book and a class-and-grade book organize the year differently, so staff should select the structure they intend to maintain through the deadline.
Step 3
Inspect the approved stories, cover design source, trim, spine assumptions and export findings. Keep the current page count consistent with the cover and the signature list. A change near deadline can require another calculation or export; the relevant result needs to be checked again.
Step 4
Record signature status, review the files supplied to the printer and reconcile the commercial records through the responsible organization. Keep a usable digital output where required. The end of the project is a set of accepted records and artifacts, with clear responsibilities for any outstanding work.
03 Editorial work
A yearbook staff needs more than a space to type. It needs a way to move reporting through review, identify what blocks progress and retain the decision that advances a story.
The editorial workflow distinguishes the steps between a pitch and a publication decision. A requested move is checked against the allowed transition sequence. Staff cannot turn an arbitrary jump into an ordinary approved step simply by selecting a later label.
The required authority also depends on the action and publication context. School oversight and publication-management exceptions are part of that decision, so the workflow should not be described as one title-holder being the only possible approver in every situation. The school needs to understand the actual role arrangement for its publication.
A successful transition returns an approval snapshot and the advanced story. That gives the team a record of the editorial decision. If the story changes while an approval is being processed, a conflict can stop the stale action. Staff should review the current story rather than repeat an outdated approval blindly.
Open blocking checklist items hold a forward move. At publication, the workflow requires saved editor-in-chief sign-off and adviser review where the publication policy requires it. It also evaluates the saved ethics inputs. Missing required checks remain a reason to stop, rather than being treated as evidence that there was no concern.
Scheduled and published states evaluate student-subject permissions for the intended use. A web placement adds its web-publication requirements. Where a web story has no tagged subjects, the workflow requires an explicit attestation that no identifiable students appear. An empty subject list is not automatically an editorial clearance.
For an illustrative club feature, a writer may have completed the interview while a name check or required review remains open. The useful next step is to resolve that specific item, then submit the current version through the appropriate stage. The workflow gives the task a place; the reporting team supplies the evidence.
A saved approval does not establish that every quotation is accurate or that the story has been physically printed. It records a decision against the supplied content and checks. Keep the writer’s verification, the editor’s acceptance and the production release distinct.
04 Book design
A yearbook should feel like a publication with a point of view. Its typography, color choices and page structure need enough consistency to hold the book together, while individual stories still have the space their content deserves.
Book design controls store the allowed colors, allowed font families, logo-lock setting and separate switches for enforcing the color and font choices. Those settings belong to the book. An authorized adviser, co-adviser or administrator can save the policy and retrieve it in another session.
For an illustrative book, the adviser might establish a dark primary color, a light paper color and a short list of type families. The important part is not the particular palette. It is that the agreed choices have a saved home, with an explicit decision about which restrictions are enforced.
No saved policy returns no policy. The system does not fabricate an enforced palette to make an empty configuration look complete. That makes setup worth checking: inspect the saved choices and the editing experience that consumes them before assuming the book is governed by rules someone only discussed.
A valid color token does not establish enough contrast in every layout. An allowed font does not establish that a caption is readable at its printed size. A locked logo setting does not decide whether a story has appropriate hierarchy. Those are page-design judgments the staff still make and the adviser still reviews.
Use a representative spread to establish the standard. Check the title, body copy, caption, folio and image treatment at the intended size. Agree on the exceptions that need review, such as a special section opener or a longer feature. A consistent system is useful when staff understand how to apply it to actual content.
| Setting | What staff establish | What still needs review |
|---|---|---|
| Allowed colors | The book’s selected color values | Contrast and use on a particular page |
| Allowed fonts | The agreed type families | Size, hierarchy and readable text |
| Enforcement switches | Whether palette and type restrictions apply | The configured editor behavior |
| Logo lock | The saved logo-governance choice | Placement and the final page composition |
The trim workflow accepts an explicit size and can calculate its impact before applying it. The review includes affected spreads, refit work, advertisement revalidation and the need to export the cover again. It also distinguishes priced, estimated and unsupported vendor information. An impact preview is not an applied change.
Confirming the change updates the stored trim and records advertisement revalidation; it does not itself refit the spread layouts. The team should complete the necessary refit and review representative pages and fresh output. A smaller page can affect image use and text flow; the cover must agree with the new interior size. The software can describe the impact, but the staff must accept the result the printer will receive.
05 Book composition
Composition starts with the adviser’s decisions about the book. Required material, optional canonical sections and personal material have different roles. The configuration makes those distinctions explicit before a selection is presented to a reader or buyer.
The book’s composition settings include whether the composition workflow is enabled, the minimum and maximum number of optional modules, whether reordering is allowed and the scope of the index. The index can follow the composed selection or the full book. A maximum may be left unbounded; where it is set, it cannot be smaller than the minimum.
These are editorial and product choices with consequences. A book with no optional sections is different from one that requires a reader to choose several. A full-book index and an index for the selected copy tell different stories about what the reader should expect to find. The adviser should decide those rules as part of the book plan.
The section grid returns the actual book sections, their names and order, their kind and their composition fields. A section can be mandatory core material, optional canonical material or personal material. It can have an optional price in integer cents, a grade gate, a grade label and a reader-facing composition label.
For an illustrative program, common school coverage might remain mandatory while an eligible optional section receives a clear label. Staff should make the label describe the content the reader will receive. The stored setting is specific to a section in that book; supplying an unrelated section identity is refused.
| Decision | Example of the question it answers |
|---|---|
| Mandatory core | Which material belongs in every composed copy? |
| Optional limits | How many eligible optional sections may be selected? |
| Grade gate | Which grade is the section intended for? |
| Reordering | May the selected sections change their sequence? |
| Index scope | Does the index describe this selection or the full book? |
An advertisement-bearing section is identified from its section kind. The adviser cannot demote that section to an optional or personal inclusion. The operation is refused so the section remains mandatory. This is a concrete composition rule: a reader’s choice of optional material must not erase the required advertisement section.
The saved configuration and section settings are returned and audited. A section without an explicitly stored inclusion is represented as mandatory core material. Staff can therefore review the actual inclusion grid instead of treating an unspecified value as permission to omit a section.
06 Cover & spine
The cover is a production surface with a front, back, spine and bleed. Its geometry depends on the interior extent, trim and binding. The design should carry the book’s identity while its production result clearly states the assumptions used to build it.
The year
we made.
We were
here.
Back on the left, front on the right. Spine and outer bleed are part of the full wrap. The illustration is not a print template.
A cover template contains front and back panel documents. Each panel can use photo slots, color fields and text blocks. Frames define their position and size within the panel. Text can be literal or bound to the book’s title or subtitle, so a reusable design can receive the correct wording at render time.
Palette roles separate the base, accent, ink and paper colors from the individual blocks. A text block can specify its font family, size, alignment and weight. An empty photo slot renders no invented image. The actual design and its populated content need to be reviewed together.
School-owned templates can be created and edited through the authorized cover workflow. Shared gallery templates can be read and used as a starting point; the school must duplicate one into its own collection to edit it. A malformed design document is refused before it is saved.
Cover export gives precedence to explicit front and back artwork, then to a linked template carrying a valid design, then to a typed title-and-theme fallback. The result identifies which source was used. A missing or unusable linked design can therefore produce a clearly labeled typed cover rather than the artwork the adviser expected.
Template preview is also an actual render workflow. A ready result can return the stored preview artifact; a blocked or stub result has no new preview link. A school-owned template can retain the successful preview reference. A gallery preview does not make the school the owner of the shared template.
The cover export derives its width from page count and binding. A saddle-stitched book has no flat spine panel. The perfect-bound calculation uses a paper-bulk coefficient, and the case-bound calculation adds an estimated board and hinge allowance. The response carries the paper-stock assumption, coefficient, allowance and an explicit estimate flag.
For an illustrative perfect-bound calculation, 96 pages at the engine’s coefficient produce about 0.216 inches of spine. At 112 pages, that becomes about 0.252 inches. These are examples of the current calculation, not approved manufacturing dimensions. The actual stock and binding specification still need confirmation with the printer.
The platform also contains profile-based and preset-based spine calculations. Their existence does not mean the cover export substitutes an assigned printer’s measured paper thickness. The export described here exposes its estimate. Staff should use that disclosure to obtain the correct production specification instead of treating every computed dimension as final.
Cover trim defaults from the book’s stored size. An explicit override can be supplied, and a difference from the book produces a warning. A missing usable page count is refused, because there is no defensible spine calculation without the extent. An unrecognized stored trim is also refused.
Cover preflight can block the render. Missing required rendering or storage produces an error, while a stub result remains labeled as such. The finished result includes the design source, dimensions, trim provenance, spine assumptions and artifact state. Review all of them before treating a preview or export as the approved wrap.
07 Photography & coverage
Coverage improves when staff can see the evidence behind it. The coverage report compares the school roster with the book’s recorded student appearances, giving advisers a basis for follow-up without pretending a count tells the whole story.
The coverage report derives its result from the roster and the book’s page-student ledger. Grade and homeroom views help the team inspect patterns in the recorded appearances. A plain report read does not save a historical trend; a separate snapshot action persists that view for later comparison.
The distinction matters when staff evaluate progress. A current count describes the ledger at the time of the read. A saved snapshot gives the team a retained reference. Neither proves that every photographed face has been identified or that the editorial quality of the coverage is equal.
Photo candidates start from approved images already tagged to the target student. Every co-depicted subject also needs the current permission appropriate to publication. A group photograph cannot be treated as an acceptable candidate solely because the target student is cleared.
The adviser can queue a coverage task after the relevant student, photo, spread, approval and permission checks. Queueing creates work for the staff. It does not insert the image into a spread or fill a blank page automatically.
A task can be marked placed or dismissed. Where an appropriate page is supplied and the photo and current permissions pass, the action can add an appearance to the ledger. A placed label can also exist without a new ledger entry. Review the actual page and appearance record before counting the task as completed coverage.
For an illustrative student with sparse coverage, staff should inspect the candidate image, confirm the caption and subjects, place the approved content through the editing process and verify the resulting page record. The goal is meaningful representation, not a higher number detached from a finished page.
Face recognition is not wired in the shipping configuration; no face template is computed from a photo.
The coverage workflow described here uses existing student tags and recorded page appearances. It does not discover identities by scanning faces. A staff member still needs to verify the student connection and the intended use of an image.
08 Proofing
The last review contains different kinds of decisions. A spelling correction, a replacement portrait, an editorial approval and an exported production file each need their own result and responsible reviewer.
A roster-proof correction can be approved, applied or rejected. Approval changes the correction’s status. It does not change the student’s name. Applying an approved correction updates the appropriate name field and records the before and after values.
That provides a clear handoff when a family reports an error. The adviser can review the correction, establish whether it should be accepted and apply it through the correct action. A rejected correction can retain the reason. The school should then inspect the actual output that depends on the changed name.
Assigning a retake photo resets the verification record to pending and clears its earlier confirmation. The replacement image does not inherit the previous portrait’s approval. Staff and the appropriate reviewer need to inspect the new result.
Proofing reminders have a narrower meaning than their label may suggest. The action selects record identities and records the reminder work; it does not itself deliver a message. A reminder count should not be presented as proof that a family received or reviewed the portrait.
| Result | What it establishes |
|---|---|
| Correction approved | The proposed correction has been accepted for application |
| Correction applied | The relevant student name field was updated |
| Retake assigned | A new portrait is bound and verification returns to pending |
| Editorial approval saved | The story advanced through the applicable review checks |
| Export ready | An artifact was produced through that export path |
09 Interior export
An export request has several possible outcomes. The book team needs the selected content, preflight result, renderer result and stored artifact to agree before handing a file into production.
The interior export path receives decoded spread snapshots from its caller. Its print target is derived from stored economics. It does not automatically prove that every current editing canvas was retrieved. Omitted spread content can produce a valid single blank page, so the presence of an export job is insufficient evidence that the full book was supplied.
The workflow can attempt to save layout information before rendering, but that optional save can fail without failing the export itself. A successful rendered file therefore does not prove that every layout persistence side effect also succeeded. Review the working book and the artifact as the separate results they are.
The render process resolves the referenced photo assets. Missing or unresolved images can refuse the request, and missing required rendering or storage produces an error. An accepted job response can report ready, blocked or stub. An accepted HTTP response is not a synonym for a ready PDF.
Open the actual stored artifact where one is produced. Check that the intended spreads are present, the order is correct and the relevant findings have been resolved. A stub is labeled and should remain distinguishable from output your staff can send to a printer.
The cover has its own export, geometry, design source and preflight information. A ready interior does not certify the cover wrap, and a ready cover does not establish that the interior contains the latest supplied spreads. After a content, page-count or trim change, inspect the artifacts affected by that change.
10 Signature tracking
A deadline can apply to part of the book. Signature tracking provides a separate state for each 16-page unit, allowing the production team to review the outstanding work without confusing a status record with a printer’s receipt.
The list derives the number of signatures from the book’s page count, rounded up in units of 16 pages. It returns the page count, pages per signature and a view of every signature in the current range. A signature with no saved submission row appears as outstanding.
For an illustrative 96-page book, that produces six signature entries. Staff can review each entry separately instead of inferring that the entire book has been submitted because one deadline was met. An empty or unusable page count does not manufacture a useful signature list.
The current page count defines the visible range. If the extent shrinks, stored rows outside that range are omitted from the returned view. That is a reason to reconcile the signature list after changing the book plan; an earlier submission record should not be mistaken for a current page allocation.
An authorized adviser, co-adviser or administrator can mark a valid signature submitted, with an optional note. The saved result includes its state and submission time, while the record retains who performed the action. A signature number outside the book’s current range is refused.
Repeating a submitted transition preserves the original submission time and reports that the state did not change. Returning a signature to outstanding clears its submission time. The operation can still save tracking information, so an unchanged transition should not be described as proof that no record was touched.
| Production question | Record to inspect |
|---|---|
| How many units are expected? | Six entries derived from the current page count |
| Which units require attention? | Each signature’s outstanding or submitted state |
| When was submission recorded? | The saved submission timestamp |
| Did a repeated action change state? | The returned changed indicator |
| Did the printer receive the files? | Separate transmission and printer receipt evidence |
These submit and unsubmit actions update the signature record. They do not send the PDF, contact the print plant or establish that manufacturing began. The term submitted describes the state staff recorded in this workflow. The actual file handoff needs its own verified destination and result.
A useful deadline review pairs the signature list with the approved interior and cover artifacts. Staff can identify what they intended to send, which version was exported and what receipt came back through the delivery process. Those records answer different questions and should remain distinguishable.
11 Book economics
A book’s economics depend on its production choices. The read-only breakdown connects pages, binding, quantity, price, personalization and trim with a route, cost basis and margin calculation. It also identifies when the result is an estimate or needs a quote.
The economics workflow uses the book’s stored or derived production inputs. It returns the selected routing lane and the reason for that route, cost in integer cents with its source and estimate flag, and margin in cents and percentage. Trim information includes its class, multiplier, confidence and change in cost.
That gives an adviser a way to ask useful questions before a production decision: which quantity is being modeled, which binding is assumed, whether personalization changes the route and whether the trim has a supported cost basis. A number without those inputs is difficult to evaluate.
Invalid economics inputs are rejected. The workflow is available to the relevant adviser or administrative role, rather than being a family-facing promise about what a card will be charged. Reading the breakdown creates no print order and moves no money.
Some cost paths use representative values or an estimated grid position. A personalized production path can also remain explicitly estimated. The result carries those distinctions instead of turning every returned cost into a firm vendor quote.
An unpriced custom-quote route can carry zero as its cost sentinel. That zero means a quote is needed. It does not mean the book costs nothing to print, and it should not be used to advertise a free-printing offer or a fully established profit margin.
| Field group | What it helps establish | What it does not establish |
|---|---|---|
| Route and reason | The production path selected from the inputs | A vendor accepting the job |
| Cost source and estimate flag | The basis and limits of the calculation | A firm quote in every case |
| Margin cents and percentage | The modeled difference using those inputs | Collected or settled funds |
| Trim class and cost change | The economic effect of the selected trim | A reviewed page refit or approved cover |
For an illustrative book review, staff might compare the effect of an added signature, a different binding or a changed quantity. The purpose is to expose the inputs and identify where a printer quote is required. The school should review the accepted production specification and commercial terms before treating the estimate as a purchasing commitment.
The direct-selling topic continues at yearbook.sale, while campaign and reminder questions have their own context at yearbook.marketing. Those links do not change the state of an order or establish that a payment connection is active.
12 Studio contracts
A school book can have a studio-side commercial record as well as its editorial and production records. The contract workflow stores the agreement’s amounts and status, with authority held by the responsible studio organization.
The book-contract workflow is for the owning studio’s authorized partner administrator or support administrator. It is not an adviser-editable contract form merely because the adviser manages the book. Editorial responsibility and commercial administration are different roles.
The record stores gross and net amounts as integer cents and supports draft, signed, invoiced and cancelled states through its ordinary update path. Net cannot exceed gross. A malformed amount or invalid relationship between the amounts is refused rather than accepted as an ordinary saved agreement.
Those fields provide a useful record of the commercial arrangement associated with a book. They do not independently establish that the parties executed a legally effective electronic signature. A stored signed status must be read together with the actual agreement and the organization’s signing process.
Paid is handled through a separate action. That action records an off-platform paid status and time and initiates the commission-accrual follow-up. It does not call a card processor to collect the contract amount. Marking the record paid describes an external payment event the operator is recording.
The operator should reconcile that event with the organization’s payment evidence. An invoice, an accepted payment and a bank settlement are not interchangeable documents. The contract record can help organize the work, but its state is not a substitute for the relevant financial receipt.
| Recorded state | Evidence the organization should retain |
|---|---|
| Draft | The proposed scope and amounts under discussion |
| Signed | The actual accepted agreement and signing evidence |
| Invoiced | The invoice and its relationship to the agreement |
| Paid through the separate action | Evidence of the off-platform payment being recorded |
| Cancelled | The decision and any required commercial follow-up |
A production team needs to know the agreed extent, binding and delivery requirements. A studio administrator needs to know the commercial status and the amounts recorded. A change to the book may require review in both places, but updating one record should not be described as automatically rewriting the other.
For an illustrative late change, the adviser first reviews the additional pages and cover impact. The studio then checks the applicable agreement and the economics basis. The records help each person understand the relevant decision, with a deliberate handoff where the responsibilities meet.
13 School book fairs
The platform also includes an adjacent library and book-fair workflow. Staff can plan the event, maintain a catalog and inspect recorded quantities and figures. That does not imply an automatic connection to a particular yearbook project or printed-book shipment.
A fair begins in setup with a name, dates and the relevant storefront and plan information. An inverted date range is refused. Rescheduling is restricted to setup. The fair then moves through open, closed and reconciled states in the permitted forward sequence.
The catalog records SKU, name, optional library-title connection, retail price, base cost, stock and active state. Staff cannot add items to a closed or reconciled fair, and a stock update cannot reduce stock below units already sold. An empty catalog prevents opening the fair.
The workflow requires the library module and the relevant staff authority. Browsing is a signed-in school-member view. It shows active items with remaining stock and relevant wish quantities; it is not evidence of an anonymous public storefront.
A staff sale requires an open fair. A prepay request can use the permitted setup or open states. The workflow checks the selected items and quantities, including repeated item quantities and stock limits, before accepting the request.
An accepted sale or prepay records a pending order and updates inventory counts. It creates no payment intent and charges no card. A pending order can therefore be real stored work while still representing no collected payment. Neither “nothing happened” nor “the family paid” describes that result accurately.
A wishlist funding action updates the recorded funded quantity and refuses an excess quantity. It does not collect a donation. The funded label describes the count being tracked; it is not a financial receipt from a giver.
The settlement view calculates figures from the recorded fair data and sends no payout. Reconciliation writes a reconciled status and amount, calculated from sold quantities and catalog prices. It is not a bank settlement. Staff should retain the distinction between their inventory and commitment records and the external financial evidence they need.
14 Supporting access
A school may want to help students obtain a book. The useful starting point is a clear description of who or what the program intends to support, followed by records that distinguish a commitment from collected funds and delivered books.
Keep the count of requested books, any recorded support quantity and the actual financial result separate. The adjacent book-fair workflow demonstrates why: a wishlist can show a funded quantity even though the action collects no donation. A pending order can exist without a payment intent. A label alone cannot establish that the financial step occurred.
The sponsorship and support topic continues at yearbook.fund. Use that conversation to establish the specific program, its authorized operators and the evidence required at each handoff. A link from this guide does not collect a gift or commit a school to a particular arrangement.
15 Read & retain
The working publication and the output someone reads are different objects. Digital export provides specific formats that staff can review, retain and use within the appropriate school-community context.
The digital publication path offers an HTML flipbook with classic, modern or contrast styling and full or reflow layout. Those choices let staff inspect different presentations of the same projected content. The output uses the authorized school context and the safe edition projection.
A separate PDF-manifest option returns structured JSON. It describes content for a PDF workflow; it is not a generated PDF. The filename or menu label should not replace inspection of what the export actually contains.
Check the intended pages and images, the reading order and the appearance at the sizes your audience uses. Image links depend on the appropriate storage configuration. An exported reading format is not an unlimited promise of permanent hosting, universal accessibility or a complete archive of every project setting.
Agree on the files and records the school needs to retain, who keeps them and how they can be retrieved. The digital-workspace topic continues at yearbook.cloud, with the specific operating arrangement still part of the review.
16 Money & AI boundaries
The financial and suggestion workflows have specific conditions. Read the returned result before treating a saved record, a computed amount or an AI request as a completed external action.
With the payment connection off, an otherwise eligible shared order-payout request is refused before creating a payout or transferring money. That does not mean every order or commercial record disappears. Book-fair orders can remain pending, and contracts can record outside payments, with their own meanings.
Processor test activity is not real money reaching a school. Review the actual financial result and the configured mode. A calculated split, an order acknowledgment and a settled transfer should remain distinct.
An unconfigured provider causes caption and theme requests to be refused. Configured provider paths exist; this is not a claim that every AI path is universally off. Returned suggestions are not automatically applied.
An editor still needs to verify a caption’s names and context and accept any design suggestion. The presence of a suggestion is not proof that the book was changed, that the underlying reporting was checked or that the final output was approved.
17 Practical questions
These are the questions that turn a feature list into a working process: what is saved, what is estimated, what requires another review and what the next person actually receives.
Discuss its audience, organization, portrait allowance and target extent. The setup supports different education levels and organizing styles, while composition settings describe mandatory and optional material. Review the returned page plan rather than assuming a small enrollment guarantees a particular page count. This umbrella connects the full process; the walkthrough can focus on the book your school needs.
No. It records allowed colors and fonts and the associated enforcement choices. Staff still review contrast, hierarchy, readable text and the actual use of photographs on a page. Inspect a representative spread after loading the saved policy, and check the finished output at its intended size.
The composition workflow treats an advertisement-bearing section as mandatory core material and refuses an adviser attempt to demote it. Optional limits, grade gates and reordering are separate book settings. Review the inclusion grid and the selected output; saving those settings does not itself create a sale or render a composed copy.
Changing the page count changes the estimated paper bulk and the width of the wrap for bindings with a flat spine. The cover export exposes its assumptions. Generate and inspect a fresh cover result and confirm the printer’s specification. A saddle-stitched book has no flat spine panel.
In signature tracking, submitted is a saved state with a timestamp. The action does not transmit the PDF. Pair that record with the approved artifacts and the actual printer handoff evidence. A repeated submitted transition preserves the original time; returning it to outstanding clears that time.
No. This page provides an inquiry path, not a transaction form. Selling continues as a topic at yearbook.sale, and sponsorship or support at yearbook.fund. Review the exact financial workflow: a pending order, a funded quantity and an outside-payment record do not each mean money was collected.
The described report uses the school roster and recorded page appearances. Candidate photographs already carry student tags. Face recognition is not wired in the shipping configuration; no face template is computed from a photo. Staff must verify identities, the intended use and the actual page placement.
Bring the outline of the book, the people responsible for it and the result you need to review. Include a difficult case: an ambiguous roster match, a required section, an estimated print cost or a changed trim. A non-sensitive example is enough to establish the shape of the work and the questions the demonstration should answer.
18 The yearbook family
These topic sites continue the conversation about the same yearbook program. A link identifies a subject to explore; it does not activate a service or establish a financial commitment.
Bring your book into the conversation
Tell us how your staff works, what kind of book you intend to make and which handoff needs the most attention. We can discuss the relevant workflow, the configured services it needs and the result your team should be able to review.
Discuss your yearbookAn inquiry about your project. No account activation or purchase is implied.