Why Corporate Businesses Must Start Preparing for Martyn’s Law

The Terrorism (Protection of Premises) Act 2025—more commonly known as Martyn’s Law—will introduce new legal responsibilities for organisations responsible for certain publicly accessible premises and events.

Named in memory of Martyn Hett, one of the 22 people killed in the Manchester Arena attack, the legislation aims to ensure businesses are better prepared to protect employees, visitors and members of the public in the event of a terrorist incident.

Although Martyn’s Law is not yet in force, the Government has published statutory guidance and confirmed an implementation period of at least 24 months from Royal Assent on 3 April 2025. Organisations likely to fall within its scope should use this time to understand their responsibilities and begin preparing. Government guidance makes clear that businesses may wish to start considering the requirements before the legislation formally commences.

Which organisations will be affected?

Martyn’s Law does not automatically apply to every corporate office or workplace. It principally applies to qualifying premises used for activities listed within the Act, where members of the public may be present.

The legislation establishes two principal tiers:

  • The standard tier applies to qualifying premises where between 200 and 799 people, including employees, may reasonably be expected to be present at the same time.
  • The enhanced tier generally applies where 800 or more people may be present at the same time.

Qualifying public events attended by 800 or more people may also come within the enhanced requirements where entry controls are in place.

Corporate groups operating shops, hotels, leisure facilities, conference venues, healthcare environments, visitor attractions or other publicly accessible locations should therefore assess each site individually. A single organisation may be responsible for several premises, but the risks and necessary procedures may differ from one location to another.

Why businesses should act now

Preparing for Martyn’s Law should not be viewed simply as another compliance exercise. At its heart, the legislation is about ensuring organisations can respond quickly and effectively when lives may be at risk.

Businesses need to consider how they would:

  • Evacuate people away from danger.
  • Move people to a safer area within the premises—known as invacuation.
  • Lock down all or part of a building.
  • Communicate clear and timely information during an incident.

For enhanced-tier premises and qualifying events, organisations will also need to consider appropriate measures to reduce their vulnerability to attack and limit the risk of physical harm.

This requires more than producing a written policy. Businesses must understand who is on their premises, control how different areas are accessed and ensure that accurate information is available to those managing an emergency.

Knowing who is on site

One of the greatest challenges during any emergency is establishing who is actually present.

Employees may work across different locations, while contractors, agency workers and visitors may arrive and leave throughout the day. Paper visitor books and disconnected systems can quickly become inaccurate, particularly across large or multi-building sites.

Ceequel Visitor Management System provides a controlled and auditable process for managing visitors and contractors. Visitors can be pre-registered before arrival, issued with appropriate site information and recorded as they enter and leave.

Contractor documentation—including RAMS, Public Liability Insurance and other compliance records—can also be managed within the system, helping organisations strengthen their wider site-control processes.

Controlling access across the organisation

Ceequel Access Control allows businesses to manage who can enter particular buildings, rooms and controlled areas.

Access permissions can be defined by person, department, role, location or time of day. Lost cards and fobs can be cancelled immediately, temporary permissions can expire automatically, and facial recognition templates can be removed from connected devices centrally.

For organisations with multiple locations, access policies can be managed from a central point while still allowing authorised local administration. This helps create consistency across a corporate estate without ignoring the individual operational requirements of each site.

When planning for Martyn’s Law, access control can also form part of a wider strategy for evacuation, invacuation and lockdown. Depending upon the organisation’s agreed procedures and system configuration, doors and controlled areas can be managed to help direct people away from danger or prevent access to higher-risk areas.

Providing accurate emergency attendance information

Ceequel Fire Register brings employee, visitor and contractor attendance information together to provide an accurate, real-time view of who is believed to be on site.

The system can identify which building or area an individual last entered and provide emergency information to authorised personnel. Photographs can also assist with identification, while mobile access allows information to remain available away from a fixed reception desk or computer.

Although originally designed to support fire evacuation, accurate attendance information can form an important part of broader emergency preparedness. Knowing who may still be inside a building, who has arrived as a visitor and where people were last recorded can support a more informed response.

Bringing systems and procedures together

No single piece of software can make an organisation compliant with Martyn’s Law. Legal responsibility remains with the organisation or individual responsible for the qualifying premises or event.

Technology can, however, provide the visibility, control and evidence needed to support well-designed procedures.

By integrating Ceequel Access Control, Ceequel Visitor Management System and Ceequel Fire Register, organisations can create a more joined-up approach to:

  • Managing employees, visitors and contractors.
  • Controlling access to buildings and restricted areas.
  • Maintaining real-time attendance information.
  • Supporting evacuation, invacuation and lockdown procedures.
  • Managing multiple locations through a central system.
  • Demonstrating that security and emergency processes have been properly considered.

Preparation should begin before the deadline

Martyn’s Law represents an important change in how organisations approach public protection. Those that begin preparing now will have time to assess their premises, identify weaknesses, review responsibilities and test their procedures properly.

The objective should not be to do the minimum necessary to satisfy legislation. It should be to create an environment in which employees, visitors, contractors and members of the public are better protected—and where those responsible for managing an emergency have accurate information when every second matters.

Ceequel can assist organisations on that journey by bringing access control, visitor management and real-time emergency attendance information together within one integrated platform.

Why ERP Shop Floor Data Collection Falls Short of Continuous Improvement

Many ERP systems now include some form of Shop Floor Data Collection (SFDC). On the surface, this appears to give manufacturers everything they need: production quantities, labour time, machine status, scrap levels and completed works orders.

However, collecting production transactions is not the same as providing the insight required for continuous improvement.

ERP systems are designed primarily to manage business processes. They are excellent at controlling works orders, inventory, purchasing, scheduling, costing and financial reporting. Their shop-floor functionality is generally designed to feed these processes with accurate production data.

Continuous improvement requires something different.

ERP Records What Happened

Most ERP-based SFDC systems concentrate on recording key transactions, such as:

  • When a works order started and finished
  • How many units were produced
  • The quantity of scrap recorded
  • The labour hours allocated to the job
  • Whether the order was completed
  • What materials were consumed

This information is important, but it usually provides a high-level summary rather than explaining what happened throughout the production process.

A works order may have taken two hours longer than planned, but why?

Was it caused by a machine stoppage, a shortage of material, an extended changeover, a quality problem, an unavailable operator or repeated short interruptions?

The ERP system may show the variance, but it rarely captures the operational detail needed to understand and eliminate its cause.

Continuous Improvement Needs Greater Detail

Continuous improvement depends upon identifying patterns, losses and recurring problems. This requires detailed, accurate and timely information from the shop floor.

Manufacturers need to understand:

  • Why machines and production lines stopped
  • How often short, unplanned stoppages occurred
  • Whether delays were caused by machines, materials, methods or labour
  • How actual cycle times compared with expected performance
  • Where bottlenecks developed
  • Why output varied between shifts, teams or products
  • What caused scrap, rework or quality failures
  • How long changeovers actually took
  • Whether corrective actions delivered a measurable improvement

Without this level of information, improvement teams are often forced to rely on spreadsheets, handwritten records, supervisor feedback and employee recollection.

By the time the information is reviewed, much of the context has already been lost.

The Problem with High-Level Downtime Codes

Some ERP platforms allow operators to select downtime or loss codes. However, these are often too broad to support meaningful root-cause analysis.

Recording “machine breakdown” does not explain which component failed, what symptoms were observed, whether the same fault has occurred previously or what action was taken to resolve it.

Likewise, “material shortage” does not identify whether the material was unavailable, delivered late, incorrectly located, rejected for quality reasons or supplied in the wrong quantity.

Continuous improvement requires structured data that allows organisations to move beyond identifying the category of a problem and begin understanding its underlying cause.

Small Losses Create a Big Problem

ERP systems are generally designed around significant production events. Yet many of the greatest opportunities for improvement are hidden within smaller, repeated losses.

A production line may suffer dozens of two or three-minute stoppages during a shift. Individually, these interruptions may not appear important enough to record. Collectively, however, they can account for hours of lost production every week.

If these micro-stoppages are not captured, categorised and analysed, they remain invisible. The ERP system may simply show that the works order took longer than expected, without revealing the repeated events responsible for the lost time.

Reporting Is Not the Same as Analysis

ERP reporting typically answers business questions such as:

  • Was the order completed?
  • How much did it cost?
  • Was the required quantity produced?
  • How much material was consumed?
  • What was the labour variance?

Continuous-improvement teams need to ask different questions:

  • Where are we losing productive time?
  • Which problems occur most frequently?
  • Which issues have the greatest impact?
  • Are the same faults recurring?
  • Which shift or product experiences the most variation?
  • Did the corrective action work?
  • What should we improve next?

Answering these questions requires data to be explored by machine, production line, product, shift, employee, reason, duration and frequency. It also needs to be presented in a way that helps managers recognise trends and prioritise action.

A standard ERP report may present the numbers, but it does not necessarily turn them into actionable operational intelligence.

Real-Time Visibility Matters

ERP information is often reviewed after a shift, production run or reporting period has ended. This is suitable for costing and historical reporting, but improvement opportunities frequently require a much faster response.

Supervisors need to see when performance begins to fall, when downtime is increasing or when a production line is operating below its expected rate. The earlier a problem is identified, the sooner action can be taken.

Real-time operational visibility helps manufacturers prevent a minor issue from becoming an entire shift of lost production.

The ERP Still Has an Important Role

This does not mean replacing the ERP system.

The ERP should remain the central platform for managing orders, materials, stock, schedules and financial information. What it needs is a dedicated operational-intelligence layer capable of collecting and analysing the detailed information that conventional ERP transactions cannot provide.

An effective solution should combine data collected directly from machinery and PLCs with information entered by employees on the shop floor. This creates a more complete picture by capturing both what happened and the operational reason behind it.

The resulting information can then be used to support OEE, downtime analysis, root-cause investigation, DMAIC, Six Sigma and other structured improvement programmes.

From Shop Floor Data to Operational Intelligence

Ceequel® Operational Intelligence goes beyond traditional Shop Floor Data Collection. It provides manufacturers with the detailed, real-time information needed to understand production losses, investigate their causes and measure the results of improvement activity.

Rather than competing with the ERP system, it complements it. Production orders and relevant business data can be shared between the two platforms, while Ceequel® captures the deeper shop-floor detail required by production managers and continuous-improvement teams.

Because collecting more data is not the objective.

The real objective is to provide the right people with clear, reliable information that helps them reduce waste, improve performance and make better operational decisions.

An ERP system can tell you what was produced and what it cost.

Ceequel® Operational Intelligence helps explain why performance varied—and what you can do to improve it.