Time attendance
Facial Recognition Time Clock: What Employers Should Check Before Employees Push Back
Before you install a facial recognition time clock, check where face data is stored, what each punch saves, how leavers are removed, and why staff object.

Before you choose
Key takeaways.
- Most recognition failures start with a poor enrollment photo or a badly placed device, not with the algorithm.
- Know where the face library lives (on the device or in a cloud service) and what each punch saves.
- Removing a leaver means deleting them in the platform and on every terminal where they were enrolled.
- Offer an alternative credential for employees who object, and check the law where you operate. In Illinois, BIPA sets consent, retention and destruction requirements.
Overview
A facial recognition time clock records attendance by matching an employee's face against an enrolled photo, which removes shared PINs and borrowed cards. Before you buy one, check three things: will it recognize your people reliably (enrollment and mounting), is it clear where face data and punch records are stored, and can you delete a leaver's data completely. Those three questions also cover most of the complaints employees raise.
Why do companies switch to facial recognition time clocks?
A face cannot be lent like a card or PIN, there is nothing to carry, and clocking in is quick.
The usual reasons are practical. A face cannot be lent to a colleague the way a card or PIN can, so "buddy punching" gets harder. There is nothing to touch or carry. And clocking in is quick. Employees who use these systems often notice the speed. In an r/CVS discussion about a face scan for credentials, u/elite_owo wrote: "It's a little dystopian but it saves a lot of time."
That comment captures both sides. The convenience is real, and so is the discomfort. A good rollout plans for both.
Why does face clock-in fail, and how do you prevent it?
Most failures start with a poor enrollment photo or a badly placed device, not with the algorithm.
Enrollment photo quality. The most common cause of "it doesn't recognize me" is the enrollment image. On a student forum, u/thekeys05 explained repeated failures: "the image you give at the time of id card was not up to the stranded" (standard).
The FCV5005 user manual sets out its enrollment photo requirements:
Feocey's product FAQ adds that file size and image dimensions can vary by software and model, so confirm the current import requirements before preparing a large batch. Take enrollment photos on site, in even light, rather than reusing old ID photos.
Height, angle and lighting at the mounting point. Placement matters as much as the photo. On the same r/CVS thread, u/thejacketmoves said they were "constantly having to move the camera because I'm short." Mount the terminal at a height that suits your workforce and test it with your shortest and tallest staff.
Check the working distance too. The FCV5000, a 5-inch terminal for access and attendance, lists a recognition distance of 0.3–1.5 m (about 1–5 ft). The FCV5005 manual's installation notes ask you to avoid backlight, direct sunlight and sunlight through windows. In practice, do not point the camera at a bright window or glass door. Test the spot at different times of day before you fix the mount.
- JPG format, 50–300 KB
- Width 512–800 pixels, height 640–1024 pixels
- Face size between 80 and 512 pixels
- A natural photo with no beauty filters, heavy makeup, sunglasses, scarves or masks
Where does the face data live?
Ask every vendor; on the FCV5005, faces are verified locally and the face database is stored on the device.
Ask every vendor this question directly. On the FCV5005, according to its user manual, face recognition is verified locally and the face database is stored on the device. It supports up to 50,000 faces and 50,000 records. With the standard access application, faces can still be recognized when the network is down, and records are uploaded again after the network returns.
Local storage has trade-offs. Punches keep working through an outage, and face data does not have to leave the building for matching. On the other hand, the data now sits on every terminal, so removal and device security need to be planned for each one.
What does the clock save on every punch?
By default the FCV5005 saves a face image with each punch, but no panoramic image and no stranger record.
Many buyers never check this, but it matters for privacy and storage. The FCV5005 manual lists these save settings for a face punch:
These can be adjusted for your deployment. Decide what you actually need for payroll disputes and security, set it on purpose, and write it into your retention policy.
| Setting | Default | What it means |
|---|---|---|
| Panoramic image | Not saved | Whether a wide image is saved with each punch |
| Face image | Saved | A face photo is saved with each punch, with higher priority than the panoramic image |
| Stranger record | Not saved | Whether attempts by unenrolled people are recorded |
How do you remove a leaver's face and credentials?
Delete the leaver from the back-end platform and from the device itself.
This is where systems that store data locally need care. For the FCV5005, Feocey's FAQ says a leaver's permission can be deleted from the back-end platform and from the device itself. Because recognition and the whitelist are stored on the terminal, the person must be removed on every FCV5005 where they were enrolled. A whitelist entry with an end time also stops working when that time passes, which is useful for temporary staff.
Make removal part of your HR offboarding checklist, and check the result on each device rather than assuming a platform change reached them all.
How should you handle employee pushback on face scans?
Address consent openly and offer an alternative credential to employees who opt out.
Some employees will object, and some objections are strong. A widely upvoted r/privacy post titled "Job wants ID scan and periodic face scans" shows how strongly some people feel about it. On X, one user wrote about a building that "always requires me to sign in via facial recognition & ID. I always refuse…"
Practical steps:
- Explain in writing what is collected, why, where it is stored and how long it is kept.
- Get written consent where the law requires it, and keep it on file.
- Offer an alternative. The FCV4907, an 8-inch terminal for staff access and attendance, supports face, fingerprint, card and password, depending on the application, so one device can serve people who opt out of face.
- Avoid using clock-in images for anything beyond what you told employees.
What does the law say? (US snapshot, November 2026)
This section summarizes the cited sources only. It is not legal advice; talk to a lawyer about your situation.
Illinois (BIPA). According to Employment Law Worldview (June 18, 2026), the Illinois Biometric Information Privacy Act requires written informed consent and a signed release, prohibits selling or profiting from biometric data, and requires a publicly available written retention and destruction policy. Individuals may recover up to $1,000 per negligent violation and up to $5,000 per intentional or reckless violation. An amendment effective August 2, 2024 (SB 2979) limited damages to accrue per person rather than per violation. On April 1, 2026, the Seventh Circuit decided in Clay v. Union Pacific that the amendment is remedial and procedural, so it applies retroactively to cases pending on August 2, 2024. The article notes that even per-person damages can be substantial in aggregate.
New York City. Int 0428-2026 would make it unlawful for an owner of a multiple dwelling to install, activate or use biometric recognition technology that identifies tenants or their guests. Its status is "Laid Over in Committee" (Committee on Technology). It has not passed.
New York State. S8223 and its Assembly version A6363 would prohibit landlords from using a facial recognition system on residential premises. As of the latest actions (January 7, 2026), S8223 is in the Senate Judiciary Committee and A6363 is in the Assembly Housing Committee. Neither has passed.
Both New York proposals concern residential buildings, not workplaces. They are listed here because buyers in New York often ask about them.
Standalone clock or connected platform: which fits?
Choose by how punches reach payroll: export from a standalone device, or connect terminals to a platform.
A time clock is only useful if its punches reach payroll. Some sites export records from a standalone device; others connect terminals to a platform. With the standard access application, Feocey provides the full MQTT protocol documentation for the FCV5005, covering event reporting, remote permission push and face enrollment, so a platform can receive punches and manage enrollments. For the hand-off from punches to HR and payroll, see biometric time attendance software: the HR handover and staff attendance software and shift changes.
What should a facial recognition time clock buyer's checklist cover?
Cover enrollment, placement, data storage, punch records, leaver removal, alternatives, payroll and offline behavior.
Our guide on how to choose face recognition devices covers door-access use. To compare attendance terminals, see our face terminals range, including the FC6826 access and attendance terminal . When you are ready, tell us your headcount, sites and how punches should reach payroll.
| Question | Why it matters |
|---|---|
| What are the enrollment photo requirements? | Bad photos cause most failures |
| What recognition distance and mounting height suit our staff? | Placement causes many of the others |
| Where is the face library stored? | Outage behavior, privacy and removal |
| What is saved with each punch, and what are the defaults? | Privacy and retention policy |
| How is a leaver removed from the platform and every device? | Complete deletion |
| What alternative credentials are supported? | Employees who opt out |
| How do punches reach payroll (export or MQTT)? | Integration effort |
| What happens to punches when the network is down? | Depends on model and configuration; test it |
How accurate are facial recognition time clocks?
It depends on enrollment photo quality, lighting at the mounting point and the size of the face library. Ask the vendor what test conditions sit behind any accuracy figure, and test with your own staff where the clock will be mounted.
Why doesn't the time clock recognize some employees?
Usually because of a poor enrollment photo, a mounting height that doesn't suit them, or backlight from a window. Re-enroll with a clear, front-facing photo and test the mounting position.
Where is the face data stored on a facial recognition time clock?
It varies by product. On the FCV5005, the face database is stored and matched locally on the device.
How do you delete a former employee's face from the clock?
Delete them in the back-end platform and on every terminal where they were enrolled, then check each device. On the FCV5005, whitelist entries with an end time also expire automatically.
Is a facial recognition time clock legal in Illinois?
BIPA regulates it. According to Employment Law Worldview, BIPA requires written informed consent, a public retention and destruction policy, and no selling of biometric data. This is not legal advice.
What if an employee refuses to use face recognition?
Offer an alternative credential such as a card, PIN or fingerprint where the terminal supports it, and record the choice.
Source references
wrote ↗explained ↗"Job wants ID scan and periodic face scans" ↗wrote ↗Employment Law Worldview (June 18, 2026) ↗Int 0428-2026 ↗S8223 ↗A6363 ↗Put the guide to work
Find the reference for your model.
Compare each device with your requirements. Confirm configuration and compatibility for the complete installation.
FCV5005 →
8-inch face authentication terminal
Ask about FCV5005 ↗FCV5000 →
Access and attendance terminal
Ask about FCV5000 ↗FCV4907 →
Face authentication terminal
Ask about FCV4907 ↗FC6826 →
Access and attendance terminal
Ask about FC6826 ↗