File Review

Review shared files with version status, reviewers, comments, approvals, and the exact changes still blocking sign-off. The screen connects Review and Versions so product teams can find the “Request review” action while checking open reviews and approved.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Pricing deck v8 · 2 comments and Launch video v12 · Approved, rather than an empty visual shell.

File Review
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Request review

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Request review” action without losing sight of open reviews, approved and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Request review is clearly available where the task happens.
  • Main view: Review keeps the starting point obvious.
  • Connected view: Versions supplies nearby context.
  • Metric: Open reviews is visible with a meaningful value.
  • Another signal: Approved helps people judge what to do next.
  • Representative record: Pricing deck v8 · 2 comments makes the example specific.
  • Second record: Launch video v12 · Approved shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading review without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for versions; clarify who can continue.
  • Success after choosing Request review; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Review → Versions → Request review → Review outcome

Patterns used

Workspace, Review, Versions, Comments, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Pricing deck v8 · 2 comments with Launch video v12 · Approved. Make open reviews clear, then use approved to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Request review” action. The happy path alone is not enough.

Related UI examples: Comments & Mentions, Resource Planning, Docs Workspace.

Start from this in Figr

Design a file review screen for our existing software product. Use our real design-system tokens, components and product language. Show Review and Versions, include believable records such as Pricing deck v8 · 2 comments, and make request review easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr