# Location-aware attendance control has been improved

- Canonical: https://qrgate.az/en/whats-new/location-aware-attendance-control
- Markdown: https://qrgate.az/en/whats-new/location-aware-attendance-control.md
- Language: en
- Date: 2026-06-05

Location context can be considered alongside attendance records for more reliable and transparent attendance control. The update does not change the record itself - it strengthens the *context* around it.

## What changed

In QRGate, location data can be used as additional context within the attendance process. In the relevant scenarios a record now carries not only the question of "when" but also, where applicable, "where".

The purpose is straightforward: to give more to work with when assessing a check-in or check-out. That matters most for companies operating several sites or running teams that work away from a fixed location.

For security reasons, how location is verified - radii, the order of checks and protective mechanisms - is not disclosed in public content.

## What it gives you

The practical benefit shows in three places.

First, **transparency**. When the context of a record is clear, the month-end question "where did this record come from?" stops appearing, and the follow-up correspondence around it drops away.

Second, **field teams**. Because records from staff moving between sites arrive with context, their attendance sits meaningfully in the same report as the office team's.

Third, **trust**. When something is disputed, the discussion rests on the record rather than on recollection - which serves both sides.

## What it does not change

Location context does not replace the record and does not make decisions on its own. It gives HR and managers more to work with; drawing the conclusion remains a human task.

Nor does the update change attendance rules. The lateness threshold, the time-off process and schedule logic still follow the company's own configuration.

## Explaining it to the team

Location is a sensitive subject, and explanation is part of any rollout. In practice three things told in advance are enough: in which situations the data is considered, who can see it, and what it will not be used for.

With those three explanations, resistance rarely appears. Without them, the team fills the gap itself - usually with the worst assumption.

## How it relates to QR check-in

Location context does not replace the QR-based check-in process; it complements it. QR describes how the record was created, while location describes the circumstances in which it was created.

We cover the general logic of QR-based attendance on the [QR code employee attendance system](https://qrgate.az/en/qr-code-employee-attendance-system) page, and the day-to-day tracking side on the [tracking attendance with QR codes](https://qrgate.az/en/tracking-attendance-with-qr-codes) page.

## Questions about security

The most common question here is how dependable the system is. Part of the answer is open: the richer the context around a record, the more accurately it can be assessed.

The other part is deliberately withheld - publishing internal verification rules reduces their value. We explain the general approach on the [is a QR check-in system secure](https://qrgate.az/en/is-qr-check-in-system-secure) page.

## Who benefits most

The update is felt most in three situations: companies with several sites, teams working at customer locations, and services where the point of work is not fixed.

For a team working in one office through a single entrance, the difference is smaller.

[See what QRGate can do](https://qrgate.az/en/advantages) or [calculate the price](https://qrgate.az/en).

## FAQ

### Does QRGate use location data?

Yes. In the relevant check-in scenarios, location data can be taken into account as additional context.

### What exactly are the GPS validation rules?

For security reasons the internal validation and location rules are not disclosed in public content.

### What is location control for?

It makes an attendance record easier to assess reliably and in context.

### What changes for field teams?

Records from teams moving between sites arrive with clearer context, so fewer clarifications are needed at month-end.

## Related pages

- Tracking attendance with QR - [Markdown](https://qrgate.az/en/tracking-attendance-with-qr-codes.md) | [HTML](https://qrgate.az/en/tracking-attendance-with-qr-codes)
- QR system security - [Markdown](https://qrgate.az/en/is-qr-check-in-system-secure.md) | [HTML](https://qrgate.az/en/is-qr-check-in-system-secure)
- QR attendance system - [Markdown](https://qrgate.az/en/qr-code-employee-attendance-system.md) | [HTML](https://qrgate.az/en/qr-code-employee-attendance-system)
- Time recording mistakes - [Markdown](https://qrgate.az/en/working-time-recording-mistakes.md) | [HTML](https://qrgate.az/en/working-time-recording-mistakes)
- Employee check-in system - [Markdown](https://qrgate.az/en/employee-check-in-check-out-system.md) | [HTML](https://qrgate.az/en/employee-check-in-check-out-system)
- Tracking lateness - [Markdown](https://qrgate.az/en/tracking-employee-lateness-automatically.md) | [HTML](https://qrgate.az/en/tracking-employee-lateness-automatically)