Guide
Twelve criteria for choosing a student information system for an independent school, the question to ask on each, and the answers that should worry you.
Choosing a student information system for independent schools comes down to twelve things, none of them on the feature list: whether the platform was built for independent schools or adapted from a district product, whether one student record runs everything, whether admissions flows into enrollment without re-entry, how it handles financial aid and variable tuition, whether payments are native, what a parent can do on a phone, what the third year costs, the contract and renewal terms, what migration actually includes, who answers the phone, how a new hire learns the system, and whether security and uptime can be verified rather than described. Every vendor passes a feature checklist. Very few pass all twelve of these.
If you’ve searched for what to look for in an SIS, or for SIS evaluation criteria, you’ve seen the list already. Customization. Integration. Security. Support. User experience. It shows up on every vendor blog, including some good ones, and it isn’t wrong. It’s just useless in a demo, because every platform on the market will say yes to all five and mean it.
We wrote this for a narrower reader: the head of school or business manager at an independent or private K-12 school. That’s not a small district. You run admissions instead of assignment zones. You collect tuition instead of drawing a per-pupil allocation. You give away financial aid out of your own operating budget. Your business office is two or three people, there’s no IT department, and your parents can leave if the experience is bad enough. And you’re small: two out of three U.S. private schools enroll fewer than 150 students, according to the federal Private School Universe Survey.
A platform built for a 40,000-student public district can technically do your job. It’ll also spend half its screen real estate on state reporting you’ll never open, and price the implementation like a capital project.
So for each of the twelve criteria below, we’ve included the question we’d ask on a demo call and the kind of answer that should slow you down. Take the SIS demo questions with you. Ask every vendor on the shortlist the same twelve, and score them while the call is still fresh, because by the third demo they blur together.
Disclosure: Sycamore is the platform publishing this guide. We’ve used our own numbers as examples where a real number is more useful than a vague one. We also wrote the criteria to be fair, which means a school working through them in good faith may well land somewhere else. That’s fine. A rubric that only ever points at its author isn’t a rubric.
| # | Criterion | Ask this | Be nervous if you hear |
|---|---|---|---|
| 1 | Built for independent schools | “What share of your schools are independent or private K-12?” | “We serve the full K-12 market” |
| 2 | One student record | “Is the financial record the same record as the student record?” | “They sync nightly” |
| 3 | Admissions into enrollment | “Does an inquiry become an enrolled student without re-entry?” | “Enrollment is a separate module” |
| 4 | Financial aid and variable tuition | “Show me a family with two kids on different awards” | “That’s handled in a partner product” |
| 5 | Native payments | “Who owns the processing relationship?” | “We integrate with several providers” |
| 6 | The family experience | “What can a parent do in the app with one login?” | “Parents use the web portal” |
| 7 | Year-three cost | “What’s the all-in cost in year three, fees included?” | One per-student number, no fee schedule |
| 8 | Contract and renewal | “What’s the minimum term, and what happens at renewal?” | Multi-year auto-renewal |
| 9 | Migration | “What do you migrate, and what do we rebuild?” | “We’ll scope that after signature” |
| 10 | Support | “Who picks up the phone, and where are they?” | Tiered support with a paid upgrade |
| 11 | Training after go-live | “How does a hire in year two learn this?” | “We can quote more training days” |
| 12 | Security, uptime, roadmap | “Where’s your status page, and what shipped this year?” | “We haven’t had significant issues” |
We put this first because the answer tends to predict several of the others. District-first platforms carry assumptions that don’t fit you. Attendance is wired to state funding formulas. There’s no native idea of a tuition contract. Alumni are an afterthought. Configuration assumes a central office with people whose whole job is configuration.
Platforms built for independent schools start from the opposite assumptions. They expect an admissions funnel, a re-enrollment season, a family who pays a bill, and a registrar who is also the office manager and occasionally the substitute nurse.
Ask on the demo: What percentage of your customers are independent or private K-12, and what’s the median school size?
If the vendor answers with total student count instead of segment mix, note it. Scale and fit aren’t the same thing, and vendors who lead with scale usually know that.
For what it’s worth, Sycamore has only ever served private and faith-based K-12 schools, since 2001, which is why the tuition record and the student record were designed as one thing instead of bolted together later.
“All-in-one” is the most abused phrase in this market, and we say that as a company that uses it. A lot of platforms marketed as unified are two or three acquired products behind a shared sign-in page, synchronizing overnight.
You feel the difference on an ordinary Tuesday. A family updates their address. Does it change in billing, in the emergency contact list, and on the report card mailing label? Or in one of the three, with the other two waiting for a batch job?
Ask on the demo: When a parent changes a phone number in the app at 9am, which records show it at 9:01?
Listen for the word “sync.” Syncing is what you do between systems. Inside a single system there’s nothing to sync.
At most schools we talk to, the handoff from admissions to enrollment is where data goes to die. The inquiry lives in one tool, the application in another, the enrollment contract in a third, and a family ends up typing the same information three times while the office re-keys it twice.
Watch for the moment in the demo where an accepted applicant becomes an enrolled student. If the presenter switches tabs, you’ve just found next spring’s re-entry project.
Ask on the demo: Take me from inquiry to signed contract to a student with a schedule, without leaving the platform.
Admissions priced as a separate module is a tell. It usually means it was built separately, or bought.
This one eliminates district-built systems faster than anything else, because districts simply don’t do it. Your reality includes a family with three children, one on a 40 percent award, one on a sibling discount, one paying full tuition, and a payment plan that started in July and changed in November.
If aid awards, discounts, and plans aren’t computed in the same place the invoice is generated, somebody in your business office is maintaining a spreadsheet to bridge the gap. We’ve seen that spreadsheet. It’s usually the real system of record, and the SIS is just where the grades live.
Ask on the demo: Show me a live family record with two children on different awards and a mid-year plan change.
“That’s handled in our partner’s grant and aid product” means two vendors, two support queues, and two renewal dates.
Two different questions hide in here. First, does the vendor own the payment processing, or resell someone else’s? Second, and more interesting for your budget, do you get to decide who absorbs the transaction fee?
Most platforms treat processing fees as a fixed cost of doing business. Some let the school choose. That choice is worth real money. A school collecting two million dollars a year in tuition sees roughly twenty thousand dollars move for every one-point change in who covers card fees.
Ask on the demo: Can the school absorb the fee, pass it to families, or split it, and can that be different for cards and ACH?
Here’s our own math as an example, since we get asked about it a lot. Sycamore acquired TuitionEP in 2025 and runs payments natively. Cards process at 2.9 percent plus 30 cents per transaction, ACH at 0.8 percent with that portion capped at five dollars, and Sycamore adds a 1 percent convenience fee on either one with no cap. So a card payment costs 3.9 percent plus 30 cents, and an ACH payment 1.8 percent with only the banking portion capped. The school picks who pays each one, and a lot of schools split the card fee down the middle with families.
Your parents aren’t opening a laptop to check a lunch balance. If the “mobile experience” is a responsive web portal with a separate login for payments, families will call the front office instead, and the front office is you.
The test isn’t whether an app exists. It’s how many screens and logins sit between a parent and the four things they want: what’s owed, what got graded, whether their kid is in the building, and what’s happening this week.
Ask on the demo: From one login, show me tuition balance, attendance, grades, and the school’s messages.
If the payments app and the school app are two different downloads, assume parents will keep one and forget the other.
Per-student pricing is the headline. It’s rarely the number you pay. Build a three-year model with five lines: license, one-time onboarding, payment processing, whichever modules turn out to be “premium,” and the staff hours you’ll spend doing work the platform didn’t absorb.
Then ask the question vendors like least. What changes in year two and year three?
Ask on the demo: Give me the all-in three-year cost for our enrollment, onboarding and processing included, and tell me what escalates.
A per-student price with no published fee schedule is a yellow flag. If the processing economics aren’t on paper, they’re negotiable, and not in your direction.
Our number, for reference: Sycamore lists at four dollars per student per month with every module included, plus a low one-time onboarding fee that’s based on school size and discounted further when the school belongs to a district, diocese, or group.
Contract mechanics decide how much leverage you’ll have three years from now. Three things matter: the minimum term, whether your rate is locked for it, and whether renewal happens automatically.
Multi-year auto-renewal is the one to watch. It turns a software decision into a standing obligation, and it has a habit of surfacing sixty days before a deadline nobody put on the calendar.
Ask on the demo: What’s the minimum term, is my per-student rate locked for it, and is renewal automatic or something we choose?
A three-year term with automatic renewal and a narrow notice window is the combination we’d push back on hardest.
Ours: Sycamore contracts start at an 18-month minimum. Longer terms lock the per-student rate for the length of the term, so a future price change can’t reach you, and there’s no multi-year auto-renewal.
Every vendor says migration is included. Fewer will tell you what “included” contains. The gap between “we import your students and families” and “we bring historical grades, transcripts, discipline records, attendance history, and the financial ledger” is roughly one summer of your registrar’s life.
Timing matters as much as scope. A migration that lands in June is survivable. The same migration landing in October is a crisis with a mailing list.
Ask on the demo: List exactly which record types you migrate, which you don’t, and what a realistic calendar from signature to go-live looks like.
No named migration owner, or a scope conversation that gets deferred until after signature, are both reasons to slow down.
You don’t have IT. The vendor’s support team is your IT department, so interview them the way you’d interview a hire.
Ask about tenure specifically. In our experience support quality tracks how long the people answering have been answering. A team with a decade of average tenure has seen your problem before, probably at a school that looks like yours. A team rebuilt every eighteen months is reading the same knowledge base you could read yourself.
Ask on the demo: Where’s your support team, what’s their average tenure, and is phone support included at every tier?
Support tiers with a paid upgrade path are a pricing model, not a service model.
Ours: Sycamore support is US-based, included for every school regardless of size, and the team averages close to a decade of tenure.
Go-live training is the easy part. The vendor is motivated and everybody’s paying attention. The harder question is October of year two, when your admissions director leaves and the replacement has never seen the platform.
If the answer is “we can quote additional training days,” you’ve found a recurring cost that won’t show up in your three-year model until it does.
Ask on the demo: What on-demand training exists, who can use it, and what does it cost in year two?
Training sold as professional services hours, rather than a library your staff can open at 9pm on a Tuesday, is the thing to watch.
Ours: Sycamore Academy is an on-demand training library at academy.sycamoreleaf.com, open to staff and families, and it’s included rather than quoted.
Two claims here are checkable. Uptime is checkable if there’s a public status page with history. Data handling is checkable if the vendor will put FERPA obligations, breach notification timelines, and data ownership in writing (the Department of Education’s student privacy office publishes exactly what a school is on the hook for, and a vendor who has read it will say so). “We take security very seriously” is not checkable, so treat it as background noise.
Ask about the roadmap too, which most guides skip. What shipped for independent schools in the last twelve months, and what’s committed for the next twelve? A platform that hasn’t released anything meaningful for your segment in a year is telling you, politely, where you rank.
Ask on the demo: Where’s your public status page, what’s your breach notification commitment in writing, and what have you shipped for independent schools this year?
Uptime described in adjectives is the red flag. Ask for the URL. Ours is public at sycamoreleaf.com/sycamore-status, and we’d expect every vendor on your list to have one.
Most independent school software selection processes go wrong at the demo, not in the paperwork, so weight the twelve before you sit through a single one. Most schools find that four of them carry the decision, and which four depends on where the pain is right now.
If the business office is drowning, weight 4, 5, and 7. If the last migration went badly, weight 9 and 10. If parents are complaining, weight 3 and 6. If you’ve been burned at a renewal, weight 8 and 12.
Score each vendor one to five on your weighted criteria during the call, not afterward. A simple weighted total beats a feature matrix every time, because a feature matrix rewards whoever checks the most boxes, and none of the boxes are weighted by how much you’ll actually use them.
Then do the thing almost nobody does. Call two reference schools the vendor didn’t hand you. Ask them one question: what surprised you in month four?
What’s the difference between an SIS and school management software?
An SIS is the system of record for student data: enrollment, attendance, grades, schedules, transcripts. “School management software” (or private school management software, if you’re searching) usually means an SIS plus the operational layer around it, meaning admissions, tuition billing, payments, and family communication. Independent schools generally need the second thing, because the operational layer is where the staff hours go.
How long does it take to switch student information systems?
For a typical independent K-12 school, four to eight weeks from signature to go-live is realistic when the historical data is clean and the calendar cooperates. Migrations that bring multiple years of transcripts and financial ledgers run longer. Starting in late spring for a fall go-live is the lowest-risk pattern we’ve seen.
What should an SIS cost for a private school?
Published per-student pricing in the independent K-12 market runs from roughly three to eight dollars per student per month, with big variation in what’s included. The more useful number is three-year total cost with onboarding, processing, and any separately priced modules folded in. Platforms that only quote on request tend to sit at the high end.
Can we keep our existing payment processor?
Sometimes. It’s worth asking what you give up. Schools that keep a separate processor usually keep a separate parent login, a separate reconciliation process, and a second support queue. The rate savings are often smaller than what it costs in business office hours.
What are Sycamore’s contract terms?
Sycamore contracts start at an 18-month minimum. Longer terms are available and lock in the per-student rate for the length of the term, protecting the school from any future price changes. There’s no multi-year auto-renewal.
Do we need an RFP to choose an SIS?
Most independent schools don’t. A weighted rubric like the one above, three or four scored demos, and a couple of reference calls will get you to a defensible decision faster than a formal process. An RFP earns its keep when a board or diocese requires one, or when the school is large enough that implementation cost dwarfs the cost of running the process.
Michaela Lamb, M.Ed., is Director of Client Strategy at Sycamore. She works with independent and faith-based schools on platform fit and pricing, which mostly means helping them figure out what to ask before they sign anything. Book time with Michaela or call client strategy at +1 (402) 442-1499.
The schools we see happy three years in are rarely the ones that found the platform with the most features. They’re the ones who were honest with themselves about which four criteria mattered, asked the uncomfortable version of each question, and believed the answer they got instead of the one they were hoping for.
Sycamore has been building for independent and private K-12 schools since 2001. Today that’s more than 100,000 students in over 40 countries. If you’d like to run these twelve questions at us directly, we’d welcome it.
Seven independent school management software platforms compared on admissions, SIS, and billing on one record, what they cost, and fit for growing schools.
Which SIS do U.S. private K-12 schools use? Seven systems scored on tuition management, parent communication, and all-in-one administration.
From Brazil to Rwanda, mission-driven international schools are ditching manual spreadsheets for a centralized Student Information System. Discover how Amazon Valley Academy and Virunga Valley Academy are leveraging Sycamore to reduce administrative friction, support diverse grading models, and enhance parent engagement through real-time mobile access.
