Copied to clipboard!
Module 6 For Educators intermediate 50 min

Operations & Communication with AI

The events and the emails that eat your week, drafted in one working session.

For Teachers · Lessons, courses, feedback, family comms

You're viewing the Administrator track. These Teacher exercises are also here. Switch to Teacher in the top bar to focus them.

Family & Parent Communication

You have to send a message a parent will read emotionally, about a grade, a behavior, a missing assignment, or good news. The wrong tone gets forwarded to the principal; the right tone builds a partnership. AI can draft the structure and give you tone variants in your own voice. But you own the facts, you own the tone, and you own the final send.

Recommended tool

claude

Claude is strong at matching a described voice and producing several tone variants of the same message so you can pick the one that fits this family. Gemini is a fine alternative. Either way, paste your Educator Context Document so the draft sounds like you, not like a form letter.

Bring to the exercise

  • The situation and the outcome you want from the family
  • The relevant (redacted) facts: grades, dates, what happened
  • The family’s context and preferred language, if you know it
  • Your Educator Context Document (for voice)
Step 1

Define the Situation, Audience, Outcome, and Tone

Tell AI who this is for and what success looks like before it writes a word.

What to substitute before pasting

  • [DESCRIBE THE SITUATION] One or two sentences. What happened and why you are writing.
  • [WHAT YOU WANT] The specific outcome: a reply, a meeting, support at home, or just an informed parent.
  • [PASTE EDUCATOR CONTEXT DOCUMENT] Your Educator Context Document from Module 2: grade, voice, how you sound to families.
I am a teacher writing a message to a family. Help me draft it.

The situation is: [DESCRIBE THE SITUATION: grade concern, behavior, missing assignment, or good news].

The outcome I want from the family is: [WHAT YOU WANT: a conversation, a signature, support at home, or simply to feel informed].

The tone should be: [WARM / DIRECT / CELEBRATORY / REASSURING]. Partnership, not blame.

Here is my voice and context so the message sounds like me:
[PASTE EDUCATOR CONTEXT DOCUMENT]

Ask me any clarifying questions before drafting.
What good output looks like
  • AI restates the situation, the audience, and the outcome you want in its own words.
  • AI asks at least one clarifying question before drafting.

Verify before using AI's output

Step 2

Draft the Message

Get a complete, send-shaped draft with a clear structure.

Draft the message now.

Structure it as:
- Subject line (specific, not alarming)
- Warm opening that names the student as "your student"
- The specific facts (only the facts I gave you)
- One clear ask or next step
- A sign-off in my voice

Keep it short. Use the tone we agreed on. Do not add any fact I did not provide.
What good output looks like
  • A complete draft with subject, warm opening, facts, one clear ask, and a sign-off.
  • Exactly one next step, not a list of three things the family must do.

Verify before using AI's output

Step 3

Pressure-Test Against an Anxious or Skeptical Parent

Read your own message the way a worried parent will, then fix what they would react to.

Now read this draft as an anxious or skeptical parent who is already worried about their child.

Tell me:
- How could any sentence be misread or taken as blame?
- Where would this parent get defensive?
- What might they forward to the principal, and why?
- What reassurance or context is missing?

Then revise the message to lower the temperature without changing the facts or dropping the ask.
What good output looks like
  • AI points to specific sentences a worried parent would react to, not a generic "be nice."
  • The revision lowers the temperature while keeping the facts and the one ask intact.

Verify before using AI's output

Step 4

Make a Plain-Language, Translation-Ready Version

Strip the jargon so the message survives translation and reaches every family.

Create a plain-language version of the final message.

- Use short sentences.
- Remove all education jargon and acronyms (IEP, RTI, MAP, standards-based, proficiency, etc.), or define them in everyday words.
- Keep the same facts, the same warm tone, and the same one ask.
- Write it so it stays clear if a family runs it through a translation tool.
What good output looks like
  • Short sentences, no unexplained acronyms or edu-jargon.
  • The facts, tone, and single ask survive intact in the simpler version.

Verify before using AI's output

Step 5

Verify Every Fact Yourself

AI cannot know a grade, a date, or what happened in your room. You confirm all of it.

List every factual claim in this message (every grade, date, assignment, and description of what happened) as a checklist for me to verify against my own records.

Remind me: do not let any fact stay in the message that I have not personally confirmed. Flag anything in the draft that reads like a fact but that I never actually gave you.
What good output looks like
  • A clean checklist of every grade, date, and event in the message for you to confirm.
  • AI flags anything that sounds like a fact but that you never supplied.

Verify before using AI's output

Step 6

Send Checklist

A 30-second gut check before you hit send.

Send checklist (you do this manually, not AI):

☐ Every fact is verified against my own records.
☐ The tone is partnership, not blame.
☐ There is exactly one clear next step.
☐ I referred to "your student" and named no other student.
☐ There is a plain-language / translation-ready version if this family needs it.
☐ I would be completely fine if this message were forwarded to the principal.

If any box is unchecked, do not send.
What good output looks like
  • You actually walked through each box before sending.

Verify before using AI's output

For Admins · PD, evaluation, operations, hard conversations

You're viewing the Teacher track. These Administrator exercises are also here. Switch to Administrator in the top bar to focus them.

Use AI to Build an Operational Plan for a Major School Event or Process

Graduation, field day, student incentive day, master scheduling, family engagement night, testing logistics: these eat administrator time. AI can build the timeline, the responsibility chart, the communications, the day-of run sheet, and the debrief tool in a single working session. You verify, edit, and own the final plan.

Recommended tool

claude

Claude excels at multi-step operational plans with timelines, responsibility charts, and packaged communications. Its longer context lets you keep the entire plan in one conversation and ask iterative follow-ups without losing earlier decisions.

