Incident Management for Commercial Buildings: A Guide for CRE Teams
Commercial buildings are not simple environments to manage. A single mixed-use development might house dozens of tenants, hundreds of contractors, thousands of daily visitors, and a security or facilities team responsible for all of it. When something goes wrong, the response has to be fast, structured, and auditable.
Incident management for commercial buildings sits at the intersection of duty of care, regulatory compliance, and operational efficiency. Get it right and you protect people, assets, and reputation. Get it wrong and the consequences are measured in liability, insurance claims, and loss of tenant confidence.
This guide covers what effective incident management looks like in a CRE context, the incident types you need to be prepared for, the responsibilities that fall to the landlord versus the occupier, the compliance obligations that apply, and the operational practices that separate reactive teams from resilient ones.
To find out more about Incident Management, read our Complete Guide to Incident Management.
Why incident management is critical for commercial buildings
A modern incident management system acts as the digital backbone of an effective property operations strategy. It ensures incidents are captured, classified, escalated, and resolved in a consistent, auditable, and efficient manner.
Key benefits include:
- Faster response times to safety, security, and facility incidents
- Improved coordination between on-site teams, property managers, and external responders
- Structured processes that ensure Emergency Operating Procedures (EOPs) and Standard Operating Procedures (SOPs) are followed
- Clear audit trails that support compliance and risk governance
- Data-driven decisions powered by real-time analytics and historical trends
Without a centralised system, incident reporting is fragmented, communication is delayed, and opportunities for improvement are often lost.
What incident types do commercial buildings face?
Before building a response model, it helps to map the terrain. Commercial buildings face a broader and more complex incident landscape than single-occupancy premises. The landlord is responsible for common areas, plant rooms, structure, and shared infrastructure, but incidents do not respect those boundaries neatly.
The main categories CRE teams need to be prepared for:
Security incidents
- Unauthorised access to common areas, plant rooms, or restricted floors
- Theft in car parks, lobbies, or loading bays
- Antisocial behaviour in shared spaces
- Contractor identity disputes and tailgating
- Aggression or threatening behaviour toward staff or tenants
Health and safety incidents
- Slip, trip, and fall incidents in common areas (RIDDOR-reportable if serious)
- Near-misses during contractor works
- Plant room accidents
- Manual handling injuries among FM staff
- Lone worker safety incidents during out-of-hours patrols
Facility and maintenance incidents
- Lift entrapment
- HVAC failure affecting tenant comfort or data centre cooling
- Water ingress or burst pipes
- Power outages affecting common areas or critical systems
- Fire suppression system activations
Environmental and emergency incidents
- Fire alarm activations – false and confirmed
- Gas escapes
- Flooding – whether from external weather events or internal plant failure
- Structural damage following extreme weather
Tenant and contractor-related incidents
- Tenant disputes in common areas
- Contractor access conflicts or on-site damage caused by third parties
- Delivery disputes at loading bays
- Incidents during fit-out or refurbishment works
Regulatory trigger incidents
Some incidents require formal notification to external bodies within defined timeframes. These include RIDDOR-reportable injuries (reported to the HSE), incidents triggering insurance notification obligations, and, for higher-risk buildings, notifications to the Building Safety Regulator under the Building Safety Act 2022. An incident management system with automated escalation rules is the most reliable way to ensure these obligations are met. See the compliance section below.
Best practices for incident management in commercial buildings
1. Immediate, mobile-first reporting
Delays in incident reporting increase risk and reduce your ability to respond effectively. Paper-based logging and retrospective reporting are not viable in a building where incidents happen around the clock across multiple floors, plant areas, car parks, and common spaces.
A security officer patrolling a 200,000 sq ft mixed-use scheme cannot return to a control room to log every incident. Mobile capture at the point of occurrence, with photo or video evidence attached, is the operational baseline. Zinc customers have moved from paper-based logging to mobile-first reporting and reduced average reporting time significantly, with incidents captured in the field rather than reconstructed hours later.
Equip frontline staff and contractors with mobile tools that support one-tap reporting and media uploads. Aim for same-hour notification for all high-priority incidents.
2. Standardised classifications across your portfolio
Consistent language is essential to consistent response. A shared taxonomy means incidents across sites can be compared, escalation rules can be applied reliably, and portfolio-level reporting is meaningful.
If you manage 15 properties across different FM contractors, inconsistent terminology makes portfolio-level analysis meaningless. One contractor’s ‘security breach’ is another’s ‘access control incident’. A taxonomy agreed at portfolio level and configured centrally in your incident management system removes this ambiguity.
Define and enforce standard categories, for example, ‘unauthorised access’, ‘HVAC failure’, ‘slip hazard’, ‘fire alarm activation’, across all properties and all contractors operating within your estate.
3. Automated escalations and notifications
Manual routing of incidents wastes time. In a commercial building, the right escalation path depends on incident type, severity, time of day, and location, not on whoever happens to pick up a phone.
A lift entrapment at 11pm requires immediate escalation to the on-call FM manager and the lift maintenance contractor, not an email picked up the next morning. A water leak in a server room needs a different escalation chain to a water leak in a ground-floor toilet. Your incident management system should enforce these distinctions automatically.
Configure rules within your system to escalate based on severity, time of day, and location. For critical incidents, alerts to security, facilities, and senior management should trigger within minutes, not after a chain of manual calls.
4. Real-time collaboration and shared visibility
CRE incident response rarely involves a single team. A typical response might require co-ordination between the landlord’s building management team, the appointed FM contractor, the security provider, a specialist contractor, and the affected tenant, simultaneously.
A centralised platform with live updates ensures all stakeholders see the same picture. Zinc customers have reported significant reductions in downtime and duplicated effort when moving to a single shared incident log with real-time status updates visible to all relevant parties, replacing email chains and phone calls as the primary coordination mechanism.
Ensure that responders, managers, and relevant tenants can see real-time updates without relying on email. Assign tasks and track their completion within the same system.
5. Analytics-driven prevention and KPI tracking
Effective incident management is not just about responding, it is about learning. Analysing patterns allows teams to fix root causes and reduce repeat incidents across the portfolio.
Track key metrics including:
- Average time to resolution by incident type
- Percentage of incidents escalated automatically versus manually
- Recurring incidents by location, type, and time of day
In a CRE context, recurring incident patterns often point to structural or operational issues, a particular building entrance generating repeated unauthorised access incidents, for example, or a specific contractor triggering disproportionate near-miss reports. Quarterly reviews against these metrics should feed directly into your asset management and contractor management decisions.
6. Structured post-incident reviews
After-action reviews turn every incident into a learning opportunity. Many teams skip this step due to a lack of structure, the incident is closed, the team moves on, and the same issue recurs six months later.
Use your incident management system to generate post-incident timelines and host structured reviews within a week of significant incidents. Capture key learnings, assign clear action items, and track their completion. For RIDDOR-reportable incidents or Building Safety Act notifications, a documented review process also supports your compliance obligations.
Apply this approach consistently. The investment is small. The value compounds.
7. IoT and sensor integration for proactive alerting
Sensor-based alerts can identify issues, water ingress, temperature spikes, access control anomalies, before they escalate into reportable incidents. When integrated into your incident management system, they enable a proactive rather than reactive model.
Connect your system with building management systems (BMS), access control, and environmental sensors. Use real-time triggers to automate alerts and initiate response workflows before a member of the FM team has seen anything on the ground. Zinc customers have used integrated sensor alerts to contain leaks within 30 minutes, avoiding multi-floor damage and major tenant disruption.
for more information on what Zinc’s Incident Management system can do, visit our Incident Management page.
Landlord and occupier responsibilities: where does incident management sit?
This is one of the most common sources of confusion, and dispute, in commercial property operations. Responsibility for incident management in a commercial building is not held by a single party. It is divided between the landlord and the occupier, with the dividing line determined by the lease, the nature of the incident, and the location in which it occurred.
As a general principle:
- The landlord is responsible for incidents in common areas, plant rooms, the structure, the building envelope, and shared infrastructure
- The occupier is responsible for incidents within their demised premises
- Grey areas include loading bays, car parks, and shared amenity spaces, responsibility here often depends on the lease terms
In practice, incidents frequently straddle this boundary. A contractor working in a tenant’s demised space causes damage to a shared riser. An HVAC failure in the plant room causes overheating in multiple tenants’ floors. A visitor is injured in a lobby that straddles landlord and tenant territory.
The implications for incident management are significant. Landlords and occupiers both need a clear, contemporaneous record of what happened, who was notified, and what actions were taken, particularly where liability is later disputed. A shared incident management platform, or a clear data-sharing arrangement between separate systems, removes ambiguity and provides the audit trail both parties need.
For larger portfolios, consider whether your incident management system can be configured to distinguish landlord-reported incidents from occupier-reported incidents, while giving both parties visibility of incidents that affect them.
Compliance obligations: what CRE teams need to know
Incident management in commercial buildings is not just an operational matter. Several statutory frameworks impose specific obligations on how incidents are recorded, reported, and managed, with legal consequences for non-compliance.
RIDDOR – Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013
Employers and those in control of premises, which includes landlords of commercial buildings, must report certain workplace incidents to the Health and Safety Executive (HSE) within defined timeframes. Reportable incidents include work-related deaths, specified injuries, over-seven-day incapacitation injuries, occupational diseases, and dangerous occurrences. An incident management system with automated escalation rules is the most reliable way to identify RIDDOR-reportable incidents at the point of logging and trigger the correct notification workflow.
The Building Safety Act 2022
For higher-risk buildings, broadly, residential buildings of 18 metres or more in height or with seven or more storeys, the Building Safety Act 2022 introduced specific obligations to the Building Safety Regulator (BSR). These include requirements to maintain a golden thread of building information and to report prescribed occurrences that could affect the structural integrity or fire safety of the building. CRE landlords with mixed-use portfolios that include residential components need to be clear on which buildings fall within scope and ensure their incident management processes support the required reporting obligations.
Insurance notification obligations
Most commercial property insurance policies require incidents above a certain value or severity threshold to be notified to insurers within a defined period, often 24 to 48 hours. Failure to notify can affect the validity of a subsequent claim. A complete, timestamped incident record generated automatically by your incident management system is the most straightforward way to meet this obligation and support the claims process.
Martyn’s Law (Counter-Terrorism and Security Act 2025)
For CRE buildings with publicly accessible ground-floor uses, retail, food and beverage, leisure, event spaces, the Protect Duty introduced by Martyn’s Law imposes obligations to put in place security measures and procedures proportionate to the venue’s capacity tier. Incident management processes form part of the required preparedness framework. CRE teams with publicly accessible occupiers should ensure their incident management system supports the documentation of security procedures and incident logs that demonstrate ongoing compliance.
For more information on Martyn’s Law, read our article: Understanding Martyn’s Law.
Zinc: built for CRE incident management
Managing incidents across a commercial property portfolio involves more variables than most incident management tools are designed for. Multiple buildings. Multiple contractors. Split responsibilities between landlord and occupier. Regulatory obligations that vary by building type and use. Zinc is built for this complexity.
Where a single-site security team needs a simple reporting tool, a CRE portfolio needs a system that can be configured by building type, escalation path, and user role, while giving portfolio managers a consolidated view across all properties. Zinc provides both: granular control at building level, and clear oversight at portfolio level.
With Zinc, CRE teams get:
- Mobile-first incident capture with rich media support
- Automated workflows for escalation and response
- Real-time dashboards for live status tracking
- Post-incident review tools with built-in analytics
- Integration with access control, BMS, and IoT systems
- Customisable taxonomies tailored to your building types and contractor structure
Zinc is trusted by leading real estate organisations across the UK to manage incidents every month, improving speed, accuracy, and confidence across portfolios.
Building resilience into your operations
In a landscape where tenant expectations are rising and operational risks are multiplying, structured incident management is no longer optional, it is foundational to how a well-run commercial building operates.
The teams that handle incidents well are not the ones that respond fastest in the moment. They are the ones that have invested in the right processes, the right systems, and the right visibility, so that when something happens, the response is structured, compliant, and consistently executed regardless of who is on shift.
Want to streamline incident response and safeguard your portfolio? Book a demo with the Zinc team.
+44 (0)20 3989 4859 
info@zinc.systems 
