Pictureday.software · School picture day platform · Early access · 2026

Picture Day Without the Chaos — two-layer consent, transparent earnings, and a photographer-first workflow

Pictureday.software is the picture day orchestration platform built for K-12 schools and the photographers who shoot them. Every student photo carries its depiction-consent state from the moment it is captured. Every order shows the exact per-item price and where each dollar goes — the school’s fundraising leg and the platform’s residual share on the same order — no markup games, no opaque deductions. The photographer arrives with the roster; the school admin sees real-time check-in; families see only their child’s proofs; and the yearbook gets a clean PSPA export. Photos are organised by QR or barcode, not by a face match. Early access — no pricing commitment, no signup, no live payments today.

Book a conversation How it works

Two-layer consentdepiction consent per student + marketing opt-in per family — captured, enforced, revocable

Photographer-firstroster-driven check-in → upload pipeline → earnings ledger — designed for the day-of reality

Radical transparencyfamilies see per-item price + where each dollar goes; photographers see gross, costs, each split leg, and net per event

No facial recognitionphotos matched to students by QR/barcode at capture — this flow runs no face match to organise photos

Consent as a feature, not compliance overhead — the structural spine

Every photo carries its consent state from the moment it is captured. That is the architectural choice.

Most picture day systems collect a paper permission slip, file it in a binder, and rely on a photographer to remember which students are excluded. Pictureday.software is built the other way around: consent is the first thing that happens, not the last thing that is checked. Before picture day, every guardian resolves two questions in the same digital intake: depiction consent (may this child’s photo appear in shared materials?) and marketing opt-in (do you want proof-ready notifications and order reminders?). These are separate decisions, resolved independently, stored against the student roster.

On picture day, the check-in system links each photo to its roster record at capture — by QR code or barcode, not by a photographer sorting a folder by memory. A student whose depiction consent is absent is excluded from every shared surface: the parent store, the proof gallery, the yearbook export. Not by a manual filter. By the engine. Revocation is immediate: a guardian who withdraws consent mid-order-window will find their child’s photo invisible across every surface within the session. The consent substrate, the depiction layer, the marketing opt-in layer, and the revocation engine are built and production-ready.

Book a conversation Full platform

How it works

Picture day in four stages — consent first, photographer-led, family-transparent

The picture day workflow runs in four stages. Each stage is described as it is built today — honest about what is live and what requires charge-rail enablement.

Step 1 — Consent collection

Before a camera appears, the consent intake runs. The school admin sends the consent form through the platform; guardians complete it online. Each family resolves two questions independently: whether their child may appear in shared materials (depiction consent), and whether they want to receive proof-ready notifications and order reminders (marketing opt-in). A student whose depiction consent is absent does not appear in any shared gallery or export — enforced by the engine, not by a photographer’s memory on picture day. The consent record is timestamped, stored, and auditable. This picture-day flow organises photos by QR or barcode at capture, not by a face match.

Step 2 — Photographer day

The photographer arrives with the session roster on a device. Each student is scanned by QR code or barcode at the moment of capture, linking the photo to the roster record. The check-in dashboard shows the admin which students have been photographed and which are still outstanding. Red-flag detection surfaces unmatched photos at the end of the session — before the photographer leaves the building. After the session, the photographer batch-uploads proofs through the upload pipeline; they land in family proof galleries within minutes, not days.

Step 3 — Parent ordering

Families who opted in to notifications receive a proof-ready message. Each family logs in to their private account and sees only their child’s photos. The parent store displays print products with a transparent, itemised price: the per-item cost, the school’s fundraising leg, and the platform’s residual share of the order are all shown before checkout. Families who did not opt in to marketing do not receive a notification and cannot inadvertently be emailed about their child’s photos. The proof gallery and the store substrate are built and production-ready. The live checkout interface that accepts payment is honest-off: present in the platform, not enabled for live transactions today.

Step 4 — Fulfillment & yearbook export

Confirmed orders route through the PhotoLabProvider seam to on-demand commercial print production and ship directly to families. The photographer’s earnings ledger updates per order: gross proceeds, lab and card costs, the school’s fundraising leg, the platform’s residual leg, and net payout, all in exact-cent records. The PSPA/SPOA export delivers the year’s photo set to the yearbook tool in the format the adviser expects. Photo records are retained for the order window and then purged on schedule unless a family archives them. The fulfillment substrate and the PSPA/SPOA export are built and production-ready. The live charge rail that moves money is honest-off.

The full platform

Five engines — honest about what is built and what is coming

Every feature is labelled honestly: Built means the underlying engine is production-ready. In development means the surface, wire-up, or charge-rail integration is in active build. We do not claim otherwise.

Picture day event management — scheduling, roster, check-in, retakes

The event management engine schedules picture day sessions with photographer assignments, locations, and timing. Roster-driven check-in tracks which students have arrived and been photographed; unmatched students are flagged at the end of the session, not discovered weeks later when the parent calls. Retake management runs a second round against the same roster, with original-session records preserved. The school admin dashboard shows real-time attendance and fulfillment status without calling the photographer. Picture day event management, roster-driven check-in, and retake management are built and production-ready.

Event management built · production-ready

Parent proof gallery — private per-family proofs, no social sharing

Each family sees only their own child’s photos, inside a private per-family account, before placing any order. There are no class galleries, no school social feeds, no “best of” shared albums. A family that has not opted in to marketing does not receive a proof-gallery notification — which means they also do not receive a surprise email about their child’s photos. Proof galleries stay live for the duration of the order window, then expire. The proof gallery engine and the per-family access model are built and production-ready.

Proof gallery built · production-ready

Print & digital fulfillment — branded parent store, per-item pricing, on-demand

The branded parent store presents each print product with a transparent, per-item price and a plain breakdown of where each dollar goes. A family sees exactly what they are paying for and how the order settles: the print/lab cost and card processing come off first, then the photographer’s and the school’s fundraising legs are set shares of what remains, and the platform keeps the residual on the same order — a named leg in the split, not a separate surcharge added on top. Fulfillment routes through the PhotoLabProvider seam to on-demand commercial print production. The store substrate, the per-item pricing engine, the PhotoLabProvider seam, and the PSPA/SPOA export are built and production-ready. The charge rail that moves money — the part that accepts a family’s payment and routes it to the photographer and the school fund — is honest-off: present in the platform, not enabled for live transactions today.

Store substrate built · charge rail honest-off

Photographer workflow — check-in, upload pipeline, earnings ledger

The photographer arrives with the roster on a device: each student scanned by QR code or barcode, matched to their roster record at capture. The proof upload pipeline batches photos from the shoot directly into the family proof galleries. Red-flag detection surfaces students whose photos did not match — so the photographer resolves mismatches the same day, before leaving the building. The earnings ledger tracks each photographer’s gross proceeds, the lab and card costs, the school’s fundraising leg and the platform’s residual leg, and the photographer’s net payout, per event, in real time — no markup games, no opaque deductions. The photographer workflow tools (check-in, QR/barcode matching, upload pipeline, red-flag detection, PSPA/SPOA export) and the earnings ledger substrate are built and production-ready. The charge rail that pays the photographer is honest-off: the ledger records it; the live payout is honest-off pending charge-rail enablement.

Workflow tools built · live payout honest-off

Who uses it

Built for the admin who schedules it, the parent who orders from it, and the photographer who runs it

For admins & yearbook coordinators

Admins configure the picture day event (date, location, photographer assignment), send the consent intake, and track progress from a real-time dashboard: attendance percentage, outstanding students, fulfillment status, and the school’s projected fundraising leg before the order window closes. The PSPA/SPOA export runs after the order window and delivers the yearbook-ready photo package directly to the design tool. Admins never need to call the photographer to find out what happened — the dashboard shows it.

For parents & families

Families who opted in to notifications receive a proof-ready message when the photographer’s upload is complete. Each family sees only their own child’s photos, in a private account. No class galleries. No shared albums. No other family can see your child’s proofs. The parent store shows a transparent, itemised price before checkout: the print cost, the school’s fundraising leg, and the platform’s residual share are all visible. Consent can be reviewed and updated at any time; withdrawal is immediate.

For photographers & studios

The photographer arrives with the session roster on a device, scans each student at capture, and batch-uploads proofs through the upload pipeline. Red-flag detection surfaces unmatched students before leaving the building. The earnings ledger shows gross proceeds, costs, each split leg, and net payout per event in real time — no markup on print costs, no hidden deductions, no guessing at the end of the season. Studios running multiple schools see a per-school earnings summary across the ledger. The PSPA/SPOA export runs cleanly from the same session data.

Radical money transparency — what the family pays, what the photographer earns

