A Montessori school does not really have grades. It has planes of development, three-year mixed-age cycles, and a record of observation that grows slowly from a child's first day in primary through their last in adolescent community. Most school management platforms were not built for that. They assume a 7-year-old is a "second grader" and a "second grader" is a row in a spreadsheet. Montessori school management software has to model the actual pedagogy, not bolt it onto a public-school template.
What Montessori schools actually track
Three records matter most: the observation log, the lesson and presentation history per child, and the sibling group across the family. None of them are well served by a generic gradebook. A Montessori guide observes, presents a lesson, watches the child work, re-observes — and that loop, over weeks, is what becomes the term report. The software needs to keep that loop frictionless, store it privately, and surface it to parents in a form that matches the school's voice.
Observation records as the core artifact
A guide should be able to drop a quick observation note tied to a specific child and a specific material in under a minute. Over a term, those notes are the spine of the narrative report. Borderset's student tracking stores observation notes alongside attendance and lesson history, so the record is a single timeline rather than three disconnected logs. Guides choose what is visible to whom — role-based access keeps observations private to the directress team until they are ready to be shared.
Multi-age cohorts and three-year cycles
A Lower Elementary classroom holds six- to nine-year-olds together for three years. The platform should treat the cohort as the unit, not the birth-year band, and it should let a child progress through a cycle without forcing an artificial "promotion" event. Pair that with schedule management that respects long work cycles rather than slicing the day into 40-minute periods. The classroom rhythm is the schedule — the software follows the pedagogy, not the other way around.
Families across siblings
Montessori families often have two or three children at the same school across different levels. Parents need one login, one tuition statement, and one stream of school updates — not a separate portal per child. FERPA-aligned parent portals handle the family-as-unit model, including consent and communication preferences per family rather than per child record.
What a Montessori-fit platform should not do
It should not force percentage grades into the gradebook. It should not collapse a three-year cycle into an annual promotion event. It should not generate parent emails that read like a district mail merge. And it should not treat the Casa, Lower Elementary, Upper Elementary, and Adolescent communities as identical environments — the records, schedules, and reports for each are genuinely different. Borderset's school blogs feature is one of the small touches that lets a Montessori school keep its voice when communicating with families, rather than sounding like every other SIS-generated newsletter.
If you are evaluating a platform for a Montessori school, run one test: ask the vendor how the guide records a presentation of the Pink Tower, and what the parent eventually sees. If the answer involves a numeric grade, the platform is not built for you. Borderset is configured by Montessori schools who want the operations side handled without the pedagogy being reshaped to fit the software.
One more consideration that often gets missed in early-stage evaluation: transitions. A Montessori child who completes Upper Elementary and moves to a conventional middle school carries a record that is mostly observation and narrative, not letter grades. The receiving school will ask for a transcript, and the family will need something that translates the Montessori record into a form the new school can read — without rewriting history into percentages. A platform that respects the Montessori record will also help you generate that translation cleanly when the time comes, with the original observations preserved alongside the formal summary. Same again for accreditation visits: an AMI or AMS visit wants to see authentic records of guide-child interaction, not a tidied-up version produced for the audit. Borderset keeps both layers — the rich observation history and the formal summary — without forcing a choice between them, so the school can show inspectors the real artifact rather than a reconstruction.