# 2. Parent Report Automation

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 2. Parent Report Automation

### 2.1 Daily Activity Summary (Optional)
**What it does:** Configures the optional daily activity summary for parents: the Super Administrator enables or disables the daily digest per parent/student segment, defining the contents (time spent online, completed activities, assessment scores, any concerns flagged) and the delivery time, so opted-in parents receive a concise daily view of their child's activity.

**Sub-features:**
- Enable/disable: the daily summary toggled on or off (optional feature)
- Segment scoping: which parent/student segments receive the daily summary
- Content selection: time spent online, completed activities, assessment scores, concerns flagged
- Delivery time: the daily delivery time and timezone
- Opt-in/opt-out: parent-level opt-in and opt-out honored
- available on web
- event logging (action performed)
- Audit logging of daily summary configuration

**Super Admin User Journey:**
1. Super Admin opens Parent Report Automation and selects Daily Activity Summary.
2. Enables the daily summary and scopes it to the target segments.
3. Selects the content blocks (time spent online, completed activities, assessment scores, concerns flagged) and sets the delivery time.
4. Saves; the platform queues the daily digest for opted-in parents.
5. A parent who opts out stops receiving the digest; the opt-out is honored.
6. Reviews a sample daily summary to confirm the content.
7. The configuration change is audit-logged with the actor and timestamp.

**Rules & Edge Cases:**
- The daily summary is optional; it is off by default and only delivered where enabled and opted-in.
- A parent who opts out is excluded immediately; no further daily digests are sent.
- A day with no student activity produces a minimal digest ("no activity today") rather than being skipped, for opted-in parents.
- Concerns flagged in the digest are limited to non-sensitive items; sensitive items route through the critical alert flow instead.
- Configuration changes are audit-logged with the actor and timestamp.

### 2.2 Weekly Parent Newsletter
**What it does:** Generates the automated weekly parent newsletter: the Super Administrator configures the weekly newsletter that summarizes the child's week (progress highlights, upcoming deadlines, teacher notes, and platform announcements), delivered on a fixed weekly cadence to opted-in parents.

**Sub-features:**
- Weekly cadence: the newsletter day and time
- Progress highlights: the week's key progress items
- Upcoming deadlines: upcoming exams, assignments, and events
- Teacher notes: teacher-added notes for the child
- Platform announcements: relevant platform announcements
- Personalization: the newsletter personalized per child
- available on web
- event logging (action performed)
- Audit logging of weekly newsletter configuration

**Super Admin User Journey:**
1. Super Admin configures the weekly parent newsletter cadence (day and time).
2. Selects the sections: progress highlights, upcoming deadlines, teacher notes, platform announcements.
3. Saves; the platform generates and delivers the newsletter weekly to opted-in parents.
4. For a parent with multiple children, each child's section appears in the newsletter.
5. Reviews a sample newsletter to confirm the personalization.
6. The configuration change is audit-logged with the actor and timestamp.

**Rules & Edge Cases:**
- A parent with multiple children receives one newsletter containing a section per child, not one newsletter per child.
- A week with no teacher notes shows an empty teacher-notes section, not an error.
- The newsletter is generated only for active enrollments; a lapsed enrollment is excluded.
- Cadence changes take effect from the next scheduled run.
- Configuration changes are audit-logged with the actor and timestamp.

### 2.3 Critical Alert Triggers
**What it does:** Defines the critical alert triggers for parents: the Super Administrator configures the conditions that raise a critical parent alert — low performance, missed sessions, engagement drop, and access issues — so parents are notified promptly when their child needs attention.

**Sub-features:**
- Low performance trigger: alert when assessment scores fall below the configured threshold
- Missed sessions trigger: alert when scheduled live sessions are missed
- Engagement drop trigger: alert when activity falls below the configured engagement baseline
- Access issues trigger: alert on login failures, subscription lapses, or device access problems
- Trigger enable/disable: each trigger toggled on or off
- Alert content: the alert message with the condition, evidence, and suggested action
- available on web
- event logging (action performed)
- Audit logging of critical alert trigger configuration

**Super Admin User Journey:**
1. Super Admin opens Critical Alert Triggers and enables the required triggers (low performance, missed sessions, engagement drop, access issues).
2. Sets the condition parameters per trigger (score threshold, missed-session count, engagement baseline).
3. Saves; the platform monitors student data against the trigger conditions.
4. When a condition is met, the platform raises a critical alert to the parent with the condition, evidence, and suggested action.
5. Reviews the raised alerts to confirm the conditions and evidence are correct.
6. The trigger configuration is audit-logged with the actor and timestamp.

**Rules & Edge Cases:**
- Each trigger is independent; disabling one does not affect the others.
- A trigger fires only when its condition is met; borderline values that do not cross the threshold do not fire.
- Repeated conditions for the same student are deduplicated per alert period; the parent is not spammed with duplicate alerts.
- Access issue alerts include the specific issue (login failure, lapse, device problem) so the parent can act.
- Trigger configuration changes are audit-logged with the actor and timestamp.

### 2.4 Parent Alert Delivery & Preferences
**What it does:** Manages how parent alerts and reports are delivered: the Super Administrator configures the parent notification channels (push, email, in-app) and the parent-facing preference controls, so critical alerts reach parents reliably while respecting each parent's channel preferences.

**Sub-features:**
- Channel configuration: push, email, and in-app channels for parent alerts
- Critical alert override: critical alerts delivered on all enabled channels regardless of non-critical preferences
- Parent preference controls: parent-level channel and frequency preferences
- Quiet hours: parent-level quiet hours honored for non-critical alerts
- Delivery tracking: per-alert delivery state (sent, delivered, failed)
- available on web
- event logging (action performed)
- Audit logging of parent alert delivery configuration

**Super Admin User Journey:**
1. Super Admin configures the parent alert channels (push, email, in-app).
2. Sets the critical alert override: critical alerts go out on all enabled channels.
3. Configures the parent preference controls and quiet hours behavior.
4. Saves; the platform delivers parent alerts per the configuration.
5. A critical alert is delivered on all enabled channels even if the parent muted non-critical alerts.
6. Reviews the delivery tracking to confirm alerts were delivered.
7. The delivery configuration is audit-logged with the actor and timestamp.

**Rules & Edge Cases:**
- Critical alerts bypass quiet hours and non-critical mute preferences; they are always delivered on enabled channels.
- Non-critical alerts respect the parent's quiet hours and channel preferences.
- A parent with no reachable channel (all failed) is flagged for follow-up; the alert is not silently lost.
- Delivery tracking shows the state per alert; failures are visible and retriable.
- Delivery configuration changes are audit-logged with the actor and timestamp.