What Escalation and Severity Levels Costs a Programme in Downtime Terms
The escalation and severity levels downtime impact is easy to lose when every lock alert enters the queue as the same event. For a facility manager, the useful question is not whether a label sounds urgent. It is which door became unavailable, what normal operation was displaced, who can authorise a workaround or unit change, and when the door became operable again. Severity describes impact; escalation directs handling and ownership. Neither restores the lock. Together, they determine whether downtime is contained, extended by handoffs, or concealed inside manual work. Use this tear-off checklist to separate those effects.
Start with the clock and the door state Put the answer
Direct answer. Open the record with the object-schedule identifier, not a room label, and capture the report time and channel. State whether normal operation stopped, continued with an agreed fallback
Use the smart lock severity classification as an impact statement, not as a diagnosis. “Lock unavailable” and “access denied for one credential” are different facts. Preserve the technician’s symptom separately from the measured observation. If the door is operable through a defined fallback, record that fallback and when it began; do not treat it as zero disruption. These first timestamps form the baseline against which later escalation decisions are judged. The buyer-side checklist sits in Fingerprint Smart Locks for Facility Managers. The catalogue side of this is the smart door locks.
Keep severity and escalation on separate lines
A sound programme uses two fields. Severity stays attached to the operational consequence at first report. Escalation changes who receives the decision, what evidence is required and which contingency opens. It must not overwrite the original impact.
Critical, Major and Minor below are illustrative buyer labels. Agree the criteria locally rather than copying names without meaning.
Use this escalation and severity levels downtime impact check to compare decisions, not promises of response or repair:
| Decision | Critical | Major | Minor |
|---|---|---|---|
| Meaning | Normal door operation is stopped and no agreed fallback is working. | Normal operation is impaired, but a defined fallback limits the disruption. | Normal operation continues while a fault or diagnostic task is investigated. |
| Decision owner | The incident lead opens the site contingency and records fallback status. | A named case owner coordinates access, technician work and return-to-service approval. | The service-queue owner schedules the check and maintains the evidence trail. |
| Next evidence | Door state, fallback status, affected operational use and required approval. | Diagnostic checks, what each ruled out, parts or unit action, and the recovery sequence. | Symptom, diagnostic result, configuration check and closure confirmation. |
Copy the row that matches the recorded impact; do not jump straight to the label. If the evidence changes, append a dated decision entry naming what changed, who decided and which operating consequence changed. This keeps a later, lower-severity view from erasing the original disruption.
Use one branch for every report and make recovery common to all levels:
flowchart TD
A[Report received] --> B[Record original impact]
B --> C{Initial severity}
C -->|Critical| D[Activate site contingency]
C -->|Major| E[Assign named owner]
C -->|Minor| F[Queue diagnostic work]
D --> G[Confirm recovery evidence]
E --> G
F --> G
G --> H[Close record and preserve history]
Each branch must identify the decision owner and the evidence required before work continues. The closure node preserves the original classification; it does not turn an early estimate into a fact.
Convert escalation decisions into measurable downtime
For door downtime measurement, retain two intervals: the reported fault to the door becoming operable again, and the reported fault to an agreed fallback becoming usable. Label the first total disruption and the second unmitigated disruption. Record any remaining workaround interval separately. Averages may summarise a population, but they hide long individual cases; review the door-level history as well.
The fault triage record must show the symptom, checks in order and what each check ruled out. This prevents a replacement from becoming the first explanation. If the technician swaps a unit, record the observation before the swap, the part or unit fitted, and the old unit retained. If credential state changed, capture it before and after. The evidence supports the conclusion rather than merely documenting activity.
Tear-off checks at the point of escalation
Use this list at the door or in the control room; tick only what the record supports.
- Confirm the object identifier, model and variant from the label or catalogue row, with the dated product-page reference.
- Record the report channel and time alongside the current physical door state.
- State the symptom separately from the measured observation and checks already run.
- Record what each check ruled out, including mechanical and electronic observations.
- Mark the fallback status and the time it became usable.
- Assign severity with a written reason while keeping the original classification visible.
- Assign the escalation owner, required evidence and next decision point.
- Capture return-to-service evidence, time, credential state and any retained unit or part.
Do not close the item because a shipment is pending. Close it when the door is operable again, or record why a different disposition has been formally approved.
Preserve the evidence that stops reclassification
Service recovery evidence should be attached to the original event rather than created as a replacement summary. It should allow a reviewer to reconstruct the impact, decision path and return to operation without relying on memory.
| Record element | Required wording | Why it matters |
|---|---|---|
| Impact snapshot | Normal operation, fallback condition and affected use | Preserves the consequence seen at report time |
| Checks performed | Test performed and what it ruled out | Separates observation from conclusion |
| Decision trail | Classification, owner, approver and timestamp | Shows why the handling route changed |
| Time points | Reported, fallback usable and door operable again | Supports buyer-computed downtime measures |
| Asset trail | Part fitted, unit swapped and old unit retained | Connects the intervention to the evidence |
Where the conclusion depends on a supplied unit, confirm on the dated product page for the specific SKU before comparing the recorded observation with a product claim. Where a supplier must approve or perform an action, ask for the evidence requirement and written owner rather than assuming the route.
Audit changes before they conceal downtime
Treat field service escalation as the route that carries a decision, not as the label that rewrites its consequence. At each review, compare the original classification with the current one. A changed value should have a reason, an approver, a timestamp and an explanation of the operational difference.
Use the Escalation and Severity Levels Worksheet You Can Fill in on Site to capture the initial call, the Measuring Escalation and Severity Levels: What to Record to align timestamps, the Escalation and Severity Levels Triage: The Branch to Follow First for branch discipline and the Escalation Path for Escalation and Severity Levels to assign ownership.
Before approval, ask the supplier to confirm in writing what support evidence it accepts, what it can authorise and which party owns each return step.
CONFIRM-PER-SUPPLIER: Request the current escalation route, evidence requirements and limits of remote support; do not treat this checklist as a promise of attendance, diagnosis or replacement.
Ask for the offer against the same requirement: request a quote.

