Campus · The operations console for high-school and district photography
Run picture day, staff, and photo orders for every school in the district from one operations console.
Campus Management is the back office for district picture day. One console runs every building, every photographer, and every order.
Schools onboard from the roster. Staff get roles scoped to a building. Picture day, retakes, and proofs track per school. Orders roll up as district totals. Consent gates all of it, from the first upload.
Free to start. No card charged today. Part of the same platform as Homeroom. Already set up? Sign in.
What the Campus Management console gives a district
Nine things it does today, on the same engine Homeroom runs on.
Onboard every school
Add a building and tie it to the district roster. Its picture-day status shows in the console the same day. One coordinator runs twenty schools without twenty spreadsheets.
Assign staff by role
A photographer, a registrar, a business-office clerk, and a yearbook adviser each get the scope their job needs. Scope is per building. Every grant leaves an audit trail.
Track every photo program
Picture day, athletics, activities, senior portraits, and the yearbook portrait pipeline each show status per school. An operations lead sees what is scheduled, shot, and released.
Schedule the season across buildings
Set a date per school and a photographer per date. Conflicts surface before they cost a day. Retake and make-up days hang off the original shoot.
Roll up orders and revenue
Order counts and revenue totals aggregate across the district for the business office. Figures are display-only and re-priced on our servers. No student is named in a rollup.
Report at district level
Coverage, participation, and revenue read out as district aggregates. A registrar or a business office can act on them. No student record crosses the desk.
Consent and privacy built in
Consent is enforced before a photo is sold or counted. Family contact details stay inside our own system. Face matching is off by default and is not wired in this product.
Run more than one studio
A district can use different photographers in different buildings. Each studio sees only the buildings it was assigned. The rollup still closes as one district total.
Export and close the books
The district owns its roster, its photos, and its family records. Export them at any time. A season closes with a reconciled total the office can file.
A season, start to finish
How a district runs picture day across every building
Eight stages, one console. This is the cycle a district repeats every year.
Roster sync
The district roster lands first. Buildings, grades, and staff come with it. Nothing is typed twice, and nothing is keyed from a printout.
Schedule per building
Each school gets a date, a room, and a photographer. Conflicts across buildings surface before the calendar is locked, not on the morning of the shoot.
Assign the staff
A photographer and a building contact are attached to each shoot. Scope follows the assignment. Nobody holds access to a building they do not work.
Shoot day
The shoot runs against the building roster. Absent students are flagged as it happens. The list is captured on the day, not reconstructed in November.
Retakes and make-ups
Absent and retake students carry forward to a make-up day automatically. The make-up list builds itself from shoot day. No one rebuilds it by hand.
Proofs and consent
Images are matched to the roster and held behind consent. A photo without a released consent is not offered for sale and is not counted.
The order window
Families order from the storefront on campus.photos. The console watches counts and totals, never names. Money is honest-off, so no card is charged today.
Close the season
Orders and revenue reconcile into one district total. The business office exports what it needs and files it. The next season starts from the same roster.
The operations desk
Five seats, five scopes, one district
Scope is the product. Every seat gets the access its job needs and nothing wider.
| Seat | What they do here | Never sees |
|---|---|---|
| District operations lead | Onboards schools, sets the season calendar, and reads the district rollup | An individual student record |
| Building secretary | Confirms one building roster and its picture-day date | Any other building |
| Photographer or studio | Works the shoots assigned to them and uploads against the roster | Rosters for buildings they were not assigned |
| Business office | Reads order counts and revenue totals, and exports the reconciliation | Family contact details |
| Yearbook adviser | Pulls released portraits for the book from the buildings they serve | Order or revenue figures |
Every grant is recorded with who made it and when. The server re-checks the grant on each request, so a scope narrowed in the morning is narrow by the afternoon.
Why a console at all
What picture day costs a district without one
These are the six failures we hear about most. Each one has an operational answer here.
The schedule lives in a spreadsheet
One file gets emailed around and three versions end up in circulation. The console holds one calendar. Every building reads the same date.
Nobody knows who was absent
Absences get reconstructed from memory weeks later. Here the make-up list builds itself on shoot day, from the roster the shoot ran against.
The district cannot see its own numbers
Totals arrive as a statement after the season is over. The console shows the rollup while the order window is still open.
Staff access is a shared login
One password gets passed around a building and nobody can say who did what. Every account here is its own, scoped by role, with an audit trail.
Consent is a paper form in a drawer
A signature in a filing cabinet cannot gate a sale. Consent lives with the student record and gates the photo directly, at the moment it would be sold.
Two buildings use two different studios
Two workflows, two file formats, and two invoices to reconcile by hand. Assign each studio its buildings. The district still closes one total.
The students who were not there
Retakes and make-ups carry themselves forward
Every district loses students on picture day. A child is absent, a shot does not work, a family asks for a retake. The expensive part is not the second shoot. It is rebuilding the list.
Here the list is a by-product of the first shoot. The sitting runs against the building roster, so an absence is recorded the moment it happens. Retake requests attach to the student, not to a note in an inbox. When the make-up day opens, the roster for it already exists.
A district coordinator sees the outstanding count per building while there is still time to fix it. That is the difference between a coverage number and a coverage problem you can act on.
Signed in, scoped by role
Operations staff see aggregates, never a student
The console is staff-gated. A district administrator or an operations lead signs in and sees the district rollup: schools, photo programs, staff, and order revenue, as counts and totals. No student record reaches an operations screen. Every scope is granted by role with an audit trail, and the server re-checks that grant on every request. It is an operations surface, not a family storefront.
More than one photographer
A district that uses several studios still closes one set of books
Large districts rarely use one photographer. The high school has its own arrangement, the elementary buildings share another, and athletics is a third. That usually means three workflows and three reconciliations.
Assign each studio the buildings it works. That assignment is the scope: a studio sees those rosters and no others, uploads against them, and never touches a building it was not given. The district still reads one rollup across all of it.
The consent gate does not vary by studio. A photo is sellable when a released consent allows it, whoever took it.
What the office can read out
Four readouts, and what each one never contains
An operations report is aggregates. We state the negative space beside every report, not once in a footnote.
Coverage by building
How many students were photographed against how many are enrolled. Read it per school or across the district.
Never contains: Which students
Program status
Which photo programs are scheduled, shot, and released in each building, and which are still open.
Never contains: Any image
Order and revenue rollup
Order counts and revenue totals, by building and by district, while the order window is still open.
Never contains: A buyer name or a card
Staff and access
Who holds which role in which building, and when each grant was made and by whom.
Never contains: A student photo
One platform, two front doors
Campus Management and Homeroom are siblings on the same engine
Campus Management is part of the same platform as Homeroom, operated by the same team. It is the operations console for institutions, not a separate company.
Same roster model, same consent gate, same accounting. Two front doors, tuned to who is at the keyboard. Campus Management speaks to district and high-school operations. Homeroom speaks to a community school and its families. Neither is a fork, and ownership is not concealed. Both are run by the same team.
| Campus Management (operations) | Homeroom (community) | |
|---|---|---|
| Built for | District and high-school operations teams | Elementary schools and their families |
| Voice | Institutional and operational | Warm and community |
| What it does | Runs schools, staff, programs, and order rollups | Finds a child and orders portraits |
| Data it shows | District aggregates -- never a student list | One family and its own photos |
| Same engine | Yes -- one platform, one consent model | Yes -- one platform, one consent model |
| Operated by | The same team | The same team |
Consent, built into the foundation
A photo counts only when consent says it can
A photo counts toward an order or a rollup only when a released consent allows it. A student under 18 is shown or sold only against that released consent. Never publicly.
Face matching is off by default. The matching capability behind it is not wired and cannot be switched on from this product. A student is found by the school roster instead. Family contact details stay inside our own system, not an outside marketing company.
A student is found by the school roster, not a face scan. Face matching is off by default. A photo is never sold or counted without a released consent. The promise a district makes to families is built into the foundation.
The posture, in four sentencesWhose data it is
The district owns the roster, the photos, and the family records
The console holds that data for the district. It does not resell it, and it does not pass family contact details to an outside marketing company. Ownership does not transfer to us because the data sits on our servers.
Export is available whenever the district wants it, not only at the end of a contract. If a district leaves, it takes its records with it and we delete on the retention terms it agreed to. Enterprise plans put those terms in writing before anything is imported.
How the order rollup works
Review an order rollup and see a receipt — no card charged today
Order and revenue figures are display-only. Our own servers re-price every line from the district catalog. A buyer can never set what bills. You can review a rollup and see a receipt, with no card charged today.
The rollup runs on the same honest-off receipt as the rest of the platform. Figures are display-only and re-priced on our own servers from the district catalog. A buyer cannot alter what bills. Live card payment turns on for a district only once its store is fully wired. There is no separate photo company holding a family record.
Plans
Start free -- pick the scope that matches your district
Every plan starts free. No card is charged today. Figures are display-only and re-priced on our own servers. Live card payment turns on for a district only once its store is fully wired.
One school
Single school console
Onboard one building. Assign staff by role. Track its season, its retakes, and its programs.
- Onboard one school and its staff
- Role-scoped staff accounts and an audit trail
- Season calendar, picture-day and retake tracking
- Photo-program status for that building
- Honest-off order and revenue figures for that school
A whole district
District console
Every school on one console. District-wide staff scopes. One order-and-revenue rollup the office can audit.
- Everything in Single school console
- Every school onboarded to one console
- District-wide staff role scopes
- Multi-studio assignment across buildings
- One order-and-revenue rollup across the district
- District aggregates only -- never a student list
Large and multi-district systems
Enterprise district console
A tailored rollout for large and multi-district systems. Data-ownership terms in writing. A named contact.
- Everything in District console
- A tailored console rollout
- Data-ownership and retention terms in writing
- A named point of contact
- Help onboarding schools and standing up staff roles
Talk to us for district pricing. No card is charged today, and no field on this page can turn a charge on.
Connected products
Campus Management is one console on a wider platform
These are real sibling addresses. They share the roster, the consent gate, and the engine.
campus.software
The institutional platform pitch to districts and high schools. Picture day, athletics photos, student IDs, and the yearbook portrait pipeline. This console is its operations face.
campus.photos
The family storefront on the same platform, where a parent finds a child photo and orders. The console rolls up the orders that storefront produces.
campus.email
School and district mailboxes on the same platform. A building contact writing to families is reachable at an address the district owns.
homeroom.software
The community-facing sibling brand for elementary schools and their families, on the same engine, roster model, and consent gate.
k12.photos
The school-photography property the platform is built around. The wider home for how picture day works across our K-12 surfaces.
FAQ
Common questions
Is Campus Management a different product from Campus on campus.software?
No. Same engine, same roster, same consent model. campus.software is the platform pitch to a district. Campus Management is the back-office console staff sign in to for onboarding schools, running the season, and rolling up orders.
What does it cost, and is a card charged today?
Every plan starts free, and no card is charged today. Order and revenue figures are display-only and re-priced on our own servers. Live card payment turns on for a district only once its store is fully wired.
Does the console show a student list or student records?
No. It rolls up schools, programs, staff, and order revenue as counts and totals. No individual student record reaches a district administrator screen. A photo counts toward a rollup only against a released consent.
How does staff access work?
Every staff account gets a role and a building scope, with an audit trail behind every grant. A coordinator in one building does not see another building. District-wide controls stay with the district.
How are retakes and make-ups handled?
Absences are flagged on shoot day, against the roster the shoot ran against. Those students carry forward to the make-up day automatically. Nobody rebuilds the list by hand weeks later.
Can a district use more than one photographer?
Yes. Assign a studio to the buildings it works. Each studio sees only those buildings and their rosters. The district still closes one reconciled total across all of them.
Does it use facial recognition to find students?
No. Students are matched by the school roster. Face matching is off by default. The capability behind it is not wired. It cannot be switched on from this product.
Can a district export its data?
Yes. The district owns its roster, its photos, and its family records, and can export them whenever it wants. The console holds that data for the district. It does not resell it.
What happens to the data if a district leaves?
The district exports what it wants and we delete on the retention terms it agreed to. Ownership never transfers to us. Enterprise plans put the retention terms in writing.
Is Campus Management connected to the family photo storefront?
Yes. campus.photos is the family storefront on the same platform. Families order there, and the console rolls up the resulting orders and revenue for the district office. Neither surface is a separate company.
Does it import from our student information system?
The console is roster-driven and the district roster is the source of record for buildings, grades, and staff. campus.software covers the roster and SIS side of the platform in detail.
Who signs in day to day?
A district operations lead, a building secretary, the assigned photographer, the business office, and the yearbook adviser. Each seat sees the scope its job needs and nothing wider.
How does Campus Management relate to Homeroom?
Same platform, same team, two front doors. Campus Management is the operations console for institutions. A district also running a community school on Homeroom shares one roster model and one consent gate.
What is true today
We are honest about what is shipped
Shipped School onboarding, staff roles and the audit trail, the consent gate, the season and retake tracking, and the district aggregate rollups are live today.
Honest-off Live card checkout is off. Order and revenue figures are display-only. You can review a rollup and see a receipt, with no card charged today. Card payment turns on once a district store is fully wired.
Off and not wired Face matching is off by default. The capability behind it is not wired. It cannot be switched on from this product.
A district administrator or a yearbook adviser can start today. No contract, and no card charged today.