FIGR / UI TEMPLATE

Permit Application

Submit applicant details, property or project scope, documents, fees, and review information for a public permit.

This form reference covers public services. Its sample screen includes Applicant information and Project address and scope and the Submit application action. Adapt its workflow to your product and design system.

Permit Application

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 application

Pattern

Permit Application form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The permit application screen supports “Submit application” while keeping applicant and project in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Submit application
  • Main area: Applicant brings the user to the relevant workflow
  • Related area: Project keeps nearby context accessible
  • Steps: 5 in the sample screen
  • Documents: 6 in the sample screen
  • Example 1: Applicant information
  • Example 2: Project address and scope
  • Input: Permit type

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

Where it fits

Applicant → Project → Submit application → Review result

Patterns in this screen

Permit Application form, Applicant, Project, permission handling, error recovery

UX choices to review

State input requirements before the user submits the form

In this example, Applicant information 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 permit application screen for an existing public services product. Use our actual design system, components, and content rules. Cover Applicant and Project, include believable records such as Applicant information, and make "Submit application" 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 ↗