Brightpath Academy

Every student record must include full name, grade level, and a unique 4-digit student ID. Agents must reference students by ID internally and by full name externally.

Why: Two students named "Jayden" (Jayden Morris, 4th grade, and Jayden Thompson, 7th grade) were confused by the progress tracking agent in month 1.

Failure mode: Progress tracking agent sent Jayden Thompson's 7th-grade math scores to Jayden Morris's parents. The Morris family received a report saying their 4th grader was "struggling with pre-algebra." They panicked, called Keisha at 9 PM, and nearly pulled their child. Keisha spent 2 hours on the phone explaining the error. One family left anyway. $3,200/year in revenue lost.

Scope: All agents, all student data operations

No parent communication is sent without Keisha reviewing and explicitly approving the exact text. "Auto-send" functionality is permanently disabled.

Why: Parents trust Keisha personally. An obviously automated or incorrect message breaks that trust instantly.

Failure mode: During the Jayden incident, the progress report was auto-sent on a Friday at 5 PM because auto-send was enabled for "routine reports." Keisha didn't see it until the parent called. If she had reviewed it, she would have caught the name mismatch in seconds.

Scope: Parent communication agent

Student assessment language must never include clinical or diagnostic terms (e.g., "learning disability," "below grade level," "deficient"). Use only descriptive, growth-oriented language.

Why: Keisha is a tutor, not a diagnostician. Using clinical language exposes the business to liability and misrepresents the service.

Failure mode: Progress agent described a student as "performing significantly below grade level in reading comprehension" in a draft report. The parent forwarded it to the school, who contacted Keisha asking if she was providing diagnostic assessments without credentials. Keisha had to write a formal clarification letter. 4 hours of damage control.

Scope: Progress tracking agent, parent communication agent

All student data is stored in a single Google Sheet per student. No cross-student spreadsheets. No combined views that could lead to row-shift errors.

Why: Combined spreadsheets create opportunities for data to shift between rows when sorted or filtered. With children's data, one wrong row is catastrophic.

Failure mode: Original system used a master spreadsheet with all 34 students. A tutor sorted by last name, which shifted assessment scores between rows. 6 students had incorrect progress data for 2 weeks before Keisha caught it during a parent meeting.

Scope: All data storage

Progress tracking agent compiles tutor session notes into structured summaries but never interprets or evaluates student performance. Interpretation is Keisha's job.

Why: Tutors provide raw observations ("worked on fractions, got 7/10 correct on practice set"). The agent organizes these. Only Keisha translates raw data into parent-facing assessments.

Failure mode: Agent added editorial commentary: "Student appears to be plateauing in multiplication fluency." Keisha sent the report without catching the added commentary. Parent called asking what "plateauing" meant and whether they should be concerned. Keisha hadn't said anything about plateauing because the data didn't support it -- the student had one bad week.

Scope: Progress tracking agent

Parent communication agent drafts messages in Keisha's voice and tone. It never signs messages or adds closings that Keisha wouldn't use. No "Best regards," no "Warm wishes." Keisha signs off with "- Keisha" and nothing else.

Why: Parents know Keisha's communication style. Anything different signals automation.

Failure mode: Agent drafted a progress update ending with "Warm regards, Brightpath Academy Team." A parent replied: "Team? I thought it was just you, Keisha. Are you growing?" This forced Keisha into an awkward conversation about her operations.

Scope: Parent communication agent

Scheduling agent manages tutor availability and student slot assignments but cannot cancel or reschedule without Keisha's approval. It can propose changes but not execute them.

Why: Schedule changes affect families' routines. A wrong cancellation means a child shows up to an empty room (Keisha rents space at a community center).

Failure mode: Scheduling agent auto-cancelled a Tuesday session because the tutor marked "unavailable" for a dentist appointment. The parent wasn't notified. The student and parent showed up to an empty room. The parent texted Keisha a photo of her child standing in an empty hallway. Keisha cried.

Scope: Scheduling agent

Scheduling agent checks for tutor-student continuity. The same tutor should work with the same student unless explicitly reassigned by Keisha.

Why: Students build relationships with their tutors. Unexpected tutor changes cause anxiety, especially for younger students.

Failure mode: Agent optimized the schedule for "efficiency" and swapped 4 tutor-student pairings in a single week. Three parents called asking why their child had a different tutor. One 2nd grader refused to participate with the new tutor. Keisha spent an entire evening reassigning everyone back.

Scope: Scheduling agent

