Case study / Education / Microschool operations

UPDATED 12 NOVEMBER 2026

Commons: microschool operations software for attendance, learner progress and family communication

Commons is microschool operations software built by Logic Square for the Indiana Microschool Collaborative. It runs attendance, learner pods with tasks, goals and badges, family messaging, role based access and activity fee payments for a network of five schools and about 223 students as of October 2026, and it is designed to exchange enrollment and attendance records with Alma, the network’s student information system, every day. Commons has been live since August 2026. An AI-assisted layer for teachers is in development; nothing AI has shipped as of October 2026.

Client
Indiana Microschool Collaborative (IMC)
Product
Commons
Industry
Education
Status
Live since August 2026; AI layer in development
Scale
Five schools, about 223 students (October 2026)
Integration
Alma SIS, enrollment in, attendance out, designed to run daily
Stack
MERN

01 / The Challenge

A school network’s backbone, without the weight

Microschools need the operational backbone of a school network without the administrative weight of one. Off the shelf school ERPs were built for large institutions with IT departments and bring the complexity the microschool model exists to escape.

IMC already had a student information system, Alma, for enrollment and state reporting. What it did not have was a daily operating layer shaped to how a mixed age, mastery based microschool actually runs: pods, goals, evidence of progress, attendance, and families who expect to see growth the way the school explains it.

02 / The Decision

Integrate with the system of record. Do not replace it.

The first decision was to leave enrollment where it already lived. Alma stays the authoritative source. Commons is designed to import student records from it and send attendance back for state reporting. Staff enter enrollment once, in Alma. Teachers record attendance once, in Commons. No competing enrollment system, no double entry for those workflows.

The second decision was about the learning model. Progress is modeled as goals, tasks and evidence inside pods, not only as grade level records, so educators review progress the way they teach and families understand growth the way the school explains it.

The third was sequencing. AI was in the ambition from the start; the decision was to earn it. Operational foundations first, then an AI assisted layer on top, which is why it is in development rather than the headline.

Alma does

Enrollment, demographics, guardians, the official student record, state reporting

Commons does

Attendance, learner pods, tasks, goals, badges, evidence, family messaging, roles by school, activity fees

Shared by design

Student identity (the Alma ID is the key), enrollment status, attendance records

Why the network kept Alma: the official record and state reporting were already working and audited. Rebuilding them would have cost months and bought nothing. The gap was the daily learning and operations layer, so that is what Commons is.

03 / What We Built

The operational spine of the network

The learner progress workflow

  1. 01

    Learner: set goals. Goals and tasks live in the learner’s pod.

  2. 02

    Evidence: record work. Work and progress are recorded against those goals; badges mark milestones.

  3. 03

    Educator: review progress. Teachers see their pods and review progress in one place.

  4. 04

    Family: understand growth. Families see their own children’s progress and messages, nothing else.

IMC pod management with student and grade counts.
LEARNER PODS, TEACHER VIEW

Alma integration: enrollment in, attendance out

Alma to Commons: enrollment and student information creates or updates Commons records. Commons to Alma: attendance recorded in Commons is sent to Alma for the schools’ state reporting process. The integration is designed to run daily and to flag errors to the team.

IMC attendance form with student status and arrival time fields.
DAILY ATTENDANCE IN COMMONS, NAMES BLURRED

Attendance, pods, messaging, fees

In production from day one: attendance; learner pods with tasks, goals and badges; family messaging; role based access; and activity fee payments for non tuition charges such as museum visits and field trips. The schools do not charge tuition through Commons.

Commons family messaging thread in the parent app; names and message text are blurred
FAMILY MESSAGING THREAD, CONTENT BLURRED

Role based access

Network admins see the network. Teachers see records permitted for their school and role. Families see only permitted information about their own children. Connections are encrypted in transit. FERPA aware handling of student records and COPPA aware treatment of data involving minors; aware by design, no certification claims.

04 / Engineering Notes

Integration first, framework list second

System of record discipline. Enrollment originates in Alma; attendance originates in Commons; each flows to the other daily.

Access boundaries. Role based permissions by school and role; families scoped to their own children.

The stack. MERN: MongoDB, Express, React, Node.js, built as one coherent platform so that a school with no IT department can rely on it every morning.

IMC network dashboard with microschool performance overview.
NETWORK ADMINISTRATOR VIEW ACROSS SCHOOLS

05 / The Results

Live since August 2026 across the network

  • Live since August 2026 for attendance, learner progress, family messaging and activity fees.
  • Five schools and about 223 students on Commons as of October 2026, figures approved by IMC’s founder for publication.
  • Alma integration designed for enrollment in and attendance out, daily, with error visibility.
  • AI assisted layer in development: drafting tasks from brief teacher instructions, helping teachers monitor progress, and suggesting next activities based on a learner’s goals. Every suggestion stays subject to teacher review. Nothing AI has shipped yet.

Separately, the Indiana Microschool Collaborative was named a 2026 Yass Prize finalist and received a $500,000 finalist award for its educational model. That recognition is IMC’s, for how it teaches; it is not an award for Commons.

“What stood out most was Logic Square’s willingness to really understand our model and build around it rather than trying to force us into a generic platform.”
George Philhower, CEO, Indiana Microschool Collaborative Clutch review, July 2026

Running a microschool or alternative education network on disconnected tools?

Book a Strategy Call

06 / Who this pattern fits

A small school network with a learning model a generic SIS cannot express, and a system of record it must keep: microschool networks, hybrid and alternative schools, learning pods, charter and private school groups, tutoring and cohort programs.

Integrate with the SIS, build the daily layer around how you teach, add intelligence once the foundations are trusted. Microschool management software usually means attendance, family communication, progress tracking and administrative workflows in one place; Commons handles that daily layer while Alma remains the system of record for enrollment. See education software for school networks. For the audit and accreditation side of a network, see the CES Academy school audit platform.

FAQ

Common questions

What is microschool management or operations software?

Microschool operations software is the daily operating layer a small school network runs on: attendance, learner progress, family communication, fees and roles, connected to the student information system of record rather than replacing it. Buyers call it microschool management software; Commons is that layer for IMC, and Alma keeps enrollment and state reporting.

Does Commons replace Alma?

No. Alma remains the enrollment and state reporting system. Commons is designed to import student records from Alma and send attendance back daily, so staff do not enter the same data twice for those workflows.

What is live today?

Attendance, learner pods with tasks, goals and badges, family messaging, role based access and activity fee payments, across five schools and about 223 students as of October 2026.

How is student data handled?

Encrypted connections and role based permissions scoped by school, role and family. FERPA aware and COPPA aware handling; we do not claim certifications or legal compliance.

What will the AI layer do?

It is in development. It is meant to reduce manual teacher workload: drafting tasks from short instructions, helping monitor progress and suggesting next activities. Recommendations remain subject to teacher judgment and approval. See our applied AI service.

Running an education network on disconnected tools?