Loopyah Icon

· 21 min read

Martyn's Law: what should UK event organisers prepare for?

Featured image for Martyn's Law: what should UK event organisers prepare for? article

If you run paid events in the UK, preparing for Martyn's Law starts with working out whether the law covers your venue, your event, or both. Then identify who has legal responsibility and compare the relevant requirements with the arrangements you already have. Buying another security service before answering those questions can leave you spending money on the wrong problem.

As checked on 16 October 2026, the main duties for venues and events are not yet in force. The legislation has passed, and official guidance is available, so you can make useful preparations now. You'll need to distinguish what the law will require from what a supplier recommends and what your existing safety arrangements already demand.

For a promoter hiring venues, that distinction matters every time the location or hire agreement changes. The company selling the tickets isn't automatically the organisation legally responsible under this particular Act. Equally, a venue having a security team doesn't settle the question. Let's work through the decisions that affect your next booking, your budget and the people working your event.

What Martyn's Law changes, and when

Martyn's Law is the common name for the Terrorism (Protection of Premises) Act 2025. It concerns preparedness for terrorist attacks at certain premises and events across the UK. The Home Office's overarching factsheet confirms Royal Assent on 3 April 2025 and an expected implementation period of at least 24 months. It also confirms that the operational requirements have not yet commenced. That expected period doesn't establish a fixed commencement date.

The Home Office has already published statutory guidance explaining scope and requirements. You don't need to wait for another summary from a trade association or a supplier to start understanding the law. Read the guidance against your actual business, including the places you hire and the way you use them.

The Security Industry Authority, or SIA, explains its regulatory role and says commencement is expected in spring 2027, with the exact date to be confirmed. Use that expectation for preparation, while checking the official date before making a claim about when a particular duty applies.

Throughout this guide, references to duties describe what covered organisations will need to do when the relevant requirements take effect. Our practical preparation suggestions are actions you can consider now. That timing distinction prevents an internal project plan turning into a claim that your business is already breaching a duty which hasn't started.

Appoint someone to monitor official developments and bring relevant changes into your planning meetings. If several people independently follow different newsletters, you'll eventually have conflicting deadlines in circulation. Record the official source, the date checked and what changed. For events booked well ahead, review the position again before agreeing final operating arrangements. Existing safety, licensing and other applicable obligations still need their own attention during the implementation period.

Check the premises before classifying your event

A useful starting question for a venue is whether it expects to be qualifying premises, and which tier it expects to enter. Ask how it reached that conclusion. A reply about room capacity alone doesn't explain the whole assessment.

The Home Office's premises scope factsheet sets out conditions covering the premises, their use, expected numbers and exclusions. Broadly, standard tier premises have 200 to 799 people reasonably expected together, from time to time. Enhanced tier premises generally reach 800 or more. Staff count, and the other scope conditions still have to be met.

Some premises receive special consideration. Qualifying places of worship and premises used for childcare, primary or secondary education, or further education remain standard tier even where the higher attendance threshold is reached. Don't assume this extends to every educational setting. The treatment of the specific premises matters, including when you hire an unfamiliar building for a commercial programme.

For a touring event business, keep the venue's answer with that venue's booking information. You might run a similar show in a conventional theatre, a hired hall and an outdoor location, yet face different arrangements in each. Reusing the previous promoter's classification without checking the new setting creates uncertainty at the point you're committing money.

Ask for clarification early if the venue has several uses or forms part of a larger site. The statutory guidance includes examples of these situations and the relationship between premises and events. A recurring larger event can affect the premises assessment. Avoid assuming that a venue remains standard tier simply because its ordinary weekday audience is smaller.

The practical output is a reasoned working assessment with an owner. Record any unresolved point and who will resolve it before your planning depends on the answer. If the classification is genuinely disputed, get advice on that particular question. A generic compliance package may never address it.

When an event qualifies separately

There is no standard tier for qualifying events. Events that meet the separate qualifying event conditions face the enhanced requirements. This is where descriptions such as "all events over 200 people" can send an organiser in completely the wrong direction.

The Home Office's event scope factsheet explains the combined criteria. They include public access, an expectation of at least 800 people present together at some point, including staff, and specified checks on entry. The location must not already be enhanced tier premises, and relevant exclusions and special treatment must also be considered. Qualifying events can take place on land without a building.

Entry checks must establish an applicable condition such as payment, a ticket, pass or qualifying membership. A dress code or a search on its own doesn't satisfy that condition. Free ticketed events can qualify too. At premises already in the enhanced tier, the event doesn't become a separate qualifying event, although the premises arrangements still need to cover the activities held there.

Events at the specially treated worship, childcare and education premises described above don't become qualifying events under this route. Check the premises' actual use against the official criteria.

