Skip to content
Implementation

How to Build a School Level Edtech Review Process Before You Buy

Jordan Lee · Education Product Lead, Borderset · 8 min read

A school edtech review process is a short, repeatable check every new tool passes before anyone signs up students. A small team scores each request on four questions: will it improve learning, is student data safe, what will it really cost, and will it add or remove teacher work. Tools that pass go to a time limited pilot; tools that do not are declined with a reason.

The short answer

Set up a review team of four to six people, a one page request form and a scoring rubric with four criteria: learning value, privacy and security, total cost and teacher workload. Any tool that will hold student data or be used with students goes through the process, including free tools. Approved tools go on a published list, start with a pilot and come up for review before each renewal.

The process does not need to be slow. Most requests can be decided in two to three weeks if the form is clear and the team meets regularly.

Why schools need a review process

Without a process, tools arrive one teacher at a time. A free app signed up for one class becomes the place where hundreds of students' names, work and sometimes voice recordings are stored, under terms nobody at the school has read. Costs appear later as renewals. Teachers end up juggling logins for overlapping tools that do the same job.

A review process prevents this without blocking innovation. It gives teachers a clear route to ask for something new and gives leaders confidence that what is in use is safe and worth the money. Large systems are moving the same way: New York City's 2026-27 AI and screen time guidance requires every vendor to pass a privacy and security review and bars schools from accepting free software as a vendor gift. You can read more in our article on NYC's Technology in Schools Coalition.

Who should review

Keep the team small and practical. A school level group usually includes:

  • A school leader who owns the budget and makes the final call.
  • One or two teachers who will actually use tools with students.
  • The IT or data lead, who checks privacy, security and integration.
  • A special education or English learner specialist, for accessibility.
  • The business or finance lead, for contracts and renewals, if separate from the leader.

Meet every two weeks during busy periods and monthly otherwise. In a district, the same structure can sit centrally, with school teams handling the learning and workload questions.

Step 1: Use a one page request form

Ask the requester to answer a few short questions before the team spends time on a tool:

  1. What problem will this solve, and for which students?
  2. What do we use for this now, and why is it not enough?
  3. Who will use it: students, teachers, families or staff?
  4. What student data will it collect or store?
  5. How much does it cost, including after any free period?
  6. How will we know if it worked?

A request that cannot answer question 1 or 6 is not ready for review.

Step 2: Judge learning value

Ask for evidence, not just marketing claims. The federal Every Student Succeeds Act defines four levels of evidence for interventions, and the U.S. Department of Education explains them in its guidance on using evidence.

ESSA levelWhat it means in practice
Tier 1: StrongAt least one well designed and well implemented experimental study shows a positive effect
Tier 2: ModerateAt least one well designed quasi experimental study shows a positive effect
Tier 3: PromisingAt least one well designed correlational study with statistical controls shows a positive effect
Tier 4: Demonstrates a rationaleA clear logic model based on research, with efforts underway to study the effects

Many useful tools, especially operational ones, will not have Tier 1 or Tier 2 studies. That is fine, as long as you know what you are buying and plan to measure results in your own pilot. Treat vendor reports as vendor claims, and ask whether any study was independent and whether its students look like yours.

Step 3: Check privacy and security

This is the step most often skipped for free tools, and the one that matters most if something goes wrong. Check at least the following, and use the U.S. Department of Education's Student Privacy Policy Office resources for detail.

  • FERPA: if the vendor receives education records, the school usually relies on the school official exception. That requires the vendor to perform a service the school would otherwise do, to be under the school's direct control for use of the records and to use the data only for that purpose.
  • COPPA: for children under 13, the Federal Trade Commission's COPPA Rule applies to the operator. Our COPPA compliance checklist for K-12 schools explains what schools should check.
  • State law and agreements: many states require a signed data privacy agreement. Check your state's rules and any statewide agreement your district uses.
  • Data practices: what data is collected, where it is stored, who can access it, how long it is kept and how it is deleted when the contract ends.
  • Security: single sign on, role based permissions, encryption and the vendor's breach notification process.
  • AI features: whether student data is used to train models and whether AI output is used to make decisions about students.

This is general information, not legal advice. Involve your district's privacy lead or counsel for contract terms.

Step 4: Work out the total cost

The sticker price is rarely the full cost. Estimate cost over three years.

