School Email
AI drafts the school email you didn't want to write. Pick the situation, set the tone, get a 4-paragraph draft to copy.
When to use this
Use School Email when you have something hard to say to the teacher, principal, or IEP team and the cursor is blinking. The hard part is the first paragraph: how to open without sounding angry, how to ask without sounding demanding, how to document without sounding litigious. Beacon writes the draft. You read, edit, send.
How it works
Pick the situation
What's the email about? Common situations: report a behavior incident, request a meeting, push back on a denial, follow up on a service. Or type your own.
Set the tone
Three tones: collaborative (you want a working relationship), firm (you want to be heard), or paper-trail (you're documenting before escalation). The same situation gets a different email per tone.
Add context
Free-text field for what only you know. Names, dates, what the teacher said last week, what your kid did this morning. Beacon weaves it in without making it sound like a verbatim transcript.
Get a 4-paragraph draft
Opening + situation + ask + close. Plain language, parent voice, no jargon unless the situation calls for it. Copy + paste into your email client. Edit freely before sending.
What Beacon stores when you use it
generator_uses: Shared with all Workshop tools. tool_type = 'school-email'. content holds the drafted email body.
| Column | Type | Example |
|---|---|---|
| id | UUID | 2d4f... Auto-generated. |
| user_id | UUID | your-user-id RLS-locked. |
| tool_type | text | school-email Fixed for this tool. |
| inputs_json | jsonb | { "situation": "incident", "tone": "firm", "context": "..." } Replayable. |
| content | jsonb | { "subject": "...", "body": "..." } Final draft. |
| used_at | timestamp | 2026-05-16T08:45:00Z Counts against quota. |
A real example
Avery was sent to the office for an outburst that was actually a sensory shutdown. Maya wants firm but not angry.
| Field | Value |
|---|---|
| Situation | Report a behavior incident I disagree with |
| Tone | Firm |
| Context | Sensory shutdown after fire drill; school called it defiance |
| Subject | Following up on yesterday's incident with Avery |
| Body paragraph 1 | I'm writing to follow up on the incident report you sent home yesterday. I want to make sure we're seeing the same thing. |
| Body paragraph 2-4 | (situation reframe + the ask: a sensory accommodation in the IEP + close) |
What Beacon auto-knows
- Every school email you've drafted + the situation + tone.
- Patterns: which tones you use most, which situations recur.
- Cross-reference: did the situation appear in Behaviors logs or Journal entries?
What Discuss with Beacon adds
- Discuss attaches the draft. 'Soften paragraph 2' or 'add a specific CFR cite' or 'shorten to 3 paragraphs'.
- Or chain: 'Write the follow-up email if the school doesn't reply in 5 days.'
Try these with Beacon
“Soften this email. It's too direct for our first email to the new principal.”
Reads the draft. Rewrites with relationship-opening language: 'Thank you for taking the time to read this...' + reframes the ask as a request for partnership rather than a demand.
“Add a specific IDEA citation to back up paragraph 3.”
Adds the relevant 34 CFR section (e.g., 300.324(a)(2)(i) for behavior consideration in the IEP) at the end of paragraph 3 with a 1-line explanation.
“Translate this draft to Spanish.”
Returns a Spanish-language version preserving the tone + structure. Useful for sending to bilingual school staff or co-parents.
“Write the follow-up if they don't respond in 5 days.”
Drafts a polite-but-paper-trail follow-up: 'Following up on the email I sent on [date]. Could you confirm receipt?' Includes a CC to the special ed director if the original was just to the teacher.