Modules · 3 of 16
People
Employment requests, new-hire onboarding, defensible seniority numbers and professional development approvals — each with an owner and a record.
A new teacher arriving without a laptop is rarely one person forgetting. It is six departments each assuming another one had it, with no shared list saying who owns which step.
HR
Employment requests, onboarding fan-out, seniority and service history.
Onboarding tracks a new hire from offer to first day — paperwork, accounts, building assignment, certifications — with an owner on every item. Seniority drives reductions, recalls, transfers and posting rights, so the numbers have to be defensible.
module key: hr · independently toggled per
district
What it does
- Request queue for position changes, leave questions and record corrections
- Onboarding workflow engine with templated multi-department fan-out
- Per-item owners, so nothing arrives unassigned on day one
- Seniority standing by bargaining unit, and lists published as of a date
- Adjustments that carry a reason and never overwrite the previous value
- Employment records holding the service history behind each number
Payroll
Pay inquiries and the off-cycle payment queue, with four-eyes release.
Not where payroll is run — where exceptions are raised, reviewed and released, with a record of who approved each one. Money leaving the district outside the normal cycle carries two deliberate frictions.
module key: payroll · independently toggled per
district
What it does
- Pay inquiries visible to the employee and to payroll staff, not to colleagues
- Off-cycle queue for corrections, missed stipends and final cheques
- Multi-factor confirmation on the irreversible release step
- Four-eyes co-sign: the person who created an item cannot approve it
- Firewall-enforced access, so payroll data does not leak across modules
Professional development
PD requests, multi-level approval, expense claims, per-diem and AP voucher PDFs.
PD requests carry the cost, the coverage implications, and who else from the building is going — the things an approver actually decides on. Registration deadlines are recorded so an approval does not arrive after the early rate expires.
module key: prof_dev · independently toggled per
district
What it does
- Requests with cost, dates, purpose and attached agenda
- Multi-level approval chains — building, curriculum, business office
- Expense claims with line items and per-diem days
- AP voucher PDF with e-signature capture
- District PD calendar, checked before requesting something external
The rest of the platform
Every module below shares this one's directory, permissions and audit log. Turn on what you need.
Technology
Helpdesk, devices, fees and account provisioning.
Facilities & operations
Work orders, preventive maintenance, custodial supply, projects.
Safety & security
Incidents, drills, plans, chemical registers, camera footage.
Students & community
Transportation, facility reservations, ID badging.
Records & finance
Student records, public records requests, contracts, finance.
Walk through People on your own data
We load a copy of your buildings and roles, turn on the modules you asked about, and show you the queues your staff would actually see.