From first bell to candle lighting.
Middos keeps students, families, academics, tuition, admissions, and the Jewish calendar connected—without making your staff live in six different systems.
Good morning, Sarah.
3 attendance notesWaiting for review
2 overdue balancesFamily follow-up
1 application readyAdmissions decision
One school record, not six disconnected systems.
Middos is organized around the real work schools do every day: finding a student, taking attendance, changing a schedule, collecting tuition, sending a family update, reviewing an application, or pulling the right record without digging through five tools.
One record that follows the student, not another folder of disconnected data.
Keep biographical information, household links, enrollment history, critical alerts, documents, attendance, grades, and school notes connected to the same student.
- Households & emergency contacts
- Custom fields and alerts
- Enrollment history
- Virtual file cabinet
The same data. The right view for the person using it.
School leadership
Enrollment, attendance, financial health, trends, incidents, and the items that need attention now.
Teachers
Rosters, attendance, grades, schedules, student context, and communication without administrative clutter.
Business office
Invoices, payments, financial aid, balances, family records, exports, and audit history.
Families
One place to see the information their school chooses to share, without exposing internal staff workflows.
Jewish school life isn’t an add-on.
Middos is being designed around the details generic SIS platforms often make Jewish schools work around manually.
Moving systems should feel controlled, not like a leap of faith.
Middos’s migration workflow is built around staging and validation first. Existing data can be reviewed before it becomes the school’s live source of truth.
Use OneRoster/API pathways or structured files from your existing SIS.
See what Middos found before anything is merged into live school records.
Catch missing links, duplicates, and fields that need attention.
Import when the school is satisfied with the preview—not before.
School data should stay under school control.
Middos separates roles and permissions server-side, keeps school workspaces isolated, hashes passwords, uses authenticated sessions, and records administrative activity. Production deployments should use HTTPS, managed backups, and a production database.
Read support & account guidance →Core capabilities, without pretending every school works the same way.
Biographical data, household contacts, critical alerts, custom fields, enrollment status, notes, and files.
Daily and period attendance, parent notes, exceptions, reporting, and teacher workflows.
Courses, rosters, schedules, grade records, report-card data, transcript-ready history, and comments.
Inquiry through application, interview, review, acceptance, and enrollment.
Invoices, balances, payment records, financial aid, and household-linked finance data.
CSV import/export, bulk updates, migration staging, validation, and audit history.
Documents linked to the correct student or family instead of loose shared-drive folders.
Message records and scheduling designed to grow into email, SMS, push, and quiet-hour delivery.
See Middos through the way your school actually works.
Tell us a little about your school and what you want to improve. Middos will save the request and send it directly to the walkthrough inbox.