For educational institutions

You see who is at risk while there is still time to help.

Every course Alma builds shows the whole cohort and any one student's progress against the course's approved learning outcomes, during the term, not after final grades.

Comes with
Every course Alma builds
Measured against
Your approved learning outcomes
Updated
As students work, all term
Who sees it
Your faculty and staff
What you see

Look at the course from every angle, while it runs.

By cohort, by student, by learning outcome and by activity, down to video lectures and the issues the AI flags. Here are five of the questions it answers.

Who has been active this week

The whole cohort at a glance, and how far each module's activities have been completed.

Course analytics, Completion tab: 50 students, 70% active this week, average progress and goals attainment, and a completion funnel for each activity in the first two modules.

Who is flagged at risk

A list, so someone can step in during the term. It does not promise better retention: it gives your faculty and student services time, and stepping in is their work.

The Students list, sorted by status: four students at risk, four to watch, the rest on track, each with progress, rubric score, goals and when they were last active.

Where in the course students stop

Module by module, which activities each student has completed, is partway through, or has abandoned.

The student progress heatmap for module 2: each student's five activities marked completed, in progress, not started or abandoned.

Attainment by learning outcome

How the cohort is spread across each learning outcome approved for the course, from excellent to not started.

Learning outcomes: for each course learning outcome, the median score and how many students are excellent, good, average, below average, poor or not started.

Any one student's progress

Faculty and student services can open it before they talk to the student. Only your own staff and the few Alma people building your course can see students' work, and it is never used to train a model.

One student's analytics: activities, rubric score, active time and alerts, progress on each learning outcome, and their course journey activity by activity.
Why it can say this

Every activity is tied to a learning outcome when the course is designed.

Most of what a program learns about a cohort arrives with final grades, when nobody can act on it. Here the record builds up week by week, because your faculty and learning designers approve the link between each activity and an outcome before anything is produced.

It says which outcome a cohort is behind on

What students do in each activity counts toward the outcome that activity was built for.

It says where students stop

Each activity has a place in the sequence, so a drop in activity points to one module and one activity in it.

It shows where to look when you revise

A revision to a course Alma built takes days, and your faculty approve it before students see it.

How it works

The analytics come with the course. There is no separate project.

Learning analytics are part of every course Alma builds, and of the activities we add to a course you already run. They cover those courses: if you want one analytics system across every course at the institution, we are the wrong choice. See the full process →

  1. Step 1

    Your faculty approve the design

    Alma's learning engineers

    We map each activity to one of the learning outcomes already approved for the course.

    Your people

    Before the build

    Your faculty and learning designers approve that map before anything is produced.

  2. Step 2

    Students take the course

    Alma's learning engineers

    As students work, the cohort view and each student's progress fill in, week by week.

    Your people

    During the term

    Your faculty and student services read them during the term and decide who to reach out to.

  3. Step 3

    You decide what to change

    Alma's learning engineers

    We show where students stopped and which outcomes the cohort was behind on. A revision takes days.

    Your people

    After the term

    Your faculty decide what goes into the next revision, and approve it before students see it.

An example

From one flag in week 5 to a better module.

  1. Week 5

    The program manager opens the cohort

    Most students were active this week. A short list is flagged at risk, and work drops off at a case study in module 3.

  2. Week 5

    Then checks attainment by outcome

    The cohort is on track for most outcomes, and behind on the one that case study was built for.

  3. Week 6

    The instructor opens one flagged student

    The student finished the lecture and the reading, then stopped before the spoken practice. The instructor and student services know where to start.

  4. After the term

    Faculty revise the module

    The case study is the first thing they look at, and the revision takes days.

Bring a course you want to follow during the term.

We build an example from your own material, at no cost, before you decide. Book a demo and we will walk through what your program managers, faculty, and student services would each see.