The SIS Decision Is Bigger Than Software
A student information system touches every person in your school — administrators, teachers, counselors, parents, and students. It shapes daily workflows, determines what data you can report on, and influences how families interact with your school. This is not a decision to rush.
Yet most schools choose an SIS based on a vendor demo and a price quote. They skip requirements gathering, do not involve teachers in evaluation, and underestimate the pain of data migration. Six months later, they are stuck with a system that technically works but practically fails because nobody wants to use it.
This guide walks through a structured evaluation process that takes 4-6 weeks and dramatically increases the odds of choosing an SIS your staff will actually adopt.
Step 1: Document Your Requirements (Week 1)
Before looking at any vendor, answer these questions:
Must-Have Requirements
- What state reporting requirements must the SIS support? List specific report names (e.g., CALPADS Fall 1, PEIMS TSDS).
- What attendance model do you use? Daily, period-by-period, or both?
- Do you need standards-based grading, traditional grading, or both?
- How many students and staff will use the system?
- Do you have an admissions/enrollment process that requires applicant tracking?
- What systems must the SIS integrate with? (LMS, assessment platforms, food service, transportation)
Nice-to-Have Requirements
- Parent and student mobile apps
- Built-in communication tools (announcements, messaging)
- Custom report builder
- Discipline and behavior tracking
- Health records management
- IEP/504 plan tracking
Dealbreakers
- Annual price above $X per student
- Implementation timeline longer than X months
- No API for third-party integrations
- Requires on-premise servers (if you want cloud-only)
Step 2: Build a Short List (Week 2)
Do not evaluate more than 3-4 vendors. More than that creates decision fatigue without better outcomes. Start with:
- Ask peer schools. Contact 3-5 schools similar to yours in size, type (public, charter, private), and state. Ask what SIS they use and what they wish they had known before choosing it.
- Check state contract lists. Many states have pre-negotiated SIS contracts. These save procurement time and often include better pricing.
- Filter by school size. Enterprise SIS platforms (PowerSchool, Infinite Campus) are built for large districts. Smaller platforms (CampusFlow SIS, Gradelink) are built for schools under 2,000 students. Using an enterprise SIS at a 300-student charter school is like using a semi truck for grocery runs.
Step 3: Run Structured Demos (Week 3)
Do not let vendors run their standard demo. Instead, give each vendor the same list of scenarios to walk through:
- Enroll a new student mid-year with a transcript from another school
- Record daily attendance for a class of 25 students
- Enter grades for a marking period and generate progress reports
- Generate your state's primary enrollment report
- Show the parent portal view for a specific student
- Add a teacher account and set up their class roster
Have at least one teacher, one front office staff member, and one administrator attend each demo. Their feedback matters more than yours — they will use it daily.
Step 4: Check References (Week 4)
Ask each vendor for 3 reference schools. Then find 2 more on your own (search online forums, ask in educator Facebook groups, check EdSurge reviews). The vendor-provided references will be happy customers. The ones you find independently give you the full picture.
Questions for references:
- How long did implementation actually take? (Compare to what the vendor promised)
- What was the hardest part of the transition?
- How responsive is support when something breaks during a reporting deadline?
- What would you change about the platform if you could?
- Would you choose the same SIS again?
Step 5: Negotiate and Decide (Weeks 5-6)
Once you have a frontrunner, negotiate on these points:
- Multi-year pricing. Lock in per-student pricing for 3 years. SIS vendors know switching costs are high and may raise prices after year one.
- Data migration support. Get a written commitment on data migration scope, timeline, and who is responsible for data cleanup.
- Training hours. Negotiate training hours for teachers and admin staff as part of the contract, not an add-on.
- Exit clause. Ensure you can export all student data in a standard format (CSV, XML) if you leave. Some vendors make data export deliberately painful.
Common Mistakes to Avoid
- Choosing based on features you will never use. A 200-student charter does not need multi-school district management. Do not pay for it.
- Ignoring the gradebook experience. If teachers find grade entry painful, they will delay it. Parents will complain about missing grades. The SIS will get blamed.
- Planning migration during the school year. Start SIS migration over summer break. Going live in October is a recipe for chaos.
- Skipping parallel operation. Run your old and new SIS simultaneously for at least one grading period. This catches data issues before they affect transcripts.
- Not budgeting for training. The SIS is only as good as the people using it. Budget 8-16 hours of training per role (admin, teacher, counselor).
Making the Final Call
Weight your decision: 40% daily usability (will staff actually use it?), 30% required functionality (state reporting, grading, attendance), 20% total cost, 10% vendor relationship. The most feature-rich SIS that nobody wants to use is worse than a simpler system with high adoption.