Employee clock-in system for attendance management
An employee clock-in system records when each person starts and ends the working day. Attendance management turns those punches into figures a manager can act on. PeopleMuster gives your team two ways to clock in: a fingerprint terminal, or the browser inside their shift window. Either way you see who came in, who was late, and by how many minutes.
The first path is a ZKTeco fingerprint terminal on your local network. PeopleMuster connects to it by its IP address and pulls new punches every 30 minutes on weekdays, with nothing installed on the device. Each punch is matched to a system user. Fingerprints stay on the terminal: PeopleMuster receives only who punched and when. A header on the page says how long ago the last sync ran, so nobody argues with a stale screen.
The second path needs no hardware. An admin switches on browser check-in. A card on the employee dashboard then lets a person check in and check out. It opens inside a window around their assigned shift, and the admin sets all four edges of that window. Miss it, and the card routes the person to a punch request for HR to review.
Both paths write the same record: check-in, check-out, hours worked and late minutes for that day. Use one, or run both side by side.
Late minutes are the number people care about, and they are measured against the shift that person is assigned. Somebody on the midday shift is not marked late at 10:05. That single detail removes most of the monthly disputes.
Days sort into present, absent, partial and leave. A partial day is its own state, not a rounding error. Admins filter by department, period, status, leave type and hours range, and can pull only the late arrivals when that is the question.
When the device misses a punch, the person files a manual punch request instead of emailing HR. The request sits in a queue with the rest, and the correction is visible on the record afterwards.
On the terminal path, getting started is mostly enrolment. Each person is registered on the device, then linked to their account through a mapping screen. That screen counts the people still unmapped, so you always know who is left to enrol. Once the list reads zero, you rarely need to open it again.
Above the daily table sit the period figures: total records, check-ins with an attendance rate, the on-time rate with its late count, and average working hours against how many hours the period fell short. A working-hours histogram sits beside them. Reading those five things takes a minute and usually answers whatever prompted the visit.
For offices that feed people, lunch and dinner counts appear on the same card. Odd on an HR screen until you have tried to reconcile a canteen bill from a spreadsheet, at which point it stops being odd.
What it does
- On-time rate
- One percentage per period, with the late-arrival count beside it. Managers look at this before they look at anything else.
- Late minutes per record
- A column on the daily table, not a flag. Six minutes and sixty minutes are different problems.
- Browser check-in
- A dashboard card for check-in and check-out, open inside each person's shift window. An admin switches it on and sets the window.
- Manual punch requests
- A tab of its own for missed and mistimed punches, so corrections leave a trail instead of a chat message.
- Meal counts
- Lunch and dinner tallies sit on the same card as the attendance figures, for offices that feed people on site.
- CSV export
- Any filtered view exports. Sort out the awkward month in a spreadsheet if you prefer.
What it needs before it works
- A check-in path. Either a ZKTeco terminal reachable by IP address on your local network, or browser check-in switched on by an admin.
- For the terminal, each employee enrolled on the device and mapped to their account. The mapping screen counts anyone still unmapped.
- Shifts set up first. Late minutes measure against them, and the browser check-in window opens around them.
- A holiday calendar, so a public holiday does not read as a floor of absences.
Questions people ask
How does an employee clock-in system work in PeopleMuster?
People clock in at a ZKTeco fingerprint terminal or on a check-in card in the browser. Terminal punches sync every 30 minutes on weekdays. Both paths write the same record: check-in, check-out, hours worked and late minutes for the day.
Which attendance device does PeopleMuster work with?
ZKTeco fingerprint terminals, set up by the device's IP address on your local network. Fingerprints stay on the terminal; PeopleMuster receives only who punched and when.
Can people check in without a terminal?
Yes, once an admin switches on browser check-in. A card on the dashboard opens inside a window around the person's assigned shift. The admin sets how early it opens and how late it closes.
What happens when the device misses a punch?
The employee raises a manual punch request. It queues alongside the other requests on the attendance screen, and the approved correction shows on the day's record.
Does a later shift count as late?
No. Lateness is measured against that person's assigned shift, so a later start time is simply a later start time. The report flags a punch that comes after the window they were given.
What does a partial day mean on the record?
A day with a punch but not a full pattern, such as a missing check-out or short hours. Partial is a status of its own, kept separate from present and from absent, so half-days do not quietly round either way.
Who can see other people's attendance?
Whatever the role model allows. Marking your own attendance is part of the baseline everyone has, while reading the whole company's records is a permission an administrator grants.