Academic Analytics provides a single workspace to understand academic progress and risk across your school.

You can begin at the Programme level and drill down through Subject Group, Subject, Class, and Student views. 

Overview

Academic Analytics brings together several core indicators in one workspace so schools can monitor progress, identify risk, and review performance across different levels of the academic structure.

The workspace includes:

• Achievement Snapshot with Concern, On-track, and Excellent status groupings
• Grade Distributions and simple trends over time
• Workload split by Formative and Summative tasks
• Submission hygiene showing On-time, Late, and Missing work where tracked

Step by Step Navigation

Access Academic Analytics

Admins can access all analytics for programme, subject group, subject, class, and student views. Teachers can access their own classes and students.

1. From the left menu, go to Insights > Academic Analytics.
2. Use the tabs to move from Programme down to Student.
3. Set the Academic Term. The selected term remains in place as you navigate deeper into the analytics.

Key Concepts

Data sources

Academic Analytics reads data that already exists in ManageBac+, including:

• Grades from class gradebooks, using points based tasks in IB DP
• Tasks with due dates for submission status
• Task Type such as Formative and Summative for workload views

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

Achievement Snapshot

Achievement Snapshot shows each student’s Achievement Status as Concern, On-track, or Excellent for each class and at aggregate levels such as subject, subject group, and programme.

Phase 1 uses two criteria and a simple rule to determine status.

Criteria used to calculate status

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

Note:

• School Admins can configure defaults per subject in settings, similar to categories and grade scales.

• Teachers can override these configurations per class through the Teacher interface.

Overall status rule

• Class level: the minimum of the two criteria, Points and Submissions, becomes the class status.
  Example: Points = Excellent, Submissions = On-track, so class status = On-track.
• Aggregations such as Subject, Subject Group, and Programme: the minimum status across the student’s relevant classes defines the aggregated status.
  Example: Programme view = Excellent, Excellent, On-track, Concern, so overall status = Concern.

MYP Specific Graphs

• Criteria Frequency: Criteria Frequency Usage shows how many times each MYP criterion (A, B, C, and D) has been used across subject groups, subjects, and classes for the selected period. The view helps quickly identify assessment coverage gaps - without having to review individual tasks.
• Criteria Snapshot Distribution: shows how students in this class are distributed across achievement statuses for each MYP criterion (A, B, C, and D). For each criterion, students are grouped into three statuses: Concern, On-Track, and Excellent
• Criteria Progresses: shows the class average grade per criterion (A, B, C, D) for each assessed task in the selected term. Each vertical cluster of points = one assessed task, ordered by date. Each point = class average for that criterion within a specific assessed task
  • Criteria Progress for classes shows student's marks per MYP criteria (A, B, C, D) across all enrolled classes for the selected term.
    • Each point = a mark awarded for a specific criterion within an assessed task.
    • Points are grouped by criterion across four sections.
    • Colours represent individual classes = use the legend to show or hide specific classes.

Using the panels

Within Academic Analytics, you can filter by scope and review several panels that support analysis:

• Scope: Programme → Subject Group → Subject → Class → Student
• Context: some panels provide toggles, such as task type filters, for clarity
• Achievement Snapshot: counts by Concern, On-track, and Excellent, with deeper drill options
• Distributions and Trends: grade movement across the term
• Workload: number of Formative and Summative tasks to support pacing
• Submission Hygiene: available outside Programme view, showing On-time, Late, and Missing breakdowns for tasks with coursework submissions enabled

Frequently Asked Questions

What data is included in Submission Hygiene?

Only tasks and deadlines with due dates in the past during the selected Period are included. Each task contributes based on its submission status using the default mapping of 100, 75, 50, or 0, which schools can review.

Our gradebooks use category weights. Does the Points Snapshot criterion match them?

Yes. The Points Snapshot criterion mirrors the class average grade calculation and respects category weights.

Can we change the Concern, On-track, and Excellent thresholds?

Yes. Defaults are provided for DP. Admins can configure thresholds at programme or subject level, and teachers may adjust them at class level where this is enabled.

Does attendance or behaviour affect the status?

The status uses Points and Submissions only. Future phases may add additional inputs according to school policy.

Why is a student showing Concern at Programme level when most classes are On-track?

Aggregations use the minimum status across the student’s classes so that areas of risk are not hidden. Drill down into the student’s classes to identify which class is driving the status.

What is an example of a Programme level concern?

A single Concern in any of a student’s classes will appear as Concern in Programme view because aggregate statuses use the minimum rule. Use drill down to locate the specific class behind it.

Why might recent improvement not be visible yet?

If submission timeliness has improved recently but your selected Period is still set to a previous term, update the Period so it includes the relevant dates.

In Summary

• Academic Analytics provides a central workspace for reviewing achievement, trends, workload, and submission behaviour across DP and MYP classes.
• Status is calculated using Points and Submissions criteria, with the minimum rule applied at class and aggregate levels.
• Admins and teachers can use drill down views, selected periods, and configuration settings to analyse risk and progress in more detail.

Use ManageBac+ Academic Analytics to monitor student performance, identify concerns early, and review academic patterns across your school.