If your teen already uses AI for homework help, or to write a birthday poem the night before, you might wonder whether all that time could count for something. A lot of homeschooling parents have asked me exactly that. Can AI become a proper high school elective?
It can, and you don't need to understand how an AI model works under the hood to run one. What you do need is a clear goal, a project your teen cares about, and one folder where all the evidence goes.
I teach high schoolers live on Zoom, and I build with AI tools myself, mostly Replit Agent. Below is how I'd set up an AI elective if a homeschooling family asked me to plan one from scratch.
Decide what your teen should be able to do by the end
AI covers a lot of ground, so it helps to narrow it down early. By the last week, I'd want your teen to be able to:
- Explain in plain English what an AI tool is doing when it answers them.
- Use AI tools responsibly, which means checking the answers and saying when AI helped.
- Build a small working product with AI and explain how it works.
The third one is what makes this a proper elective. A finished product gives your teen something to show people, and it gives you something concrete to grade.
What goes into the course
I'd build the course around four threads that run through every week.
How AI works, roughly. Your teen doesn't need any maths for this part. They should understand that these tools learned from huge amounts of text and work by predicting a likely answer. That explains why a tool can sound completely sure of something and still be wrong.
Asking well. This means clear instructions, enough context and good follow-up questions, and then checking what comes back every time.
Building. An AI building tool like Replit Agent can turn a plain-English description into a working website or small app. Most of the hours go here, and it's usually the part teens enjoy most, along with plenty of "why is it doing that?" moments.
Responsibility. This covers privacy, bias and being open about AI use. It also includes a dull but important step: before your teen signs up for any tool, check that its terms allow their age and that you've given permission where the terms ask for it.
A sample 8-week outline
Plan on a few hours a week, split between some learning, a lot of building, and a short written reflection at the end of each week. Slow it down or speed it up to suit your teen.
Week 1. What AI can and can't do. Try two or three AI tools together and find something each one gets wrong. Start a learning log, which is just a document where your teen writes down what they did each session and what they figured out.
Week 2. Asking better questions. Practise writing detailed prompts. Pick a topic your teen knows inside out, like a video game or a sport, and fact-check what the AI says about it. Teenagers love catching a computer being wrong. Finish with a paragraph on what it got wrong and why.
Week 3. Find a problem worth solving. Your teen talks to a few people about something that annoys them in their week, such as a sibling, a neighbour or someone at co-op. Then they pick one small problem to work on.
Week 4. Plan it. Your teen writes one sentence on what they're building and who it's for, sketches the main screens on paper, and lists the features. Then they cross most of the features out.
Week 5. Build version one. Use an AI building tool to make a first working version. In the log, your teen notes what the AI built, what broke and how they fixed it.
Week 6. Test it on people. Your teen hands the product to the people from Week 3 and watches them use it without helping or explaining. That's harder than it sounds, but it's where the most useful notes come from. Then they fix whatever confused people.
Week 7. Check it over. Does it collect personal information it doesn't need? Is anything inaccurate or unfair? Your teen writes a short piece on which parts the AI did and which parts they did.
Week 8. Launch day. Your teen presents to an audience. Family is fine, and a co-op group is even better. They explain the problem, show a demo, walk through how it works and say what they'd build next.
Eight weeks is enough for one focused project. For a longer course, run the cycle twice with a bigger second project, or add a unit on programming basics.
How to document it for a transcript
Homeschool record rules vary a lot between states, provinces and countries. Some places ask for plenty and some ask for almost nothing, so check your local rules first. If you use an umbrella school, a curriculum provider or an accrediting body, ask them how they want electives written up.
Whatever your local rules say, these are the records I'd keep for any elective. They make the course easy to describe later, to a college or to anyone else who asks.
- Course title. Keep it plain. "Introduction to Artificial Intelligence and Product Design" works, and so does "Building with AI".
- Course description. One short paragraph. There's a sample below.
- Learning objectives. Three to five lines that start with "The student will be able to…".
- Hours log. Dates, hours and one line on what happened. The learning log from Week 1 covers most of this.
- Work samples. The product (a link or screenshots), planning notes, testing notes, reflections and the final presentation, all in one folder.
- Assessment. A simple rubric. You could score understanding, product quality, testing, responsible use and the presentation.
- Credit and grade. How much credit an elective earns, and how hours turn into credit, depends on your local rules. Decide using those rules, and write down how you decided.
A sample course description you can adapt
In this project-based elective, the student learned how modern AI tools work, how to use them accurately and responsibly, and how to build a working digital product with AI assistance. The student identified a problem by interviewing potential users, planned and built a product using AI development tools, tested it with users, revised it based on feedback, and presented the finished product to an audience. The course also covered privacy, bias, accuracy and honest disclosure of AI use.
Edit it so it matches what your teen did. Anyone reading a transcript will trust an accurate description more than an impressive-sounding one.
What I'd tell any parent running this
Let the project belong to your teen. If you choose the problem, you'll probably be the only one who cares about it. Teens work much harder on their own ideas, even slightly silly ones.
Pick something they can finish. A tiny app that three people have tried is worth more than a big one that stalls halfway.
Ask them to explain things. "Show me how this part works" is the most useful question you can ask. If they can't answer it, you've found next week's lesson.
Make the presentation an event. Invite people and put out snacks. Teens often act unbothered about presenting and then practise several times in their room beforehand.
If you'd rather not teach it yourself
Some families enjoy running this at home. Others would rather have a teacher and a few other teens involved. My small-group classes are live on Zoom with no more than six teens, and homeschooled teens are very welcome.
If you'd like help running it yourself, I also train homeschool parents, including how to use AI for lesson planning.
You can read about my training for homeschool parents or my small-group classes.