Editorial Review

Review drafts with comments, requested changes, owner context, due dates, and approval status in one focused queue. This example brings Needs review and My reviews together so content and product teams can find the next task without losing context.

It includes representative records such as Pricing announcement and Security case study. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Editorial Review
Use this template in Figr

Template facts

Screen

Inbox

Primary action

Approve draft

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to approve draft while keeping waiting, due today and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Needs review gives users an obvious place to start.
  • Supporting view: My reviews keeps the related context close.
  • Primary action: Approve draft stays visible when people need it.
  • First signal: Waiting shows a useful value (12).
  • Second signal: Due today gives additional context (5).
  • Sample record: Pricing announcement.
  • Next record: Security case study.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Needs review → My reviews → Approve draft → Review outcome

Patterns used

Inbox, Needs review, My reviews, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to needs review and my reviews. People need to distinguish Pricing announcement from Security case study. Keep waiting 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 “Approve draft”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Publishing Workflow, Template Gallery, Version History.

Start from this in Figr

Design a editorial review screen inside our existing product. Use our current components, tokens and content language. Include Needs review and My reviews views, credible records like Pricing announcement, and a clear “Approve draft” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr