With a single site, almost any HR system works fine: one calendar, one leave policy, one person responsible for health and safety. Add a second location and those same pieces start colliding. Local public holidays in one city aren't the same as another's, a manager approving leave at one site shouldn't see personal data from another, and occupational health checks need to be organized site by site, not company-wide.
Most of these problems aren't solved by adding more features -they're solved by better scoping: making sure every calendar, every permission and every health obligation can be limited to whoever it actually applies to, instead of standing up a separate setup per site.
One calendar per team, not one for the whole company
Local holidays, opening hours and shift patterns aren't the same in Madrid as in Bilbao, and the same logic applies anywhere a company runs several offices. Cantevia's customizable team calendars let you define those differences by department or site, instead of forcing a single national calendar that every manager then has to correct by hand. It's a small difference in initial setup and a large one day to day: nobody has to remember "this site is on local holiday today" outside the system.
Occupational health, site by site
In Spain, health surveillance under the occupational risk prevention law (Article 22) and issuing protective equipment aren't a single company-wide formality -they depend on the role and the site where someone actually works. Cantevia's People module tracks training, issued protective equipment and health monitoring per person, so it's possible to see at a glance who has a pending check-up at each site, instead of relying on a separate spreadsheet someone has to consolidate by hand every month.
Equipment that moves between people and sites
With multiple locations, IT equipment -laptops, phone lines, access cards- also changes hands and sites more often than in a single-site company. If the system only tracks "who has what" with no further context, reconstructing the history of one laptop -which sites it's been through, who had it before- turns into asking whoever's been at the company longest.
Cantevia tracks every piece of equipment by serial number: a unit that already has history can't be deleted, only decommissioned. That leaves a permanent record of which sites and people a given laptop or access card has passed through -something that starts mattering the moment a company outgrows a single building.
Permissions that respect structure, not just the org chart
A manager at one site shouldn't be able to approve leave or see data from another site just because the system doesn't distinguish scope. Granular permissions per module, with a level (read, write, admin) and a scope (own, team, company-wide) configurable per role, let a site manager have exactly the reach that role should have -no more, no less.
Adding locations shouldn't multiply spreadsheets. If a system forces you to keep a separate calendar or a separate safety tracker per site, it hasn't solved the multi-location problem -it's just repeated it several times.