Claude Project: Your School's AI Communications Hub

What This Builds

A Claude Project that functions as your school's institutional AI — pre-loaded with your school name, policies, communication guidelines, staff names, and tone standards. Every communication you generate from this project is automatically consistent, school-appropriate, and compliant with your privacy standards. No more re-explaining what your school is or what your policies say at the start of every AI session.

Prerequisites

• {{tool:Claude.plan}} subscription ({{tool:Claude.price}}) — Projects require a paid account
• Your school's key policies written down (attendance, discipline, dismissal, etc.)
• Standard communication tone and format you use (even a few past examples help)
• School name, principal's name, main phone number, website
• 3-5 examples of communications you've written that you're proud of

The Concept

A Claude Project is like a trained assistant who has already read your school's policy manual, communication guidelines, and past letters. Every time you open the project, that context is already there — you just describe what you need and get output that fits your school. It's the difference between briefing a temp on day one every day versus working with a staff member who already knows everything.

Build It Step by Step

Part 1: Create the Project

1. Log in at {{tool:Claude.url}} with your paid account
2. Click Projects in the left sidebar → Create Project
3. Name it: "[School Name] Communications Hub" or "[Your Name] School Office Assistant"
4. Click into the project

Part 2: Write Your School Brief (Project Instructions)

1. Click the Project Instructions section (usually on the right side panel). Paste and fill in this template:

## School Identity
You are the AI assistant for [School Name], a [elementary/middle/high] school in [City, State]. We serve approximately [enrollment] students in grades [K-5 / 6-8 / 9-12].

## Communication Standards
Our parent communications are: [warm but professional / formal / friendly and community-focused]
We always include: school name in sign-off, main phone number ([PHONE]), and website ([WEBSITE])
We never: use threatening language, include student PII (names, IDs), make promises about legal outcomes

## Key Policies
Attendance: [brief description — e.g., "Students may have 3 unexcused absences before a formal letter. 10 unexcused = mandatory meeting. 15+ = potential truancy referral."]
Discipline: [brief description]
Dismissal: [options and procedure]
Late arrival: [procedure]
Absences: [how parents notify — portal, phone call, note]

## Staff (first names/roles for mention in communications)
Principal: [Name]
Assistant Principal: [Name if applicable]
Office Manager (me): [Your Name]
School Counselor: [Name]
Nurse: [Name]

## Communication Types I Create
- Attendance concern letters (3 levels of escalation)
- Parent FAQ email responses
- Weekly school newsletter
- Emergency/safety notices
- Event announcements and field trip forms
- Meeting agendas and minutes
- Congratulatory letters (honor roll, student of month)

## FERPA Note
IMPORTANT: Never include student full names, student IDs, or identifying information in generated content. Always leave [STUDENT NAME] and [GRADE] as placeholders. I will add student-specific information manually before printing or sending.

1. Save the instructions.

Part 3: Upload Reference Documents

1. Click Add Content to upload reference files (Claude Pro allows file uploads):

   • School policies summary: A 1-2 page document with key policies in plain language
   • Sample communications: 3-5 letters you've written in the past that reflect your best work
   • Communication calendar: Upcoming events and key dates for the semester

Alternative if you can't upload: Paste the most important reference content directly into the Project Instructions using clear headers.

Part 4: Test with Real Situations

1. Start a new conversation within the project

2. Try these test requests:

   • "Write a first-level attendance concern letter"
   • "Draft a parent FAQ response about changing dismissal"
   • "Write a weekly newsletter with these updates: [paste notes]"

3. Review each output. Check: Does it use your school's name automatically? Does it reflect your policies? Is the tone right?

Part 5: Refine Until It's Right

1. If outputs feel off in some way:

   • Too formal → add example sentences to Instructions: "Example of our ideal tone: 'We're so glad [student's first name] is part of our school community!'"
   • Wrong policy details → update the Policies section in Instructions
   • Missing a common situation → add a new section to Instructions: "Common communication #6: field trip permission follow-up when forms haven't been returned"

Real Example: A Typical Thursday

Without the project: You open Claude, spend 5 minutes explaining your school, ask for a newsletter draft, get generic output, spend 15 minutes editing.

With the project: You open "[School Name] Communications Hub," paste your teacher notes, say "draft this week's newsletter." Output uses your school's name, reflects your recent events, matches your tone. You spend 5 minutes editing.

Another example — 8am Monday: You have 3 attendance concern letters to send, each for a different level of absence. You open the project:

• "Write level 1 attendance concern for a student in 3rd grade with 4 unexcused absences."
• "Write level 2 for a 7th grader with 9 unexcused."
• "Write level 3 for a 5th grader at 16 unexcused."

Each letter reflects the correct policy escalation level, uses your school name, matches your tone, and has [STUDENT NAME] and [GRADE] placeholders ready for you to fill in. Three letters done in 8 minutes.

What to Do When It Breaks

• Output ignores your policies → Check that the Policies section is specific enough. Vague policy descriptions produce generic outputs.
• Tone is off → Add example sentences. "Our tone sounds like this: [paste 2-3 sentences from letters you love]."
• FERPA concern — student data appeared → Remind in the message: "Remember: use [STUDENT NAME] placeholder, not a real name." Also check your Instructions — the FERPA note should be prominently placed.
• Project instructions getting too long → Prioritize the most-used information. Move rarely-used reference material to uploaded files instead.

Variations

• Simpler version: Use Claude without Projects but start each session by pasting a short school brief: "I'm the office manager at [Name] School. [2-3 sentences on tone and policies]." Not as seamless but still valuable.
• Extended version: Create separate Projects for different contexts — "Parent Communications," "Staff Communications," "Admin/Principal Reports" — each with specialized instructions.

What to Do Next

• This week: Build the project. Test it on 5 communications you'd normally write.
• This month: Refine Instructions based on outputs that were off. Add more reference documents.
• Advanced: Share the Project with your principal (if they also use Claude) — they can generate their own letters with the same school voice consistency.

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