# 5. Report Analytics

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

---

## 5. Report Analytics

### 5.1 Report Open Rates
**What it does:** Measures how often automated reports are opened: the Super Administrator views the open rate per report type and channel (email opens, in-app views, PDF downloads), so the platform can identify which reports recipients actually engage with.

**Sub-features:**
- Open rate per report type: the percentage of delivered reports opened
- Channel breakdown: open rates per channel (email, in-app, PDF)
- Segment breakdown: open rates per recipient segment
- Trend over time: open rate trends across periods
- Benchmark comparison: open rates vs. platform averages
- available on web
- event logging (action performed)
- Audit logging of report analytics access

**Super Admin User Journey:**
1. Super Admin opens Report Analytics and selects Report Open Rates.
2. Views the open rate per report type and the channel breakdown.
3. Filters by segment and period to see trends.
4. Compares a report type's open rate against the platform average.
5. Identifies low-engagement report types for content or timing review.
6. The analytics access is event-logged.

**Rules & Edge Cases:**
- An open is counted once per recipient per report; repeated opens do not inflate the rate.
- Open rates require a minimum delivery count; low-volume reports are marked "insufficient sample".
- PDF open rate is measured by download + view, not just download.
- Trends are computed on the platform's standard period boundaries.
- Analytics access is event-logged.

### 5.2 Alert Response Times
**What it does:** Measures how quickly recipients respond to alerts: the Super Administrator views the acknowledgement and response times per alert type and severity, so the platform can evaluate whether alerts are acted on promptly and where escalation is needed.

**Sub-features:**
- Acknowledgement time: the time from alert delivery to acknowledgement
- Response time: the time from alert delivery to a recorded resolution action
- Per alert type and severity: response times broken down by type and severity
- Escalation rate: the share of alerts that required escalation
- Unacknowledged share: the share of alerts never acknowledged
- available on web
- event logging (action performed)
- Audit logging of alert response analytics access

**Super Admin User Journey:**
1. Super Admin opens Report Analytics and selects Alert Response Times.
2. Views the acknowledgement and response times per alert type and severity.
3. Reviews the escalation rate and unacknowledged share.
4. Identifies alert types with slow responses for threshold or routing review.
5. Confirms the escalation rate aligns with the configured escalation rules.
6. The analytics access is event-logged.

**Rules & Edge Cases:**
- Response time is measured from delivery (not generation); undelivered alerts are excluded and counted separately.
- An alert acknowledged at any escalation level counts as acknowledged at that level's time.
- The unacknowledged share is measured at a defined cutoff (e.g., 7 days).
- Response times are shown as medians to avoid outlier skew.
- Analytics access is event-logged.

### 5.3 Engagement with Reports
**What it does:** Measures deeper engagement with report content: the Super Administrator views the time spent on reports, sections viewed, actions taken from reports (e.g., a student revisiting a flagged topic), and follow-through rates, so the platform can assess whether reports drive action.

**Sub-features:**
- Time spent: the average time spent per report
- Sections viewed: which report sections are viewed
- Actions taken: actions triggered from report content
- Follow-through rate: the share of recommended actions completed
- Per report type: engagement broken down by report type
- available on web
- event logging (action performed)
- Audit logging of engagement analytics access

**Super Admin User Journey:**
1. Super Admin opens Report Analytics and selects Engagement with Reports.
2. Views the time spent and sections viewed per report type.
3. Reviews the actions taken and follow-through rate from report recommendations.
4. Identifies report sections that are ignored for content review.
5. Confirms the follow-through rate for pre-exam recommendations.
6. The analytics access is event-logged.

**Rules & Edge Cases:**
- Time spent is capped per session to exclude abandoned tabs.
- An action is attributed to a report only when taken within the attribution window.
- The follow-through rate requires the recommended action to be trackable; untrackable recommendations are excluded.
- Engagement data is aggregated; individual recipient-level data is not exposed in this view.
- Analytics access is event-logged.

### 5.4 Report Effectiveness Metrics
**What it does:** Measures the overall effectiveness of the automated reporting program: the Super Administrator views composite effectiveness metrics (engagement impact, performance correlation, alert-to-improvement rate, and program ROI indicators), so the platform can evaluate whether automated reports and alerts improve outcomes.

**Sub-features:**
- Engagement impact: the change in recipient engagement after report delivery
- Performance correlation: the correlation between report delivery and performance change
- Alert-to-improvement rate: the share of alerted students who improve after the alert
- Program summary: the composite effectiveness score per report/alert program
- Period comparison: effectiveness compared across periods
- available on web
- event logging (action performed)
- Audit logging of effectiveness analytics access

**Super Admin User Journey:**
1. Super Admin opens Report Analytics and selects Report Effectiveness Metrics.
2. Views the engagement impact and performance correlation per program.
3. Reviews the alert-to-improvement rate for the critical alert program.
4. Compares effectiveness across periods.
5. Uses the composite score to prioritize program improvements.
6. The analytics access is event-logged.

**Rules & Edge Cases:**
- Correlation is not presented as causation; the metric is labeled as correlation.
- The alert-to-improvement rate requires a defined improvement window (e.g., 30 days post-alert).
- Programs with insufficient history are marked "insufficient data" rather than scored.
- The composite score weights are configurable by the Super Admin and versioned.
- Analytics access is event-logged.