If your company operates more than one site in Cape Verde — branches on different islands, a shop in Praia and another in Mindelo, or departments spread across several buildings — you already know the problem that single-site companies never face: every location ends up tracking time and attendance its own way. One terminal here, a paper sheet there, a spreadsheet someone emails at month-end. The result is predictable: numbers that don’t match, payroll closing late, and HR spending hours reconciling data instead of using it.

The good news is that the technology to fix this is accessible to companies of any size operating in Cape Verde: a single time and attendance platform connected to biometric terminals at each branch, consolidating everything into one real-time database. You don’t have to choose between “one system per site” and “no automation at all” — you can have one terminal per site and still get a single, unified view.

This article explains how centralised multi-branch attendance works, what problems it actually solves, and what to check before investing — based on experience installing these systems for companies across Santiago, São Vicente and other islands.

The problem with running branches without a central system

When each branch handles attendance in isolation, the same issues tend to show up everywhere:

  • Different rules at every location. One branch tolerates a 10-minute delay, another tolerates none; one counts overtime to the minute, another rounds to the hour. Without a shared policy enforced automatically, every manager decides “their own way”.
  • Slow payroll closing. If HR has to request separate files from each branch, merge them manually and chase down discrepancies, the monthly close drags on and the risk of error goes up — paying overtime that never happened, or missing overtime that did.
  • No real-time visibility. Management only finds out who was or wasn’t on shift once someone sends a report — usually too late to act on it.
  • Harder to catch time fraud. Without a reliable, auditable record, it’s easier for “buddy punching” (a colleague clocking in for someone else) or unexplained manual edits to slip through.

We covered how biometrics solve the time-fraud problem at a single site in our earlier piece on biometric time attendance. The question that’s left unanswered is: how does that scale to several locations without multiplying the administrative work?

How centralised multi-branch time and attendance works

The architecture is simpler than it sounds. Each branch gets one or more clock-in terminals — face, fingerprint or card, depending on the team’s profile and how many people pass through at peak hours. Every terminal talks to one central management platform, hosted in the cloud or on a central server, which:

  • Receives clock-ins from every branch as they happen;
  • Applies the schedule, grace-period and overtime rules defined centrally — or per branch, when that makes more sense;
  • Produces consolidated reports (company-wide) and also per branch, department or employee;
  • Exports the data ready for payroll, with no manual re-entry.

One detail that surprises many clients: the biometric terminals RADAR installs store clock-ins locally whenever the network or internet connection drops — something that happens from time to time outside Santiago and São Vicente — and upload them automatically to the central database once the connection is back. No record is lost because of a network outage at a remote branch.

What HR and management gain from a single platform

Payroll-ready reports, without the spreadsheet step

Instead of receiving loose files from each location, HR works from a single dashboard: hours worked, absences, late arrivals and overtime, already calculated and grouped by branch, department or the whole company. This cuts payroll closing time significantly — and, more importantly, cuts the errors that cost money (paying hours that weren’t worked, or missing overtime that was owed).

Face, fingerprint or card — mixed per location

Not every branch needs the same method. A shop with high staff turnover may prefer facial recognition, faster in a queue at opening time; a warehouse with fewer people can stick with fingerprint or card. The central platform treats the data the same way regardless of which capture method each terminal uses, so you can mix technologies without losing the unified view. We compared the two approaches in facial recognition vs fingerprint: which to choose.

Profiles, zones and schedules — not just attendance

When the same biometric platform also handles access control, the company gets more out of it: an employee’s profile can define not only their working hours, but also which areas of the building they can enter and when. We detailed this profile/zone/schedule logic in our article on access control: profiles, zones and schedules — and attendance can share the same employee database, instead of duplicating records.

Integration with HR and payroll software

Centralisation only delivers its full value once the data reaches the payroll software directly, without passing through an intermediate spreadsheet. The systems RADAR installs integrate with HR and payroll software, including PRIMAVERA, removing manual re-entry and the errors it brings.

What to check before choosing a multi-branch system

Not every multi-branch attendance project is built the same way. Before committing, it’s worth confirming these points with any supplier:

  • Does each branch work offline? Ask explicitly what happens to a clock-in if the internet drops at that exact moment — if the answer is “it’s lost”, look elsewhere.
  • Can rules vary by branch? Some companies need one single policy; others need different grace periods and schedules per location or role. The software should support both.
  • Do reports come out in the format HR actually needs? Ask to see a sample report before deciding — some systems export raw data that still needs manual cleanup.
  • Is there technical support on the islands where you operate? A broken terminal at a branch with no nearby technician can sit idle for days if the supplier only has staff in Santiago.
  • Is biometric data protected? Ask where and how the data is stored, and who has access to it.

Biometric data protection in Cape Verde

Biometric data — fingerprints, faces — counts as sensitive personal data. In Cape Verde, personal data processing is governed by Law No. 133/V/2001, amended in 2013 and 2021, under the supervision of the National Data Protection Commission (CNPD), according to the legal guide published by advogados.cv1. In practice, this means a company collecting fingerprints or facial images for attendance control must inform employees about the purpose of the processing, limit the use of that data strictly to that purpose, and put adequate security measures in place to protect it. We always recommend that clients validate these points with their own legal counsel before rolling out any biometric system, especially when it will run across several branches with separate HR teams.

How RADAR can help

RADAR installs and configures time and attendance and access control systems for companies with one or several branches on any island of Cape Verde, with biometric terminals (face, fingerprint, card), central software with HR reports, integration with payroll — including PRIMAVERA — and local technical support. See our full attendance and HR software solution (Portuguese page). We also help plan the move from “every branch on its own” to a single platform, without interrupting a single payroll cycle along the way.

Frequently asked questions

Can branches on different islands connect to the same software?

Yes. As long as each branch has an internet connection, even an intermittent one, its terminals sync with the central platform. When the connection drops temporarily, clock-ins are stored on the terminal itself and uploaded automatically once the network is back.

Do we need to replace every terminal at once?

Not necessarily. The rollout can be phased, starting with the branch with the most control problems and extending to the others, as long as the chosen platform supports terminals being added progressively.

Does the system handle very different schedules across branches?

Yes. Schedule, grace-period and overtime rules can be set per branch, department or individual employee, while still producing one consolidated report for the whole company.

How does it integrate with the payroll software we already use?

The systems we install export attendance data ready for payroll processing, with direct integration into platforms such as PRIMAVERA. This avoids manually re-entering hours worked and absences into the payroll system.

What happens to biometric data when an employee leaves?

Good data-protection practice requires that an employee’s biometric data be deleted from the system once it’s no longer needed for attendance purposes — normally once they leave the company. This should be part of the company’s internal data-protection policy.

If your company runs more than one site and wants to stop depending on loose spreadsheets to calculate attendance, contact RADAR and book a free technical assessment, no obligation.

Sources: 1. Advogados.cv — Data protection in Cape Verde: what the law says.

WhatsApp