Gradebook

Review student scores, missing work, weighted categories, feedback, and grading actions in one instructor gradebook. This example brings Gradebook and Assignments together so learners and course teams can find the next task without losing context.

It includes representative records such as Ava Carter and Noah Williams. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Gradebook
Use this template in Figr

Template facts

Screen

Table

Primary action

Enter grades

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 enter grades while keeping students, class average and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Gradebook gives users an obvious place to start.
  • Supporting view: Assignments keeps the related context close.
  • Primary action: Enter grades stays visible when people need it.
  • First signal: Students shows a useful value (42).
  • Second signal: Class average gives additional context (84%).
  • Sample record: Ava Carter.
  • Next record: Noah Williams.

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

Gradebook → Assignments → Enter grades → Review outcome

Patterns used

Table, Gradebook, Assignments, 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 gradebook and assignments. People need to distinguish Ava Carter from Noah Williams. Keep students 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 “Enter grades”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Quiz Builder, Student Progress, Assignment Submission.

Start from this in Figr

Design a gradebook screen inside our existing product. Use our current components, tokens and content language. Include Gradebook and Assignments views, credible records like Ava Carter, and a clear “Enter grades” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr