← Back to Email Templates

The Termination of Care Notice

Parent
Difficult Conversations
Direct

For when the decision has been made to end a family's enrollment — and you need to put it in writing with clarity, dignity, and a clean record.

Use this only after the decision is final and you've told the family in person or by phone. This email confirms and documents — it is never the delivery mechanism for the news itself. If you haven't had the honest earlier conversation (The "How We Can Best Support" Invitation), pause and ask whether you owe the family that step first; the answer is almost always yes, unless safety makes a faster timeline necessary.

Not for nonpayment terminations — those follow the collections process referenced in the Unpaid Tuition Notice and your enrollment agreement.

BEFORE YOU SEND

  • Make it yours: this email is ready to use as-is for one common version of this situation — edit to your style and your situation's needs. The second paragraph summarizes a sample history (a support plan with spring meetings) — rewrite it with your real timeline.
  • Reread your enrollment agreement and match its notice period exactly. If your agreement says two weeks, the end date is two weeks out — a termination notice that violates your own contract invites a dispute you'll lose.
  • Have the phone or in-person conversation first, then send this the same day. The gap between conversation and confirmation is where families start rewriting what was said.
  • If your program chooses to offer transition help — transferring records, suggesting other programs, flexibility on the last day — add it as a short bullet list before the closing. Offer only what you'll cheerfully honor; most programs keep this email to the essentials, and that's fine.
  • Keep a copy in the child's file. This email is a record; write every sentence knowing a licensing analyst or a lawyer could someday read it.
EMAIL TEMPLATE — EDITABLE
CUSTOMIZE FREELY
Subject:
[Child's Name]'s Enrollment — Confirming Our Conversation
Tone
Direct · Compassionate · Final
Click anywhere in the email to edit · Replace all [bracketed fields] with your specifics

Adapt It

The relationship has broken down and the parent is hostile: Strip the warmth back — not the respect. Cut the "privilege to know" sentence and keep the logistics precise. Warmth a hostile reader doesn't believe reads as sarcasm.

Safety requires immediate or short-notice termination: State the authority and the reason plainly — "Under section [X] of our enrollment agreement, enrollment ends effective [immediately / date] due to [factual safety reason]." Skip the shared-history paragraph. Compassion here is clarity and a fast records handoff, not a softened timeline.

The family chose to leave after the earlier conversation: Different email entirely — confirm their decision graciously, skip any language about your conclusion. "Thank you for letting me know your decision. We support it fully, and here's how we'll make [Child's Name]'s last weeks great ones."

What Not To Say

  • "This just isn't working out." — Vague endings feel arbitrary, and arbitrary feels unfair. Name the factual basis in one calm sentence; the family should recognize it from conversations they've already had.
  • A catalog of incidents. The email confirms a decision; it doesn't prosecute a child. Your documentation file holds the history — this email holds one summary sentence of it.
  • "We're so sorry to have to do this" (more than once). One acknowledgment is human. Repeated apology tells the family you're not sure — and if you're not sure, they'll ask you to reconsider, and now the decision is reopened.
  • Anything about the child's character. "Difficult," "aggressive," "not ready" — these sentences follow a family to their next program. Describe what your program can't provide, not what the child supposedly is.

Related Articles

TODO: In Webflow Designer, replace this paragraph with a Collection List bound to this template's Related Articles field. Inside the list item, add a heading and link bound to the Platform post name and URL.