The first time you bring AI into your classroom, it feels like you need a tech degree. You don't. But you do need to think through three things: access, accounts, and what happens when it breaks.
Before you start: the access question
Your school WiFi is probably your first problem. You don't know that yet, but you will on day one when 25 kids try to log into ChatGPT at the same time and the connection dies.
Check these things *before* you plan the lesson:
- Can every student access the tool you want to use, or only from school WiFi?
- If it's browser-based, does your school filter it?
- If it requires an account, can a 13-year-old create one, or does it need a credit card?
- How many devices will you actually have? (Chromebooks only, or can students use phones?)
Talk to your tech coordinator. Ask: "If I want 30 students to access [tool name] at the same time, will the WiFi hold?" They'll tell you the truth.
The account setup that actually works
Accounts are boring but essential. Pick one approach and stick with it:
Option 1: School email + app
- Best for: Younger kids, first-time tech users
- You set up one teacher account, students use school login
- Requires: your IT department to have pre-approved it
- Reality: This almost never exists yet, but ask anyway
Option 2: One shared demo account
- Best for: First introduction, no sensitive work
- You log in, project it on the board, students watch and shout suggestions
- Requires: nothing except a projector
- Reality: Works great for showing what AI can do without the logistical mess
Option 3: Individual student accounts
- Best for: Ongoing use, they build portfolios
- Each student makes their own account
- Requires: clear COPPA/FERPA guidelines and written parent permission
- Reality: Takes 15 minutes of class time, worth it for serious integration
Write down which one you're using and tell students the day before. "Tomorrow we're using a shared demo account, so you'll see my screen, not your own screen."
What breaks and how to handle it
Something will go wrong. You'll start the lesson, and:
- The tool is down (unlikely but happens)
- The WiFi craps out (likely)
- Half the students are locked out of their accounts (very likely)
- The feature you wanted doesn't exist anymore (you'd be surprised)
Have a backup. Not a complicated backup. Just: "If the tech doesn't work, we're doing this on paper instead."
If you plan an AI brainstorm session, have index cards and pencils ready. If you plan AI text generation, have a printed example of what good output looks like. Your lesson doesn't require the tech to work—the tech is the accelerant, not the whole thing.
The conversation you need to have first
Before you bring AI into the classroom, tell families what's happening. One sentence: "We're learning about AI tools by trying them ourselves. Students will use [tool name] for [specific assignment]."
You're not asking permission (yet—check your district policy). You're being transparent. Teachers who skip this step get surprised emails.
Also: tell colleagues. Your neighbor teacher might be doing the same thing. You can problem-solve together, and you'll feel less alone when WiFi fails at 1:45 on a Tuesday.
The setup that stuck for me
Here's what actually works in a real classroom with real constraints:
1. Start with one tool, not five
2. Use a demo account the first time
3. Have a low-tech backup ready
4. Tell families what you're doing
5. Set one clear rule: "If it's not working, we move on without it"
The goal isn't a perfect tech day. It's teaching kids that AI exists, what it's good for, and what it's not. You'll refine the logistics after you see what breaks.
Start messy. It gets better.
