Fire Safety in a Multi-Tenant Building: Organising the Landlord-Tenant Interface

Fire safety in a multi-tenant building is an interface task

In a multi-tenant building, fire safety rarely begins with the question of where an extinguisher is mounted. The decisive question is who identifies a deviation, who decides on a measure, who commissions it, and who retains the evidence. Those roles share common areas and escape routes. The building operator responsibility topic area helps turn those touchpoints into a verifiable operating model instead of clarifying duties only after a defect is found.

A sound role matrix starts with actual use and the contract documents, not with blanket blame. Under section 535 BGB, a landlord must provide the rented property in a condition suitable for the agreed use and maintain that condition during the term. It does mean that rooms, shared systems, tenant fit-outs, and known defects must be recorded separately before anyone accepts or passes on a task.

For workplaces, a second layer applies: the employer organises protection for its employees in the areas it operates. Section 4 of the official Workplace Ordinance addresses, among other things, maintenance of emergency lighting, fire alarms, and extinguishing equipment, as well as keeping traffic routes, escape routes, and emergency exits clear. It must make clear which tenant checks its workplace, how observations from common areas are passed on, and what happens when a defect cannot be remedied immediately.

The role matrix: area, trigger, decision, evidence

In practice, a matrix with four columns works well: area or system, triggering event, responsible role, and evidence. For a fire door, the trigger may be a blocked closing area, a maintenance notice, or an observation during an inspection. The matrix then sets more than a contact person. The guide to documented delegation of duties in facility management explains why selection, briefing, and oversight belong together when tasks are delegated. A name without that chain is not yet a reliable organisation.

Common areas deserve their own section because many assumptions collide there. Owners and tenants shape those areas in different ways. A deviation in a stairwell can still affect both sides. Link the matrix to an inspection calendar for assets, state rules, and responsible roles. It makes visible which recurring check is planned, which maintenance provider is involved, and which open observation must be resolved before the next appointment.

The matrix should also distinguish reporting, deciding, and performing. Reception can report a blocked door without deciding on a technical repair. A property manager can approve work without performing the functional check. A specialist provider can issue an inspection report without organising how people work with a temporarily restricted escape option. This separation prevents silent handovers and preserves traceability.

For tenants, a short and dependable interface description is more valuable than a long policy in a folder. It should state which areas they keep clear each day, which alterations or storage arrangements they clear in advance, what emergency information their employees receive, and where they report a defect. In return, the operator can define when reports are acknowledged, how urgent cases escalate, and what closure feedback the tenant receives.

AI-generated

Keep evidence so it helps when a deviation occurs

Fire-safety evidence is not an end in itself. It must help a person answer quickly: what was the condition, who made the observation, what immediate control applied, who owned the next step, and how is closure recognised? The building operator responsibility framework provides a common language for this. For each entry, define location, owner, date, risk, and closure feedback. Loose emails or photos without context make later decisions harder.

For assigned tasks, the record should not end with the work order number. Record why the role is suitable, what briefing or property information it received, which check points apply, and who reviews the result for plausibility. The detailed practice on selection, briefing, and oversight of appointees shows how delegation can be designed as a controlled process rather than a one-time signature. The organisation can then explain how a task was actually managed even when personnel change.

Not every finding is a repair order. Some entries require an immediate control, others a scheduled action, and others specialist clarification with the landlord, tenant, or fire-safety planner. That is exactly why evidence needs a status and an escalation threshold. Use labels such as open, temporarily controlled, commissioned, under review, and closed, together with a date and owner. Closure without a verification note or feedback to the reporting area merely creates a new information gap.

Routines for escape routes, plant rooms, and common areas

The most common daily weakness is not missing knowledge but missing repetition. Daily examples include stored material, held-open doors, and plant-room storage. The official requirement to keep escape routes clear requires escape routes and emergency exits to be kept clear at all times. Translate that into short, observable routines: who looks at which area and when, what counts as a deviation, and which immediate control may be applied without further approval? A rule becomes effective only when it appears in daily work.

ASR A2.2 is an important guide for measures against fires in workplaces. It does not replace a building-specific assessment. It does help avoid treating instruction, alarms, extinguishing equipment, escape routes, and organisational measures as separate topics. Do not therefore plan inspections only around maintenance dates. Add typical use situations: deliveries, fit-outs, events, evening operations, and changes of service providers.

Practise escalation before it is needed under time pressure

An escalation chain should work without interpretation. For every critical deviation, it needs at least a reporting route, a deputy, a decision threshold, and feedback to the originating area. Test the chain with a realistic scenario, such as a blocked escape door shortly before an event. Who may stop use, who informs tenants or visitors, who commissions the specialist, and who documents release for use again? The scenario reveals interfaces.

Exercises do not need to be dramatic to become useful. A twenty-minute tabletop session with leasing, site management, reception, and one tenant can check whether numbers, keys, access, and communication templates are correct. Document not only the outcome but also the open assumption behind each decision. This creates a small improvement plan with an owner and date. Repeating the same exercise after a fit-out or staffing change turns a one-off alignment into a dependable operating routine.

Secure interfaces during fit-out, contractors, and daily operations

Fit-outs and contractor work often change the risk picture faster than documentation changes. Before work begins, clarify affected areas, free passages, access control, and immediate reporting. The inspection calendar for assets and responsible roles can act as the shared cadence: add temporary measures, contact roles, and a removal or acceptance date. A provisional solution then does not disappear from view when the project team moves on.

Communication with tenants also needs a fixed cadence. Do not merely announce restrictions. State the concrete action: do not block access, do not wedge doors, report a defect with location and photo, and use the agreed route in an emergency. Good notices name a contact and period of validity. They also avoid legal remote diagnoses. When the technical or building-law assessment is open, secure the area and involve the qualified party instead of improvising a binding statement.

AI-generated

Build a reliable starting point in 30 days

Start with a limited estate, for example one building and its common areas. First record recurring conflict points and existing evidence. Then choose three to five critical scenarios, assign reporting, decision, performance, and closure for each, and test the chain once. Only then is it worth extending to further properties. This approach creates visible progress without requiring perfect complete documentation as the starting condition.

Training does not replace specialist planning or an authority inspection. Its role is to ensure that involved people understand the same triggers, terms, and escalation routes. The building operator responsibility overview shows how role knowledge can connect to documented processes. Build short learning units from real building scenarios and then test not only knowledge but a concrete action: recognise a defect, report it correctly, secure the area, and follow closure.

Sources and scope

This article is an organisational aid, not legal advice or fire-safety engineering. The specific lease, use, technical system, applicable state building code, and any authority requirements remain decisive. For the workplace-related duties and fire measures mentioned here, the official Workplace Ordinance and BAuA rule ASR A2.2 were used. When in doubt, owners, operators, and tenants should involve the qualified specialist side early.