Assignment Submission

Submit coursework with the brief, rubric, due date, files, draft saving, and review before final submission. This example brings Brief and Rubric together so learners and course teams can find the next task without losing context.

It includes representative records such as Final research memo and Interview synthesis.pdf. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Assignment Submission
Use this template in Figr

Template facts

Screen

Form

Primary action

Submit assignment

Pattern

Form

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 submit assignment while keeping due, files and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Brief gives users an obvious place to start.
  • Supporting view: Rubric keeps the related context close.
  • Primary action: Submit assignment stays visible when people need it.
  • First signal: Due shows a useful value (Sep 18).
  • Second signal: Files gives additional context (2).
  • Sample record: Final research memo.
  • Next record: Interview synthesis.pdf.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Brief → Rubric → Submit assignment → Review outcome

Patterns used

Form, Brief, Rubric, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to brief and rubric. People need to distinguish Final research memo from Interview synthesis.pdf. Keep due 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 “Submit assignment”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Lesson Player, Quiz Builder, Course Detail.

Start from this in Figr

Design a assignment submission screen inside our existing product. Use our current components, tokens and content language. Include Brief and Rubric views, credible records like Final research memo, and a clear “Submit assignment” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr