> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/field-app/run-a-field-survey.md).

# Run a field survey

Turn a Felt map into a field data capture tool. Build a survey on the web, and watch your team's results arrive on the map as they capture them.

Set up a survey map on the web, then invite your team to capture data in the Field App. Their updates sync to the map so everyone can follow progress.

A survey in Felt gives you:

* Consistent data: every crew fills in the same form, with dropdowns and required fields where you need them.
* Precise locations: crews can place features at their GPS location and attach photos to them.
* Live progress: styling and dashboard components update as features come in, so you can see what's done and what's left.

Everyone who captures data needs a seat and Contribute or Edit access to the map. People who only follow the survey can view and comment without a seat.

For example, a city preparing to upgrade the lights in its parks might send crews to check the condition of every light pole, fix inaccurate trail data, and photograph damage. The project manager follows progress on the map and sends leadership a summary at the end of each day. To see this survey in action, watch the [Field App webinar](https://felt.com/webinars/bringing-the-full-power-of-gis-to-the-field-with-felts-field-app).

## Step 1: Create the survey layer and its form

Create the survey layer on the web. Its attributes become the fields in the form your field team fills in.

1. Create a layer for the assets you want to survey, and choose its geometry type: point, line, or polygon. See [Create layers](/layers/create-layers.md).
2. Click **Add attribute** for each detail the team needs to record, such as status, condition, or notes.
3. Optional: Give text and number attributes a dropdown list so the team selects a value instead of typing one. See [Add a dropdown list](/layers/forms.md#add-a-dropdown-list).
4. Optional: Add an **Image** attribute so the team can attach photos.
5. Click **Create layer**. The empty layer appears in the legend.

To use an existing layer instead, add attributes to it. See [Edit features](/layers/edit-features.md#add-rename-or-delete-attributes).

Optional: Upload reference data, such as parcels or trails, to help the team find their way. See [Upload files](/upload-anything/files.md). You can also switch to a satellite basemap. See [Basemaps](/styling/basemaps.md).

### Add required fields and follow-up questions

{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}

Advanced forms let you make a survey field required or show a follow-up question only when an earlier answer calls for it. For example, ask for damage severity only when the crew records damage. See [Forms](/layers/forms.md).

## Step 2: Color the survey layer by status

Coloring the survey layer by a status attribute turns the map from "where things are" into "what's happening." Crews can see which assets still need a visit, and you can follow progress without opening every feature.

1. Select the survey layer in the legend.
2. In the **Style** tab, change the style type from **Simple** to **Categories**.
3. In **Color by**, select the status attribute. The map and the legend show a color for each status.

See [Style vector layers](/styling/style-vector-layers.md).

## Step 3: Add a survey progress dashboard

{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}

The map shows where work is happening, and dashboard components show how much is done. Add a Statistic component to count the features your team has recorded.

1. Click **Dashboards** in the center of the toolbar at the top of the map.
2. Under **Components**, select **Statistic**, then select the survey layer. A feature count appears under the layer in the legend.

Optional: In the component's **Title**, enter a name such as `Total assets`, and turn on **Update based on view** to count only what's on screen. To break progress down by status, add a Bar chart too. For component settings and other types, see [Dashboards](/analysis-and-dashboards/dashboards.md).

## Step 4: Invite your field team

1. Click **Share** at the top right of the map.
2. Enter the email addresses of your field team.
3. Select **Contribute** so they can add and edit features.
4. Click **Invite**. Each person gets an email with a link to the map.

On a phone with the Field App installed, the link opens the map in the app. See [Set up the Field App](/field-app/set-up-the-field-app.md) and [Share a map](/share/share-a-map.md).

## Step 5: Capture survey data in the Field App

The field team opens the survey map in the Field App, taps the **+** button, and selects the survey layer under **Add feature**. For the full steps, including photos and editing, see [Capture field data](/field-app/collect-field-data.md). To measure a trail segment or a damaged area, crews can use the Measure tool. See [Measure](/tools/measure.md#measure-a-distance-or-area).

Crews heading somewhere without cell service can download the survey area before they leave. See [Work offline](/field-app/work-offline.md).

When the survey is done, export the survey layer from Felt on the web. See [Export data](/export-and-print/export-data.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.felt.com/field-app/run-a-field-survey.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.