Inside the platform
A branch manager carries a whole day: that the team is complete, that each employee starts their shift, that what needs a decision passes without delay, and that their figures match what reaches payroll. They have no time to gather that from messages. This page explains how TAC HR shows you your branch, what it works out for you, what asks for your decision and what it does not do, so that before your admin account arrives you know what you will open before the shift starts and what will reach you without opening anything.
01
Your branch on today's dashboard
Your admin account is given a scope of one or more branches or departments, so the dashboard and reports are limited to the staff in your scope, while a holder of the full permission sees the whole company. The dashboard shows today's counters, and you open the daily report with check-in and check-out times, the detailed one, the monthly summary and overtime. Whoever is past the set grace after their shift began, 120 minutes by default, and has not punched with no leave and no attendance request for the day, is flagged to their direct manager once a day, and if they have no manager with an admin account the attendance admins are flagged. The alert has no financial effect: absence is counted by the attendance report as it stands.
02
Shifts and minutes
A shift carries a start and end time, a lateness grace, an early-leave grace and days off, and is assigned to the employee so lateness is counted on their own shift. An employee can have more than one main shift in a day as long as they do not overlap in time, and for a shift crossing midnight the check-out limit is its end plus three hours, so it is not counted as forgotten. A shift missed entirely on a day when the employee attended another counts as partial absence by its minutes, and the gap between two shifts is never overtime. A change to a shift's times takes effect on an effective date and stays as a record that is never deleted, and an employee's shift changes by a Work time change request or a bulk assignment. Official holidays and weekly rest enter the reports, so their day is not counted as absence.
03
Requests and approval
Each request type has a route the company sets, with steps by role, by user or by the direct manager, so requests from those who report to you reach you on the requests screen. Their types include permission, early leave, forgotten check-in, late removal, overtime, shift change and location change. When you approve an overtime request its minutes are written to the attendance day, and the run counts them under the overtime source the company set. Whoever holds the on-behalf permission can raise a request for an employee within their scope, such as a forgotten punch, and you write your note in the request's chat with attachments. Automatic approval within limits stays off until the company switches it on.
04
Tasks and escalation
Task lists have columns the company sets, and every task has an owner and a due date. The system reminds the day before and on the day, then escalates after the grace, two days by default, to the task's creator and their direct manager. A daily job at 08:30 in the morning handles that reminder and escalation. Among the ready templates is Maintenance work with a location column and a priority, and Sales follow-up with a stage and a follow-up date. The assigned employee gets a notification of the task, sees it in My tasks on their phone and finishes it with a Done button, and you see the list on the web with who finished and who is late.
05
Protection and devices
Before each punch the app inspects the phone and rejects spoofed locations, emulators and modified devices, and the system checks the employee's punch place: one site, several or anywhere, rejecting what falls outside it with a message naming the nearest allowed site and the distance. A rejected attempt is recorded with its reason and distance and you review it on the web, and it is not shown to the employee. If your branch has a compatible fingerprint device with a private key, its punches enter the same attendance log that phone punches enter, and whatever cannot be recorded is kept in a rejected log with its reason. Attendance correction needs a dedicated permission, and each correction is recorded with what it was before and after and who made it.