Why do schools adopt AI planning tools by department?
Departments share courses, textbooks and common assessments, which makes them a natural unit for trying an AI planning tool. Teachers who teach the same course can compare output, agree on conventions, and share what works.
CourseSmith builds from the uploaded textbook, so when every teacher in a department uploads the same adopted book, lesson plans and tests draw on the same content. That gives the team a shared starting point instead of each teacher prompting a blank chatbot.

How should a department roll out CourseSmith?
A small, structured pilot gives a department real evidence before a wider decision. The steps below are one practical approach.
01 Pick one course
Choose a course several teachers share, such as grade 9 biology, and confirm everyone uses the same adopted textbook.
02 Agree on conventions
Decide on shared settings, such as test length, question types, point values and the Easy, Medium and Hard mix.
03 Pilot one unit
Each pilot teacher uploads the book to their own account, plans one unit, and reviews every output before teaching it.
04 Compare and share
Meet to compare plans and tests, then save the strongest Word downloads in the department's existing shared folder.
05 Decide on scale
If the pilot works, contact SuperMIA at hello@supermia.ai to discuss volume pricing for the department or school.
How does department curriculum planning stay consistent?
Consistency comes from a shared source and shared settings. When teachers plan from the same textbook and agree on test length, point values and difficulty mix, students in different classrooms get comparable materials.
Academic Schedules help with pacing. If every teacher enters the same planned weeks, hours per week and lecture duration, each gets a week-by-week plan with main topics, key objectives and chapter references that the department can compare in a meeting.

What does CourseSmith do with school data?
The CourseSmith privacy policy sets out how uploaded material is handled. The table summarizes the points school leaders ask about most.
| Question | What the privacy policy says |
|---|---|
| Where are uploads stored? | In private cloud storage, such as AWS S3 |
| How are documents processed? | With large language models and a separate vector database for each document |
| Do AI providers train on our material? | Providers such as OpenAI process text under data processing agreements and do not use it to train their public models |
| What happens when a teacher deletes content? | Deleting a syllabus, lesson plan or persona deletes the associated files |
| Can one teacher see another's content? | Sign-in uses email with a one-time code and token-authenticated access, so users see only their own content |
What should school leaders set as ground rules?
Clear ground rules protect students and teachers alike. CourseSmith is built to plan from textbook content, so most rules focus on what goes in and who checks what comes out.
- Upload textbooks and course documents, not student records or personal information.
- Require teacher review of every lesson, test and answer key before classroom use.
- Verify any standard code against the official document, since CourseSmith does not tag standards.
- Run hands-on activities through existing safety procedures.
- Review the privacy policy and terms with your technology team before scaling.
What does CourseSmith not do for schools?
CourseSmith is a planning and content tool for individual teachers. It does not offer team workspaces, sync with learning management systems, grade student work, or report student analytics.
Its teaching analytics cover each teacher's own activity and mix of delivery methods and question types, not student results. Tests and assignments download as editable Word files that teachers share through the systems the school already uses.







