FIGR / UI TEMPLATE

Service Request 311

Report a municipal issue with category, location, photos, description, urgency, department routing, contact preference, and resolution updates.

This form reference covers public services. Its sample screen includes Choose issue category and Confirm location and the Submit request action. Adapt its workflow to your product and design system.

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 request

Pattern

Service Request 311 form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The service request 311 screen supports “Submit request” while keeping report issue and my requests in view. It should show the current state even when data is missing or access is restricted.

What to look for

Primary action: Submit request
Main area: Report issue brings the user to the relevant workflow
Related area: My requests keeps nearby context accessible
Open nearby: 23 in the sample screen
Avg response: 1.8d in the sample screen
Example 1: Choose issue category
Example 2: Confirm location
Input: Issue 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 request and say what happens next

Where it fits

Report issue → My requests → Submit request → Review result

Patterns in this screen

Service Request 311 form, Report issue, My requests, permission handling, error recovery

UX choices to review

State input requirements before the user submits the form

In this example, Choose issue category 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 request 311 screen for an existing public services product. Use our actual design system, components, and content rules. Cover Report issue and My requests, include believable records such as Choose issue category, and make "Submit request" 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 ↗