# Build one screen that shows what is happening where

Build an operations dashboard: a map with counts, charts and filters that your team keeps open, refreshed by a routine and opened from a link.

Video: Build one screen that shows what is happening where (1 min 18 s): /images/docs/videos/operations-dashboard.mp4

## Best for

Anyone running an operation who needs one shared picture of where the work is: service desks, maintenance and field teams, emergency and programme managers. Some call it an ops dashboard or a common operating picture. You end up with a map of the open work, with charts and filters beside it and the areas that are falling behind shaded, which the team opens from one link.

**The example in this guide** is a real export from NYC Open Data: the 311 Service Requests dataset, filtered to Brooklyn, to requests created from 4 to 10 November 2026, and to requests that were not closed. It has 6,708 rows, each with an ID, the date created, a status (Open, In Progress, Assigned and a few others), the agency handling it, a complaint type and description, an address, a ZIP code, a community board, and a latitude and longitude. 87 rows have no coordinates. Every ask below was sent with that file. With your own records, keep the shape of the asks and change the words.

## What you need

- **Your records as a spreadsheet,** one row for each job, incident or request, with coordinates or an address, and the columns you want to count and filter by (status, team, type).
- **A Free, Creator or Creator Max seat** for the map. Keeping it current with a routine needs a Creator or Creator Max seat on a workspace that pays for its seats.

## Before you start

- **Name the few numbers that matter.** Say what to count, what to chart and what to filter by. Mapstack builds what you list and adds what a reader would expect, such as pop-ups and a search box.
- **Decide how fresh it must be.** A routine refreshes the data at most once an hour. That suits a screen the team checks through the day, not one used to dispatch in real time.

## The prompt

> This is every open 311 request in Brooklyn from the last week. We need one screen for the operations team: a map of where the open requests are, counts of open vs in progress, a chart by complaint type, and a filter by agency.

## What to expect

1. **Mapstack places your records and asks what to build**

   Your file becomes a dataset, with each request placed from its coordinates. Mapstack then sets out what it understood (the audience, the data, the parts you asked for) and asks whether you want an interactive map or a web app.

   Choose the map when the screen has to stay current. A map is drawn from its datasets, so when a routine refreshes them the map shows the new records. An app changes only when you ask for a change in a session.

   > The interactive map, please. It needs to stay current, so build it as a map the team can keep open.

2. **You get the map, with charts and filters beside it**

   The requests are points coloured by status. The **Charts** tab holds a bar chart of requests by complaint type, counted over all the requests or only those on screen. **Filters** narrow the map by agency and by status, the search box finds a request by address or ID, and selecting a point shows the full record.

   ![Example: open 311 requests in Brooklyn coloured by status, over community districts shaded by open requests, with the chart of requests by complaint type.](/images/docs/operations-dashboard/open-requests-by-status-with-charts.jpeg)

3. **You show which areas are falling behind**

   Counts by area tell a manager where to send people. Ask for the areas you report on:

   > Add the Brooklyn community district boundaries and show how many open requests each district has, so the team can see which districts are falling behind.

   Mapstack fetches the boundaries itself, counts the open requests inside each area and shades the areas beneath the points. Each area's pop-up gives its open, in-progress and total requests. In the example it named the five districts with the most open requests, led by District 17 with 417, and the three with the fewest.

4. **You check the numbers against your file**

   Treat the screen as a colleague's first draft and compare its totals with what you sent. The charts count what is on the map, and a row without a location cannot be placed. In the example the charts showed 6,621 requests against 6,708 rows in the file:

   > The charts say 6,621 requests but the file has 6,708. Which ones are missing from the map, and why? Also add a chart of open vs in progress next to the complaint type chart.

   Mapstack confirmed that 87 rows could not be placed (in the source file all 87 had no coordinates), gave the count for each status, and added a chart of requests by status under the complaint type chart. It offered to list the unplaced requests or export them as a CSV.

5. **You keep it current with a routine**

   A routine is a job Mapstack runs for you without a session: here, fetch the latest requests, refresh the dataset and recount the districts. Mapstack explains how to set one up when asked:

   > Can this keep itself up to date? We'd want it refreshed every hour from the 311 data.

   1. Select **Routines**, then **New routine**.
   2. Give it a name, and write the **Instructions** as you would brief a colleague: where the new records come from, and which datasets to refresh.
   3. Under **When should it run?**, choose **Hourly**.
   4. If your team drops new exports into Google Drive, OneDrive or Dropbox, connect it under **Connectors** so the routine can read the new files.
   5. Select **Create routine**.

   See [Routines](/docs/automate/set-up-a-routine) and [Choose when a routine runs](/docs/automate/when-a-routine-runs).

6. **You give the team the link**

   Sharing is done on the map itself. For people in your workspace, select **Share**, then **Copy link**. A colleague with a Viewer seat can open the map, filter it and ask questions about it, but cannot change it. For people outside the workspace, select **Publish**, then **Public**, then **Make public**, then **Copy link**. Anyone with the link can then use the filters and charts without signing in. See [Share with people in your workspace](/docs/share/share-with-people).

## Make it your own

> Make it so the team can open it from a link without changing anything.

## Common questions

**Should I choose a map or an app?**

A map, if the screen has to stay current. A map is drawn from its datasets, so when a routine refreshes them it shows the new records. An app changes only when you ask for a change in a session.

**Why does the map show fewer records than my file?**

Rows with no location cannot be placed. Ask which ones are missing and why, or ask for them as a list to fix and attach again. In the example 87 of the 6,708 rows had no coordinates.

**Does it count by location or by the area column in my file?**

By location: Mapstack counts the records that sit inside each boundary. The two can differ: in the example District 5 had 339 open requests by location and 346 by the file's community board column. Say which you want counted.

**Can it refresh faster than hourly?**

No. A routine runs at most once an hour, which suits a screen the team checks through the day. For anything closer to real time, refresh it in a session when you need it.

**Can the team use it without changing it?**

Yes. A colleague with a Viewer seat can open the map, filter it and ask questions about it, but cannot change it. On the map, select **Share**, then **Copy link**.

## Related

- [Make a map](https://mapstack.io/docs/make/maps.md)
- [Data Mapstack can find for you](https://mapstack.io/docs/find-data/data-mapstack-finds.md)
- [Set up a routine](https://mapstack.io/docs/automate/set-up-a-routine.md)
- [Choose when a routine runs](https://mapstack.io/docs/automate/when-a-routine-runs.md)
- [Share with people in your workspace](https://mapstack.io/docs/share/share-with-people.md)
- [Make something public](https://mapstack.io/docs/share/make-it-public.md)