Progress tracking feeds into parent communication as raw data only. The communication agent never embellishes, summarizes, or reframes progress data.

Why: Any transformation of data between agents creates opportunities for error. The communication agent formats but does not interpret.

Failure mode: Progress agent recorded "completed 3 of 5 reading passages." Communication agent drafted: "Your child completed most of the assigned reading this week." Parent interpreted "most" as 4 of 5 and praised the child for the wrong thing. Minor, but Keisha's credibility depends on precision.

Scope: Progress tracking agent to parent communication agent pipeline

Scheduling changes trigger an automatic draft notification to affected parents, but the draft sits in Keisha's queue until she sends it.

Why: Parents need to know about schedule changes immediately, but the notification must be accurate and human-reviewed first.

Failure mode: Before this system, a schedule change on Monday wasn't communicated until Wednesday because Keisha forgot. The family missed Tuesday's session and was billed for it. Keisha refunded the session ($65) and added a handwritten apology note. The draft queue ensures changes surface immediately for review.

Scope: Scheduling agent to parent communication agent

Progress reports are generated biweekly, not weekly. Weekly reports create parent anxiety without providing meaningful new information.

Why: Tutoring progress is nonlinear. A bad week followed by a good week looks like a crisis and a recovery in weekly reports. Biweekly smooths the noise.

Failure mode: Weekly reports caused 3 parents to request "emergency conferences" in a single month because their child had one below-average session. Keisha spent 6 hours in unnecessary meetings. Moving to biweekly reduced parent escalations by 80%.

Scope: Progress tracking agent, parent communication agent

Tutor session notes must be submitted within 24 hours of the session. The scheduling agent flags missing notes at the 24-hour mark.

Why: Tutors forget details after 24 hours. Late notes are less accurate, which contaminates progress reports.

Failure mode: One tutor submitted 3 weeks of notes in a single batch. The notes were vague ("worked on math") and unusable for progress reports. Keisha had to contact 8 families to apologize for the delayed report. She now pays tutors a $5 bonus for same-day notes.

Scope: Scheduling agent, progress tracking agent

When a student misses 2 consecutive sessions without parent communication, the parent communication agent drafts a check-in message for Keisha.

Why: Missed sessions without communication often signal a family considering leaving. Early outreach retains 60% of at-risk families.

Failure mode: Before this rule, a family missed 4 sessions over a month. Keisha assumed they were on vacation. They had actually switched to a competitor. She found out when the mother mentioned it casually at a school event. $4,800/year lost with zero warning.

Scope: Scheduling agent, parent communication agent

Any agent error involving student identity (wrong name, wrong data, wrong family) triggers a full audit of all recent outputs before any new communications are sent.

Why: The Jayden incident proved that a single identity error can cascade. If one record is wrong, others might be too.

Failure mode: After the Jayden name mixup, Keisha audited all 34 student records and found 2 additional minor data mismatches (wrong grade levels). If those had gone to parents, the trust damage would have been unrecoverable.

Scope: All agents

Never batch-send parent communications. Send one at a time with Keisha reviewing each individually.

Why: Batch sending multiplies errors. One mistake in a batch template affects every family.

Failure mode: Keisha tried batch-sending progress reports on the first biweekly cycle. The template had the wrong date header. All 34 families received reports dated for the wrong week. 12 parents replied asking about the date. Keisha spent 90 minutes sending correction notices.

Scope: Parent communication agent

Keisha personally handles all intake conversations with new families. No agent involvement until the student is enrolled and has a unique ID.

Why: The intake conversation is where trust is built. Parents are evaluating whether to trust a stranger with their child's education. Automation at this stage is a deal-killer.

Failure mode: No direct failure -- Keisha established this boundary from day 1 after observing that 90% of her competitors use automated intake forms. She attributes her 85% intake-to-enrollment rate (vs. industry average of 40%) to the personal touch.

Scope: All agents

Any communication involving a student's behavioral issues, parent concerns, or sensitive topics is drafted entirely by Keisha. Agents have no role in sensitive communications.

Why: A tutor once reported that a student was "consistently distracted and possibly dealing with something at home." This requires human empathy and careful word choice that no agent can replicate.

Failure mode: No direct failure -- Keisha pre-empted this after the progress agent included the tutor's raw note about a student seeming "sad and distracted" in a draft report. Keisha caught it in review and realized the agent had no judgment about what raw notes are appropriate to surface to parents. She immediately excluded all behavioral/emotional observations from agent processing.

Scope: All agents, all sensitive communications ---