Display and tribute ads for the yearbook
The yearbook ad engine manages every stage of an ad sale from the school side: adviser opens inventory, sets the slot count and sizing, assigns a price per slot, and sends a shareable link to the community. A business or family claims a slot, uploads their artwork (or uses a simple template), and the adviser approves the content before it is placed. Ads run only if content-approved and paid in full — the fail-closed rule is enforced by the engine, not by a manual process. The ad inventory, pricing logic, content-approval gate, and placement engine are built and production-ready. The charge rail that moves money is honest-off: no live checkout today.
Ad engine built · charge rail honest-off
Family senior tribute and recognition ads
Families place tribute ads to celebrate seniors, graduating classes, and student milestones directly in the yearbook. A tribute ad is a family-composed page — a photo, a short message, and a shared memory — that lives alongside the editorial pages rather than replacing them. The school sets the price; the family pays; the adviser approves the final content. The tribute revenue is paid into the school’s account rather than a national vendor’s. The tribute-ad flow shares the same approval gate and content-discipline rules as business display ads: content-approved, paid-in-full, slot-sells-once.
Tribute-ad engine built · charge rail honest-off
One network across yearbook, newspaper, program, and playbill
A local business that sponsors the yearbook can also appear in the sports program, the theatre playbill, and the newspaper honor section — under a single conversation with the school. Cross-format ad packages are supported in the inventory engine: a sponsor picks which publications to appear in, the school sets the pricing per format, and the adviser approves placement in each. The ad-sales storefront, the program/playbill booster engine, and the playbill slot builder are built. The cross-format package UI that bundles them for a business is in active development.
Per-format engines built · cross-format package UI in development
The school keeps the revenue
Ad revenue goes to the school’s programme account — not to a national intermediary who owns the inventory and remits a fraction back months later. The school sets prices, owns the inventory, and decides when and how to use the proceeds. The funding model is described plainly: the school keeps the ad-revenue share it sets, and the Yearbook Ad Network’s platform take is a residual on that revenue. That platform fee model is in design (honest-off, founder-gated); no take-rate is charged today.
Revenue-share model designed · payment rail honest-off
Adviser-approved, fail-closed
No ad appears in a school publication without the adviser reviewing and approving it. The content-approval gate is enforced by the engine: an ad is queued for placement if and only if it is content-approved AND payment is confirmed. A slot sells exactly once — the inventory engine prevents double-booking at the data layer. The approval flow is built into the ad-sales storefront and the program/playbill booster engine. Minors appear in publications only with appropriate consent on file; the ad engine does not sidestep the publication consent layer that governs all student appearances.
Approval gate built · fail-closed by design