Procurement Requests

Move purchase requests through review, budget approval, sourcing, and ordering with requester, spend, urgency, and policy context visible. This example brings Requests and Approvals together so operations managers can find the next task without losing context.

It includes representative records such as Analytics warehouse upgrade and Design research tooling. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Procurement Requests
Use this template in Figr

Template facts

Screen

Board

Primary action

New request

Pattern

Board

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Operations managers need to new request while keeping open requests, awaiting approval and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Requests gives users an obvious place to start.
  • Supporting view: Approvals keeps the related context close.
  • Primary action: New request stays visible when people need it.
  • First signal: Open requests shows a useful value (36).
  • Second signal: Awaiting approval gives additional context (11).
  • Sample record: Analytics warehouse upgrade.
  • Next record: Design research tooling.

States worth designing

  • No cards in this stage: say what changed, protect progress, and offer a clear next step.
  • Movement in progress: say what changed, protect progress, and offer a clear next step.
  • Move blocked by rules: say what changed, protect progress, and offer a clear next step.
  • Ownership updated: say what changed, protect progress, and offer a clear next step.
  • Archived item restored: say what changed, protect progress, and offer a clear next step.
  • Permission to edit missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Requests → Approvals → New request → Review outcome

Patterns used

Board, Requests, Approvals, contextual actions, error recovery

Why these choices work

Use real domain stages with a clear owner. Confirm high-impact moves and explain when permissions or missing work block an item.

Pay attention to requests and approvals. People need to distinguish Analytics warehouse upgrade from Design research tooling. Keep open requests 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 “New request”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Delivery Dispatch, Purchase Orders, Fleet Tracking.

Start from this in Figr

Design a procurement requests screen inside our existing product. Use our current components, tokens and content language. Include Requests and Approvals views, credible records like Analytics warehouse upgrade, and a clear “New request” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr