Districts and private schools run more third-party software than most mid-size companies — and every one of those vendors touches student records. We manage the environment and the paperwork that has to follow it.
The Real Problem
A teacher signs up for a free classroom app. It is genuinely useful, and it now holds student names and progress data. Under New York’s Ed Law § 2-d, that vendor relationship carries obligations the district owns — whether or not anyone in the technology office ever heard about the signup.
Classroom tools adopted teacher by teacher, each one a data agreement nobody in the district signed.
Take-home fleets leave with students and come back missing, unpatched, or not at all.
Accounts for seasonal staff, student teachers, and coaches accumulate and rarely get closed.
Infrastructure changes can’t happen mid-semester, so a missed summer means waiting a full year.
What We Handle
A register of which edtech vendors hold student data and what each agreement actually commits them to.
1:1 and cart fleets imaged, enrolled, tracked through the year, and collected at term end.
Staff, substitute, and student accounts provisioned at intake and closed on departure.
Building-wide connectivity with filtering that satisfies obligations without blocking legitimate coursework.
Student information systems and shared drives protected, with restores tested before you need them.
Cabling, refreshes, and migrations staged into the windows when buildings are actually empty.
Most districts can’t produce that list quickly. We’ll build it with you, and map what each one obligates you to.
