Skip to main content
UI Coach Logo
Back to challenges
Hard

Verified Community Safety Alerts

Design a public safety app for receiving verified local notices and reporting non-emergency incidents without enabling surveillance or vigilantism.

Mobile, Responsive web

The brief

Understand the problem

Background

Residents need timely safety information, but rumor-driven alerts and public suspect identification can expose innocent people to harassment. Reports must reach the right authority without turning neighbors into investigators.

User context

Imani receives a verified notice about repeated vehicle break-ins near her transit stop. Later, she notices damaged lighting and an abandoned bag but cannot tell whether either requires emergency help.

Product problem

The product must distinguish official notices, non-emergency reports, and urgent calls while protecting locations, identities, and unverified details.

Objective

Create a safety notice and guided reporting experience centered on verification, privacy, and appropriate escalation.

What to design

Define the experience

Required experience

  • Verified alert feed with geographic relevance
  • Guided incident assessment
  • Private report submission and status

Screens and states

  • Local safety overview
  • Report triage
  • Submission confirmation and updates
  • Urgent help handoff

Core user flow

Follow the critical path

  1. 01

    Imani reviews the source and affected area of an alert

  2. 02

    She starts a new report

  3. 03

    The service asks whether anyone is in immediate danger

  4. 04

    Her non-emergency report is submitted with a coarse location and reference number

Product rules

Requirements and constraints

Requirements

  • Label the authority and verification status of every notice
  • Direct immediate danger to emergency services
  • Keep reporter identity private from the public
  • Prevent public uploads from naming or identifying alleged suspects
  • Explain how submitted evidence will be used

Constraints

  • The app cannot guarantee police response times
  • Location sharing must be optional and adjustable
  • Reports may involve trauma or limited literacy

Reality check

States worth considering

The user reports an active emergency
A notice is corrected or withdrawn
Location permission is denied
The user needs language or accessibility support
A report contains identifying accusations

Ready-to-use content

Mock data

Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.

Safety notices

  • Transit entrance lighting outage, verified by City Works
  • Vehicle break-ins reported within 500 meters, verified by District Safety Office
  • Earlier road closure notice resolved at 18:40

Finish line

What to deliver

  • A five-screen mobile safety and reporting flow
  • A content hierarchy for verified, corrected, and unverified information

If you want more

Optional extensions

Add anonymous follow-up messages with an agency
Design a neighborhood preparedness checklist

Optional direction

Visual resources

Use these as a starting constraint if you want one. They are not part of the required solution.

Color palette
#79674F
#EDE6D2
#090C0F
#B7B7B7
#A7A7A7
Font pairing
Open SansPrata

Open Sans & Prata

Clear interface writing gives people the confidence to understand what changed and decide what to do next.

Icons
Illustrations