The daily report
The question at nine in the morning — who is in, who is not yet, who was late — and the same question about any day of the last month. One row a person a day, with the times they actually clocked in and out, where each punch came from, and how many minutes late or early.
A day with two stretches stays one row. The times, the minutes and the status are split inside the row, one line for the morning and one for the afternoon, so each stretch reads straight across.
Before you start
- The
attendance.viewpermission, the same one the monthly grid needs. You see the people your role reaches: a manager over one unit sees that unit. - People exempt from attendance are not listed: they have nothing to clock in for.
Steps
- Open Daily report. It opens on today, in the company's own time zone.
- Choose the days in From and To, up to 31 days, or press Today or Yesterday.
- Narrow it if you need to: a branch, a unit (with every unit beneath it), or one person — type part of their name or their staff number.
- Press one or more status labels above the table to keep only the rows that show them. All clears them again.
- Click a column heading to order the table by staff number, name, date, or minutes late or early. Click a name to open that person's day in full.
- Press Export to Excel to download what the table is showing.
What you should see
The status labels above the table come in groups: arriving (Not in yet, Late in), leaving (Not out yet, Out early), and how the day came out (the rest). Each shows how many rows carry it, counted after the branch, unit and person filters.
Each stretch shows one of these:
| Status | Meaning |
|---|---|
| Not in yet | Rostered, the stretch is not over, and no check-in yet. |
| Late in | Clocked in after the start and its grace minutes. |
| Not out yet | Clocked in, not yet out, and the stretch is not over. |
| Out early | Clocked out before the end and its grace minutes. |
| Complete | Both punches, neither late nor early. |
| Miss scan | One punch of the two, once the stretch is over. A correction request fixes it; Add punch beside it files one from here. |
| Absent | No punch at all, once the stretch is over. |
| Leave | Approved leave, with its leave type. |
| Public holiday | A public holiday of the person's branch, with its name. |
| Day off | A rest day of the branch week, a day with no shift, or a day of a suspension. |
A later stretch that has not begun yet — the afternoon, at ten in the morning — shows Not started yet and no status. A whole day is Complete only when every stretch in it is.
Today is read as it stands. Somebody rostered who has not punched has nothing recorded yet, and is still listed as Not in yet rather than missing from the list. A stretch only becomes absent or a missing punch once it has ended. A night shift belongs to the day it starts, so last night's shift is on yesterday's row, on shift until it ends in the morning. Days that are over read exactly what the monthly grid shows. The page does not refresh by itself; press the refresh button beside the export.
Nobody is listed before their first day of attendance or after their last day worked, and days after today are not listed.
Adding a punch somebody missed
A stretch marked Miss scan has Add punch beside it, for anyone who may file requests on behalf of others. It opens a small form on the report: the person, the day and the stretch, one time for each punch that is missing — offered at the stretch's scheduled time, change it to when they actually arrived or left — and a note. Sending it files a miss scan in that person's name, exactly as the on-behalf page would, and it goes to the same approver. Nothing on the report changes until that request is approved: a punch is never written by hand, so the correction always has a request behind it and somebody who approved it.
If you may also decide requests in an approver's place (request.override), the punch goes straight in instead. The note becomes Reason and is required, and the button reads Add the punch. The miss scan is filed and approved by you in one step, so no approver is asked, the day is recalculated at once and the report shows it. Any annual leave already taken for that missing punch goes back. The person is told in Telegram, as for any approval, and the activity log records who added it and why. The on-behalf page still sends a miss scan to the approver.
Either way, if the day's period is already locked, or a miss scan for that day is already waiting, the form says so and saves nothing.
Taking the data away
Export to Excel downloads an Excel file of exactly the rows the filters leave, status labels included, for the people your role reaches. It has one line a person, a day and a stretch, so it filters and totals without split cells: date, weekday, staff number, name, branch, unit, shift, stretch, the shift's start and end, the times clocked in and out with where each came from, minutes late and early, the status, and the leave type or public holiday when there is one. A day off or a holiday is one line with no stretch. The headings are in your language, every heading has a filter and the first row stays put. Each export is written to the activity log.
If something goes wrong
Somebody is not listed. They are exempt from attendance, outside the branch, unit or person chosen, outside what your role can see, or they had not started yet or had already left on that day.
Everybody is "not in yet" before the shift starts. That is the first stretch of the day: until somebody clocks in, they have not. It changes as people arrive.
A stretch says absent but the person was there. Their punch may have fallen outside the hours the stretch accepts, or the wrong shift was assigned to that day. Open their day from the name to see the punches as recorded. A correction request fixes a missed punch.
Everybody at one branch is absent on the same day. That day is probably a public holiday nobody has declared yet. Adding it recalculates the day.
Last checked 04/11/2026