How to choose school software

Most failed school software projects were not lost on a missing module. They were lost when admissions, fees, and the register disagreed after go-live.

A feature grid makes every vendor look identical. The test is one student, one awkward case, one calendar. Do this against working days on one student record, with publish gates, not a generic weekday grid. Named facts: working days, one student record, publish gates. Name the owner before the first family sees a receipt.

Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house.

Buying an ERP because the dashboard looks corporate.
Skipping parent-portal publish gates in the demo.
Assuming September is the year start worldwide.

Write three awkward cases

Mid-year joiner, concession after invoicing, holiday on the calendar. If a demo cannot walk those, stop. Write the three cases on paper before the demo: a mid-year joiner, a concession after the invoice exists, and a day the holiday master already closed. If the vendor opens a second list for any of them, stop.

For choosing school software, “Write three awkward cases” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Buying an ERP because the dashboard looks corporate. Should we write our own school software? Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house. Named facts: working days, one student record, publish gates.

“Write three awkward cases” for choosing school software fails when this is skipped: Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns.

The cost is the coordinator time reconciling spreadsheets. Price the first fee cycle and the first exam week.

Write three awkward cases
Buying an ERP because the dashboard looks corporate.
Named facts: working days, one student record, publish gates.

Name the calendar owner

Working days drive attendance, exams, and leave. Ask who publishes official exceptions. Ask who may publish an official exception the same day, and whether attendance, exams, and leave all read that change. A calendar nobody owns will be retyped by every department.

For choosing school software, “Name the calendar owner” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Skipping parent-portal publish gates in the demo. Is open source cheaper? The cost is the coordinator time reconciling spreadsheets. Price the first fee cycle and the first exam week. Named facts: working days, one student record, publish gates.

“Name the calendar owner” for choosing school software fails when this is skipped: Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns.

The one whose errors currently reach parents: usually fees or admissions.

Name the calendar owner
Skipping parent-portal publish gates in the demo.
Named facts: working days, one student record, publish gates.

Score honest limits

Statutory ledgers, live board-portal filing, SSO, and biometric hardware are not universal. Mark them not met if absent. Mark statutory filing, live board-portal submission, enterprise SSO, and biometric hardware as not met unless that deployment actually has them. A slide that says “supported” is not a receipt.

For choosing school software, “Score honest limits” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Assuming September is the year start worldwide. What is a good first module? The one whose errors currently reach parents: usually fees or admissions. Named facts: working days, one student record, publish gates.

“Score honest limits” for choosing school software fails when this is skipped: Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns.

Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house.

Score honest limits
Assuming September is the year start worldwide.
Named facts: working days, one student record, publish gates.

Phase modules

Roster and fees first, then timetable and exams, then HR. Unused modules do not have to go live on day one. Go live with roster and fees, then timetable and exams, then HR. Unused modules stay off. The first parent-facing error should be the module you turned on, not a feature you have not configured.

For choosing school software, “Phase modules” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Buying an ERP because the dashboard looks corporate. Should we write our own school software? Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house. Named facts: working days, one student record, publish gates.

“Phase modules” for choosing school software fails when this is skipped: Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns.

The cost is the coordinator time reconciling spreadsheets. Price the first fee cycle and the first exam week.

Phase modules
Buying an ERP because the dashboard looks corporate.
Named facts: working days, one student record, publish gates.

How this playbook changes for a real campus

choosing school software still starts from the holiday master, not a borrowed weekday grid. Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns.

Working days, one student record, and publish gates are the checks. Receipts have to match finance before families see a result.

Buying an ERP because the dashboard looks corporate. Skipping parent-portal publish gates in the demo. Assuming September is the year start worldwide. Named facts: working days, one student record, publish gates.

The cost is the coordinator time reconciling spreadsheets. Price the first fee cycle and the first exam week.

Write three awkward cases
Named facts: working days, one student record, publish gates.
the boards the campus reports to

Where this usually breaks

Buying an ERP because the dashboard looks corporate. Skipping parent-portal publish gates in the demo. Assuming September is the year start worldwide.

A second spreadsheet for the real list is the usual failure. Named facts: working days, one student record, publish gates.

choosing school software still fails when this is skipped: Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns. Saved marks stay drafts until the school publishes them.

Schoolyi is built around one student record and one academic calendar. Book a demo with your three awkward cases, not a slide deck.

Buying an ERP because the dashboard looks corporate.
Skipping parent-portal publish gates in the demo.
Assuming September is the year start worldwide.

How Schoolyi fits

Schoolyi is built around one student record and one academic calendar. Book a demo with your three awkward cases, not a slide deck.

Open /platform after you can describe the awkward case for choosing school software. This page is a playbook, not a feature grid. Name the owner in the demo. Named facts: working days, one student record, publish gates.

That walkthrough still uses the holiday master the school will go live on and the fee heads families can see on a receipt.

Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house.

Playbook: /how-to/choose-school-software
Product: /platform
Book a demo with your awkward case, not a slide deck

Questions

Should we write our own school software? Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house.

Is open source cheaper? The cost is the coordinator time reconciling spreadsheets. Price the first fee cycle and the first exam week. Named facts: working days, one student record, publish gates.

Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns. Named facts: working days, one student record, publish gates. Ask these before the demo.

What is a good first module? The one whose errors currently reach parents: usually fees or admissions. Named facts: working days, one student record, publish gates.

Should we write our own school software? Only if you want to own calendar exceptions, fee receipts, and publish gates forever. Most schools should buy an operations system and keep pedagogy in-house.
Is open source cheaper? The cost is the coordinator time reconciling spreadsheets. Price the first fee cycle and the first exam week.
What is a good first module? The one whose errors currently reach parents: usually fees or admissions.

Bring this playbook to a demo

Score the handoff: the accepted applicant becomes the roster row, the fee account, and the attendance denominator on the holiday master the school already owns. Schoolyi is built around one student record and one academic calendar. Book a demo with your three awkward cases, not a slide deck. Named facts: working days, one student record, publish gates. Book the demo with that owner in the room.

Score statutory filing and hardware as not met unless the deployment actually has them. Publish gates still decide what families see.

Write three awkward cases

Open /platform
Book a demo with the awkward case
Named facts: working days, one student record, publish gates.

How to choose school software