The company has turnstiles, every entry is logged, so the attendance problem must be solved. The conclusion sounds logical and is usually wrong. A turnstile and attendance system do two different jobs: one decides who may enter the building, the other calculates how much each person worked. Those functions do not overlap, and using one in place of the other produces unexpected work at month-end.
What a turnstile is actually for
A turnstile exists for physical access control. Its purpose is simple: keep out anyone without permission.
For that purpose it is an excellent instrument. It does three things well: it physically restricts entry, it logs each pass, and it gives security real-time information.
Note that none of those three answers the question "how many hours did this person work today?" A turnstile knows about passages, not about working time.
What an attendance system is for
An attendance system answers a different question: what is the gap between expected and actual time?
To do that it needs at least four things: the work schedule, leave and time-off records, a working calendar, and a correction process.
A turnstile holds none of the four - and should not, because that is not its job. We explain the general logic on the what is an employee attendance system page.
An entry log is not a schedule
The turnstile log contains "08:52 entry". What does that record tell you? One thing only: that person walked into the building.
An attendance decision needs three more pieces of information: what time their shift started that day, whether it was a working day for them at all, and whether they left and returned during the day.
| Question | Can a turnstile answer it? |
|---|---|
| Who entered the building | Yes |
| When they entered | Yes |
| Were they late | Only if a schedule exists |
| Were they on leave | No |
| Was it a working day | No |
| How long they worked | Indirectly and incompletely |
Being in the building is not the same as working
The weakest point of turnstile data is that it measures time on the premises, not working time.
Three situations make that gap serious. An employee who stays in the building over lunch appears to have worked continuously. Someone arriving early and waiting appears to have started early. And a person who works on site and then returns to the office has most of their actual working time recorded nowhere.
Those three distort the month-end report systematically, in both directions.
The leave and time-off gap
This creates more manual work than anything else. If there is no turnstile record, that can mean six different things: annual leave, approved time off, sickness, a business trip, a rostered rest day, or a genuine absence.
A turnstile cannot separate them, because leave does not exist in its data model. So at month-end HR checks every empty line by hand and fills it in from other sources.
That step - reconciling the access log with HR records - is the longest month-end task in many companies.
Field and remote workers
The turnstile model rests on one assumption: every employee comes to the same building every day. That assumption is becoming less true.
Sales representatives, installation crews, couriers and hybrid workers never pass a turnstile. Which means part of the company sits outside the attendance system entirely.
In practice a dual structure forms: the office team is managed through the turnstile and everyone else through spreadsheets or chat. At month-end the two sources are merged by hand.
What a turnstile genuinely gives you
None of this makes turnstiles unnecessary. They have one strength and it is irreplaceable: physical control.
An attendance system cannot physically stop someone from entering a building. A turnstile can. In facilities with security requirements nothing substitutes for it.
The right question is not "which is better?" but "which system does which job?"
Running both together
The most practical model keeps the turnstile for access control and an attendance system for working-time records. Three conditions then matter:
- Turnstile records must be able to flow into the attendance system, or the other way round.
- Schedules, leave and time off belong on the attendance side.
- Field teams need their own recording method, and reporting must stay unified.
The third condition is broken most often, and it is exactly what creates the month-end workload.
When a turnstile alone is enough
One case works: the entire team is in one building on one fixed schedule, leave and time off are properly maintained elsewhere, and reporting requirements stay simple.
In practice those conditions hold in a single 20 to 30-person office. Add a branch, a shift pattern or field work and the model starts to crack.
A practical example
A 90-person company in a two-storey office ran attendance from the turnstile log for five years. It worked, because everybody was on the same schedule.
Opening an installation service changed that: a new 14-person team spent the day at customer sites and never passed a turnstile. For three months their attendance was managed through chat.
Merging the two sources at month-end began consuming two days of HR time. The company kept the turnstiles - they were needed for access control - but moved working-time recording into a separate system and brought both teams into one report. We compare the QR approach with turnstiles on the QR attendance or turnstile page.
How to assess your situation
Four questions clarify it: what share of the team comes to the same building daily; where are leave and time off recorded; how many schedule types exist; how many hours does reconciling the access log take at month-end?
If the last number exceeds an hour, the turnstile is already trying to do an attendance system's job. We wrote about running schedules and attendance together on the managing schedules and attendance together page.
Next step
Open last month's access log and check one week: for how many lines did you need information from another source?
QRGate keeps working-time records with schedule, leave and time-off context, so office and field teams appear in the same report. See what QRGate can do or calculate the price.