For a mixed event, describe the areas separately before asking for a classification. An open public programme and a controlled ticketed area can raise different questions. Send the assessor a clear description of the boundaries, uses and admission arrangements. A promotional site map may leave out the information they need.

Keep the classification discussion connected to the commercial decision. If you're adding a ticketed evening programme to an existing daytime format, check the consequences while you can still change the brief, staffing agreement and budget. Leaving it until tickets are selling can turn a manageable planning decision into an expensive argument about who agreed to deliver what.

Count the people you expect together

Ticket inventory, tickets sold and the number of people present together answer different questions. Treating them as interchangeable can distort your scope assessment before you have even discussed the security arrangements.

The Home Office's guidance on assessing expected attendance focuses on the greatest number reasonably expected at the same time. Work from a defensible description of how the event operates. An overall weekend sales total doesn't tell you how many people share the site during a particular programme period.

For your preparation meeting, bring the public ticket allocation alongside information about staff and other people working in connection with the event. Ask the person making the assessment to confirm the appropriate counting boundary. Include the evidence and reasoning behind the estimate so someone else can understand it later.

Include volunteers in that discussion. Being unpaid doesn't make a person disappear from the number expected on site in connection with the event. Ask suppliers about their actual staffing plans instead of estimating every contractor's presence from the names printed on the programme.

Consider an illustrative programme with separate daytime and evening sessions. If the daytime audience stays for the evening, your assumption about turnover fails. If the event clears between sessions, you need a reliable basis for that assumption. The timetable, admission conditions and actual operating practice should tell the same story. Don't quietly assume that everyone leaves precisely when a session ends.

Attendance history can inform the conversation, but explain changes that make this event different. A new headliner, a larger ticket allocation or an added public area may make last year's attendance a weak basis for this year's decision. Likewise, the maximum number a building could hold doesn't automatically describe what is reasonably expected under your actual operation.

Avoid designing the ticket allocation around an arbitrary promise to remain below a threshold while overlooking workers or an overlap between audiences. If a genuine operational limit affects your assessment, agree how it will work and who maintains it. The objective is an honest assessment of the event you intend to run, with changes reviewed before they invalidate the assumptions.

Identify the legally responsible organisation

The phrase "responsible person" can be misleading because it sounds like a named employee. Under this law it may be a company or another organisation. Start with control of the relevant premises or event, then identify the people acting for that organisation.

The Home Office's responsible person factsheet distinguishes control of qualifying premises for their relevant use from control of premises for a qualifying event. It also explains that delegating work to a contractor doesn't delegate the responsible person's legal responsibility. Where several parties have relevant control, coordination or cooperation duties may apply in the circumstances set out in the Act.

Read the hire agreement alongside what will actually happen on site. Who controls the premises for the relevant use? What authority does the promoter receive during the hire? Which decisions does the venue retain? The organisation paying a security invoice and the organisation holding legal responsibility aren't necessarily the same.

Bring those questions to the venue before signing a vague clause saying that the organiser handles "all compliance". The contract needs to describe the agreed work, access to information, permissions and costs. A broad sentence doesn't resolve a disputed legal classification or make an impossible delivery arrangement workable.

You can then name an internal project owner who gathers information and chases actions. Keep that administrative role distinct from legal responsibility and any formal senior designation the enhanced requirements call for. A junior producer can coordinate a meeting without acquiring authority to approve expenditure or change venue operations.

One contract discussion concerns changes requested after the original brief. Suppose the venue agrees its arrangements on the basis of a seated performance, then you propose changing the layout for a standing show. Agree who reassesses the changed conditions, who supplies the revised information and how any additional work is approved. The same conversation should cover changes proposed by the venue. You need to hear about something affecting your delivery before the crew arrives to discover it. Record the decision in the event brief and send it to the affected leads. This connects the commercial agreement to delivery and records which assumptions changed and who accepted them.

If the venue says it handles everything, ask what support it needs from you. It may need programme changes, audience information or confirmation that your contractors understand the venue's procedures. If you're responsible for a qualifying event on hired land, establish what cooperation you need from the landowner. Either way, unanswered requests should reach someone who can resolve them before the event agreement becomes final.

Prepare procedures people can understand

The standard duty factsheet explains the public protection procedures required, as appropriate and so far as reasonably practicable. These concern evacuation, invacuation, lockdown and communication. In plain language, they address moving people out of danger, moving them to a safer place within the premises or event, securing the location, and communicating instructions. They concern suspected or actual attacks at the location or in its immediate vicinity. Relevant staff must understand their role in carrying them out.

The same factsheet makes clear that there is no statutory requirement to complete a particular training course. The procedure requirements don't impose a universal purchase of equipment or physical alterations either. Start by understanding what your setting needs and what you already have available.

For the event team, the useful preparation is checking understanding. Ask a ticketing supervisor to explain where their instructions come from and how they contact the relevant lead. Ask the incoming shift how they find the current briefing. You'll learn more from those answers than from a folder full of documents nobody has opened.

Keep event instructions consistent with the venue's established arrangements. If the production briefing and the venue briefing use different names for the same space, correct that before people arrive. If a contractor hasn't received the instructions relevant to its work, resolve the handover with its supervisor.

Our guide to an event security plan develops the wider operational agreement between the organiser, venue and providers. Use that work to identify the people and handoffs involved here. Martyn's Law preparation should improve the arrangements your team uses, rather than produce a separate set of instructions that contradicts the first one.

Understand what the enhanced requirements add

The enhanced duty factsheet describes additional public protection measures, documentation and, where the responsible person is an organisation, designation of a senior individual. The measures cover monitoring, movement, physical safety and security, and information security. They must be appropriate and implemented so far as reasonably practicable. The senior individual needs sufficient authority and influence to support compliance, rather than a title assigned to whichever employee has time.

Enhanced requirements are a reason to examine the event in more detail, not an instruction to buy every security product offered to you. Ask anyone recommending a purchase which identified problem it addresses, how it would work with your current arrangements and what the ongoing delivery requires.

For example, a tool that creates another alert still needs someone able to receive, interpret and act on that alert. Ask who performs that work during the event and whether the proposed contract covers it. If the answer is your already occupied operations lead, the quote hasn't yet explained how delivery will work.

Documentation should explain the reasoning behind the procedures and measures and how they meet the relevant objectives. Prepare by identifying who can supply the information, who checks it and who keeps it current. A security provider may contribute specialist material, while the venue supplies information about the building and the event team confirms how the space will be used.

Follow the current official instructions for submission when those requirements take effect. Don't treat a supplier's completed template as proof that every obligation has been discharged. The responsible organisation needs to understand what has been documented, what has actually been implemented and which planned actions remain outstanding.

Prepare for notification without inventing a filing process

Notification to the SIA will apply across standard tier premises, enhanced tier premises and qualifying events. It is separate from having the right procedures in place. Completing a planning document for your venue doesn't automatically tell the regulator who is responsible.

Prepare by agreeing who will manage the notification for the responsible organisation and who will check the information. That person needs access to current details and a way to learn when responsibility or previously supplied information changes. If the administrative task goes to a coordinator, identify the manager who can resolve uncertainty rather than making the coordinator guess.

For a promoter working across different venues, avoid assuming that one organisational record covers every location and event in the same way. Confirm the applicable requirements against the official instructions. Keep your venue correspondence easy to retrieve so the person handling notification doesn't need to reconstruct the hire arrangements from an old inbox.

As of this review, the SIA says it is building an online portal and will announce when it opens for general use. Use the official service when available and check its current instructions. Agree who monitors those announcements, then put the relevant action into your planning calendar. That is more useful than circulating an unverified submission deadline through the production team.

If a venue is handling notification, your preparation record should say so and identify the contact who confirmed the arrangement. If your company needs to handle it, record who will do the work. Either answer should follow the responsibility assessment already made, so everyone is preparing around the same understanding.

Budget against identified work

Once you understand the likely classification and responsibilities, compare the requirements with your existing arrangements. This is the point at which a budget becomes useful. Before that, a single line labelled "Martyn's Law" tells you almost nothing about the work it is supposed to fund.

Ask for costs against specific activities and agreed deliverables. Separate planning time, staff instruction, event delivery and any justified physical work. Identify which items the venue already provides under the hire and which require an additional agreement. Otherwise, both organisations can budget for the same activity while leaving another activity uncovered.

The official guidance explains "reasonably practicable" as a context dependent judgment involving the protective objective and the cost, time and difficulty of implementation. Use that discussion carefully. A limited budget doesn't automatically dispose of an issue, and an expensive proposal isn't automatically the appropriate answer. Ask what options were considered and why the proposed approach fits this event.

Our event risk assessment guide can help organise the wider discussion about hazards, existing arrangements and assigned actions. Keep the specific Martyn's Law assessment connected to the event's current information, while preserving the distinction between different legal requirements.

Be equally clear about preparation costs and recurring costs. A review before the next booking may be an occasional task; staff time to deliver an agreed measure during every event needs to appear in the operating budget. If the venue charges separately, establish what triggers that charge and what changes could increase it.

When a supplier says a service is compulsory, ask for the official requirement supporting that claim. The answer may reveal a genuine event specific need. It may also reveal that the supplier has described its preferred service as a universal legal duty. Resolve that difference before you approve the purchase.

Keep ticketing and security responsibilities clear

Ticket records can help describe your planned audience. They don't independently establish who is physically present, and scanning a ticket doesn't demonstrate compliance with public protection duties. The people assessing attendance and designing arrangements need to understand what the available records actually measure.

