FIGR / UI TEMPLATE

Service Report

Capture work completed, diagnostics, parts used, labor, photos, recommendations, customer signature, and follow-up work at the end of a visit.

This form reference covers field service & customer operations. Its sample screen includes Work completed and Parts and labor and the Submit report action. Adapt its workflow to your product and design system.

Service Report

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Form

Primary action

Submit report

Pattern

Service report

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The service report screen supports “Submit report” while keeping work done and parts in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Submit report
  • Main area: Work done brings the user to the relevant workflow
  • Related area: Parts keeps nearby context accessible
  • Reports today: 26 in the sample screen
  • Submitted: 22 in the sample screen
  • Example 1: Work completed
  • Example 2: Parts and labor

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Disable duplicate submits while keeping entered values visible
  • Empty: Show required inputs and help people start without a blank form
  • Error: Keep filled fields and identify the exact problem to fix
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Submit report and say what happens next

Where it fits

Work done → Parts → Submit report → Review result

Patterns in this screen

Service report, Work done, Parts, permission handling, error recovery

UX choices to review

State input requirements before the user submits the form

In this example, Work completed is one of the records worth checking. Keep the sample data clearly separate from a live system.

Keep progress and entered values when people move between steps

Show clear permission, validation, and recovery states near the affected control

Try a similar screen in Figr

Design a service report screen for an existing field service & customer operations product. Use our actual design system, components, and content rules. Cover Work done and Parts, include believable records such as Work completed, and make "Submit report" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