Cost itemQuestions to ask
LicensesPer student, per teacher or per school? What happens to the price after year one?
ImplementationSetup, data migration, rostering and integration with your SIS
TrainingInitial and refresher training, and the cost of staff time to attend
Devices and bandwidthDoes it need new hardware, accessories or more network capacity?
SupportWhat is included, and at what response times?
ExitCan you export your data, and what does leaving cost?

Compare that total with what the tool replaces. A tool that removes two others can save money even with a higher license fee.

Step 5: Measure teacher workload

Every new tool asks something of teachers. Ask teachers on the team to estimate the effect honestly.

  • Setup time: how long to create classes, assignments or content.
  • Daily friction: another login, another place to check, another set of notifications.
  • Duplication: does it repeat data entry that already happens in your SIS or learning platform?
  • Time saved: what work does it remove, and is that confirmed by teachers who have used it?

A tool that improves learning but adds hours of weekly admin will not be used well. Our guide on reducing teacher admin workload covers how to count these hidden hours.

A simple scoring rubric

Score each criterion from 1 to 4 and set a minimum for privacy that cannot be offset by a high score elsewhere.

Criterion1234
Learning valueNo evidence or clear purposeLogic model onlyPromising evidence or strong local pilotModerate or strong evidence plus local fit
Privacy and securityFails a required checkGaps that need contract changesMeets requirementsMeets requirements with strong controls
Total costUnaffordable over three yearsAffordable but adds costCost neutralSaves money by replacing other tools
Teacher workloadAdds significant workAdds some workNeutralRemoves work

A practical rule: approve only if privacy scores 3 or 4 and the total is at least 11 out of 16. Adjust the threshold to your context, but write it down so decisions are consistent.

Step 6: Pilot, decide and review

  1. Run a time limited pilot, usually six to ten weeks, with a few classes.
  2. Agree the success measure before the pilot starts, using question 6 from the request form.
  3. Collect teacher and student feedback at the end.
  4. Decide: adopt, extend the pilot or decline, and record the reason.
  5. Add approved tools to a published list with the owner and renewal date.
  6. Review each tool before renewal: is it used, is it working and is it still the best option?

Keeping an inventory of approved tools also makes it easier to answer families' questions and to respond quickly if a vendor has a data incident. If you are choosing a core system rather than a classroom tool, see how to choose a school management system.

Edtech review checklist

  • Review team named, with a meeting schedule
  • One page request form published for staff
  • Free tools included in the process
  • Learning value judged against ESSA evidence levels and local fit
  • FERPA, COPPA and state privacy requirements checked
  • Data privacy agreement signed where required
  • Three year total cost estimated
  • Teacher workload estimated by teachers who will use it
  • Scoring rubric applied, with a minimum privacy score
  • Pilot with a success measure agreed in advance
  • Approved tools list published, with owners and renewal dates
  • Review before every renewal

How Borderset helps

Borderset is designed to pass this kind of review. Role based access and audit trails control who sees student data, and one platform for student tracking, scheduling, exams, payments and family announcements can replace several separate tools, which reduces logins and duplicate data entry for teachers. To run Borderset through your own review, book a demo and ask for the security and privacy documentation.

If you are deciding whether to build or buy, read open source vs SaaS school management software. For AI tools specifically, use our school AI use policy checklist, and for state privacy rules, see our guide to Texas student data privacy for school software.

Frequently asked questions

What is an edtech review process?

It is a short, repeatable check that every new technology tool passes before it is used with students, covering learning value, privacy and security, total cost and teacher workload.

Who should be on a school edtech review team?

A school leader, one or two teachers, the IT or data privacy lead, a special education or English learner specialist and, if separate, the business or finance lead.

Do free edtech tools need to be reviewed?

Yes. Free tools often collect student data under terms nobody at the school has checked, and free periods can turn into paid renewals.

What are the ESSA evidence tiers?

Tier 1 strong, Tier 2 moderate, Tier 3 promising and Tier 4 demonstrates a rationale. They describe how strong the research is behind an intervention, from experimental studies to a research based logic model.

How long should an edtech pilot last?

Usually six to ten weeks with a few classes, with a success measure agreed before the pilot starts and teacher and student feedback collected at the end.

How often should approved tools be reviewed?

Before every renewal. Check whether the tool is used, whether it is working and whether it is still the best option.

Back to all posts