The main office runs the school.Now it has a system.
Coverage scrambles, conduct referrals, device fines, the family call that has to happen by Friday — the work that actually keeps a building moving lives in spreadsheets, inboxes, and someone's memory. Main Office Works is the system for that work.
Built by an assistant principal · Battle-tested in a New Jersey high school
The day doesn't wait for the software.
A main office absorbs the whole building's exceptions, one interruption at a time. One morning, three interruptions — and where each one lands.
The coverage scramble starts before the coffee does: who is free period 3, who covered yesterday, which sub actually confirmed. Teacher Coverage turns the absence report into a daily plan — assignments, internal offers, cover sheets — before first bell.
Explore Teacher CoverageA referral is a promise someone has to keep.
Google Forms can collect a referral. It can't chase the follow-up, share the resolution with the right people, or remember the pattern in March. Conduct runs the whole loop — and every step lands on one student record.
- 01Teacher submits the referral or cut slip
- 02Administrator reviews, decides, resolves
- 03Counselor · secretary · teacher receive the resolution
- 04Family contacted when appropriate — never automatic
- 05Student record timeline updated, case closed
The 7 a.m. scramble, retired.
Absences come in from Aesop. Coverage builds the day: substitutes assigned, internal coverage offered to free staff — first yes wins — sub-study called, cover sheets printed per substitute, pay and savings reported. Watch the board: the uncovered period covers itself.
Running now in a live pilot, in parallel with the manual process, until the verifiers say it's boring. That's how everything here ships.
Explore Teacher CoverageOne record. Every module. Nothing re-entered.
Modules don't bolt together — they sit on one Core: districts, schools, staff, students, school years, roles. A student is entered once; conduct, devices, and coverage all read and write the same record.
- Referral 2027-0398 resolved — resolution shared with counselorOct 8
- Fine cleared — charger returned at Station BSep 30
- Cut slip 2027-0311 excused — attendance note attachedSep 22
- Chromebook CB-1102 assignedSep 3
A teacher sees submission. An AP sees the queue. Tech staff see devices. Hiding a button is never the security model.
Sensitive actions record who, what, and when — the kind of answer a board or a records request actually needs.
DeviceOps runs the 1:1 device lifecycle end to end; Staff Attendance tracks swipes, absences, and patterns on the same identity.
Built at the counter, not in a boardroom.
Main Office Works was built by an assistant principal to run his own building — a real New Jersey public high school — because the referral queue at 8:05 a.m. and the June device collection were his problems before they were product ideas.
There are no invented customer logos on this site and no numbers we can't stand behind. What exists is a working platform, in daily use where it was built, and a demo environment with fully anonymized data we'll gladly walk you through.
See it on a school day like yours.
A demo is a guided walkthrough of the working product on realistic, fully anonymized school data — no real student information, ever. Tell us about your building; the founder replies by email.