The per-item price, the school’s fundraising leg, and the platform’s residual share — all visible before checkout

A family ordering prints sees an itemised breakdown: the per-item print cost, the school’s fundraising leg, and the platform’s residual share of the order (a named leg in the split, shown in the order summary, not a separate surcharge on top). There is no markup on print costs, no per-student seat fee charged to the school, and no hidden deduction between what the family pays and what the photographer receives. This transparency is a design constraint, not a marketing promise: the pricing engine renders all three components in the order summary before the family confirms.

The photographer’s earnings ledger mirrors the same breakdown from the other side. Every order that touches a photographer’s session updates the ledger: gross proceeds, lab and card costs, school fundraising leg, platform residual leg, net payout — per order, per event, per season. A photographer who shoots twelve schools a year can see their full earnings history in one ledger, with every split leg shown the same way in every row. The ledger substrate is built and production-ready. The live payout that moves money to the photographer is honest-off pending charge-rail enablement.

What is built and what is coming — plainly

The engines are built. The charge rail is not live yet.

Built and production-ready today: picture day event management (scheduling, roster-driven check-in, retake management, day-of dashboard); two-layer consent substrate (depiction consent per student, marketing opt-in per family, revocation engine); parent proof gallery (private per-family, no social sharing, per-consent access); photographer workflow tools (QR/barcode matching, upload pipeline, red-flag detection for unmatched photos); the earnings ledger substrate (gross, costs, each split leg, and net per event, exact-cent); the print fulfillment store substrate (branded parent store, per-item pricing, PhotoLabProvider seam); and PSPA/SPOA export.

Not yet enabled for live use: the payment rail (the part that accepts a family’s payment and moves money to the photographer and the school fund), the live checkout interface in the parent store, the live payout to photographers, and live carrier delivery for parent communications. These are honest-off — present in the platform, not enabled for live transactions. There is no live checkout here. No billing. No subscription. We say so directly because schools and photographers deserve to know what is production-ready and what is still being wired.

Connected to the school platform

Picture day captures the photo. Seen puts it on the recognition page. Assembly captures the moment. The yearbook collects it all.

Pictureday.software handles the picture day logistics: consent, capture, proofing, and print. Seen is the recognition layer: the programme that ensures every student lands on a real page in the yearbook, the newspaper, or the programme — adviser-approved and consent-verified. Assembly is the moment layer: live school events captured, ticketed, and archived. The yearbook itself is built on homeroom.software — the school publishing platform that takes the PSPA export directly and turns it into a designed, printed yearbook or digital edition. For the photographer’s broader school photography business, schoolphoto.network is the studio-side home.

seen.school assembly.school homeroom.software schoolphoto.network

Early access · School admins, yearbook coordinators, photographers, studios

Book a conversation to see the current state honestly

Pictureday.software is in active development. We do conversations that show the current state honestly: how the consent intake captures both layers (depiction + marketing opt-in), how the roster-driven check-in runs on picture day, how the proof gallery gives each family private access to only their child’s photos, how the earnings ledger shows gross/fee/net per event to the photographer, and how the PSPA/SPOA export delivers to the yearbook tool. There is no pricing commitment and no signup. If it looks right for your school or studio, we discuss what early access looks like.

To book: email [email protected].

FAQ

Common questions

What does “two-layer consent” mean in practice?

Two-layer consent means the platform captures two separate decisions from each guardian before picture day. The first is depiction consent: may the school or photographer share, display, or export your child’s photo? (This covers the parent store, the yearbook export, and any digital delivery.) The second is marketing opt-in: do you want to receive notifications when proofs are ready and reminders before the order window closes? These are two separate checkboxes, resolved independently. A guardian can opt out of marketing and still grant depiction consent — or grant marketing opt-in and revoke depiction consent later. An unconsented student’s photos are excluded from every shared surface by the engine, not by the photographer manually sorting a folder after the fact. Revocation is immediate and logged: a photo becomes invisible the moment consent is withdrawn.

Is the checkout live? Can families order prints yet?

Not yet. The parent store substrate, the proof gallery, the per-item pricing engine, the PhotoLabProvider seam for fulfillment, and the earnings ledger are all built and production-ready — the logic, the ledger, and the order workflow are there. The charge rail that accepts a family’s payment and routes it to the photographer and the school fund is honest-off: it exists in the platform but is not enabled for live transactions today. There is no live checkout, no billing, and no subscription. When the charge rail is enabled (a founder-gated decision), schools and photographers will be notified. The CTA here is “book a conversation,” not “start ordering.”

