Attendance

How each day's status is worked out from punches and the roster, how to fix a day, and how a month is closed.

Attendance turns punches into a status for every person and day: present, late, half day, absent, on leave or on a weekly off. It compares each punch with the person’s shift for that day, so a day recalculates on its own when the roster or a request changes it. At month end HR locks the month and downloads the export for payroll.

How punches come in

The capture policy (Setup › Policies › Capture, under How time is captured) sets which ways each person may punch:

Mobile punch with GPS: staff punch in and out from the staff app on their phone, with their location.
Biometric device: staff scan their face, finger or card on an eSSL or ZKTeco device at the outlet, and the device sends the punch to Maska. Punches reach attendance within about 5 minutes, and Maska decides IN or OUT from the person’s last punch. Set up the device, and match each person’s attendance number to their User ID on it, as described in Biometric devices.
Manual entry by a manager: a manager adds a missing punch by hand for someone in their team.
Web clock-in from the HR console: people clock in and out from the HR console in a browser, with their location. Off by default.

HR can also bring in punches from another system or a paper register through Setup › Data import › Attendance punches.

Every punch, whatever its source, goes through the same rules, and the day log shows where each one came from.

Fixing a day: the 48-hour window

When the system first flags a day (a missing punch, a late or early out, a short or half day, an absence, or overtime), the person’s reporting manager or a department manager has 48 hours to fix it. Staff cannot fix their own days.

Managers work the To fix tab under Attendance, or Attendance to fix under My team in the staff app. Items are grouped by deadline and fixed directly, with no approval step: add or move a punch, let off a late or short day, record that an absent person did work, or approve, trim or reject overtime.
A reminder goes to the managers 24 hours after the flag.
When the window closes, the day freezes with its policy outcome and the managers are told. Overtime nobody decided is not paid. Only HR can change a frozen day, from the Frozen tab, with a reason of at least 12 characters.
At month end, a day still in its window blocks the lock. HR can wait for the window or use Freeze now on the lock screen.
Staff see each day’s status on Home: waiting on the manager (with the deadline), fixed and by whom, frozen, or overtime not paid.

The Time dashboard

Time › Dashboard shows what needs you, scoped to what you manage:

Open exceptions by deadline come first: overdue, due within 24 hours, and later, with the earliest few by name. Each opens your To fix queue. HR also sees the count across the organisation and the frozen days only HR can change.
Waiting on your approval: the requests in your Approvals inbox, by kind.
Unpublished boards: next week’s roster boards you publish that are not out yet. A department manager sees only their own boards.
Today (present, late, missing punch, absent, on leave, not in yet) and Late, last 7 days give the context.

If one part cannot load, only that part shows an error; the rest still work.

Coming Soon

A full guide to the day view, the month muster, regularisation, overtime and month close is being written.