# How to run attendance without fingerprints

- Canonical: https://qrgate.az/en/attendance-without-fingerprint-scanners
- Markdown: https://qrgate.az/en/attendance-without-fingerprint-scanners.md
- Language: en

Whether you can build **attendance without fingerprints** is a question that usually comes out of a practical situation: there is no budget for hardware, the landlord will not permit installation in a rented office, sites change often, or several employees decline to give biometric data.

The answer is yes, with one condition: what makes a record reliable is not the method but the layers built around it. Each of those layers is opened up below.

## What a recording point consists of

In a hardware-free model the recording point is made of two things: a code placed on the wall, and the app on the employee's own phone.

What matters is that the point is tied to the company structure - to a branch, a department, a specific entrance. Without that link the record is just a timestamp; with it, the record later answers the question "at which site". In a company with branches, a warehouse and retail points, this is the single setup detail that decides whether the reporting is usable.

Because no installation, cabling or hardware acceptance is required, opening a new site does not create an extra budget line - the point is essentially a row in the structure.

## Binding the record to a person

This is the most frequently asked question: can someone photograph the code and send it to a colleague?

If the reliability of the record rested only on the existence of the code, that would be a real problem. In practice the record passes through several layers:

- **Device** - the device the record was made on is stored. Device history exists, so a picture builds up over time.
- **Device change** - an employee moving to another device appears as a separate event, and the relevant people can be notified of it. Two devices of the same make and model can be identified as distinct devices.
- **Location** - the record is checked against the location of the entry point.
- **Notification** - anything that does not line up reaches the responsible person, so the matter is discussed the same day rather than at month end.

The effect is that control moves out of the code itself and into the context around the record. This does not reproduce the instant confirmation a fingerprint gives, but in practice it closes the same question - whose record is this - by a different route.

## Location matching

Location adds the answer to "where". That matters in two cases in particular: in field work, where the site changes daily, and in multi-branch structures where an employee may work at several sites.

Two things should be accounted for in advance. First, dense construction, basement floors and thick walls reduce positioning accuracy - which is why location should never be built as the single deciding criterion. Second, the team needs an explanation: this is about a match at the moment of the record, not about being tracked all day. Without that explanation, even a technically sound system runs into a trust problem.

## Handling exceptions

Every company has employees without phones, or areas where phones are not allowed. That is not a weakness of the model - it is simply a case to plan for.

Two routes exist, both inside the same system:

- **An NFC point** - faster at a loading area where hands are full, or at an entrance where a queue forms.
- **A manual record** - entered by the manager, leaving a trace with its author and timestamp.

The important part: the exception has to live inside the system. An exception kept on a separate paper list or in a separate file becomes a second source at month end and pulls the record straight back into reconciliation work.

## Reporting and the timesheet

Changing the recording method does not change what is required of the reporting. The expectation stays the same: the record is compared against the work schedule, the rules on lateness, breaks and overtime are applied, and a ready timesheet comes out.

Five points are worth checking in practice:

1. Are there cuts by branch, department and section, or only one general list?
2. Is the method the record was made by stored and visible in the report?
3. Do corrections leave a trace with author, reason and original value?
4. Are leave and time-off entries in the same timesheet, or in a separate file?
5. Do the spreadsheet and PDF exports match the format accounting expects?

Check these five concretely during a demo - left unanswered, the system turns into nothing more than a store of records, whatever method it runs on.

## Setup sequence

**1.** Write the rules: lateness threshold, break rule, list of exceptions, work schedules. This is the longest stage and it is not technical.

**2.** Build the structure: branches, departments, entry points.

**3.** Trial it in one unit - not the simplest, but the one whose rules change most and whose conditions are hardest.

**4.** Run a parallel month. Old and new records side by side both expose gaps and build trust.

**5.** Switch on notifications - for one or two events at first, not all of them.

**6.** Measure after three months: hours spent on reports, rows corrected by hand, disputed records, the date the timesheet closes.

## A worked example: a rented office

A services company rented two floors in a business centre. The building had its own turnstile, but the records were not passed to tenants - they belonged to the centre's security service.

The company wanted to install a terminal at its own entrance and was refused: mounting to the wall and running cable were against the lease.

