September 11-14, 2026 (pre-cons Sept 11; main programming Sept 12-14)
Carolina Photo Expo 2026
Raleigh, NC -- Embassy Suites by Hilton Raleigh Durham Airport Brier Creek, 8001 Arco Corporate Drive
School-photography studio operations
Run your picture-day business on the platform built for it.
Most studios running picture-day programs across a district manage contracts in email threads, commission splits in spreadsheets, and delivery against a roster they had to request from the school. This platform puts the operating model — however your studio runs it — on one system: the per-part handler matrix, the territory engine, the agreement engine, and the commission ledger are all built. Here is exactly what is live, what is in early access, and what is coming.
The operating model, territories, agreements, and commission ledger are built and running today. The commission payout disbursement (the step that moves money) is the fast-follow; we say so plainly rather than presenting it as live.
The operating model
Picture-day programs vary: studio-owned end to end, school-run with studio fulfillment, co-run. The platform accommodates all of them through a per-part handler matrix that assigns each leg of the operation to the right party and enforces it.
The per-part handler matrix
Picture day has three distinct parts: selling orders, tracking them, and fulfilling them. Each part has its own handler assignment — the studio can run any combination independently. A studio that sells and fulfills itself sets both legs to studio-owned. A school that sells direct but hands fulfillment to the studio sets the sell leg to school-run and the fulfillment leg to studio. The platform tracks every part and its assigned handler so nothing falls between arrangements. Shipped
Mix-and-match operating models
No operating model is locked in at the account level. A studio can run a fully studio-operated program at one school, co-run with the school at another, and let a school run entirely self-served at a third — all within the same platform. The handler matrix persists per scope and per product line. Changing the arrangement for one school does not affect any other. Shipped
Granular territories by product line
A territory in this platform is scoped to a scope AND a product line within that scope. Representative A can hold the yearbook territory at a given school while Representative B holds the photography territory at the same school — the unit is scope x product-line, not just a school assignment. Territory reads are enforced server-side: a rep can only read the orders, proofs, and data belonging to their own territory assignment. Shipped
The rep PII wall
A territory assignment determines what a representative can read — and strictly limits it. The rep PII wall prevents a rep from reading student or guardian PII outside their own territory. The single-school FERPA wall means a rep assigned to one school cannot read another school’s student records, even within the same district. These are database-layer constraints, not UI-layer conventions. Shipped
How a picture-day program runs on this platform
A studio onboards a school by binding it to a scope in the platform and setting up the territory assignments for each product line. The handler matrix is configured: who sells, who tracks, who fulfills, and who receives the school-leg revenue. Contracts are created through the agreement engine and signed by the relevant parties. Representatives are assigned territories by product line, each with its own PII wall.
When picture day runs, the portrait intake binds each image to the school’s roster — the same authoritative record the gradebook uses — so every portrait lands on the right student record without a manual match step. Subject-sovereign proofs give each subject a view of their own portraits only; a guardian confirms or requests a retake. Approved portraits flow through fail-closed print preflight into the delivery targets: the directory, ID cards, team composites, and the yearbook.
Orders and revenue are tracked on the commission ledger. Each order posts a revenue record that splits across the four legs — studio, photographer, school, and platform — on an exact-penny, append-only basis. A representative’s earned commission accumulates on the ledger. The ledger is built and running; the disbursement step that moves the money to a bank account is the fast-follow currently being wired.
The agreement engine manages the contract lifecycle between the studio and the school. An agreement is created, assigned to the relevant parties, and advanced through a closed status sequence: draft, sent, countersigned, active, expired. The engine enforces who can advance each step and audits the before and after state at every transition.
Agreements and commissions
Two engines handle the business layer of running a district program: the agreement engine manages the contract lifecycle between studio and school, and the commission ledger tracks what every rep has earned on every order.
The agreement engine
One engine manages every contract and agreement the studio runs: school contracts, district master agreements, and per-event arrangements. An agreement is created with a title, a type, the relevant parties (studio, school, district), and a validity window. The status sequence is closed: draft to sent to countersigned to active, with expiration enforced. The engine records who advanced each step and when. No agreement state is writable by the wrong party. Shipped
The commission ledger
The representative commission engine runs an exact-penny, append-only ledger. Each order posts a commission event to the ledger: the amount, the funding source, the rep it belongs to, and the order it references. Commission reads are scoped by territory: a representative reads their own ledger only. The ledger is append-only — entries are never edited or deleted, only superseded by a subsequent correcting entry with its own audit record. Platform administrators retain the ability to correct records with a dated audit entry; no silent deletion occurs. Shipped
Commission funding and the four-way split
A portrait order settles on net and splits four ways: the studio leg, the photographer leg, the school leg, and the platform leg. The split percentages are configured per territory and per product line. The school leg is the part incumbents omit entirely; this platform routes it to the school on every order. The ledger records all four legs at the moment of settlement. Early access — payout wiring is the fast-follow
Representative commission payout
The commission ledger accumulates the earned balance for each representative. The disbursement step — the operation that moves the accumulated balance to a rep’s bank account — is the launch-critical fast-follow currently being wired. We do not present this as live. A rep’s earned balance is visible on the ledger today; it will disburse when the payout wire is complete. Payout wiring in progress
Delivery and proofing
From roster-bound intake through subject-sovereign proofing to fail-closed preflight and delivery — the platform handles the full portrait pipeline without a separate fulfillment tool.
Roster-bound portrait intake
Portraits are bound to the school’s official student roster at intake — not by face match, but by the authoritative record the school already uses for grades, attendance, and the directory. A portrait that cannot be bound to a roster record does not enter the workflow until it is assigned. This eliminates the manual match step that creates errors in bulk picture-day jobs. Shipped
Subject-sovereign proofs
Each subject receives a proof view of their own portraits only — no other subject’s photos are visible in the same view. A guardian confirms the portrait or requests a retake from within the proof. Proof consent is enforced: a portrait moves to a deliverable state only when the proof step is resolved. The proof surface runs on the platform’s consent model; a do-not-publish flag suppresses a portrait end to end. Shipped
Fail-closed print preflight
Before any portrait enters a print-ready delivery target — the directory, ID cards, team composites, or the yearbook — it passes a fail-closed preflight gate. The preflight checks resolution, format, binding, consent status, and the do-not-publish flag. A portrait that fails any gate is rejected and flagged for review rather than printed with a defect. The preflight result is recorded per portrait per delivery pass. Shipped
Directory, ID cards, and composites
Roster-bound portraits flow automatically into the directory page, individual ID-card composites, and team or club composites — all from the same portrait record, with the same preflight gate applied. A portrait update propagates to every delivery target that has not yet been printed. An ID card run and a directory update pull from the same record without a second upload. Shipped
What is in progress and what is planned
These are not presented as available today. They are named so a studio evaluating this platform can see where it is going and hold us to the honest timeline.
Commission payout disbursement
The commission ledger accumulates earned balances per representative today. The disbursement step — the banking wire that moves a rep’s balance to their account — is being wired now. When complete, a rep will be able to request or schedule a payout from within their commission view. We name this plainly: the ledger runs, the disbursement does not yet. In progress
School-leg payout wiring
The four-way split routes a leg of every settled order to the school on the ledger. The step that delivers those funds to the school’s bank account is the same fast-follow as the rep payout wire. The school leg is real, tracked, and accumulating; the disbursement to the school’s account follows the payout infrastructure completion. In progress
Studio command center
A dedicated command-center dashboard for the studio operator: district-wide order volume, territory coverage, agreement status at a glance, commission ledger totals by rep, and outstanding proof approvals. The data that backs it is built; the aggregated dashboard surface for the studio role is planned. Planned
Online booking integration with the slot engine
Picture-day family booking runs on a fixed-slot identity engine (one student per slot, unique slot identity, no overlap). The booking integration that surfaces available slots to families for self-scheduling is connected via schedule.software — the same slot engine the platform runs for admissions and senior sessions. The integration spec is finalized; the booking surface wiring is planned. Planned
District-wide agreement rollup
For studios operating across a district, a district master agreement can govern the terms for all school-level sub-agreements. The agreement engine supports party hierarchies and agreement cascades in the data model. The district rollup surface — a single view of all active, pending, and expiring agreements across all schools in a district — is planned. Planned
E-signature finalization
The agreement engine advances contracts through a ‘countersigned’ status; the architecture has a signing-provider injection point at that step. No external e-signature provider is wired today. Agreements close through the studio and school party confirmation steps while the signing-provider connection is built. Planned
Who this is built for
This platform is built for the studio or photographer who runs picture-day programs as a business: who holds district contracts, manages representatives across multiple schools, and delivers portraits to school directories, ID-card programs, and yearbooks. The audience here is the operator — not the families who buy a portrait package, and not the school administrator who manages HR and staff. Those are distinct surfaces.
A representative using the platform reads their own territory: the schools they are assigned, the product lines they cover, and the orders and commission events within that scope. The rep PII wall prevents reading student or guardian data outside their territory. The single-school FERPA wall prevents reading another school’s records even when a rep covers multiple schools — each school is accessed through a separate, role-gated session.
A studio administrator reads across the full set of territories they own: all active agreements, all commission ledger totals, all outstanding proof approvals. The studio role does not have access to the platform’s school management, HR, or student-record surfaces — those belong to the school and district roles. The studio operator manages the picture-day program; the school manages the school.
Family and student data on this platform is consent-gated and school-controlled. The studio processes portraits and delivers them through the platform’s proofing and preflight pipeline; student PII is never exported to the studio in bulk. A do-not-publish or under-13 flag suppresses a portrait end to end — it does not reach a storefront, a directory, or a print job. The platform’s FERPA obligations run through the school, not the studio; the studio is a data processor acting under the school’s direction.
Common questions
Does the platform support a studio that runs picture day end to end?
Yes. The handler matrix lets the studio own all three legs: selling, tracking, and fulfillment. The studio sees the full order flow, manages proofing, and drives delivery through the platform’s preflight pipeline. School-run and co-run arrangements use the same matrix with different handler assignments.
Can a representative cover multiple schools but see only their own territory?
Yes. A territory is assigned per scope and per product line. A rep sees the schools and product lines in their territory; the rep PII wall prevents reading student or guardian data outside it. The single-school FERPA wall means each school’s student records are gated separately — holding multiple school territories does not create a cross-school data view.
Is the commission payout live today?
The commission ledger is live: every order posts an exact-penny commission event and the rep’s earned balance accumulates in real time. The disbursement step — the banking wire that moves that balance to a rep’s account — is in progress. We name this plainly: money does not move from the platform to a rep’s account today; that wiring is the fast-follow.
How does portrait delivery to the yearbook work?
A roster-bound portrait that passes fail-closed preflight is available to the yearbook as a resolved portrait for that student record. The yearbook pull reads from the same roster; no second upload or matching step is needed. The preflight gate — resolution, format, consent, do-not-publish — runs before the portrait enters any delivery target, including the yearbook.
Does the studio get access to student PII in bulk?
No. The studio operates the picture-day pipeline through the platform’s proofing and delivery surfaces. Student PII is scoped by the school’s FERPA obligations; the studio does not receive a bulk export of student records. Portrait processing and delivery happen within the platform, not in a studio-side file transfer.
Can we get in touch to see the platform before committing to anything?
Yes. There is no contract required to get a walkthrough. Use the “Get in touch” link above and someone will schedule a demo with you. No checkout, no automatic billing, no commitment at the inquiry stage.
Related tools and surfaces
Pholio
The family-and-school front door for the photos: consent-gated parent galleries, the portrait storefront, and “find my child” by roster lookup. The public-facing counterpart to the studio operator tools here.
Senior Photo Studio
The senior-portrait vertical: session scheduling, the yearbook-photo submission workflow, and the senior-specific operating model. A distinct product from the grade-wide picture-day programs this platform covers.
Schedule
Picture-day family booking on the same fixed-slot identity engine: one student per slot, unique slot identity, no double-booking. The booking surface families see when a school opens picture-day appointments.
The Platform
The full-platform overview: yearbook, picture day, student records, family communication, and school management on one shared student record.
On the conventions calendar
Upcoming conventions and conferences
The next confirmed dates for School Photography programs, taken directly from each organization’s official page -- nothing invented or carried forward from a prior year.
November 7, 2026 (8:00 AM to 5:00 PM; Save the Date)
Professional Photographers of South Carolina Annual Conference 2026
South Carolina -- venue TBA (historically Columbia Metropolitan Convention Center, Columbia SC)
January 19-22, 2027 (Save the Date; Early Bird opens August 2026)
SPAC 2027 Annual Conference
Las Vegas, NV -- venue TBD (historically South Point Hotel Casino & Spa)
What is built and what is honest-off
The per-part operating model, the handler matrix, the territory engine, the rep PII wall, the single-school FERPA wall, the agreement engine, the commission ledger, roster-bound portrait intake, subject-sovereign proofing, fail-closed print preflight, and delivery into the directory, ID cards, and team composites are built today and running. The four-way revenue split is in early access: the ledger routes the school leg and the platform leg on every settled order; the disbursement step that moves money to a rep’s or school’s bank account is in progress — we do not claim dollars move today. E-signature finalization, the studio command-center dashboard, and the district agreement rollup are planned. We name these plainly rather than listing a capability set and leaving you to discover the gaps.
School Photo Studio is the studio-operator surface from Stanley Studios — the platform that also powers Pholio, the family-facing school-photography front door, on one shared consented student record.