Quality Inspection

Record inspection results for received or produced goods with checklist items, photos, defects, severity, disposition, and reviewer sign-off. This example brings Checklist and Defects together so operations managers can find the next task without losing context.

It includes representative records such as Verify packaging integrity and Check dimensions. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Quality Inspection
Use this template in Figr

Template facts

Screen

Form

Primary action

Complete inspection

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Operations managers need to complete inspection while keeping checks, passed and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Checklist gives users an obvious place to start.
  • Supporting view: Defects keeps the related context close.
  • Primary action: Complete inspection stays visible when people need it.
  • First signal: Checks shows a useful value (18).
  • Second signal: Passed gives additional context (14).
  • Sample record: Verify packaging integrity.
  • Next record: Check dimensions.

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

Checklist → Defects → Complete inspection → Review outcome

Patterns used

Form, Checklist, Defects, 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 checklist and defects. People need to distinguish Verify packaging integrity from Check dimensions. Keep checks 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 “Complete inspection”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Supplier Portal, Operations Incident Log, Receiving Inventory.

Start from this in Figr

Design a quality inspection screen inside our existing product. Use our current components, tokens and content language. Include Checklist and Defects views, credible records like Verify packaging integrity, and a clear “Complete inspection” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr