RESEARCH ARTICLE / STUDENT INTELLIGENCE
Student 360: Building a Complete, Evidence-Based View of Every Learner
A Student 360 is not a larger profile page. It is a governed longitudinal model that helps authorized users understand a learner’s trajectory across multiple dimensions without collapsing the learner into a score.
Schools generate student information continuously: enrolment, attendance, timetable participation, assessments, homework, behaviour, achievements, communications, interventions and support records. The problem is rarely the total absence of data. The problem is fragmentation, chronology and context.
“A Student 360 should answer not only ‘Who is this student?’ but ‘What has changed, what evidence supports that interpretation, and what has the institution already done?’”
1. From profile to trajectory
A profile is mostly static. A trajectory is longitudinal. OECD defines longitudinal student information systems as systems that connect student-level data across time, maintain extensive information about schooling and outcomes, and make that information usable through reporting, visualisation and analysis. That distinction is foundational to Student 360.
The value comes from sequence. A grade of 72 may be unremarkable in isolation. A movement from 91 to 84 to 76 to 72, alongside rising absence and missing homework, tells a different story.
2. The Student 360 information model
Identity and enrolment: verified student identity, class, campus, academic year and authorised family relationships.
Attendance: daily status, lateness, absence patterns and longitudinal trend.
Academics: grades, assessment history, subject-level trajectory and learning evidence.
Homework and engagement: completion, submission patterns and relevant learning activity.
Behaviour and wellbeing: governed records with strict sensitivity controls.
Risk and early warning: explainable signals, not opaque labels.
Interventions: reason, owner, due date, actions, follow-up and outcome.
Achievements and portfolio: strengths, awards, projects and positive evidence.
Communication: relevant, authorised interaction history.
Evidence and timeline: source, timestamp, provenance and chronology.
3. Why ‘360’ must not mean ‘everyone sees everything’
The phrase 360 can be dangerous if interpreted as unrestricted visibility. A complete institutional model and a complete user view are not the same thing. Different users require different projections of the same underlying student reality.
A subject teacher may need academic and attendance context for assigned students. A counsellor may need additional support information. A finance officer may require fee information without access to sensitive wellbeing notes. A parent should see only information permitted for their own child. Senior leadership may see aggregate or cross-campus patterns under broader authority.
“Student 360 should be comprehensive in architecture and selective in disclosure.”
4. Evidence lineage and the right to challenge
Any consequential insight should be traceable to its source. If a risk indicator says attendance deteriorated, the user should be able to inspect the underlying attendance period. If an intervention is recommended, the system should show why. This is both an operational and governance requirement.
Student 360 should also allow corrections to source records through governed processes. Intelligence built on inaccurate data becomes confidently inaccurate intelligence.
5. Strengths belong in the model too
A common failure of risk-oriented systems is deficit bias: they become excellent at cataloguing problems and weak at representing strengths. A responsible Student 360 should also capture improvement, achievement, participation, portfolio evidence and successful interventions.
This matters because leadership decisions are better when they understand the learner as a developing person rather than a collection of exceptions.
6. From Student 360 to coordinated intervention
The strongest use case is not visual consolidation but coordinated action. A principal or authorised support lead should be able to move from trajectory to evidence to intervention without reassembling the case manually across modules.
“Identity + Attendance + Academics + Homework + Behaviour + Risk + Interventions + Achievements + Communication + Evidence + Timeline”
That architecture creates the basis for explainable early warning, but the human institution still determines what response is appropriate.
7. Design principles for an executive-grade Student 360
Longitudinal by default: show change over time, not just current state.
Evidence-first: every important conclusion should be inspectable.
Role-aware: disclose only what the user is authorized to see.
Strength-balanced: represent positive trajectory as well as risk.
Action-connected: allow authorised users to create and follow interventions.
Auditable: record consequential access and changes where appropriate.
Context-sensitive: avoid universal thresholds where local policy matters.
Interoperable: connect authorised data without forcing leaders to reconcile duplicate identities.
Human-centred: never reduce the learner to one composite score.