Bring to the exercise

  • Event or process name and purpose
  • Date or general timeline (if known)
  • Stakeholders (students, staff, families, vendors, district leaders, community)
  • Required spaces, schedule constraints, transportation needs
  • Materials, technology, safety considerations
  • Past plans (what worked, what failed)
  • Known pain points
Step 1

Define the Event or Operation

Frame the goal and the people before AI starts producing artifacts.

What to substitute before pasting

  • [DISTRICT NAME] / [SCHOOL NAME] Your district and school name.
  • [EVENT OR OPERATION] Graduation, field day, master schedule rollout, student incentive day, etc.
  • [INSERT PAST ISSUES] What went wrong last time? What near-miss are you trying to avoid?
I am a school administrator at [DISTRICT NAME] / [SCHOOL NAME] planning [EVENT OR OPERATION].

The purpose is [INSERT PURPOSE].

The people involved are: [STUDENTS / STAFF / FAMILIES / VENDORS / DISTRICT LEADERS / COMMUNITY MEMBERS].

Here is what has to happen: [INSERT KNOWN REQUIREMENTS: date, location, scale, must-haves].

Past pain points and failures we want to avoid: [INSERT PAST ISSUES].

Help me organize this into a complete operational plan. Ask clarifying questions before drafting.
What good output looks like
  • AI asks at least 2 clarifying questions before drafting the plan.
  • AI captures past failures as risks to mitigate, not just as backstory.

Verify before using AI's output

Step 2

Build the Planning Categories

Get the planning surface area mapped before drilling into any one category.

Create a planning framework for this event or operation.

Include these categories:
- Timeline
- Major tasks
- Responsible people
- Required materials
- Communication needs (staff / families / students / vendors)
- Safety considerations
- Technology needs
- Space needs
- Transportation needs
- Family-facing information
- Staff-facing information
- Student-facing information
- Risks
- Backup plans

For each category, list 3–7 items specific to this event.
What good output looks like
  • Each category has 3–7 specific items, not generic placeholders.
  • AI flags categories that are not applicable instead of inventing items.

Verify before using AI's output

Step 3

Create the Task Timeline

Sequence tasks so nothing slips through the cracks at week-of.

Build a timeline for this event or operation.

Organize by:
- 6–8 weeks before
- 4 weeks before
- 2 weeks before
- 1 week before
- Day before
- Day of
- After the event (debrief + documentation)

For each item, include task / owner / deadline / dependencies / notes.
What good output looks like
  • Every task has an owner and a deadline (not "TBD").
  • Dependencies are named where they exist.

Verify before using AI's output

Step 4

Create a Responsibility Chart

Make ownership impossible to dodge.

Create a responsibility chart for this plan.

Use this format:
| Task | Owner | Backup Owner | Deadline | Materials needed | Dependencies | Status |

Each row is one task. The Backup Owner is the named person who picks it up if the Owner is absent.
What good output looks like
  • Backup Owner is named for every task.
  • Status starts as "Not started," not "TBD."

Verify before using AI's output

Step 5

Identify Risks and Failure Points

Pre-mortem the event before it happens.

Identify what could go wrong with this event or operation. Be specific.

Include:
- Staffing issues (call-outs, coverage gaps)
- Communication gaps (families miss the message)
- Student supervision issues
- Weather concerns
- Transportation problems
- Technology failures
- Family confusion
- Schedule conflicts
- Safety concerns
- Vendor / external dependency failures

For each risk, provide:
- Likelihood (high / medium / low)
- Impact (high / medium / low)
- Prevention step
- Backup plan if it happens anyway
What good output looks like
  • Risks are specific to the event, not generic.
  • Prevention and backup are different actions.

Verify before using AI's output

Step 6

Create Communication Drafts

Get the messages drafted in voice now, not in a panic 48 hours before.

What to substitute before pasting

  • [DISTRICT NAME] Your district name and brand voice.
Create communication drafts for this event or operation.

Include:
- Staff email (announce + key dates + who to contact)
- Family email (in [DISTRICT NAME] voice: clear, warm, scannable)
- Student announcement (age-appropriate, short)
- Reminder message (1 week out)
- Day-before message (logistics, where to be)
- Follow-up message after the event (thank-you + what's next)

Keep each message ≤ 200 words and end with a clear ask or next step.
What good output looks like
  • Each message has a clear ask in the last line.
  • Family email is scannable on a phone (not a wall of text).

Verify before using AI's output

Step 7

Create Day-Of Materials

Build the run sheet so day-of has no improvisation.

Create day-of-event materials.

Include:
- Day-of schedule (with time blocks)
- Staff assignment chart (who is where, when)
- Student movement plan (entrances, exits, transitions)
- Supervision plan (named adults at named locations)
- Materials checklist (what arrives, who confirms it)
- Emergency contact list template
- Command center checklist (decision rights, who calls what)
- End-of-day cleanup checklist (named owner, deadline)

Format for printing on a single page where possible.
What good output looks like
  • Run sheet is single-page printable.
  • Decision rights are named (who pulls the trigger if X).

Verify before using AI's output

Step 8

Create Debrief Process

Lock in next year’s improvements while it is still fresh.

Create a post-event debrief process.

Include:
- Questions to ask staff (3–5, open-ended)
- Questions to ask students (if appropriate)
- Questions to ask families (if appropriate, via short survey)
- What data to collect (attendance, feedback themes, cost)
- What to document for next year (what worked, what to change)
- What should become part of the standard operating procedure (so this doesn't get re-invented)
- Owner of the debrief document and deadline
What good output looks like
  • Debrief produces a documented SOP delta, not just a vibe check.
  • Owner and deadline are named.

Verify before using AI's output