
Build a checklist of AI safeguards to evaluate before adopting new EdTech
You'll have a vendor evaluation rubric specific to child protection that your school can use repeatedly when considering new AI-powered tools.
What you'll make
AI EdTech Safeguards Checklist
- Red Flags: features that build dependency by design
- Testing Protocols: what to try before you buy
- Vendor Questions: claims that require proof
- Implementation Safeguards: deployment rules that protect learning
Write each safeguard as a yes/no checkpoint with specific evidence criteria
The 3 parts
Each part ends with a check you can see.
Map How AI Erodes Student Agency
Identify the specific ways AI EdTech can replace student thinking without teachers noticing
Done when
A ranked list of 5-7 cognitive dependency patterns with concrete examples from real EdTech interfaces
Test Whether Tools Build Skill or Dependence
Design experiments that reveal whether AI EdTech actually develops student capabilities or just produces impressive outputs
Done when
Three tested protocols that distinguish between genuine skill development and performance theater in AI EdTech tools
Create Implementation Safeguards
Translate your testing insights into a reusable checklist that protects student learning during AI EdTech procurement and deployment
Done when
A complete safeguards checklist with specific yes/no criteria and implementation rules ready for immediate use in vendor evaluations
Capstone: you put together your AI EdTech Safeguards Checklist.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Run a systematic evaluation of at least one AI EdTech vendor using child-protection criteria
- Identify the 3-5 cognitive risks that standard vendor security doesn't address
- Have a reusable checklist that flags dependency-building features before purchase
- Know which vendor claims require independent testing vs which you can take at face value
Who it's for
- School administrators evaluating AI-powered learning platforms
- IT directors responsible for EdTech procurement in K-12 settings
- Curriculum coordinators who need to assess cognitive impact of new tools
- Anyone making vendor decisions for student-facing AI systems
What it won't cover
- General cybersecurity auditing — this assumes you have those protocols
- Budget analysis or contract negotiation tactics
- Technical integration with existing school systems
- Legal compliance beyond cognitive protection
Skills you'll practise
- Cognitive risk assessment in educational AI
- Vendor claim verification through controlled testing
- Dependency pattern recognition in EdTech interfaces
- Child-protection criteria development