> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gettap.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Field coverage

> Which areas your team actually covers, and which they never reach.

Field coverage answers a question a CRM can't: **where did the team actually go?**

It maps the areas your reps recorded meetings in, as a heat map beside a ranked list. Dense areas are where the time went. Empty ones are either not worth covering or quietly neglected — and that distinction is usually worth a conversation.

<Note>
  Field coverage is an **Enterprise** feature, like the advanced Meeting Intelligence widgets. It sits at the bottom of the Team Insights default tab.
</Note>

## What it needs

A meeting appears on the map only if it was **recorded with location switched on**. Everything else is counted but not placed.

The header tells you the ratio up front — *"312 of 480 meetings have a location"* — and warns you when it's too low to trust: *"Only 34% of meetings have a location, so the map isn't the full picture."*

<Warning>
  Read the coverage ratio before you read the map. A map built from a third of your meetings tells you where that third happened, which is not the same as where your team went. If the ratio is low, the fix is getting location switched on, not re-planning territories.
</Warning>

The footer accounts for the rest: meetings with no location, and meetings **outside the areas we map**. Neither is shown.

## Reading it

Hover an area for its numbers: meetings, how many reps, and the average lead score there. Click it to zoom in and see the smaller areas inside it.

Use the **city chips** to jump between cities, or **All areas** to come back out.

| What you see | What it means |
| - | - |
| Darker shading | More meetings in that area |
| **12 meetings · 3 reps** | Volume, and how many people produced it |
| **Avg lead score** | Whether the leads from that area are any good |
| **Most meetings: Omar · 14** | Who covers the area |

Clicking an area also **filters the page to it**, so the rest of Team Insights narrows to that area's conversations.

## Areas nest

An area sits inside a larger one. Filtering by a district includes the neighbourhoods within it, so you can read coverage at whichever level makes sense — a whole city, or one neighbourhood inside it.

## Using it well

<AccordionGroup>
  <Accordion title="Average lead score beats meeting count" icon="fire">
    The busiest area isn't automatically the best one. An area with half the meetings and a much higher average lead score is where the next rep should go. Volume tells you where habit took the team; score tells you where the pipeline is.
  </Accordion>

  <Accordion title="One rep in an area is a risk, not a win" icon="user">
    An area with twenty meetings from one person is one resignation away from zero coverage. The rep count is the more useful number for planning.
  </Accordion>

  <Accordion title="Empty isn't automatically a gap" icon="map-pin">
    Some areas have nothing worth visiting. Check against where your customers actually are before treating a cold patch as a failure.
  </Accordion>

  <Accordion title="Compare the same season" icon="calendar">
    Coverage is seasonal for most field teams. Compare this quarter to the same quarter last year rather than to last month.
  </Accordion>
</AccordionGroup>

## When it's empty

*"No meeting locations yet — meetings recorded with location on show up here."*

Nothing is wrong. Either no meetings have been recorded in the period, or location was off for all of them. See [Meetings](/en/leads/meetings).

<Card title="Insights overview" icon="arrow-left" href="/en/insights/overview">
  Everything Team Insights covers.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.