When to use it
A critical service fails or repeatedly degrades.
Property decision guide
Critical Property Service Outage Coordination
An outage plan connects the affected service, the people relying on it and the person authorized to arrange a safe response. It should work when the usual manager, vendor or communication channel is unavailable.
Identify the service impact and qualified responder
Record what is observed, the time reported, affected areas and current uncertainty. Escalate an immediate danger or entrapment through the relevant emergency response channel. Keep technical diagnosis, isolation and restart decisions with the qualified responder; a coordination guide does not authorize staff to operate unfamiliar equipment.
Use the asset register to identify the equipment, current service provider, response contact, access sponsor and escalation route. Link the responder to known service history. Separate a confirmed fault from a resident’s description or a monitoring alert so the record does not turn an untested explanation into a diagnosis.
Organize interim service around actual needs
Consider the users and functions affected: mobility, essential water service, controlled entry, deliveries and scheduled work. Assign someone to coordinate support requests through a restricted channel. Collect only information needed for the response and share it with the authorized recipient.
Document the interim arrangement, its limits, approval and review point. Confirm the relevant responder’s instructions before implementing a workaround. A temporary measure should have an owner and end condition, especially when a prolonged outage changes how residents enter or use the building.
Communicate known facts and the next update
Issue a concise notice with affected service and area, current instructions, support contact and next update time. Distinguish an estimate from a confirmed restoration time. Repeat messages through the appropriate alternate channel if a portal, power supply or internet connection is also affected.
Maintain one incident timeline for responder arrival, instructions, approvals, repair milestones and notices. Record why an expected completion changed. This helps the board understand the operational impact and prevents conflicting updates from separate participants.
Require restoration evidence and follow-up
Record the qualified responder’s release or test evidence appropriate to the system, then verify the service from the user’s perspective. The completed repair invoice and restored service are separate evidence items. Keep any operating restrictions visible in notices and the maintenance record.
Review repeat failures against service history, maintenance tasks and replacement plans. Assign corrective work and track it after the incident closes. Hypothetical example: an elevator returns to service after repair but has another fault the next week. The incident review should connect both events and obtain a qualified explanation before treating them as unrelated tickets.
Hypothetical worked example
A service returns but a dependent function does not
A fictional system restart restores the main equipment while a dependent control or user function remains unavailable. A restart log does not establish complete service.
Original fictional example · no completed client assignment or property inspection is represented.
| Record to obtain | Review question or calculation |
|---|---|
| Affected service and dependencies | Define the minimum usable result |
| Qualified response and restrictions | Test dependent functions with the appropriate reviewer |
| Functional restoration evidence | Retain any continuing limitation and its owner |
Useful working output: A restoration status based on a tested user journey and active restrictions.
Adapt the record request to authorized access, governing documents and the actual property. The example does not verify any unknown input or replace a professional conclusion.
Property Tabletop Exercise: Scenario, Decisions and Follow-Up · More operations and maintenance examples
Before acting on this guide
Set the review boundary and the acceptance test.
What the evidence does not prove
Do not describe a temporary workaround as permanent restoration.
What to verify before acceptance
Retain qualified response evidence and test the agreed service outcome while recording restrictions and recurrence follow-up.
Original proposed coordination checks · adapt to authorized access, the actual obligation and the appropriate professional review. These are not findings about your property.
Follow the related handoff workflow · Read the review definitions
Frequently asked questions
Should management promise a repair time?
Report confirmed information and label estimates. Give the next update time even when restoration timing remains uncertain.
Who can authorize restarting equipment?
The person qualified and authorized for that system under the applicable arrangement. Coordination staff should record that decision and its evidence.
How should repeated outages be measured?
Track events by asset, duration, service impact and confirmed cause, then connect them to maintenance and corrective actions. Avoid counting reopened tickets as unrelated successful closures.