Reporting
AuraScore 81/100

Learning Management System Engagement Analytics Plan

An operational plan for learning analytics teams to report student LMS interactions and course risks to faculty.

Use this template when architecting a recurring learning analytics report derived from online learning environments. It enables instructional design and analytics teams to surface actionable student engagement indicators directly to teaching faculty.

Template

Role: Senior Learning Analytics Specialist with deep domain expertise in instructional technology, learning telemetry, and pedagogical data reporting.

Context

  • Academic Institution: {{educational_institution}}
  • Core LMS Environment: {{lms_platform}}
  • Primary Engagement Signals: {{engagement_indicators}}
  • Participating Faculty: {{faculty_cohort}}
  • Risk Alert Triggers: {{intervention_targets}}
  • Delivery Medium: {{distribution_channel}}

Task

Formulate an operational analytics reporting plan that collects LMS interaction data, transforms it into actionable teaching insights, and delivers regular engagement reports to {{faculty_cohort}}.

Method

  1. Define ingestion points for {{engagement_indicators}} extracted from {{lms_platform}} event logs.
  2. Standardize weekly activity baseline calculations across course formats and disciplines.
  3. Establish privacy-safe data scoring that highlights disengaged students per {{intervention_targets}}.
  4. Design intuitive dashboard views and email digests tailored to {{faculty_cohort}}.
  5. Outline early-alert workflows connecting instructor review to student support services.
  6. Schedule report generation and dissemination via {{distribution_channel}}.
  7. Create a feedback loop to evaluate report adoption and pedagogical intervention effectiveness.

Constraints

  • MUST anonymize non-essential behavioral data to protect learner digital privacy.
  • MUST NOT frame analytics as punitive performance scores for either faculty or students.
  • Keep metric visualizations straightforward and interpretable without advanced data training.
  • Ensure data latency from {{lms_platform}} does not exceed 48 hours.
  • Restrict actionable alerts to validated {{intervention_targets}}.

Output format

  1. Telemetry Ingestion Plan (log data types, frequency, extraction methods)
  2. Metric Definitions and Risk Scoring Logic (clear criteria for each indicator)
  3. Faculty Report Layout (structured wireframe description with 3 distinct insight modules)
  4. Operational Delivery Schedule (weekly/term timeline via {{distribution_channel}})
  5. Student Support Escalation Pathway (table of triggers, owners, and recommended interventions)

Self-review

  • Verify that every metric in {{engagement_indicators}} has a defined pedagogical purpose.
  • Ensure the escalation pathways do not compromise student privacy policies.
  • Confirm that delivery through {{distribution_channel}} fits faculty workflows.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-reporting
education-research
learning-analytics
lms-reporting
educational-technology