Reports from the public

Also called service request, report a problem, citizen request

Reported by a resident from a code or link, with a photo, routed to the department that handles it, and closed, with the resident notified. We build it to work the way you handle reports now.

Video coming

Start to finish

From a code on a post to the department that fixes it.

Here’s how it runs in Flow Forms. The steps marked on its own happen without anyone, and everyone else is notified when it’s their turn.

  1. 1
    The resident

    Scans a code on a sign, a park post, or the counter, or opens a link on your website, and reports it on any device, with no account. A photo helps. The form only asks what applies to that kind of problem.

  2. 2
    The routingOn its own

    Goes to the department that handles that kind of problem: public works, parks, code enforcement, or whoever your process names.

  3. 3
    The department

    Assigns it to a crew or an officer. If it sits, reminders go out. If they’re out, it goes to their backup.

  4. 4
    Whoever’s assigned

    Handles it and closes their part, with a photo of the finished work if your office wants one.

  5. 5
    The resident, againOn its own

    Notified that it’s been handled, if they left a way to reach them.

  6. ✓
    On fileOn its own

    The record keeps the report, the photos, who handled it, and when, including reports filed without a name. If anyone edits it later, the edit is logged.

What it handles

The details, built in.

  • Right where the problem isA code on a sign or a park post opens the form, no login, nothing to install.
  • The right departmentRouted by the kind of problem, so nobody sorts reports by hand.
  • Photos from the residentAttached with the report, in front of whoever goes out.
  • Anonymous reportsResidents can report without a name, and the record still keeps every step.
  • Patterns by placeReports by kind of problem, location, or how long each took to close.

Yours needs something that isn’t here?

Bring it to the first call. We’ll build it in while you walk us through how it works.

Book a conversation →

Or see what’s included with every process →

How it varies

Every office handles reports from the public a little differently.

We don’t start from a standard report form. We start from how yours runs today. And when something changes, like a new kind of problem or a new department, tell us and we change it.

We build it to yours.

  • What residents can reportPotholes, streetlights, water leaks, graffiti, code concerns, or compliments too.
  • Who it goes toPublic works, parks, code enforcement, utilities, or the clerk to sort.
  • NamesRequired, optional, or anonymous for some kinds of reports.
  • Where the codes goPark posts, trailheads, bus stops, the counter, or utility bills.
  • UpdatesA notice when it’s closed, at each step, or none.

Questions

About reports from the public.

Do residents need an app or an account?

No. They scan a code or open a link and report it on any device, with nothing to install.

Can residents attach a photo?

Yes. Photos attach to the report, and whoever handles it sees them.

Can different problems go to different departments?

Yes. Each report routes by the kind of problem, so a pothole reaches public works and a code concern reaches code enforcement.

Can residents report anonymously?

Yes, where your office allows it. The record still keeps every step and who handled it.

Does the resident hear back?

Yes, if they left a way to reach them. They’re notified when it’s been handled.

Read how offices handle it →

Bring us yours.

We’ll build it with you.

Tell us what residents report now, how it reaches the right department, and how they hear back. Not a demo. A conversation about your process.

Book a conversation