Build Your Educator Context Document

Every time you start an AI conversation cold, you re-explain your role, your school, your priorities, your tone. That is wasted minutes you cannot get back, and the drafts still come back generic.

A context document is a single page, the "About my role" you paste at the top of every AI chat. A teacher describes their classes, their students, and their teaching philosophy; an administrator describes their building, their staff, and their leadership approach. Paste it into Gemini, NotebookLM, or Claude. AI then shows up already knowing your role, your building, and what "good" looks like for you.

Never paste real student or staff names into AI. Use role labels: "Student A," "a 9th-grade teacher," "a parent." This is a FERPA and state data-privacy line, and it holds for every module and every tool in this track.

• Who you are. Your first name, your role, your building or district, years in the role, where you came up.
• School and district context. Type, size, grade band, demographics, programs, recent history. The stuff every newcomer would have to ask about.
• What you actually do. Your day-to-day. A teacher: the classes and caseload you carry. An administrator: evaluations, scheduling, family communication, hiring, discipline.
• Your priorities this year. The two or three things you are pushing, and why they matter.
• Your teaching or leadership philosophy. What you stand for and will not compromise on.
• Preferred tone. Direct? Warm? Brief? Detailed? Use this so AI matches your voice in drafts.
• What "growth" looks like. For a teacher, growth in your students. For an administrator, growth in your teachers. Name the standard you hold.
• Constraints. Time, budget, contract, calendar, technology, FERPA and state data-privacy rules, district mandates.
• Common pain points. What slows you down? What conversations or tasks do you keep avoiding?
• Recurring tasks. The five to seven things you do every week, month, or year. These are your targets for repeatable workflows.
• Standards for quality work. What does "done well" look like for you? Be specific, not just "high quality."

• Claude. Save as a Project. Every conversation in that Project starts with your context.
• Gemini. Save as a Gem, or paste at the top of any new conversation.
• NotebookLM. Upload as a source document. Reference it in every prompt.
• Any chat. Paste it at the very top of the conversation, before your actual request.