FieldCamp

Service Areas — Map Your Coverage | FieldCamp

The FieldCamp Service Areas record defines the geographic zones you cover. See its fields, how it connects to Team Members, and how coverage routes work.

A Service Area is a geographic zone your business covers — a radius around a depot, a set of zip codes, or a list of named cities. It is how FieldCamp knows where you work and who works there.

Each area carries the shape of the zone, the arrival times you offer inside it, and the team members assigned to cover it, so the system can put work where someone is already positioned to take it rather than sending a technician across the region.

Service Areas are what let coverage drive scheduling: when a job lands, the area it falls in points at the people who serve there.

FieldCamp works for any size, from a single-truck operator covering one town to a multi-location franchise with a zone per branch, residential or commercial.

What a Service Area captures

A Service Area record holds three things: a name, the geographic shape of the zone, and the arrival times you offer inside it.

The shape can be drawn three ways — a radius around a point, a set of zip codes, or a list of cities — and you pick the one that matches how you think about coverage.

The table below lists the fields a Service Area carries.

Identity and shape

FieldWhat it is
NameWhat you call the zone — "North County," "Downtown," "Branch 3." Required.
TypeHow the zone is drawn: a radius, a set of zip codes, or a drawn boundary.
Center pointThe address the radius is measured from, with its map location.
RadiusHow far the zone reaches from its center point, in kilometers.
Zip codesThe postal codes the zone covers, when you define it by zip.
CitiesThe named cities the zone covers, when you define it by city.
BoundaryThe drawn outline of the zone, for areas that follow a custom shape.
StatusWhether the zone is active and in use.

Arrival times and capacity

FieldWhat it is
ScheduleThe days and time slots you offer work inside the zone, with how much can be booked in each.
Team schedulesPer-person overrides to the zone's schedule, when a team member keeps different hours there.
Date overridesOne-off changes to the schedule for specific dates, such as a holiday or a blackout day.
Scheduling modeWhether you book a fixed start time or offer an arrival window inside the zone.
Default service durationHow long a job in the zone is expected to take, used when sizing the day.
Arrival window settingsThe configuration behind arrival-window booking, including how capacity is counted.

A Service Area is not part of the standard day-one set of records. It is added when you set up coverage-based scheduling.

Once added, it works the same way as the core records — with its own fields, its own assignments, and full customization.

How Service Areas connect

A Service Area belongs to your organization and is covered by the people you assign to it.

The link runs through the Team Member record: each team member carries the list of areas they serve, and each area is served by everyone whose list includes it — a many-to-many relationship.

The area itself does not hold a fixed roster of jobs; instead, where a job's site falls determines which area, and therefore which team members, can take it. The diagram below shows how a Service Area sits between your people and the work.

Read the connections outward from the Service Area:

  • Your Organization owns every Service Area and every Team Member; the areas are yours to define and the people are yours to assign.
  • One Team Member can cover many Service Areas, and one Service Area is covered by many team members. A technician who works two adjacent zones appears in both.
  • A Service Area scopes a Job by where its site falls — the area a job lands in points at the team members positioned to serve there.
  • A Service Area shapes the arrival times offered on a Visit, since the schedule and capacity that govern when work can be booked live on the area.

The connection between a Service Area and the people who cover it lives on the Team Member record, not on the area. To put someone on a zone, you set their service areas on their profile.

See Team Members for how coverage is assigned to a person.

Routing work to the right team

A Service Area earns its place by answering one question: for a job at this address, who is positioned to do it? Coverage is the bridge between a location on the map and the people on your team.

The flow below shows how a job's site narrows to a team that can do the work.

Draw the zone

Define each area the way your business thinks about coverage — a radius around a depot for a single-truck operator, a set of zip codes for a city contractor, or a list of cities for a multi-location franchise.

The shape is what lets FieldCamp decide whether a given site falls inside the zone.

Assign your people to it

Each team member carries the list of areas they cover, set on their profile. Because the link is many-to-many, one person can cover several adjacent zones and one busy zone can be backed by a whole crew.

This is the map from "where" to "who": the people on a zone are the candidates for work in that zone.

Match work to coverage

When a job's site falls inside an area, the team members who cover that area are the ones positioned to take it.

Coverage narrows the field to people already working nearby, which is what keeps a technician from being sent across the region for a job a closer team member could handle. Skills then decide who among them is qualified, and the working schedule shapes the day.

Offer the right arrival times

The schedule and capacity on the area govern when work can be booked inside it — fixed start times or an arrival window, with a set amount that fits in each slot.

Date overrides handle the exceptions, and per-person schedules let a single team member keep different hours in one zone than another.

Service Areas describe where you work and who covers it; they do not by themselves dispatch a job. Coverage tells FieldCamp which people are in range for a location — qualification by skill and availability by schedule then settle who actually takes the work.

Make it your own

The Service Area record is a starting point, not a boundary. You can shape zones to match exactly how your business divides the map, and add your own custom fields to track whatever a zone needs to carry.

The same Service Area record serves a single-truck operator with one zone and a multi-location franchise with a zone per branch.

A one-person business may draw a single radius and cover it themselves; a franchise keeps a zone for each location, assigns each crew to its own, and runs the same coverage rules at every site.

Residential or commercial, a Service Area is the same building block — draw the map, assign the people, and let coverage point work at the team that serves it.

See also

More in the FieldCamp data model.

Hands-on, step-by-step guides from the rest of the FieldCamp documentation.

On this page