Spain requires every employer to keep a daily record of the start and end time of every employee's working day. Every employee — including the staff engineer working remotely from Valencia who has never clocked in for anything in their life.
That obligation is the thing foreign employers most often discover late, and the one that most reliably collides with how a technology company thinks it should treat senior people. It is also entirely manageable once you understand what the rule actually asks for, which is far less than the phrase "clocking in" suggests.
The headline numbers, before anything else: a legal maximum of 40 hours a week averaged over the year, a nine-hour daily ceiling on effective working time, twelve hours' rest between shifts, and 30 calendar days of paid holiday. This guide covers that legal frame, the schedule culture around it that no statute describes, and how the companies that hire well in Spain turn working hours into a reason candidates say yes.
Who this applies to, and who it does not
Everything in this article governs the relationship between a Spanish employee and their employer. That means one of two situations:
- You have a Spanish entity — usually an S.L., the Spanish limited company — and the person is on your own payroll. You are the employer and every obligation below is yours directly.
- You hire through an employer of record such as Deel. The EOR is the legal employer on paper and carries the compliance, but the schedule, the on-call rotation and the meeting culture are still yours in practice, so the constraints still shape how you can run the team.
None of it applies if you engage someone as a contractor. A Spanish autónomo invoicing you is running their own business: they set their own hours, take holiday when they decide to, and there is no working-time limit, no rest period and no daily time record to keep on your side. You agree a scope and a rate, and how they organise their week is not your decision to make.
That is a genuine difference in administrative weight, and it is one of the reasons a lot of US companies start in Spain with contractors. It is also why a contractor rate and a salary are not comparable numbers — the salary buys a set of obligations the invoice does not. Our developer salary guide for Spain works through what that difference actually costs.
If you are still deciding between the two, read the rest of this article as a description of what the employment route commits you to.
The legal frame: 40 hours a week, nine a day, 30 days' holiday
Spain's rules on working time come from the Estatuto de los Trabajadores, the national labour statute. Four numbers do most of the work.
Maximum ordinary working time is 40 hours a week, calculated as an average over the year. Not 37.5. You will read the lower figure in a great many places, including articles published in 2026: the reduction to 37.5 hours was agreed between the government and the unions, but the bill was rejected in Congress in September 2025 and has not passed since. As of 2026 the legal maximum remains 40. What has moved is the market rather than the statute — the average working week actually agreed in Spanish collective bargaining is now around 37.8 hours, so a large share of employees already sit below the legal ceiling.
Nine hours is the daily limit on effective working time, unless a collective agreement or a written arrangement distributes it differently while respecting the rest between shifts.
Twelve hours of rest between shifts is the minimum. This constrains on-call rotations more than anything else on the list.
Thirty calendar days of paid holiday — roughly 22 working days — is the legal minimum, not a benefit you offer. Foreign employers used to the US norm of 10 to 15 accrued days should treat this as a floor and plan capacity around it; UK and northern-European employers will find it closer to familiar.
Two more that matter operationally: weekly rest is a minimum of one and a half uninterrupted days, and overtime is capped at 80 hours a year, excluding hours compensated with time off within four months.
"Effective" working time excludes breaks, and that changes how you plan
The statute limits effective working time. In technology that distinction causes constant confusion around breaks, meals, travel, on-call availability and time spent logged in without actually working.
Translate it for an engineering team like this: you cannot design a schedule that depends on systematically stretching the day. And you cannot assume the rules apply more loosely because these are high-autonomy profiles. They apply identically. What changes is how you plan delivery, not the legal frame.
A common startup failure looks like this: a nominally flexible schedule, with sprints and releases planned as if the team can absorb continuous peaks without any change in capacity. The law does not correct bad planning. It only leaves you more exposed when that bad planning becomes chronic.
Rest between shifts, in practice
The twelve-hour minimum is the point most founders remember only when an inspection, a claim or a dispute with a manager arrives. In roles with incidents, on-call or night deployments, it determines how you build rotations.
A practical rule: if an engineer finishes late because of a critical incident, do not compensate informally the next day. Record it, reschedule, and leave a trail.
In small teams this forces better thinking about coverage. A SaaS company selling service continuity cannot run on permanent on-call heroes. It needs shifts, handovers or explicit agreements. Without them, support, development and availability blur into each other.
The collective agreement layer
This has no clean American or British equivalent and it catches people out. Beyond the national statute, most Spanish employees are covered by a convenio colectivo — a sector-level or company-level collective agreement that sets terms above the statutory floor and binds you whether or not you negotiated it. Many technology companies fall under the consultancy and IT services agreement — the Convenio Colectivo Estatal de Empresas de Consultoría — which sets its own annual hours, minimum pay by professional category and rules on how the schedule is distributed.
Before you write a contract, find out which agreement covers your activity. It answers questions the statute leaves open, and its terms override anything less favourable you put in the contract.
How to comply with the daily time-tracking obligation
The daily time record is where most startups trip. Not because it is theoretically complex, but because it collides with a technology culture that wants autonomy and rejects visible control. The obligation exists regardless, and it covers essentially every employee — full-time, part-time, office, hybrid, remote — whether they sit on your Spanish entity's payroll or on an EOR's. (Senior executives on a personal de alta dirección contract sit outside it; almost nobody you hire will. Contractors sit outside it too, for the reasons above.)
What works:
- Simple tools that record start and end without invading the day.
- A written policy covering breaks, travel, availability and meetings outside the normal window.
- Traceability for remote, hybrid and distributed profiles.
What does not:
- "We're a startup, we don't need to clock in here."
- Treating Slack or Google Calendar as a substitute for a formal record.
- Leaving the interpretation to each team's manager.
Records must be kept for four years and made available to employees, their representatives and the labour inspectorate. In practice a declarative digital tool — where the employee confirms their own start and end — satisfies the obligation and does the least damage to trust. Tools like Factorial or Personio fit better than anything built to prove constant activity. The name matters less than the usage model: the closer a system gets to surveillance, the more it costs you in senior candidates.
One change to watch. A reform requiring the record to be digital, tamper-evident and remotely accessible to the labour inspectorate has been working through the process for some time. As of August 2026 it has been pushed to the autumn, and if approved would take effect around spring 2027. If you are choosing a tool now, choose one that already produces an auditable digital log rather than a spreadsheet.
The schedule culture no statute describes
The legal frame tells you what you may do. Local convention tells you what a candidate expects, and misreading it makes an otherwise good offer feel foreign.
The Spanish day runs later than the northern European one. A 9am meeting is early. Lunch is around 2pm and is a real break rather than a sandwich at the desk. The evening starts later in every sense. For a US employer this is mostly good news: the afternoon overlap with the East Coast is more natural than the time difference suggests.
Jornada partida versus jornada continua. The split day — a morning block, a long midday break, then a late afternoon block ending at 7pm or later — is still common in Spain and actively disliked by technical talent. The continuous day, running roughly 8am or 9am to 5pm or 6pm with a short break, is what engineers want and what most technology companies now offer. Proposing a split day for a role that could run continuously is one of the few schedule decisions that will cost you candidates outright.
Jornada intensiva in summer. Many Spanish companies run a shortened, continuous day through July and August, often finishing at 3pm. It is not a legal requirement; it is a widespread convention and a genuinely valued benefit. If your Spanish team has it and your head office does not understand why, have that conversation before June rather than during it.
August is quiet. Not empty, but planning a launch or a hiring push for August is planning against the country.
Remote work has its own law: Ley 10/2021
If someone works remotely for 30% or more of their working time over a three-month reference period, Spain's remote work law — Ley 10/2021, de trabajo a distancia — applies. Two consequences matter to a foreign employer.
- You need a written remote work agreement, separate from the employment contract, setting out the equipment, the split between remote and on-site, the reference schedule and the rules on availability.
- You must compensate the expenses the employee incurs by working remotely. What counts and how much is largely left to the collective agreement or to your agreement with the employee, but "nothing" is not an available answer.
Remote work is also voluntary and reversible on both sides. You cannot impose it, and you cannot unilaterally withdraw it once agreed.
Remote is not the same as flexible
Many companies conflate the two. Remote work is freedom of location. Schedule flexibility is latitude over when the work happens. You can have either without the other, and candidates ask about both.
Real flexibility means an employee can shift part of their schedule without informal penalty. If an engineer starts later because they drop a child at school and it affects no deliverable or key coordination point, the company absorbs it. Paper flexibility means saying "the hours don't matter" and then scheduling early meetings, watching Slack presence and rewarding whoever replies at night. Legally you have a record. Culturally you are still managing by visibility.
If an employee has to ask their manager every time they move their start time by an hour, they do not have flexibility. They have permission, granted case by case.
Schedules that win technical hires
The companies that recruit best in technology do not always offer fewer formal hours. Their advantage is in how they organise time.
Core hours: fix the overlap, free the rest
Fix a common window for collaboration and leave the rest flexible. For hybrid and distributed teams this is the most useful formula available, because it solves the main problem with total flexibility: never knowing when you overlap with anyone. Done well it concentrates meetings, protects deep work outside the window, and coordinates teams across cities or countries.
Core hours carry no special legal status. Their force is operational, and they need to be documented in your internal policy to be worth anything.
Async-first: fewer interruptions, wider talent pool
Popularised by companies like GitLab and Buffer, async-first does not mean eliminating meetings. It means not depending on them for everything. Senior talent finds it attractive because it reduces interruptions and leaves room to work with judgement. It also makes international hiring easier, because it lowers the pressure to always be live at the same moment.
The failure mode is a company that calls itself asynchronous while still deciding everything important by video call and urgent chat. Async work is not leaving messages in Slack. It is documenting well, deciding with context, and accepting that not everything needs an immediate reply.
The four-day week: legal only if you redistribute the hours
It attracts attention because the benefit is instantly legible. In Spain it needs legal care first: with a nine-hour daily ceiling on effective working time, a 40-hour week does not fit into four days — ten-hour days exceed the limit. It works only where the collective agreement or a written arrangement redistributes the hours and the twelve-hour rest between shifts still holds. Beyond the legal fit, it works when it is designed as a complete model — meetings, prioritisation, response times and client expectations all redefined. Otherwise it becomes five days of work crammed into four.
What to put in the offer
Many companies have a reasonable practice and explain it badly, or leave it out of the offer entirely so it surfaces late in the process. Document five things from the start:
- Ordinary working time and how it is distributed. What is expected weekly and how it is organised.
- The common collaboration window, if there is one, in plain language.
- The presence model. Office, hybrid or remote. No euphemisms.
- The time-tracking system. Which tool, how it is used, and how much real flexibility sits around it.
- The rules for incidents and out-of-hours work. Especially in infrastructure, security or support.
This reduces risk and improves close rates at the same time. When a company can explain clearly how time works, it signals control and honesty. For a candidate who has no intention of decoding your collective agreement mid-process, that clarity is worth more than another line of benefits.