Cohort Management

Manage learning cohorts, instructors, curriculum, enrollment, schedules, attendance, and progress from one operations view. This example brings Cohorts and Learners together so learners and course teams can find the next task without losing context.

It includes representative records such as PM Cohort · September and Analytics Cohort · Q3. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Cohort Management
Use this template in Figr

Template facts

Screen

Table

Primary action

New cohort

Pattern

Table

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 new cohort while keeping active cohorts, learners and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Cohorts gives users an obvious place to start.
  • Supporting view: Learners keeps the related context close.
  • Primary action: New cohort stays visible when people need it.
  • First signal: Active cohorts shows a useful value (12).
  • Second signal: Learners gives additional context (384).
  • Sample record: PM Cohort · September.
  • Next record: Analytics Cohort · Q3.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Cohorts → Learners → New cohort → Review outcome

Patterns used

Table, Cohorts, Learners, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to cohorts and learners. People need to distinguish PM Cohort · September from Analytics Cohort · Q3. Keep active cohorts 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 “New cohort”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Student Progress, Certificate Issuance, Gradebook.

Start from this in Figr

Design a cohort management screen inside our existing product. Use our current components, tokens and content language. Include Cohorts and Learners views, credible records like PM Cohort · September, and a clear “New cohort” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr