What do insurers consider to be a known event?

Known events are one of the most significant exclusions in travel insurance. You are only insured for unexpected and unforeseen events. If a disruption, such as a strike, severe weather, or airline insolvency, was already publicly known or being reported before you purchased your insurance policy or booked your trip (whichever is later), no cover typically applies. The practical test is not whether you personally knew about the event, but whether you could reasonably have been expected to know about it at the relevant time.

Insurer definition of known events

What counts as "known"?

It does not matter whether you personally read the news, understood the severity, or believed the event would affect your trip. What matters is whether a reasonable person in your position could have been aware of the event at the relevant date. A family member being admitted to hospital is a known event even if the diagnosis has not been confirmed. A strike ballot being announced is a known event even if the strike has not yet been called. A named storm being designated by the Met Office is a known event even if it has not yet made landfall.

Most insurers apply a "constructive knowledge" test. This means the exclusion is based on what you "knew, or could reasonably be expected to have known" at the relevant date. It does not matter that you did not actually read the news or check the weather forecast. If the information was widely available, you are treated as though you knew it.

One exception to watch for: some policies use a narrower "actual awareness" test, excluding events only where you were personally "aware" that your trip would be disrupted. Oasis is an example of this approach. In principle, this is more favourable to the consumer, although in practice insurers may still argue that widely reported events should have been known to any reasonable person.

When should an event be "known"?

Getting the timing wrong is one of the most common reasons claims fail. Most policies use one of three trigger-date formulations.

Approach 1: "Whichever is later"

The trigger date is the date you purchased your policy or booked your trip, whichever came second. This means the exclusion moves with you: if you bought an annual policy in January but booked a specific trip in June, any event that became known between January and June is still excluded for that trip because the booking date is the later of the two. The effect is that holding a policy in advance does not grandfather in cover for disruptions that emerge before you commit to a particular journey. This is the broadest formulation and the one least likely to work in the customer's favour, because it resets the "known" clock every time you book.

This is the most common approach and is used by most leading insurers. Some policies, such as Staysure, also include renewal or extension of the policy as a trigger point alongside purchase and booking, which is worth checking for if you hold an annual multi-trip policy.

Approach 2: Fixed window (e.g. 7 days)

Some policies tie the trigger to a specific number of days around the booking date. For example, AXA's trip disruption section excludes any strike or adverse weather publicly announced prior to purchasing the policy or within 7 days of booking a trip. This creates a defined, auditable cutoff: either the event fell inside the window or it did not. The advantage for customers is certainty: an event announced 10 days before you booked would not be caught by this rule, whereas under the broader "whichever is later" approach it almost certainly would. The number of days varies by insurer, so check your own policy for the specific period.

Note that a policy may use both approaches in different sections. AXA applies the broader "whichever is later" test in its general exclusions and cancellation section, but uses the specific 7-day window for strikes and adverse weather under its travel disruption section.

Approach 3: Policy start or renewal date

The trigger is the date the policy commenced or was renewed. Anything known at that single fixed point is excluded for the entire policy year, regardless of when individual trips are booked. This formulation is common in annual multi-trip cancellation sections and is straightforward to apply.

What to look for in your own policy

The knowledge test. Check whether the exclusion is based on what you "knew or could reasonably be expected to have known" (the standard most insurers use) or on what you were personally "aware of" (a narrower test used by some). The broader test is harder for consumers to challenge.

The scope of the exclusion. Some policies apply the known events exclusion only to cancellation and disruption sections, while others apply it as a general exclusion across all sections. A general exclusion means the known events test could affect medical, baggage, or personal liability claims too, not just trip cancellation. Staysure and Aviva, for example, include known events in their general exclusions.

Specific triggers for weather. Most policies use general "publicly announced" language. AXA is an outlier that provides more certainty: it defines the trigger for adverse weather as the moment a weather event "is officially named by the Met Office, Environment Agency or any similar body." This removes ambiguity about when the exclusion starts.

Strikes and industrial action. Most policies call out strikes specifically, in addition to the general known events exclusion. The typical formulation excludes any strike or industrial action that was publicly known, had started, or had been announced at the time of purchase or booking. Some policies (such as AXA) set a defined day-count window for this; others rely on the general "whichever is later" test.

Renewing an annual travel insurance policy requires a review of known events

If an annual travel policy renews, the customer is expected to be mindful of events that may cause them to cancel a future holiday at the point of renewal. The policy is not necessarily viewed as continuous. Most insurers reset the "known events" clock at the renewal date, treating the renewed policy as a new contract.

Some policies make this explicit by listing renewal alongside purchase as a trigger point for the known events exclusion. Others achieve the same result because the "date of purchase" for a renewed policy is the renewal date.

Renewing a policy after a family member falls ill, or while a widely reported strike is ongoing, and then claiming for a cancellation linked to that event, is unlikely to succeed. Each renewal creates a new contract with its own assessment date for known events.

The Financial Ombudsman Service (FOS) interpretation of known events

Symptoms at the time of purchase

In DRN-4631066 (Society of Lloyd's, 2024), a customer visited her GP with a cough, cold and post-nasal drip, and bought an annual travel insurance policy the same day. She tested positive for Covid-19 the following day and subsequently cancelled her trip. The FOS did not uphold her complaint, finding it was reasonable for the insurer to conclude that her symptoms at the time of purchase, which proved to be Covid-19, were circumstances that could reasonably have been expected to lead to cancellation.

The practical rule is straightforward: if you are feeling unwell in a way that might affect your ability to travel, purchasing a policy at that point and then claiming for a related cancellation is unlikely to succeed, even if you have not yet received a diagnosis.

Renewed policies are separate contracts

In DRN-5199115, the FOS found in favour of the insurer, Red Sands Insurance Company (Europe) Limited, on the basis that a renewed annual policy and the previous annual policy were separate contracts in their own right, not continuous cover. Because the customer's daughter's illness was known at the time of the renewal, the subsequent cancellation of their travel due to this illness was excluded as a known event under the renewed policy.

This confirms the position set out in most policy wordings: renewing a policy resets the assessment date for known events. If a circumstance has arisen between the original policy start date and the renewal date, it becomes a "known event" for the purposes of the renewed policy.

Strikes and publicly known disruption

The FOS has consistently upheld insurers' decisions to decline claims where strikes or industrial action were publicly known before the policy was purchased or the trip was booked. If you are booking a trip during a period of ongoing or announced industrial action, check carefully whether your policy will provide cover. In most cases, it will not.

Travel insurance complaints at record levels

According to the FOS, travel insurance complaints reached their highest level since the pandemic in the 2023/24 financial year, with 4,466 cases. The FOS has identified failure to disclose pre-existing medical conditions and disputes over known events as among the primary drivers. The FOS urges consumers to check policy terms carefully, understand exclusions, and remember that travel insurance is not private medical insurance.

Notes on this guide

This is general guidance based on a selection of representative UK travel insurance policy terms from leading insurers.

This is a summary of common terms. Always read your specific Policy Wording and IPID document. This guide is for information only and does not constitute financial or legal advice.

This document is based on a detailed, expert review of UK travel insurance policies from March 2026.

Always read your specific policy documents and contact your insurer or the FOS directly if you have a dispute.