> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/modules/time-and-attendance/reports/geolocation-clocks.md).
# Geolocation Clocks
Map-based view to visually verify the physical location of employee clocks
The Geolocation Clocks report provides a map-based view to visually verify the physical location of employee clocks for a selected day. This feature displays data from clocking methods that capture GPS coordinates, such as WhatsApp Clocking.
The report defaults to showing all clock locations for the current day.
1. **Navigate to the Report**: To access the map view, navigate to [**Reports / Geolocation Clocks**](/modules/time-and-attendance/reports/geolocation-clocks.md) in the main menu.
2. **Select a Date**: Use the date selector to view clocking data for a specific day. You can only view one day at a time.
3. **Filter by Employee:** Use the filter to search for and select one or more employees. The map will update to display clocks only for the selected individuals.
4. **View Clock Details**: Click on any pin on the map to open a pop-up with additional information about the clocking event.
* Clock-in events are represented by green pins, and clock-out events are represented by blue pins.
* The pop-up displays the employee's name, team, the exact time of the clock, and any associated activity.
* Click **View Timeline** to open the employee's daily timeline, where you can make changes or add overrides to their clocks.
{% hint style="info" %}
**Which map to use.** This report covers **every employee across a whole day** — use it to check your operation as a whole, or to find the clock that looks out of place. The [employee timeline](/modules/time-and-attendance/reports/employee-overview.md#capture-locations) has a map of its own covering **one employee's day**, shown next to the records those positions came from — use that once you know whose day you are investigating.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.allwage.com/modules/time-and-attendance/reports/geolocation-clocks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
