How to make Claude your co-teacher
Everything from the session in one place: set up a planning partner, keep student data out of it, and start with prompts that already work.
- Sign up by June 30, 2027 for a full year of free access to premium features.
- Verify with your school email plus a document showing your role (school ID, contract, or certificate).
- Model training is off for verified teacher accounts.
- Includes teaching skills (lesson planning, differentiation), standards for all 50 states through Learning Commons, and connectors like Brisk, Canva, Diffit, and MagicSchool.
Build your co-teacher in 20 minutes
A Claude Project is a workspace with standing instructions and reference files. Every chat inside it starts already knowing your course.
Claim your free teacher account
Go to claude.com/solutions/teachers, sign up with your school email, and upload your verification document.
Check your settings first
Open Settings → Privacy and confirm what is saved and shared. Then read your district’s AI and data policy. Your district decides what student data, if any, may go into a tool.
Create a Project per course
Name it for the job: Co-Teacher · 10th World History. One course per project keeps answers focused.
Paste in your project instructions
This is your co-teacher’s job description. Copy the template and fill in the brackets.
TemplateYou are my co-teacher for [course], grade [X], in [state]. My students: [general description — reading levels, ELL %, schedule length. No names.] My teaching style: [e.g., inquiry-based, lots of discussion, thinking routines]. Standards: [state] standards for [subject]. Cite the standard code when you align something. When I ask for materials: – Ask me 2–3 clarifying questions before drafting anything long. – Give a teacher version and a student-facing version. – Include one scaffold and one extension. – Keep student-facing reading at grade level unless I say otherwise. Ground rules: – Never ask me for student names or personal details. If I paste any by mistake, tell me and do not repeat them. – Flag anything you are unsure is accurate so I can check it. – Push back if an idea won’t fit my class time.Add project knowledge
Upload the files a co-teacher would want to read:
- Syllabus and pacing calendar
- Unit plans and a lesson you are proud of
- Rubrics and your grading policy
- Department or school expectations
Leave out rosters, gradebooks, IEPs, and anything with a student’s name on it.
Connect only approved tools
Google Drive, Learning Commons (standards), Brisk, Canva, and others can be connected. Turn on only what your district has approved.
Start with the interview
Your first chat should let Claude learn how you work.
First chatInterview me like a new co-teacher on their first day. Ask me one question at a time about my classes, my routines, what I struggle to find time for, and what a great lesson looks like to me. After 8 questions, summarize what you learned in a short “how we work together” note I can add to this project.
PII safety checklist
Claude can plan with patterns. It almost never needs identities.
Never paste
- Student names, nicknames, or initials with context
- Student ID numbers, birthdates, addresses
- IEP, 504, or health information
- Discipline or counseling notes
- Grades or scores tied to a name
- Photos of students or student work with names
- Parent emails with family details
Do this instead
- Use roles: Student A, Group 3, “a student who…”
- Share totals: “7 of 26 missed question 4”
- Delete the name column before uploading data
- Describe needs generally: “two students read 3 grades below level”
- Write parent emails with [Student] and [Parent] placeholders
- Add names back yourself, outside Claude
| Instead of… | Try… |
|---|---|
| “Marcus Jones has an IEP for dyslexia. Adapt this reading.” | “Adapt this reading for a student who needs decoding support and audio access.” |
| Uploading the gradebook export | Uploading item-level results with the name column deleted |
| “Email Sarah’s mom about her 3 absences.” | “Draft a warm email to [Parent] about [Student]’s recent absences.” |
Before you hit Enter
- Could anyone identify a student from what I typed or uploaded?
- Would I be comfortable if this prompt were projected in a staff meeting?
- Did I remove names, IDs, and headers from every file?
- Is this tool and this use approved by my district?
- Will I review the output before a student or parent sees it?
FERPA obligations sit with your district. Anthropic offers a K-12 data agreement and a separate district version of Claude for Teachers, but privacy experts point out that an individual teacher usually cannot consent to sharing student records on the district’s behalf. When in doubt, de-identify.
↑ Back to topStarter prompt bank
Use these inside your co-teacher project. Replace the brackets.
Unit backward-design
Tomorrow’s lesson, fast
Find the hard part
Three versions of one text
Scaffold and stretch
Read the room from exit tickets
Rubric from a task
Family newsletter
Hard email, kind tone
Lesson debrief
Critical friend
How I built my own planning space
This is the project I use for 10th grade Modern World History. Upload order matters: the official documents go in first, and everything after is read against them.
District curriculum map
Upload the real scope and sequence, not a summary of it, and label it as the authoritative version.
Standards framework
I upload the full NCSS C3 Framework PDF so Claude works from the document instead of its memory of it.
Lesson plan templates
One for 53-minute periods and one for 90-minute blocks, so plans come out in the format I actually teach.
State scoring rubric
Assessments start from a rubric my colleagues recognize and the state requires.
Teaching philosophy and grading reference
The things no district file says: how I grade, retakes, late work, my activity library. Then ask Claude what else it needs to know about how you teach, and add its questions to the file.
Philosophy + grading templateTEACHING PHILOSOPHY AND GRADING REFERENCE Course: [course, grade level] Schedule: [e.g., 53-minute periods 3 days a week, 90-minute blocks 2 days a week] What I believe about learning: – [e.g., Students learn history by arguing about it, not memorizing it] – [e.g., Mistakes are data. Retakes are part of learning, not a favor] – [e.g., Play and weirdness are serious tools for engagement] Grading: – System: [e.g., total points, not weighted categories] – Retakes: [e.g., open by default on any assessment] – Missing work: [e.g., 50% floor instead of a zero] – Late work: [e.g., no penalty except on 2–3 major deadlines per semester] – Non-traditional work: [e.g., “Binary + 1” rubric: met / not met, plus one stretch point] My activity library (suggest these before generic activities): – [e.g., See/Think/Wonder] – [e.g., Circle of Viewpoints] – [e.g., Philosophical Chairs] – [add your go-to routines] What I avoid: – [e.g., worksheets that only check recall] – [e.g., activities that need a full period of setup] Things Claude asked me that I’ve answered: – [add Claude’s follow-up questions and your answers here over time]Instructions file
The standing rules: ask for topic, length, and objectives first; ask standard or block; use a fixed lesson structure; name the standard code at the top; never invent a source.
Instructions file templateINSTRUCTIONS FOR THIS PLANNING SPACE Source order: 1. The district curriculum map is the authoritative version of what I teach and when. 2. The standards document comes next. Work from the uploaded file, not from memory. 3. Use my lesson templates and the state rubric for structure. 4. Read my teaching philosophy file in light of the official documents above. Before you generate anything: – Ask me for the topic, the length of time, and the learning objectives. – Ask whether this is a [standard / block] period. – If anything is unclear, ask. Do not guess. Every lesson plan uses this structure: – Standard and code at the top – Warm-up – Direct instruction – Practice – Closure – Assessment – Differentiation notes – Teacher reflection space Sources and accuracy: – Never invent a source, author, page number, or publication date. – If nothing relevant is uploaded, say so and suggest what I could add. – Flag anything you are not sure is accurate. Student privacy: – Never ask me for student names or personal details. – If I paste any by mistake, tell me and do not repeat them. Style: – Suggest routines from my activity library before generic activities. – Keep student-facing materials at [grade level] reading level unless I ask otherwise.Test it with one lesson
A good project asks clarifying questions, cites the right standard, and says “I don’t have a source for that” instead of making one up.
Read the full walkthrough on teacher’s plAIground →
↑ Back to top