Understanding the Report-It flow

Report It lets members of the public tell you about a problem at a specific place, such as fly-tipping, a broken streetlight or a damaged sign, by marking it on a map. This article explains what happens from the moment someone drops a pin to the moment a report lands in your own system, and where you have choices along the way.

There are four steps. The map can live anywhere, the checks run against your own data, and the finished report ends up wherever you already work.

The user marks the location

XMAP map on your website, in Power Pages, or inside another form

The user drops a pin or draws an area. The map can offer address search so they can jump straight to the right street, and it can show existing reports so duplicates are spotted early.

Power Pages via the XMAP control, a plain web page, or another supplier's form. Same map, same behaviour.

The map hands the location to your page.

The location is checked

XMAP Hub, using checks you define

Before the form goes any further, the page asks a question about the spot: is this inside your area of responsibility, which asset or site is nearest, has it already been reported. You decide which checks exist and which of your layers they use.

The answer is a yes or no, or a short list of what was found. The page then allows or blocks the next step.

Check passed. The user fills in the rest of the form.

The report is submitted

One of two routes, chosen when Report It is set up for you

The completed form, with the location, is saved as a report.

Either way the report is stored on your side, with a reference number, ready for the next step.

Through the XMAP Hub

Written straight into your database. Your own rules can route it onwards from there.

Through a Power Pages form

The form saves the record into your Dataverse table. Power Automate and your existing processes take it from there.

Report saved. The Hub route then notifies you straight away.

Your system is notified

Sent by the XMAP Hub to an address you choose

The moment the report is stored, the Hub sends it on to wherever you want it: a Power Automate flow, your CRM or ticketing system, a Microsoft Teams channel.

The report is already saved before the notification is sent, so a slow or offline receiver never loses one.

Settings, no new software Adding a check, a report target or a notification address is a settings change on your side.

Your data stays yours Checks run against your own layers on your own database. The Hub passes requests through and keeps nothing.

Host it anywhere The same map runs in Power Pages, on a plain web page, or inside another supplier's form.