Inside the platform
A maintenance and operations company sells its technicians' time. The contract with the client sets how many technicians are at its site and for how many hours, so quality is measured by precise attendance at the right site, and any hour of absence turns into a deduction from the client or a complaint. So TAC HR is built around the site and the technician together: a site per contract with its boundary, a technician assigned the sites where they may punch, tasks with a priority and an escalation, and on-call duty with its overtime. The run reads all of it. This page explains how that runs in a company operating several contracts, and what stays outside the system.
01
A site per contract
Every site in the system has a name, a city and a boundary drawn on the map as a polygon or a circle. At the punch the system checks the phone's coordinates against the boundary: inside it the punch is accepted and attributed to the site, and outside it the punch is rejected with a message naming the nearest allowed site and the technician's distance from it, and the attempt is recorded for admins on the web. Before every punch the app inspects the device, rejecting spoofed locations, emulators and modified devices. The site name shows beside the check-in and check-out times in the attendance sheet, which can be printed with paper and signature options or exported as a spreadsheet file, so the manager has what proves to the client that the technician was at their site.
02
A technician called to another site
Each employee has a punch place setting that overrides the company's: only their assigned site, or several sites you choose, or all of the company's sites, or anywhere. So a technician called to a job at another site can punch there with no transfer request, and that site is recorded. If they move to a new contract for good they raise a location change request, or an admin who holds the on-behalf permission within their scope raises it for them. For a technician who moves between sites all day, field tracking is switched on with a rep seat: they record their visit to an approved client site inside a radius the system checks, and their position is shown on the map during the shift only, with their consent.
03
Maintenance tasks
The tasks section has a ready template called Maintenance work with a location column holding coordinates, a priority of urgent, high or normal, and an estimated cost, and you add your own columns to it. A task is assigned to a technician with a due date, and they get a reminder the day before it and another on the day, and if it reaches the configured escalation grace, two days by default, the escalation goes to the task's creator and the technician's direct manager. So a task due on 10 November reminds on 9 November and on 10 November, and escalates on 12 November if it is not done. The technician completes it from their phone and comments under their own name, so the manager sees from the morning which call is still open, not when the client complains.
04
On-call duty and trips
Faults do not follow the shift schedule, so a shift is defined for evening or night on-call duty, and the check-out punch of a shift that crosses midnight stays open until three hours after its end so it is not counted as forgotten. The overtime source is an explicit setting: approved assignments only is the default. Under the Saudi labour law model on basic pay, an overtime hour is paid at 1.5 times the normal hourly rate: a technician on a SAR 4,800 basic has a normal rate of SAR 20.00 an hour, so five approved hours appear on the payslip as a separate line with its formula, worth SAR 150.00. Someone assigned to work in another city raises a business trip request whose days are not counted as absence, and a daily allowance the company sets is worked out for them: four days at SAR 180 come to SAR 720.00.
05
Documents and the run
A daily job at 06:00 checks the iqama, passport, medical insurance and contract-end dates in each technician's file, and the uploaded documents that carry an expiry date, including the professional card. Every document moves through its stages on the company's lead times, 60, 30 and 7 days by default, and admins receive one daily summary, so the papers are ready when the client asks. The run draft is created automatically on a day the company sets, and both GOSI shares are worked out by the employee's system: a Saudi technician on the previous system with a contributory wage of SAR 5,000 has SAR 487.50 withheld at 9.75%, and the company carries SAR 587.50 for them. Before export the wage file page checks IBANs, IDs and the company number.