Higher Education Student Retention Dashboard Specification
Design a production-ready dashboard specification to monitor academic risk indicators and student retention trends.
Use this template when planning an early-warning student success dashboard across LMS and SIS data. It establishes data schemas, alert triggers, and advisor workflow interfaces.
Role: Senior Higher Education Business Intelligence Architect
Context
- Target Institution: {{institution_name}}
- Student Segment: {{target_cohort}}
- Virtual Learning Data Source: {{lms_data_source}}
- Core Student Information System: {{sis_data_source}}
- At-Risk Threshold Model: {{risk_threshold_rules}}
- User Access & Governance: {{advisor_role_permissions}}
Task
Generate a comprehensive functional and technical dashboard specification for an early intervention student retention dashboard, enabling academic advisors to identify and support struggling students prior to key census milestones.
Method
- Map data ingestion pipelines from {{sis_data_source}} and engagement metrics from {{lms_data_source}}.
- Define primary student risk metrics based on {{risk_threshold_rules}} (e.g., assignment latency, attendance dips, grade trajectories).
- Establish cohort filtering parameters tailored to {{target_cohort}} across colleges and degree programs.
- Draft layout wireframes spanning executive overview, course-level risk grids, and individual student profile views.
- Specify row-level security and data privacy safeguards compliant with {{advisor_role_permissions}}.
- Detail interactive component behaviors including drill-through paths, note logging, and intervention flagging.
- Define alert notification triggers and threshold breaches for immediate advisor outreach.
- Outline required data refresh frequencies, caching policies, and latency expectations for {{institution_name}}.
Constraints
- MUST maintain FERPA-compliant privacy rules preventing unauthorized cross-department visibility.
- MUST NOT display raw personally identifiable medical or financial aid notes on aggregate reporting cards.
- Every metric calculation must include exact numerator and denominator logic.
- Layout must account for responsive viewing on standard staff desktop and tablet viewports.
Output format
Provide a technical specification structured under these exact headers:
- Executive Summary & KPI Architecture (under 250 words)
- Data Ingestion & Integration Matrix (table format: Source, Field, Frequency, Join Key)
- Visual Component Specification (detailed component breakdown by screen zone)
- Security & Permissions Matrix (role-to-object visibility mapping)
- Validation & Edge Case Rules (bulleted list)
Self-review
- Ensure all variables ({{institution_name}}, {{target_cohort}}, {{lms_data_source}}, {{sis_data_source}}, {{risk_threshold_rules}}, {{advisor_role_permissions}}) are referenced.
- Confirm calculations for retention indicators are mathematically unambiguous.
- Verify student privacy safeguards are explicitly documented across all screens.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.