Budget Planning

Build a department budget with owner, category, baseline, scenario assumptions, approval, and variance context before locking it. The screen connects Budgets and Scenarios so product teams can find the “Create budget” action while checking planned and allocated.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Engineering · 3.2M and Sales · 2.1M, rather than an empty visual shell.

Budget Planning
Use this template in Figr

Template facts

Screen

Form

Primary action

Create budget

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Create budget” action without losing sight of planned, allocated and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create budget is clearly available where the task happens.
  • Main view: Budgets keeps the starting point obvious.
  • Connected view: Scenarios supplies nearby context.
  • Metric: Planned is visible with a meaningful value.
  • Another signal: Allocated helps people judge what to do next.
  • Representative record: Engineering · 3.2M makes the example specific.
  • Second record: Sales · 2.1M shows the pattern works beyond one item.

States worth designing

  • Missing required details; show what people can do instead of leaving a blank panel.
  • Loading budgets without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for scenarios; clarify who can continue.
  • Success after choosing Create budget; 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

Budgets → Scenarios → Create budget → Review outcome

Patterns used

Form, Budgets, Scenarios, Departments, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Engineering · 3.2M with Sales · 2.1M. Make planned clear, then use allocated 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 “Create budget” action. The happy path alone is not enough.

Related UI examples: Expense Management, Checkout, Invoice Management.

Start from this in Figr

Design a budget planning screen for our existing software product. Use our real design-system tokens, components and product language. Show Budgets and Scenarios, include believable records such as Engineering · 3.2M, and make create budget easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr