Student Progress

Track learner completion, pace, scores, engagement, overdue work, and intervention signals over time. This example brings Overview and Courses together so learners and course teams can find the next task without losing context.

It includes representative records such as Product Strategy and SQL Analytics. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Student Progress
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Create intervention

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to create intervention while keeping completion, avg score and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Courses keeps the related context close.
  • Primary action: Create intervention stays visible when people need it.
  • First signal: Completion shows a useful value (71%).
  • Second signal: Avg score gives additional context (86%).
  • Sample record: Product Strategy.
  • Next record: SQL Analytics.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Courses → Create intervention → Review outcome

Patterns used

Analytics, Overview, Courses, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to overview and courses. People need to distinguish Product Strategy from SQL Analytics. Keep completion visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Create intervention”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Gradebook, Cohort Management, Quiz Builder.

Start from this in Figr

Design a student progress screen inside our existing product. Use our current components, tokens and content language. Include Overview and Courses views, credible records like Product Strategy, and a clear “Create intervention” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr