Mobile & Location Settings
Overview
Depending on the way you plan to track punches for your workforce, supports 4 different methods for tracking punch details. Consider the following points with regard to tracking punch locations along with punches.
- Is the client/agency concerned with reviewing the locations of punches?
- Is the client/agency interested in restricting punches if they are not performed at the authorized work location?
- Is the client/agency interested in restricting punches if they do not include a punch location?
- Is the workforce mobile or is it centralized?
Mobile & Location Services Settings
There are four settings allowed for punches with regard to Location Services:
Geo Location Not Requried
With this configuration, mobile devices are not required to share Location Services. Punches will be captured and sent to with or without location data, and employees will not see any warnings about Location Services while using the app. This setting may be good if a workforce is mostly mobile or not tied to a central location and managers are not concerned with tracking punch locations.
- Agency is not concerned with reviewing punch locations.
- Agency is not interested in restricting punches.
- Workforce may be either mobile or centralized.
Geofence Warning
This configuration will prompt employees with a warning that their punch locations are outside of the Authorized Distance. Employees may bypass this warning to record a punch. This setting may be good if a workforce is partially mobile, but most work will occur at a centralized location. Employees do not have to enable location services on their mobile devices, but a Geo-fence is defined.
Read more about this in Location Services.
- Agency wants to review punch locations.
- Agency is not interested in restricting punches.
- Workforce may be either mobile or centralized.
Geo Location Required
In this configuration, Mobile will restrict any punch on a device where Location Services are disabled. This means that for punches where a location cannot be determined, Mobile will not allow punches and will inform the user they can not punch in or out. This setting is ideal for a largely mobile workforce where management prefers to track the specific location of punches. Punches will not be restricted based on location.
See more about this in Location Services
- Agency wants to review punch locations.
- Agency wants to restrict punches only if punch locations are not shared.
- Workforce is mobile or not centralized.
Geo-fence Required
With this setup, Mobile punches are compared to the location at which they are created. If the location of the punch is outside of the Geo-fence, Mobile will inform the employee that the punch is from an unauthorized location and not allow the employee to punch. All punches must be created from within the Geo-fence. This configuration is ideal for a workforce that works at a central location with no chance of employees creating punches from outside of the work location. Location Services must be enabled on employee mobile devices.
Learn more about this in Location Services.
- Agency wants to review punch locations.
- Agency wants to restrict punches to an approved location only.
- Workforce is centralized and not mobile.
Geo-location may not be fully accurate within large buildings. Customers should test that phones can accurately identify their location within the site prior to turning on geo-fencing. Not testing prior to turning on this setting can risk users not being able to clock in while actually on site. Accuracy is based on the location services provided by the mobile phone and some inherent difficulties with GPS due to line of sight to satellites.