Employee entry and exit report¶
For each employee and each day, this report finds the first entry, the last exit and the worked hours, using access control events (readers, turnstiles, doors). It compares those hours with the expected workday and shows the completion percentage. The result can be exported to CSV for payroll or HR.
Before you start¶
- You need access to the Reports and Metrics menu (
dashboard:canUseDashboardpermission). - Employees must be registered as people in Netsocs, and access events must arrive linked to that person (for example, when they badge in or are recognized by face).
- Know which objects mark an entry (for example, the entry reader on the main turnstile) and which mark an exit.
TIP Ideally, use separate readers for entering and leaving. If one door logs both entry and exit with the same reader, the report cannot tell them apart.
Step 1: Open the report¶
In the sidebar, open Reports and Metrics → Employee Entry & Exit (route /reports/employee-entry-exit).
Step 2: Pick the date range¶
In Date Range, pick the first and last day. The default is yesterday to today. The report produces one row per employee per day in the range.
Step 3: Set the expected workday¶
In Expected Work Hours, enter the normal length of a workday, in hours. The default is 8. It is used to calculate the Average column.
Step 4: Pick the employees¶
- Click Add employee.
- In the people table, tick the employees to include.
- Confirm. The button shows how many you picked.
Step 5: Pick the entry and exit objects¶
- Click Add entry object and tick the readers or doors that count as an entry. The table shows ID, name, domain, type and device ID to help you identify them.
- Click Add exit object and tick the ones that count as an exit.
NOTE The Entry/Exit events field (Add event) does not affect the calculation yet: the report uses any event of the person on the chosen entry and exit objects. What decides entry versus exit is the objects.
Step 6: Read the result¶
The report recalculates by itself whenever you change a parameter. Your setup is stored in the browser, so next time it opens with the same employees and objects.
| Column | Contents |
|---|---|
| Employee ID | The person's identifier. |
| Employee Name | Full name. |
| Lists | Lists the person belongs to. |
| Report Date | The day the row refers to. |
| Entry Date Time | First event of the day on an entry object. |
| Exit Date Time | Last event of the day on an exit object. |
| All Entries / All Exits | Every mark of the day; open Show all entries to see them. |
| Worked Hours | Time between the first entry and the last exit, in decimal hours (for example, 8.2500 = 8 h 15 min). |
| Average | Worked hours ÷ expected hours × 100. |
The Average color helps you spot cases to review:
| Color | Meaning |
|---|---|
| Green | Over 95% of the workday. Bold when above 100% (overtime). |
| Yellow | Between 80% and 95%. |
| Red | 80% or less (short day, or a missing entry or exit mark). |
Example: 8 h expected workday. Ana enters at 08:02 and leaves at 17:10 → Worked Hours 9.1333, Average 114% (green, bold).
Step 7: Export¶
Click Export to CSV. employee-entry-exit.csv downloads with one row per employee per day. See the columns in Export data.
Things to keep in mind¶
- Days are split in UTC. Each day runs from 00:00 to 23:59 UTC. If your site is far from UTC (for example, UTC-5) and some shifts cross that hour, a workday can be split across two days. Check those cases with All Entries / All Exits.
- Night shifts: a shift that starts one day and ends the next is not merged into a single row.
- If a day is missing its entry or its exit, worked hours cannot be calculated for that day.
- There is no paging: with many employees and a long range, the table can get long. Export to CSV to work with it.
- To automate the calculation (for example, email it every week), use the Get worked hours node in an automation with a schedule trigger.