Academic Overview and Analytics

Overview

Academic Analytics provides a single workspace to understand academic progress and risk across your school. Start at the Programme level, then dive deeper into Subject Group → Subject → Class → Student.

The workspace brings together:

• Achievement Snapshot (Concern / On-track / Excellent)
• Grade Distributions & simple trends over time
• Workload split by Formative vs Summative
• Submission hygiene (On-time / Late / Missing), where tracked

Phase 1 supports IB Diploma (DP) classes. Additional programmes will be added in later releases.

Accessing Academic Analytics

Who can access the Academic Overview and Analytics

In the first release Admins (who can see all analytics for programme, subject groups, subjects, and class/student views) and Teachers (who can see their own classes and students)

1. From the left menu, select Insights -> Academic Analytics
2. Use tabs to move from Programme down to Student.
3. Set the Period (term). The term selected remains in place while navigating deeper into analytics.

Data sources

Academic Analytics reads data that already exists in ManageBac:

• Grades from class gradebooks (points-based Tasks in IB DP)
• Tasks with due dates (for submission status)
• Task Type (Formative / Summative) for workload views

Only records within the selected Period are included. Tasks without coursework submissions are excluded from submission hygiene.

What is the Achievement Snapshot and how is it calculated?

Achievement Snapshot shows each student’s Achievement Status (Concern, On-track, Excellent) per class and in aggregates (subject, subject group, programme). 

Phase 1 uses two criteria and a simple rule.

Criteria to calculate status:

1. Points criterion - based on the student’s current average grade in the class.
   1. Mirrors class gradebook average (respects category weights).
   2. Default DP thresholds:
      • Concern: < 4
      • On-track: ≥ 4 and < 6
      • Excellent: ≥ 6
2. Submissions criterion - based on submission timeliness for tasks/deadlines in the class.
   1. Includes only tasks with due dates in the past.
   2. Each task’s status contributes a percentage (defaults):
      • Early / On-time: 100%
      • Early and Late: 75%
      • Late: 50%
      • Not Submitted (Past Due): 0%
   3. The class average submission % maps to status (defaults):
      • Concern: < 60%
      • On-track: 60–85%
      • Excellent: > 85% 

Note: 

• School Admins can configure defaults per subject in settings (similar to categories/grade scales)
  
• Teachers can override configurations per class via the Teacher UI.
  

Overall status (rule)

• Class level: the minimum of the two criteria (Points, Submissions) is the class status.
  Example: Points = Excellent, Submissions = On-track → class status = On-track.
• Aggregations (Subject / Subject Group / Programme): the minimum status across the student’s relevant classes defines the aggregated status.
  Example: Programme view: Excellent, Excellent, On-track, Concern → overall = Concern.
   

Using the Academic Overview and Analytics

Filters & Drill down

• Scope: Programme → Subject Group → Subject → Class → Student
• Context: some panels allow toggles (e.g., task types) for clarity

Panels you’ll see

• Achievement Snapshot: counts by status (Concern / On-track / Excellent) with deeper dive options.
• Distributions & Trends: grades movement across the term.
• Workload: number of tasks by type (Formative / Summative), useful for pacing.
• Submission Hygiene: (not in Programme view) On-time / Late / Missing breakdown (all Tasks with Coursework Submissions forms enabled).

FAQs

Q: What data is included in Submission Hygiene?
A: Only tasks/deadlines with due dates in the past during the selected Period. Each task contributes based on its submission status using the default mapping (100/75/50/0), which schools can review.

Q: Our gradebooks use category weights. Does the Points Snapshot criterion match them?
A: Yes. The Points Snapshot criterion mirrors the class average grade calculation and respects category weights.

Q: Can we change the Concern/On-track/Excellent thresholds?
A: Defaults are provided for DP. Admins can configure at programme/subject level; teachers may adjust at class level where enabled.

Q: Does attendance or behaviour affect the status?
A: Phase 1 uses Points and Submissions only. Future phases may add additional inputs per school policy.

Q: Why is a student showing Concern at Programme when most classes are On-track?
A: Aggregats use the minimum status across the student’s classes to avoid hiding areas of risk. Drill down to identify the class and review the evidence.

Examples

• Raising a concern at Programme level: A single Concern in any of a student’s classes will reflect as Concern in Programme view because aggregates use the minimum rule. Use drill to find the class behind it.
• Improvement not visible yet: If submission timeliness has improved this week but your Period is last term, update the Period to include recent dates.