The solution lay in the recording point not being a physical device. The code was placed in a frame in the reception area and the point was registered in the structure as "head office". No installation was required and no permit was needed.

A year later the company moved to another building. The move took one day: the code was reprinted and the point's address was updated in the structure. No device was dismounted, because there was no device.

The lesson of this example: in a rented office the main constraint is not technical but contractual - and a hardware-free model does not touch that constraint at all.

## What has to be explained to the team

Three things should be stated clearly on the first day of the rollout, and all three fit on one page.

**What is recorded:** the start and end of the working day, the point the record was made at, the device the record came from.

**What is not recorded:** movement between working hours, personal locations, time outside working hours.

**What the employee sees:** their own records, their own schedule, their own lateness, their leave and time-off balance.

The third is the most often skipped and makes the biggest difference. An employee who can see their own timesheet reports a mismatch without waiting for month end - which directly reduces HR's workload.

## The next step

The practical advantage of starting without buying hardware is that the decision is reversible: if the trial does not deliver, the only thing left behind is a written document of your rules - and that is useful either way.

See how the attendance process can be built without installing a terminal in [what QRGate does](https://qrgate.az/en/advantages), or [calculate the price](https://qrgate.az/en).

### Related pages

- [Alternatives to a fingerprint system](https://qrgate.az/en/alternatives-to-fingerprint-attendance)
- [Employee attendance without hardware](https://qrgate.az/en/employee-attendance-without-hardware)
- [Is a QR check-in system secure?](https://qrgate.az/en/is-qr-check-in-system-secure)
- [Mobile attendance system](https://qrgate.az/en/mobile-attendance-system)

## FAQ

### What does a recording point consist of when there is no fingerprint reader?

A code placed on the wall and the app on the employee's own phone. The point is tied to the company structure - to a branch, a department, a specific entrance - so the record later answers the question "at which site". No installation, cabling or hardware acceptance is required, which is why opening a new site does not create an extra budget line.

### Isn't sharing the code as a photo a problem?

It would be if the reliability of the record rested only on the existence of the code. In practice the record passes through several layers: the device it came from is stored, device changes appear as separate events, and the record is matched against the location of the entry point. When something does not line up, a notification reaches the responsible person - so the case surfaces that same day, not at month end.

### What happens where phones are absent or not allowed?

Two routes exist and both sit inside the same system: a record made at an NFC point, or a record entered manually by the manager. A manual correction leaves a trace with its author and timestamp, so no part of the record stays opaque. The important thing is that the exception is held in the main timesheet, not in a separate file.

### Does this model work in production and warehouse conditions?

Conditions have to be checked point by point. Because the reading happens on the employee's own device, dirty hands, gloves or poor lighting do not stop the record - which is the most common complaint about fingerprint terminals. In exchange two conditions appear: phones must be permitted on site, and coverage must be adequate. Both should be tested before rollout.

### Is the record as accurate as with a terminal?

Accuracy is determined by the calculation layer, not by the recording method. If the system compares the record against the work schedule, applies the rules on breaks, lateness and overtime, and keeps a trace of every correction, the result is a ready timesheet. Without that layer, any method - terminal included - leaves you with nothing but a store of records.

## Related pages

- Actual working time - [Markdown](https://qrgate.az/en/determining-actual-working-time.md) | [HTML](https://qrgate.az/en/determining-actual-working-time)
- Biometric attendance - [Markdown](https://qrgate.az/en/biometric-attendance-system.md) | [HTML](https://qrgate.az/en/biometric-attendance-system)
- QR, card, biometrics - [Markdown](https://qrgate.az/en/qr-card-biometrics-comparison.md) | [HTML](https://qrgate.az/en/qr-card-biometrics-comparison)
- Check-in without turnstiles - [Markdown](https://qrgate.az/en/employee-check-in-without-turnstiles.md) | [HTML](https://qrgate.az/en/employee-check-in-without-turnstiles)
- QR or turnstile - [Markdown](https://qrgate.az/en/qr-attendance-or-turnstile.md) | [HTML](https://qrgate.az/en/qr-attendance-or-turnstile)
- Attendance system costs - [Markdown](https://qrgate.az/en/attendance-system-costs.md) | [HTML](https://qrgate.az/en/attendance-system-costs)