Does the platform use facial recognition to organise photos?

No. Picture-day photos are organised by QR code or barcode, not by a face match. A photographer scans a student’s ID at the moment of capture; the engine links that photo to the roster record, so no face match is needed to sort or identify a student in this flow. Any optional face-matching capability elsewhere on the wider platform is off by default and runs only if a school or guardian turns it on; when it does run it is permission-checked, kept inside our own private systems, and built to honor each state’s biometric-privacy law. The retention schedule marks face data due for destruction when consent is withdrawn or the window ends; the step that carries out that destruction is not yet enabled, so a marked template is retained until it is. Families and school admins can verify exactly what runs on their students’ images by reviewing the data-processing statement.

How does the school earn a fundraising leg from picture day?

When a family places an order, the platform settles the proceeds using an exact-cent split engine. The lab/print cost and card processing come off the gross first to reach the net; the photographer’s leg and the school’s fundraising leg are then set shares of that net, at the percentages the school and photographer agreed to at setup, and the platform keeps the residual that remains on the same order — it is a named leg in the split, not a separate surcharge. A largest-remainder reconciliation pass makes the distribution total to the cent. The school sees its projected fundraising leg before the charge rail runs, not after. The split engine is built and production-ready. The charge rail that moves money is honest-off.

How does photographer earnings work? Are there hidden fees?

The earnings ledger records every order against the photographer’s account: gross proceeds, the lab and card costs, the school’s fundraising leg, the platform’s residual leg, and the photographer’s net payout — all in one view, per event, in real time. Every leg of the split is shown in the order breakdown; there is no markup on print costs, no per-student seat fee, and no hidden deduction. A photographer can see their projected net before the order window closes. The earnings ledger substrate is built and production-ready. The live payout that moves money to the photographer is honest-off pending charge-rail enablement.

What happens to photos after the order window closes?

Proof photos are retained in private family accounts for the duration of the order window. After the window closes, proofs are purged on a defined schedule unless a family has archived their order. Raw photographer uploads are retained for the fulfillment window and then removed. Photos are stored and processed on our own systems, encrypted in transit, and are never sold or shared with third parties for profit. Families can request deletion at any time; the request is logged and fulfilled within the platform’s retention schedule. No family photo is ever visible to another family.

What does the PSPA/SPOA export deliver, and when?

The PSPA (Professional School Photographers of America) and SPOA (School Portrait Order Acknowledgement) export formats deliver a standardised, lab-ready image package and order manifest from the session. The export runs after the order window closes and fulfillment routes to the print lab. The yearbook-ready PSPA export delivers the session’s consent-passing student photos in the format the yearbook adviser expects for import into the design tool. Students whose depiction consent is absent are excluded from the export by the engine. The PSPA/SPOA export is built and production-ready.

Can we use our own print lab or do we have to use yours?

The platform is built around the PhotoLabProvider seam — an interface layer that routes fulfillment orders to a print lab without hard-coding a single vendor. The design intent is to support multiple labs through the same seam, so a school or studio can keep an existing lab relationship while gaining the platform’s order management, consent, and proof gallery layers. In a conversation we discuss which lab connections are live, which are in build, and what a custom lab integration looks like for your program.

What can we actually use right now?

The platform is in active development. In a demo we walk through the current state honestly: the consent intake capturing both layers (depiction + marketing opt-in), the roster-driven check-in dashboard on picture day, the proof gallery with per-family private access, the earnings ledger showing gross/fee/net per photographer per event, and the PSPA/SPOA export. None of those involve live payments today. A conversation is the honest next step — we show what is built, what the charge-rail timeline looks like, and what early access means for your school or studio.

How is this different from a general event scheduling tool?

A general event scheduling tool manages calendars and attendance; it does not understand a picture day. It has no concept of roster-to-photo matching, no model for depiction consent distinct from marketing opt-in, no earnings ledger for the photographer, no PSPA/SPOA export, and no mechanism for a school’s fundraising leg to run alongside the photographer’s earnings. Pictureday.software is built around the operational reality of K-12 school photography — by people who run a real school photography business, not by a calendar company that added a “school photos” checkbox. The consent model is not a compliance add-on; it is the structural layer every other feature is built on top of.