The Challenge: Three Problems, One Entry Gate
At the main gates of a large engineering conglomerate's manufacturing facilities, three separate problems converged every morning. Employees and contract workers arrived simultaneously, queued at entry points, and were processed by systems that did not talk to each other — or in some cases, by security guards holding clipboards.
The first problem was headcount accuracy. The HR and Industrial Relations teams were supposed to monitor planned versus actual headcount on the shop floor. In practice, the manual gate registers never matched reality. Workers entered through different gates, some registers were updated retrospectively, and contractors signing in under master contractor records made individual tracking impossible. The planned-vs-actual report was more aspiration than fact.
The second problem was contractor compliance. Work permits were tracked in physical files at the gate office. When a permit expired, the renewal process depended on someone noticing — either the contractor themselves, or a vigilant gate security officer who happened to check. Expired permits were discovered routinely only after the fact, sometimes weeks after expiry.
The third problem was vehicle throughput. Employees who drove to work — a significant portion of the workforce at a large engineering campus — faced manual vehicle checks at boom barriers. A security guard would verify the vehicle registration, check the occupant's identity, and raise the barrier by hand. At peak arrival times, this created queues that could stretch for hundreds of metres and added fifteen to twenty minutes to some employees' commutes. It also created an inconsistent security process: under pressure, manual checks became cursory.
The payroll team sat downstream of all three problems. Month-end attendance reconciliation required consolidating gate register data, contractor timesheets, and shift records — a process that took several days and regularly surfaced errors that HR and IR had to investigate individually.
Dual-Mode Authentication: Speed Where It Counts, Security Where It Matters
The Teamnet HRMS implementation deployed two complementary authentication mechanisms, each optimised for its context. RFID card readers at high-volume turnstiles handle the majority of entry events. An employee taps their card, the reader queries the attendance engine, and access is granted or denied in under a second. At peak throughput, this means hundreds of entry events per minute without congestion.
Biometric fingerprint verification is deployed at entry points to high-security zones — specific production areas, server rooms, and sensitive storage. Here, speed is less critical than certainty. The fingerprint check provides a match against the enrolled biometric that an RFID card cannot — it verifies the person is who they claim to be, not just that they are holding the right card. This prevents buddy-punching (where one employee swipes in for an absent colleague) in areas where headcount accuracy is essential for safety and security protocols.
Both modes feed the same attendance engine. The system does not distinguish between an RFID event and a biometric event when calculating attendance — it sees a verified entry record and applies the same policy logic regardless of the authentication method used.
Contractor authentication is handled through the same gate infrastructure, but with an additional compliance check layer. Before access is granted, the system verifies the contractor's work permit status, insurance validity, and any facility-specific clearances — identical to the logic described in the contractor compliance implementation. The gate is the enforcement point for the compliance framework, not a separate process.
Vehicle Tracking: No Stopping, No Queue, No Manual Check
The vehicle access problem required a different hardware approach. Long-range RFID readers — capable of reading a windshield-mounted RFID tag from several metres while the vehicle is moving at low speed — are installed at each boom barrier. Employees whose vehicles are registered in the system receive an RFID tag to affix to their windshield.
As the vehicle approaches the barrier, the reader identifies the tag, the system looks up the registered employee, verifies their attendance status for the day, and triggers the boom barrier to raise. The vehicle does not stop. There is no window interaction with a security guard. The entire sequence takes two to three seconds and is logged automatically as an attendance event.
The system handles edge cases that manual processes handle poorly. If an employee attempts vehicle entry but has already exited, the system flags the anomaly. If the vehicle enters but the employee has a pending attendance exception, the exception is queued for HR review without blocking entry. Visitors and unregistered vehicles are directed to a separate lane for manual processing, keeping the automated lanes clear.
For security, every vehicle entry and exit is logged with timestamp, gate number, and linked employee record. The audit trail is comprehensive and queryable — security teams can pull vehicle movement reports by employee, by gate, by time window, or by any combination of these dimensions.
Payroll Integration: From Days to Automatic
The downstream value of unified attendance data is realised at payroll. Every attendance record — turnstile entries, biometric verifications, vehicle accesses, contractor check-ins — flows into the central attendance engine, which applies shift rules, overtime thresholds, and late-mark policies before producing a finalised daily record per employee.
These records feed directly to the payroll system. At month-end, the payroll team receives a complete, validated attendance dataset that includes:
- Total working days and present days per employee
- Late arrivals and early departures, with applicable deductions calculated
- Overtime hours, categorised by day type and shift
- Contractor hours logged against specific contractors and work permit categories
- Leave interactions — where approved leave records modify the attendance calculation
The multi-day reconciliation process that previously occupied the payroll team has been eliminated. The data is clean when it arrives because the exceptions — anomalous records, mismatched contractor data, expired permit entries — were caught and resolved at the gate in real time, not surfaced in bulk at month-end.
For an organisation where the payroll run covers thousands of employees and contractors across multiple pay structures, the accuracy of the input data is not an administrative nicety. Errors in attendance data produce errors in salary outputs, which generate employee grievances, IR complications, and rectification cycles that cost time at every level of the organisation. A gate system that feeds clean data to payroll is, in a direct sense, a payroll accuracy investment.