Defining Geofenced Site Boundaries on a Map

A site boundary is rarely just a circle

When people picture a geofence, they usually imagine a center point with a radius drawn around it — that's how most first-generation location tracking tools model a site. Real field operations rarely look that tidy. A property management company might be responsible for a complex made up of several separate blocks with a road running between them. A security firm's patrol area might span a few parcels with gaps in between. A maintenance crew's job site might split into a storage building near the entrance and the main construction area some distance away. A single circular boundary can't represent any of that accurately — either you draw it too wide and lose the precision that made the tracking worth setting up, or staff moving between two legitimate areas keep triggering "left the site" the moment they cross the gap.

The right approach is to draw the boundary freehand on the map instead of forcing it into a circle, and to allow that boundary to consist of more than one disjoint area when the job actually requires it. This post walks through how to set up site boundaries on a map, how to make disjoint areas count as a single site, and the setup mistakes that come up most often.

The practical steps for drawing a boundary

Defining a site boundary doesn't require typing coordinates or guessing at a radius. In HR-Tech, it comes down to three steps:

1. Trace the site's actual shape on the map. A manager marks the physical edges of the site over satellite imagery — the building facade, the garden wall, the construction fence become the boundary too. This makes the area the system treats as "inside" match the area staff are actually working in.
2. Assign staff and a site manager to it. Every site can have one or more people responsible for it; anyone not assigned to a site is never evaluated against it, which removes the risk of someone being pulled into another team's site by accident.
3. Check the active dates. An employee is only evaluated against sites assigned to them and active on that date — a past project or a handed-over site never enters the calculation. Deactivating a site once a project ends keeps old records from bleeding into the current period.

Once the boundary is drawn correctly, a session opens automatically the moment staff enter the area and closes when they leave. Nobody presses a button, and nobody gets a reminder to share their location — the inside-or-outside decision happens on the server, not the phone, so the record comes from a single source of truth that can't be altered by changing device settings afterward.

Setting up one site out of disjoint areas

This is where the real practical question comes in: treating areas that don't physically touch as a single site. In HR-Tech, a site's boundary doesn't have to be one closed shape — the same site record can include several disjoint areas. Blocks 1, 4 and 7 of a complex might be physically separate, but if the same management company is responsible for all three, they count as one site. As a guard patrols between blocks, the system doesn't flag every crossing as "left the site, re-entered" — because the definition was set up from the start to treat them as a single whole.

That has three concrete benefits in practice:

• No noisy violation alerts. A few minutes walking between blocks doesn't land on a manager's screen as "left the site" — since the disjoint areas belong to the same site, the gap between them isn't a violation.
• Timesheets add up correctly. Time spent across different blocks during the day isn't split into fragments; it's summed under one site, so the daily total comes out right.
• No repeated setup. Adding a new block or parcel later just means adding a new area to the existing site definition — there's no need to open a separate site record and reassign staff.

This is the concrete version of the "boundary accuracy" principle we cover in automating field staff timesheets: the more faithfully a boundary reflects real field operations, the more trustworthy the record it produces.

Common mistakes when drawing boundaries

Boundary setup looks simple, but a handful of recurring mistakes tend to erode trust in the first few weeks:

• Drawing the boundary too wide "just in case." Padding a boundary to cover the neighboring street to avoid edge cases actually defeats the purpose — staff can show up as "inside" before they've even reached the site.
• Opening separate sites for disjoint areas. Creating individual site records for blocks that don't touch but belong to the same team fragments reporting and clutters everyone's multi-site assignment list for no reason.
• Drawing it once and never revisiting it. When a site expands, a new entrance opens, or a neighboring area gets added to the contract, failing to update the boundary lets the gap between reality and what the system sees grow over time.
• Leaving finished sites active. A completed project or a handed-over site left active in the system keeps padding staff lists and reports with data nobody needs anymore.

Verifying the setup after go-live

Drawing the boundary isn't the last step in rollout. For the first few days, it's worth checking the live map to confirm staff positions actually line up with the drawn boundary — even a building facade marked a few meters off produces a visible skew in entry and exit records. Unexpected violation alerts during this period are usually a sign the boundary needs a small correction, not that staff did something wrong. For short, job-related trips outside the boundary, an approved off-site duty entry records the exception properly without forcing you to loosen the boundary itself.

Conclusion

Getting the site boundary right on the map is the most critical step in location-based timesheets and field tracking — the more accurately it reflects the physical reality of the site, the less room there is to argue with the record it produces. Grouping disjoint areas under a single site definition cuts down on false violation alerts and keeps the whole setup simpler to maintain.

To define your sites on the map and put field tracking on autopilot, take a look at HR-Tech's field tracking and geofencing module, or reach out directly through our contact page and we can plan the setup together.