FIGR / UI TEMPLATE

Claims Submission

Guide policyholders through incident details, affected property, supporting evidence, witnesses, and payout information when filing a claim.

This form reference covers insurance & claims. Its sample screen includes Incident details and Damage assessment and the Submit claim action. Adapt its workflow to your product and design system.

Claims Submission

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 claim

Pattern

Claims submission

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The claims submission screen supports “Submit claim” while keeping incident and damage in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Submit claim
  • Main area: Incident brings the user to the relevant workflow
  • Related area: Damage keeps nearby context accessible
  • Drafts: 18 in the sample screen
  • Avg completion: 11m in the sample screen
  • Example 1: Incident details
  • Example 2: Damage assessment

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 claim and say what happens next

Where it fits

Incident → Damage → Submit claim → Review result

Patterns in this screen

Claims submission, Incident, Damage, permission handling, error recovery

UX choices to review

State input requirements before the user submits the form

In this example, Incident details 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 claims submission screen for an existing insurance & claims product. Use our actual design system, components, and content rules. Cover Incident and Damage, include believable records such as Incident details, and make "Submit claim" 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 ↗