Discuss the event's admission process with the venue and provider before deciding that an existing check solves a different problem. Booking support, ticket validation, crowd management and security decisions can involve different staff and different authority. The plan should explain the connection between those jobs without expecting the ticket desk to improvise specialist judgments.

For a change in ticket allocation, agree who reviews the consequences before the extra tickets go on sale. A marketing decision can affect the assumptions used by the operations team. If the sales team and production team hold different versions of the event brief, fix the information flow while there is still time to make a considered decision.

Check emergency communication with the same care. An attendee email or app message may help deliver routine information, but ask what happens when a person cannot receive or understand it. The event accessibility checklist is useful for reviewing that wider attendee journey. Bring the relevant access arrangements into the conversation with the venue and the people delivering instructions.

Public arrival information and internal operational material serve different purposes. Tell attendees what they need to prepare for their visit, where to obtain help and how to follow instructions on site. Keep sensitive internal information restricted to those who need it for their work. Review distribution when an outside supplier or temporary member of staff joins or leaves the project.

Make preparation part of staff induction

A briefing needs to reach the people actually working the event, including replacements and later shifts. Sending a document to the supplier's office doesn't tell you whether the supervisor on site has received the relevant instructions. Ask how that supplier briefs its team and how you will confirm the handover.

ProtectUK offers free counterterrorism awareness learning. Consider it alongside the instructions people need for their specific roles. General awareness can support understanding, but a course certificate doesn't tell a worker what has been agreed at this venue or whom to contact on this shift.

Use a short discussion with the relevant leads to test an ordinary coordination problem. Suppose a replacement contractor arrives after the main briefing. Ask who receives them, checks which instructions apply and confirms that they understand the reporting arrangements. You don't need to invent a dramatic attack scenario to discover that nobody owns this handover.

Include deputies in that discussion. A plan depending on one person answering every call is fragile during breaks, shift changes and routine competing demands. The deputy needs enough information and authority to perform the agreed role, and the other teams need to know when that person takes over.

After the discussion, assign the corrections to named people and confirm completion. If an instruction is unclear, change the instruction and circulate the current version. Recording that confusion occurred is useful only if the next worker receives something clearer. Keep the session focused on the jobs people are expected and equipped to perform.

Keep records that explain your decisions

Start a working preparation record containing the scope assessment, evidence behind expected attendance, identified responsible organisation and outstanding questions. Add agreed actions and the person resolving each one. This is a suggested management approach, rather than a claim that every tier requires the same compliance document.

Where enhanced documentation requirements will apply, develop the formal record against the current official guidance. Keep the preparation notes useful to the people producing it. They should be able to distinguish a confirmed fact from a proposal, an implemented arrangement from a planned change, and a settled responsibility from an open question.

The SIA's September 2026 preparation update explains that it was developing notification arrangements and optional templates. That is another reason to keep checking the official position before submission. A preparation document drafted during implementation shouldn't preserve an outdated process simply because the team approved it earlier.

Decide what triggers a review within your business. A different venue, changed admission arrangements, an altered programme or a new hire agreement can affect previous assumptions. A review date alone is a weak safeguard if the event changes substantially before that date arrives.

For repeat events, retain useful reasoning and update the facts. Copying last year's answer without its supporting assumptions makes the document harder to challenge. The incoming producer needs to see why the decision was made and whether those conditions still apply. Keep access controlled, especially where records include sensitive information about the premises or its operation.

Work through your next venue booking

Imagine you're booking a paid evening performance in a venue you haven't used before. Your producer has a provisional audience plan, the venue has sent a standard hire agreement, and the security provider has offered a package. Treat this as a preparation example, not a legal classification of an unnamed venue.

The first conversation is with the venue about its expected status and the basis for that assessment. Ask whether its wider programme affects the answer. Then establish the relevant responsible organisation and what information or cooperation each side needs. If someone says the promoter is responsible, ask them to explain that conclusion against control of the relevant premises or event.

Next, reconcile the audience plan with the people working on site and the way the programme runs. Confirm which facts support the estimate and who reviews later changes. Only then compare the proposed security package with the identified work and the venue services already included in your hire.

Finish the meeting with decisions people can act on. The venue confirms its arrangements and supplies the relevant information. Your producer corrects the event brief and routes unresolved scope questions to the appropriate adviser. The provider explains any additional work it recommends, including delivery and cost. Your internal owner records what remains open and when it must be resolved. Before the final commitment, that owner checks the answers have arrived and updates the people relying on them, including the colleague approving the event budget.

That's a useful result even before the operational duties commence. You understand the booking well enough to agree the work, price it honestly and brief the people delivering it. Start with that conversation for the next event in your calendar, using the official guidance current at the time.

Loopyah Icon

Author: By the Loopyah Content Team

The Loopyah Content Team shares expert insights, practical guides, and industry updates to help event organizers create unforgettable experiences and stay ahead in the event planning world.