Schedule Management (HR)

What this guide covers

Schedule Management (Time & Attendance Configuration) is the HR control room behind attendance: the work schedules people are measured against, the public holidays calendar, the daily attendance record with manual edits, and the scan sync that feeds it all from the clocking devices.

Who can open it: it needs HR access.

The tabs

Base Schedules

The library of work-schedule templates (the shift patterns and tolerances employees are measured against). For each schedule you set the target and minimum daily hours and the clock-in / clock-out tolerance bands, and one can be the default. Use New Schedule to add one; edit or delete from the row. These are the policies; an individual's working pattern is set per employee (see Manage schedules).

Public Holidays

The holiday calendar, per country. Add a holiday with New Holiday (date, name, country); edit or delete from the row. Holidays change how a day is treated (pay and whether it's a working day), so keeping this current matters for correct attendance and pay.

Daily Attendance Monitor

The generated daily records with a manual editor. Each row shows the date, employee, status (Planned / Present / Absent), hours, and whether it's a locked manual override. HR can edit a day (correct a status or hours) and Generate Future Schedule to roll records forward. Use the editor to fix genuine anomalies — a manual override locks that day from being recomputed.

Hikvision Sync Logs

The log of every access-control scan coming from the Hikvision devices, with a sync status (Completed / Pending / User-not-found / …). If scans didn't process, Force Resync (All Failed Records) retries them. This is where you diagnose "the employee scanned but it didn't register."

Failed Sync Records

A focused view of just the failed or pending scans — the employee scanned but the event wasn't processed (e.g. an unknown worker ID, device offline). Fix the cause (or use Force Resync on the Sync Logs tab) so those scans count as worked time.

Which schedule a day was built from

A day is not built from one schedule but from a stack, and knowing the order saves a lot of guessing when a day looks wrong. The engine takes the first answer it finds: a schedule override covering that date, taking one attached to the person before one attached to the template; then the template's day for that weekday and rotation week; then the Base Schedule attached to the template; and finally the department or company default.

The two halves carry different things. The Base Schedule carries the rules - daily target, minimum hours, clock-in and clock-out bands, break allowance and overtime policy. The template carries the pattern - which days are working days, their start and end times, and the rotation. An override carries only a date with a start and an end, or a rest-day flag.

Because the rules and the pattern live in different places, changing one does not change the other. Editing a template's day times moves the shift window without changing how many hours the person owes that day; that number is the Base Schedule's daily target.

Days already recorded keep the rules that applied when they were created. After changing a template or a Base Schedule, recalculate the affected days if the change needs to show in history - one row at a time from Manage hours, or in bulk from the Detail Attendance report.

Good to know

Scans are the source of truth. If hours look wrong, check the sync tabs first — a missed scan is usually a sync problem, not a calculation one.
A manual override locks a day so the engine won't overwrite your correction — use it for genuine fixes only.
Holidays and schedules drive pay — an out-of-date holiday or wrong tolerance band quietly distorts attendance and overtime.

Manage schedules — setting an individual employee's working pattern (line-manager screen).
Daily monitoring & attendance reports — reviewing what the records show.
Clock in and out remotely — how employees create the scans.