Resource Planning

Balance project demand against team capacity, surface overloaded people, and make allocation tradeoffs explicit. The screen connects Capacity and People so product teams can find the “Assign work” action while checking team capacity and overallocated.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Engineering · 92% used and Design · 84% used, rather than an empty visual shell.

Resource Planning
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Assign work

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Assign work” action without losing sight of team capacity, overallocated and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Assign work is clearly available where the task happens.
  • Main view: Capacity keeps the starting point obvious.
  • Connected view: People supplies nearby context.
  • Metric: Team capacity is visible with a meaningful value.
  • Another signal: Overallocated helps people judge what to do next.
  • Representative record: Engineering · 92% used makes the example specific.
  • Second record: Design · 84% used shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading capacity without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for people; clarify who can continue.
  • Success after choosing Assign work; 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

Capacity → People → Assign work → Review outcome

Patterns used

Analytics, Capacity, People, Projects, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Engineering · 92% used with Design · 84% used. Make team capacity clear, then use overallocated 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 “Assign work” action. The happy path alone is not enough.

Related UI examples: File Review, Comments & Mentions, Docs Workspace.

Start from this in Figr

Design a resource planning screen for our existing software product. Use our real design-system tokens, components and product language. Show Capacity and People, include believable records such as Engineering · 92% used, and make assign work easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr