Claude Project: Your School's Persistent AI Voice and Knowledge Base

What This Builds

You'll build a Claude Project (a persistent AI workspace) configured with your school's mission, authorizer framework criteria, communication templates, and tone guidelines. Once built, every conversation in this project starts from that shared understanding. Instead of re-explaining your school's demographics, voice, and constraints every single time you open Claude, you have one place that already knows everything. Every observation write-up, parent letter, policy document, and board narrative you draft from this project will sound like your school, consistently.

Prerequisites

• A Claude Pro account ($20/month at claude.ai, required for Projects)
• 1 to 2 hours to gather your school documents and configure the project
• Comfortable using Claude for basic drafting tasks (Level 3)
• Your authorizer's performance framework PDF (or the text of the criteria)
• Examples of your best parent communications (3 to 5 emails or letters)

The Concept

A Claude Project is like a new staff member who has read your entire employee handbook, memorized your mission statement, studied your authorizer framework, and reviewed every communication template you've ever written before their first day. You set it up once, and then every conversation starts from that shared foundation. Instead of spending 5 minutes re-explaining your school's context at the start of every Claude chat, you spend 0 minutes, because it's already there.

Build It Step by Step

Part 1: Set up your Claude Project

1. Log into claude.ai with your Claude Pro account
2. In the left sidebar, click Projects (or look for a "+" icon to create a new project)
3. Click New Project or Create project
4. Name it something clear: "Charter School Admin [School Name]"
5. You'll see a project setup page with a Project instructions section and a Knowledge section

What you should see: A project workspace with an instructions text area and an option to upload files.

Part 2: Write your project instructions

Click into the Project instructions text area and paste a customized version of this:

You are an AI assistant for [School Name], a K-8 charter school in [city/state].

SCHOOL CONTEXT:
- Grades: K-8 | Enrollment: ~380 students
- Demographics: 78% free/reduced lunch, 45% ELL, 12% students with disabilities
- Mission: [paste your school's actual mission statement]
- Core values: [list 3-5 values — e.g., excellence, community, perseverance, growth]
- Authorizer: [authorizer name] — charter renewed through [year]
- Academic approach: [brief description — e.g., structured literacy, Danielson framework for observations]

COMMUNICATION VOICE:
When drafting communications for families:
- Tone: warm, direct, accessible — not bureaucratic or legalistic
- Reading level: approximately 8th grade
- Always lead with what the family needs to know, not with procedure
- For difficult communications (discipline, complaints): acknowledge first, explain second, invite conversation third

When drafting communications for staff:
- Tone: professional but collegial — we are a team
- Be direct and clear about expectations without being punitive
- Reference our shared mission and values when framing school-wide decisions

When drafting authorizer documents:
- Tone: formal, evidence-based, confident
- Always frame challenges with our response/trajectory
- Reference specific data; avoid vague claims
- Audience: authorizer staff who are evaluating our charter renewal

TEACHER OBSERVATION FRAMEWORK:
We use the [Danielson / Marzano / school-specific] framework for teacher evaluations.
Domains: [list your framework domains]
When writing observation feedback: lead with strengths, frame growth areas as "next steps" not deficiencies, always tie to specific evidence from the observation.

AUTHORIZER FRAMEWORK SUMMARY:
Our authorizer evaluates us on four domains:
1. Academic Performance: [brief description of what "meets expectations" looks like]
2. Financial Health: [brief description]
3. Operational Compliance: [brief description]
4. Governance: [brief description]

Always: do not mention specific student names or student IDs — all communications should reference "the student" or use placeholder language.

Click Save after pasting and customizing this.

Part 3: Upload your knowledge files

In the Knowledge section of your project, upload the following documents (PDF or text files):

1. Your student/family handbook (or the most recent version)
2. Your authorizer's performance framework criteria document
3. 3 to 5 examples of your best parent communications (copy them into a Word doc and upload)
4. Your current teacher evaluation rubric (if you use Danielson/Marzano, upload the abbreviated rubric)

How to upload: Click Add content or Upload files in the Knowledge section → select your files. Claude will index them and be able to reference them in conversations.

What you should see: Your uploaded files appear listed in the Knowledge section with green checkmarks indicating they've been processed.

Troubleshooting: PDFs with scanned images (not searchable text) may not index well. If a PDF isn't working, copy the text into a Word document and upload that instead.

Part 4: Test and refine your project

Start a new conversation within your project (click New conversation inside the project, not from the main sidebar). Test it with a few typical requests:

Test 1: "Draft a parent letter for a 3rd grade student who had a fight with another student during recess. Consequence: one day of in-school suspension, parent meeting requested. Tone: professional and empathetic."

Test 2: "Convert these observation notes into formal Danielson-referenced feedback: [paste 3 to 4 sentences of notes]"

Test 3: "Draft a 3-sentence statement about our K-2 reading challenge for our authorizer annual report. Our data: below national norms, response: added 30-min daily intervention block."

Check: Does the output sound like your school? Does it use the right tone for each audience? If not, go back to the project instructions and add more specific guidance.

Real Example: A Monday Morning with Your Project

Setup: You've built your project with school context, communication guidelines, authorizer framework, and uploaded your handbook and 5 example letters.

Input (Monday, 7:45am): Open your Claude Project. There are three things on your desk: a parent complaint email from Friday night, an observation write-up you haven't finished, and a reminder that the authorizer annual report is due in 30 days.

Task 1: Parent complaint (8 minutes): Type: "A parent sent this email Friday evening: [paste email]. They're upset about their child not being placed in the gifted reading group. Draft a response that acknowledges their concern, explains our placement process, and invites a phone call."

The project already knows your school's voice, your demographics, your communication tone. The draft it returns sounds like you, not a generic AI response.

Task 2: Observation write-up (12 minutes): Type: "Here are my raw observation notes for Ms. Chen's 4th grade math class: [paste notes]. Convert to Danielson-referenced feedback."

The project knows your evaluation framework and your school's coaching tone. No re-explaining.

Task 3: Authorizer report planning (10 minutes): Type: "I need to draft the Academic Performance domain for our authorizer annual report. Remind me what our authorizer looks for in this domain, and then ask me for my data so you can draft the narrative."

The project pulls from the authorizer framework you uploaded. It asks you the right questions.

Time saved: 30 minutes of re-explaining context and reprompting replaced by 0 minutes. The project knows.

What to Do When It Breaks

• Output doesn't match your voice: Go back to project instructions and add a specific example: "For parent discipline letters, here is an example of our preferred tone: [paste example letter]"
• Claude references old policy from your uploaded handbook: Update the knowledge files. Delete the old version and upload the revised handbook.
• Responses feel too generic: Add more specifics to your project instructions. The more school-specific context you give, the more specific the outputs.
• Long documents aren't being referenced: Claude Pro's project knowledge has limits. If your handbook is very long, upload only the most-referenced sections rather than the full document.

Variations

• Simpler version: Instead of a full project, save a detailed "school context prompt" in a Google Doc and paste it at the start of any important Claude chat. This gives you 80% of the benefit with no setup.
• Extended version: Add your staff directory roles (so Claude knows who the instructional coach, operations manager, and board chair are) and your current school improvement plan as a knowledge file.

What to Do Next

• This week: Set up the project with your school profile and test it on 5 real tasks you normally do
• This month: Upload your handbook and authorizer framework and refine the instructions based on what sounds off
• Advanced: Create a second project specifically for grant writing (see the Level 4 grant writing assistant guide)

Advanced guide for charter school administrator professionals. These techniques use more sophisticated AI features that may require paid subscriptions.