
What to Request From an SIS Vendor Before Sharing Student Data
November 4, 2026
SIS Data Migration Checklist for School IT Directors
November 18, 2026A charter school executive director needs to know whether staff can use the student information system (SIS) on a regular school day and whether the reporting lead can verify the data before submission. Ask the people who own those jobs to build the demo script together. Their observations will give your selection team something concrete to compare.
Table of contents
- Start with three tasks
- Check the New York reporting handoff
- Score the evidence and make a recommendation
- FAQ
- Sources
Start with three tasks
Give each vendor the same short script and ask for a live walkthrough using fictitious records. Invite a teacher, an operations or enrollment lead, and the person responsible for state reporting. Have each person record where they would need help or a separate tool.
| Task | What to ask the vendor to show |
|---|---|
| Correct attendance | A teacher marks a student absent. Office staff update the record when the student arrives. Show who can make the change and how staff can review it. |
| Process a midyear enrollment | Add a student who starts after the first day of school. Show how staff record the start date, assign classes, and spot missing or duplicate information. |
| Prepare a reporting file | Generate a sample export with an intentional error. Show where the error appears, who corrects it, and how staff produce a revised file. |
For any step that needs a workaround, name the person who would do it and how often. Ask the vendor to identify which steps are available today, which depend on a separate service, and which are still planned.
Check the New York reporting handoff
The New York State Education Department (NYSED) includes charter schools in its guidance for the Student Information Repository System (SIRS), which covers school-year data collections and reporting deadlines. Start with the current guidance and have your reporting lead identify the files and checks that apply to your school. NYSED SIRS guidance
Choose one collection for the demo. Ask for the sample export in the format your reporting process expects, then have your reporting lead review the fields and codes. Write down who prepares the file, who receives it, who reviews errors, and who confirms the corrected data. If an outside reporting partner handles a step, confirm the handoff with that partner directly.
Score the evidence and make a recommendation
Before the demos, agree on which tasks are required for launch. For each task, use a simple scale: 2 if the team verified it in the demo, 1 if it depends on a documented manual step or separate service, and 0 if it remains unverified. Record what your team saw alongside the score.
Keep any unresolved launch requirement open even when a vendor scores well overall. Before making your recommendation, ask for written confirmation of what data will move, who checks it after import, who trains staff, and what setup and support cost. Include any remaining manual work in your estimate. EduSchool’s SIS cost worksheet
In your recommendation, list the vendor you would advance, the strongest evidence for that choice, and any conditions that must be met before you sign. Give each open condition an owner and a due date.
FAQ
Can we use the scorecard if we have one person handling operations and reporting?
Yes. Have that person test both workflows and ask a teacher to review the attendance task. If one person would own several steps, name a backup for deadline-sensitive work.
What if a vendor says a required feature will be ready before launch?
Record it as unverified. Ask for a written delivery date and agree on when your team can test it. Set a decision date that leaves time to use an alternative if the test falls through.
Book an EduSchool walkthrough
Bring one daily workflow and one reporting question so you can discuss how they would work for your school. Book an EduSchool walkthrough

