Do holidays count towards an employee's Schengen limit?

A traveller gets one Schengen day allowance, not a work allowance and a separate holiday allowance. Employers still need to be careful about how they collect the personal side of the calculation.

The short answer

Yes. A personal holiday in the Schengen Area counts towards the same 90 days in any rolling 180-day period as a business trip.

The rule follows the traveller. It does not distinguish between a client meeting in Paris, a conference in Berlin, and a family weekend in Barcelona. If all three trips fall within the same rolling window, all three draw from the same allowance.

For employers, that creates a genuine operational problem: a company may approve a business trip using an incomplete travel history. The answer is to collect the minimum dates and locations needed for the calculation, explain why the information is needed, and restrict who can see it. It is not to ask for an employee's full holiday itinerary.

One person, one allowance

UK passport holders using the visa-free short-stay route can normally spend up to 90 days across the Schengen Area in any rolling 180-day period. The complete guide to the 90/180-day rule explains the calculation.

The purpose of a trip does not create extra days. Neither does the payer.

The calculation also counts both the arrival and departure dates. A Friday evening arrival and Sunday morning departure normally uses three days.

How a holiday can make a work trip unsafe

Consider an employee who has recorded 70 business days in Schengen during the relevant rolling window. Their manager sees 20 days remaining and approves a two-week assignment.

The employee also spent 10 days in Portugal with family, but the company never asked about personal travel. The proposed 14-day assignment would take the real total to 94 days, not 84.

Nothing unusual happened. The manager checked the business-travel system, and the employee reasonably assumed their private holiday was private. The process produced the wrong answer because neither side knew what information the other needed.

This is why a policy should explain the narrow purpose of collecting personal Schengen travel before the first urgent booking arrives.

What an employer actually needs to know

For a day-count calculation, the necessary facts are usually modest:

• the employee concerned;
• the country or enough information to establish whether it counts towards the common allowance;
• the entry date;
• the exit date; and
• whether a residence permit, long-stay visa, or other status changes how the stay should be treated.

The calculation does not normally need the hotel name, flight number, travelling companions, reason for the holiday, photographs, restaurant bookings, or a day-by-day itinerary.

There may be a reason to retain evidence in an individual high-risk case, but that should be a separate, justified decision. “We might need it one day” is not a useful retention policy.

The data-protection boundary

Personal travel data is still personal data when an employer collects it for compliance planning. UK data-protection rules therefore apply.

The Information Commissioner's Office says employers must identify the minimum information needed for their purpose and must not hold more than that. Employers also need to tell workers why information is being collected, the lawful basis, how long it will be kept, who will receive it, and what rights the worker has.

That leads to a more sensible process than treating privacy and compliance as opponents.

Define the purpose

Be precise. “Travel monitoring” sounds broad and intrusive. “Checking whether proposed company travel would breach the employee's short-stay allowance” is a narrower purpose that staff can understand.

Choose and document a lawful basis

Do not assume employee consent solves the issue. The employment relationship can make consent difficult to treat as freely given. The appropriate basis depends on the organisation, purpose, and circumstances, so document the decision with your data-protection lead or adviser.

Collect only from people in scope

There is little reason to ask every employee about every holiday. Limit the process to people whose nationality and status make the calculation relevant and who may travel for work.

Restrict access

A line manager may need a safe/not-safe result without needing to see private locations. HR, travel operations, or a designated compliance owner can manage the underlying dates with tighter access.

Set a retention rule

Old travel stops affecting the rolling calculation, although audit or dispute needs may justify a defined additional period. State the rule and delete data when there is no longer a purpose for keeping it.

Give employees a correction route

Wrong dates create wrong decisions. Make it easy for an employee to see the travel attributed to them and correct a missing or inaccurate trip.

A low-friction reporting process

The best process is small enough that people will use it.

1. During onboarding or before an employee enters the frequent-traveller group, explain the Schengen rule and the personal-travel overlap.
2. Ask for relevant Schengen entry and exit dates from the previous 180 days, not a lifetime travel history.
3. Let the employee enter personal trips directly into the restricted system where possible.
4. Show the employee what was recorded and how it affects the forecast.
5. Ask them to add future personal Schengen trips before requesting company travel, or to update the record when plans change.
6. Recalculate at approval time rather than relying on a saved number.

A useful policy sentence might read:

If you travel to the Schengen Area for work, we will ask for the entry and exit dates of relevant personal Schengen travel within the rolling 180-day window. We use this only to assess proposed company travel, restrict access to the designated travel-compliance team, and retain it under our published retention schedule.

That wording needs adapting to the company's actual privacy notice, lawful basis, access controls, and retention practice. It should not promise a safeguard the organisation has not implemented.

What if an employee does not want to disclose a holiday?

Start by checking whether the request is broader than it needs to be. An employee may object to sharing their companions or itinerary when the company only needs dates and qualifying countries. They have a point.

If the minimum information is genuinely needed to approve business travel, explain the purpose and the consequence of an incomplete calculation. A practical fallback may be to withhold approval for the proposed company trip until the employee can confirm that the combined total is safe, rather than forcing disclosure through an informal manager conversation.

The right answer depends on the company's policies, lawful basis, employment arrangements, and risk. Get HR or data-protection advice before turning the issue into a disciplinary one.

Keep private travel private by design

Software cannot remove the judgement from this process, but it can reduce unnecessary exposure. A manager can receive a forecast outcome while a smaller authorised group maintains the dates behind it. Audit records can show who changed a trip without making the entire company aware of where someone went on holiday.

Collect enough to make the travel decision, but no more. That gives the company a more accurate Schengen country and day count without turning a compliance tool into an employee-surveillance file.

Sources and review date

• GOV.UK guidance on the shared Schengen 90/180-day allowance (opens in a new tab)
• ICO guidance on collecting and keeping employment records (opens in a new tab)
• ICO guidance on data minimisation (opens in a new tab)

Sources last checked: 2026-09-07.

This article gives general operational and data-protection information. It is not legal advice. Employers should confirm their lawful basis, privacy information, access controls, and retention position for their own workforce and systems.

See privacy-conscious team tracking or check a set of dates without creating an account.