Start where people actually arrive
Attendify represents each site with a circular boundary. Choose the intended attendance point: a gate, reception area or site office. A property’s geometric center may be far from that point, especially on a long or irregular site.
Inspect nearby roads, homes and adjacent premises before choosing a radius. A wider circle may reduce legitimate rejections while also admitting locations outside the intended working area. There is no single radius that resolves that trade-off everywhere.
Measure before adjusting
GPS.gov’s accuracy explanation describes how environment and equipment affect location. A reported accuracy value is context, not proof of an exact physical position. Test more than one actual device, at the arrival time and in the conditions your workers face.
Scroll the table sideways to read all columns.
| Test location | Expected outcome | Record |
|---|---|---|
| Intended entrance | Legitimate capture should work | Device, time, coordinates, result |
| Indoor work area | Assess capture feasibility | Whether a usable fix is available |
| Nearby unrelated premises | Should not qualify for the intended boundary | Distance and observed result |
| Adjacent company site | Assignment must be clear | Assigned site and resulting attribution |
If legitimate workers are rejected, check coordinates, assignment, permissions and location quality. Widening the circle may hide an incorrect pin or admit an unintended area.
Know the failure policy
A system can block a punch, accept and flag it, or record a rejected attempt for later review. Those are separate design choices. Do not assume a block necessarily means a server retained every rejected input.
Attendify rejects submissions outside a required geofence. The mobile capture flow also checks the assigned site. A terminal sync rejection removes that queued capture and selfie from the phone; the worker needs a supervisor route if genuine attendance is missing.
Treat overlapping sites as an assignment problem
Suppose two site circles overlap near a shared car park. Coordinates alone do not tell you which job the worker was assigned to or whether they moved during the day. Confirm the intended assignment and agree who updates it when the working plan changes.
The server evaluates reported coordinates; it does not authenticate a device’s physical position. Pair location with appropriate evidence and review, without promising that a boundary eliminates spoofing.
Keep a setup record
Save the purpose of the boundary, test results, chosen radius, responsible administrator and review date. Recheck after an entrance moves or repeated failures appear. Use a documented fallback rather than assuming every missing record is an absence.
See GPS attendance behavior and new-site onboarding for the surrounding workflow.