One Picture of a Student, and the Student Sees It Too

ApolloSRM’s status radar turns a student’s standing into a single spider chart: academics, pace, attendance, and financial standing, each on a 0-to-100 axis against your program’s real SAP minimums, so a reader sees shape against target at a glance instead of opening five panels. The student sees the identical chart on their own portal, framed to motivate, with the staff-only risk axis removed by construction.

Why “what is this student’s status?” takes five panels today

A student is doing fine on GPA, slipping on attendance, behind on pace, and carrying a balance, and in most systems those four facts live on four different screens. To answer “how is María doing?” an advisor opens the transcript, the attendance grid, the SAP evaluation, and the ledger, then assembles the picture in their head. Multiply that by a caseload and a deadline, and the synthesis just does not happen, until it is a SAP failure or a withdrawal.

How the status radar works

One chart, a few axes, all from the live record: Academic (cumulative GPA against your program minimum), Pace (SAP credits earned over attempted), Attendance (for attendance-taking programs), and Financial (the ledger balance). Your program’s configured SAP floors are drawn as a dashed target ring behind the student’s polygon, so a shape that dips inside the ring on an axis is a student under a minimum, instantly. For staff who have turned on the early-warning system, a fifth inverse-risk axis joins in. The same degree-audit and SAP engine that already runs your compliance feeds the chart, so the numbers match what you would file.

The part that matters most: the student sees it too

The exact same chart renders on the student’s /learn home: here is where you are strong, and here is where to focus. Showing a student their own trajectory is one of the most reliable nudges in retention research. But a student should never see a risk prediction about themselves. That is a sensitive judgment for an advisor, not a label to hand the subject. So the student route computes the radar with the risk axis switched off at the code path, not behind a setting someone could misconfigure: the endpoint that serves the student literally cannot return a risk signal. That is the FERPA floor written as architecture.

Honest by design

Only the SAP axes claim a real floor. Financial and risk are shown as context, not graded against a gut-tuned threshold nobody can defend. Every axis is paired with its actual value (“3.20 GPA, minimum 2.00”) and a plain-text “below minimum” flag, never color alone, so the chart is complete for a screen reader and for a director skimming on a phone (WCAG 2.1 AA). And if a record is not enrolled yet, the chart simply does not appear, with no fabricated shape.

A read in five seconds

Status is a shape, and a shape is faster to read than a stack of reports. Give your advisors one glance that says academics good, attendance slipping, pace behind, give the student the same honest picture to act on, and you turn a five-panel investigation into a five-second read. It is the cockpit instrument that shows the whole flight on one dial, with the privacy line drawn in code.