Senior-portrait studio software
The senior portrait workflow, built for studios that specialize in seniors.
Senior portrait work is its own discipline. The session series, the proof review, the portrait selection, the consent check before anything leaves your studio, the grad-template fan, and the hand-off into the yearbook’s senior-photo pages are not afterthoughts on a general picture-day platform — they are the whole job. This is the software built around that job: a named senior series that tracks across years, recolorable grad templates in a curated blank set, subject-sovereign proofing your senior controls, and a direct binding from the approved portrait into the yearbook record. Here is exactly what is built and what is still coming.
The senior series, the proofing workflow, the consent gate, the print preflight, and the yearbook binding are built. The parent-facing storefront and the school revenue leg are in early access — the payout wiring is the fast-follow. We say what is live rather than presenting early work as finished.
What is built
The modules below exist and run. Anything marked “in early access” has a built engine; the full workflow surface or the payout wiring behind it is the fast-follow. We label each one plainly.
Named senior series with per-year identity
Each senior session series carries a deterministic series key and a human-readable name that ties to the graduating year — so a 2025 senior series is distinct from a 2026 series, and a studio can track a cohort across a season without rebuilding the naming structure by hand. The series is the organizing spine that the templates, the proofs, and the yearbook binding all read from. Shipped
Recolorable senior and grad templates
Senior-series design templates and grad blanks are personalized and fanned across a curated set of layouts. A senior’s name, year, and portrait slot in. The template color fields are recolorable per subject — so a studio can offer the school’s palette or the senior’s choice without maintaining a separate file set for each variation. The senior wills surface is built on the same template layer. Shipped
Subject-sovereign proof review
Proofs are served to the senior directly — the subject of the portrait, not a parent acting on their behalf — using the own-data consent carve-out that treats a student’s own images as the student’s own data. A senior reviews their proofs, makes a selection, and the approved portrait is recorded under their identity. A studio does not need to mediate every selection manually. Shipped
Roster-portrait resolver for yearbook binding
When a senior approves a portrait, the resolver binds the approved image to the student’s record in the yearbook system. The yearbook editor does not pull proofs from a separate system or chase down which photo was selected — the resolved portrait is already in the record, attributed to the right senior, ready to drop into the senior-photo layout. Shipped
Consent gate, fail-closed per subject
Before a senior portrait is offered for sale, published in a yearbook, or exported from the studio system, the consent gate reads the on-file record for that subject. No consent means no sale and no publish — the gate is enforced in code, per subject, and fails closed: the default state is not sellable until consent is on file. A missing or withdrawn consent record locks the portrait, not the workflow. Shipped
Fail-closed print preflight for senior print products
Every senior print product — an 8x10, a wallet strip, a grad announcement, a template fan — runs through the same print preflight that gates the full platform’s publication workflow. The preflight checks resolution, bleed, trim, and the capability of the target printer against the job. A job that would produce a bad print does not go to press; it surfaces the specific fault to the studio operator before an order is placed. Shipped
Senior portrait into the yearbook's senior-photo pages
The binding from the approved senior portrait to the yearbook’s senior-photo page layout is built. When the yearbook editor opens the senior section, the resolved portraits are in the record — the studio does not need to export a file set and hand it off by USB or email. The senior portrait arrives in the layout automatically, attributed by the resolver. Shipped — parent storefront around it in early access
How the senior portrait workflow fits together
The workflow starts at the series. A studio creates a named senior series for the graduating year; every session booked under that series inherits the series key and the template set. When portraits come back from the session, they are entered into the proofing layer under the student’s roster record — not filed by filename or by memory, but bound to the student identity the yearbook already knows.
The senior reviews their own proofs. The own-data consent carve-out gives the senior direct access to their images without requiring the studio to mediate every decision. The senior makes a selection; the resolver records the approved portrait against the student record. The consent gate runs automatically at that binding step — an approved portrait without sale consent on file is recorded but not marked as sellable. The studio does not need to remember to check; the gate runs for every subject on every binding.
From the approved portrait, two things happen in parallel. First, the yearbook binding: the resolver makes the portrait available to the yearbook editor’s senior-photo layout immediately, without an export step. Second, the parent-facing storefront (in early access): the approved, consented portrait becomes available for purchase by the family through the studio’s storefront. The four-way revenue split — studio, photographer, school, and platform — is the ledger that routes each leg. The payout wiring to the school is the fast-follow behind the storefront; we do not claim those dollars reach a school’s account today.
Throughout the workflow, print preflight runs on any senior print product before an order is accepted. The preflight checks the job against the printer’s declared capabilities — resolution, bleed, trim — and blocks orders that would produce a bad result rather than surfacing the failure at delivery.
The session series: a senior's journey across the year
First look and casual sessions
Many seniors book an early spring session before their senior year begins — a first look, a casual outdoor shoot, or a summer-before-senior-year portrait. The series keys those sessions to the graduating year, so the studio can offer a full season of session types under one cohesive series without losing track of which year a portrait belongs to.
The formal senior session
The fall formal session — cap and gown, school drape or tux, the portraits that go into the yearbook — is the anchor of the senior series. The formal session lands the yearbook-eligible portrait: the one that runs through the consent gate, gets bound to the student record by the resolver, and shows up in the senior-photo layout without the editor having to chase it down.
Grad-announcement and senior-wills templates
The grad-template set and the senior wills surface share the same template layer as the portrait series. A studio can produce a grad announcement from the approved senior portrait — personalized, recolorable, preflight-checked — without maintaining a separate design workflow for announcements alongside the session workflow.
What is in progress and what is planned
These are not presented as available today. They are named so a studio considering this platform can see where the workflow is going and what the honest timeline looks like.
Parent-facing senior portrait storefront
The storefront that lets a family purchase prints, digitals, and products from the approved senior portrait is in early access — built on the consent gate and the proofing layer that are already running. A family sees only their senior’s approved, consented portraits. The four-way revenue split is the ledger behind it. Early access
Four-way revenue split with a school leg
An order through the senior portrait storefront routes on an exact-penny, append-only ledger to four legs: studio, photographer, school, and platform. The ledger is built. The payout wiring that moves the school’s leg to an account is the fast-follow behind the storefront launch — we do not claim dollars reach a school’s bank today. Early access
Multi-session bundle and series pricing
A studio that sells a spring casual session plus a fall formal session as a bundle — or offers a returning-senior discount for seniors who booked last year — is a pricing model the session series structure is designed to support. The surface for configuring bundle and series pricing is planned. Planned
Senior mini-session booking
A time-slot booking flow for senior mini-sessions — a fixed-length slot, a single photographer, a limited seat count per day — that hands off into the series workflow on completion. The platform’s scheduling module supports fixed-slot booking; the senior-mini-session skin on top of it is planned. Planned
Who uses each part of this
The senior series, the proof management, the template fan, and the yearbook-binding resolver are studio and photographer tools. A studio operator creates and names the series, manages the template set, and reviews the resolved portraits before they go to the yearbook. The studio is the primary user of this workflow; the senior and the family are downstream recipients of the proofing and storefront surfaces, not the operators of the studio workflow.
The senior is the direct user of the proof-review surface, under the own-data consent carve-out. A senior can review their own proofs and make a selection without a parent acting on their behalf, because the portrait is their own data. A guardian can review on behalf of a minor who has not been given direct access; the consent model handles both flows. What neither the senior nor the guardian can do is bypass the consent gate: the gate runs at binding, not at selection.
The yearbook editor is the consumer of the yearbook binding, not the operator of it. When the senior portrait is resolved and bound, it appears in the editor’s senior-photo layout without the editor needing to import a file. The yearbook side does not need to know which proofing tool the studio used; it reads the resolved portrait from the student record.
This page’s scope is senior portraits. Whole-school picture-day programs for underclass students, the general territory and commission engine for studio reps, and the broader public-facing “find my child” experience are separate tools for separate workflows. A studio running both senior and underclass work uses both surfaces; they share the same underlying student record and consent infrastructure but do not share a page or a workflow surface.
Honest answers to questions studios ask
Does this replace the yearbook editor for the senior section?
No. The binding puts the approved portrait in the record the yearbook editor reads. The editor still lays out the senior pages, chooses the grid, and approves the final spread — the resolver just means the portrait is already there when they open the layout, attributed to the right senior, rather than arriving by file transfer.
What happens to a senior portrait if the student has not given consent?
The consent gate is fail-closed: an absence of on-file consent means the portrait cannot be sold and cannot be published. The portrait is held in the studio’s system; it does not surface in the storefront or the yearbook binding until consent is recorded. A studio operator can see which seniors are gated and reach out to collect consent; the gate does not auto-resolve.
Can a senior review proofs on a phone?
The proof-review surface is browser-based and responsive. A senior accesses their proofs through a link tied to their roster identity — no app install required. The own-data carve-out gives them direct access; they do not need a parent to log in on their behalf, though a guardian access path exists for minors who have not been given direct access.
Is the print preflight separate from the yearbook preflight?
No. The same preflight engine that checks yearbook publications checks senior print products. The printer capability gate runs on the job specifications — resolution, bleed, trim — against the declared capabilities of the target printer. A job that would fail at press is rejected before the order is placed, whether it is a 400-page yearbook or a single 8x10 senior portrait.
How does the school revenue leg work, honestly?
The four-way revenue split routes a school leg on an append-only ledger per order. The ledger is built and the split is in early access. The payout wiring — the step that moves the school’s leg to an actual bank account — is the fast-follow behind the storefront launch. We do not claim dollars reach a school’s account today. A studio considering this for district relationships should know the ledger is running but the physical payout is not yet live.
Does this platform handle whole-school picture day for underclass students?
No, not on this page. Whole-school picture-day programs for underclass students, the territory and commission engine for reps, and the broader picture-day operations workflow live at schoolphoto.studio. The public-facing family gallery and “find my child” experience lives at pholio.photos. This platform is the senior-portrait studio vertical. A studio running both senior and underclass work uses both surfaces.
Related tools in the photography family
School Photo Studio
Whole-school picture-day programs for underclass and elementary students: the territory and commission engine, the rep workflow, and the school-wide session coordination.
Pholio
The public school-photography front door: privacy-first school photography, consent-gated family galleries, and the roster-lookup “find my child” experience for families.
Pholio Software
The picture-day software for studio and school operators: the private-system capture pipeline, the consent gate, and the roster-portrait binding for operators running picture day.
What is built and what is honest-off
The named senior series with per-year keys, the recolorable senior and grad templates, the subject-sovereign proof review using the own-data consent carve-out, the roster-portrait resolver binding an approved portrait to the yearbook student record, the consent gate (fail-closed per subject), and the fail-closed print preflight are built today. The path from the approved senior portrait into the yearbook’s senior-photo pages is built for the binding; the parent-facing storefront around it is in early access. The four-way revenue split is in early access — the ledger is running, but the payout wiring to the school is the fast-follow, not yet live. We name these plainly rather than hiding them.
This page addresses studios and photographers who specialize in seniors. It does not cover whole-school picture-day program operations (schoolphoto.studio), the general public-facing family gallery and “find my child” experience (pholio.photos), or any theatre or performing-arts director tools. Those are separate surfaces for separate audiences.