Escalation and Severity Levels Triage: The Branch to Follow First
An escalation and severity levels decision tree gives a facility manager one controlled route from an incoming smart lock fault to the responsible branch. It starts with whether the door remains operable, rather than with the component suspected by the reporter. That order prevents a detailed technical complaint from hiding an immediate access problem.
Direct answer. In brief, this article covers escalation and severity levels decision tree from escalation and severity levels decision tree to escalation-and-severity-levels. It states what to confirm about escalation and severity levels decision tree on the dated product page where a figure is involved. An escalation and severity levels decision tree is a lifecycle guide. It starts where the invoice ends. escalation and severity levels decision tree is what has to be measured to keep the escalation and severity levels decision tree record usable.
On escalation and severity levels decision tree, this article uses escalation and severity levels decision tree as the definition. It treats escalation and severity levels decision tree as a working definition specific to this market and product, rather than a general one.
- Set the interval — define how often escalation and severity levels decision tree is inspected
- Set the trigger — name the condition that forces a change to escalation-and-severity-levels
- Track the number — keep one metric that shows assign runbook is healthy
- For escalation and severity levels decision tree, escalation and severity levels is what each step has to answer to.
Use this operations runbook after award, during normal service, and whenever a lock issue could affect a defined group of occupants. The output is not merely a severity label. It is a recorded branch, an accountable owner, the evidence collected so far, and the next authorised action.
Assign the runbook before live use
The facility manager should approve the labels, owners, evidence requirements and escalation contacts before incidents begin. Record those approvals as configuration of the service process, not as part of the individual fault record. The commercial end of this decision is the smart door locks.
| Runbook element | Decision to fix before use |
|---|---|
| Scope | Which doors and installed-base records are covered |
| Severity authority | Who may classify, raise or lower a case |
| Operational owner | Who receives each branch and keeps the case open |
| Evidence source | Which system or form receives the immutable event history |
Complete the Office Smart Lock Site Survey before handover, and use the Smart Lock Retrofit Site Survey where existing doors are affected. These records establish the physical context needed for branch-first fault triage.
Set the smart lock severity classification
Smart lock severity classification should describe current operational impact, not the apparent technical complexity of the fault. The fault triage levels below are starting labels that the buyer can adapt to its approved operating plan.
| Severity | Working definition | Typical first route |
|---|---|---|
| Critical | The normal authorised route is unavailable and no verified alternative route is currently available. | Site access continuity branch |
| High | Normal access is impaired for an identified group, but an approved alternative route is verified. | Field-service branch |
| Medium | The door remains operable, while a credential, configuration or operational function is degraded. | Access administration or technician branch |
| Low | No current operability or access-continuity effect is evident; the issue can enter the planned work queue. | Scheduled follow-up branch |
A symptom description alone cannot establish severity. The reporter may call a fault critical when it is not, or dismiss an access issue because a lock still responds to an app. The person assigning severity must check the branch conditions before accepting the label.
Use the Escalation and Severity Levels Worksheet You Can Fill in on Site to capture these decisions consistently. Severity changes belong to the facility manager or an authorised delegate, not to whichever party next touches the case.
Run the escalation and severity levels decision tree
The first branch is determined by access continuity. Only after that branch is selected should the team identify the likely technical path and decide who needs to attend.
flowchart TD
A["Fault received"] --> B{"Door operable through normal authorised route"}
B -->|"No"| C["Access continuity branch"]
B -->|"Yes"| D{"Normal access impaired"}
D -->|"Yes"| E["Service impact branch"]
D -->|"No"| F{"Configuration or administrative impact"}
F -->|"Yes"| G["Access administration branch"]
F -->|"No"| H["Planned follow-up branch"]
C --> I["Activate approved site access procedure"]
E --> J["Assign technician and evidence owner"]
G --> K["Assign access administrator"]
H --> L["Schedule owner action"]
This branch-first fault triage separates access continuity from diagnosis. A technician can investigate the lock while the duty owner handles an unavailable door, but the two records should remain connected.
| Observed condition | First branch | Initial severity guide | First action | Evidence to capture |
|---|---|---|---|---|
| No normal authorised route and no verified alternative | Access continuity | Critical | Follow the approved site access procedure and assign a duty owner | Door operability status, approved-route check and report record |
| Normal route impaired but an alternative is verified | Service impact | High | Assign a technician and preserve the pre-visit state | Symptom, affected credential group and physical observation |
| Door opens normally but a credential or administration function fails | Access administration | Medium or Low according to actual impact | Check identity, rights and configuration records | Credential state before and after, configuration change history |
| Door operates and no current access effect is evident | Planned follow-up | Low | Place the owner action in the planned queue | Observations and the reason no urgent branch applies |
Do not improvise access methods during this branch. Where emergency or alternative access is involved, use the site's approved procedure and the designated authority.
Preserve the fault before sending a technician
Before components are reset or units are exchanged, record the symptom in the technician's words and the corresponding measured observation. Confirm the door operability status by asking whether the normal authorised route works, not merely whether an indicator light appears.
| Check order | Observation to record | What the check helps rule out |
|---|---|---|
| 1 | Locked or unlocked state and whether the handle moves freely | Door alignment, closer force and latch preload |
| 2 | Whether a mechanical override moves freely, where fitted | A seized lock body |
| 3 | What the indicator and management application report | The difference between low power, jam and no response |
| 4 | Power condition and any emergency input, where fitted | Loss of power as the explanation |
| 5 | Physical door state against the recorded state | Configuration or synchronisation mismatch |
| 6 | Response from the cylinder or fingerprint reader, where fitted | The credential path rather than the motor |
| 7 | Whether the same fault appears on another door of the same model | A configuration, firmware or batch-level pattern |
| 8 | Unit swap only after the preceding checks | Avoids premature replacement |
A low-battery alert is a threshold indication, not a complete power measurement. Do not erase configuration merely to test whether it clears the fault, because that removes evidence needed to determine whether the door is actually operable.
Send one handoff packet down the facility escalation path
The facility escalation path should have named role holders rather than a general support inbox. A service-impact branch normally goes to the first-line technician, an access-administration branch to the credential or access owner, and an access-continuity branch to the duty owner immediately.
| Role | Decision or action | Handoff evidence |
|---|---|---|
| Service desk or reporter | State what was observed and when it was reported | Exact words, affected door identifier and contact route |
| Facility manager | Approve the branch, severity and operational priority | Branch reason, named owner and recorded approval |
| First-line technician | Run the ordered checks and preserve evidence | Check sequence and what each check ruled out |
| Access administrator | Review identity, rights and configuration state | Credential state before and after the action |
| Supplier support | Answer a specific technical or authorisation question | Case record, model variant, dated product-page reference and evidence |
Do not make attendance, replacement, freight or warranty handling an assumed supplier commitment. Ask for written confirmation of what the agreed support route covers.
Put severity change control on every case
Severity change control prevents the original classification from disappearing when the case moves between teams. The initial severity is an event, not a label that can be overwritten.
Apply these rules:
- Record the initial branch, severity, decision maker and supporting evidence.
- Raise severity when a defined impact condition appears; do not wait for a technician to reach the door if the branch evidence already supports a change.
- Lower severity only after the changed condition has been checked and the authorised owner approves the reason.
- Preserve both the previous and new values, with timestamps, the evidence and the approving role.
- Close the case without rewriting the history. Final service performance and the peak incident severity remain separate records.
A workaround does not automatically restore the original classification. Record what remains impaired, who can use the alternative route and whether normal operation has been verified.
Complete the minimum field record
The case record should be capable of reconstructing both the access impact and the technical reasoning. Complete the structure set out in Measuring Escalation and Severity Levels: What to Record.
| Required field | Minimum content |
|---|---|
| Object identifier | Door or unit identifier from the object schedule, not a room number alone |
| Unit identity | Model and variant read from the label or catalogue row; confirm on the dated product page for the specific SKU |
| Event times | Date and time reported, acknowledged and the door was operable again |
| Symptom | Technician's wording plus the measured observation |
| Door state | Door operability status, normal authorised route and any verified alternative |
| Checks | Checks in the order performed and what each one ruled out |
| Action | Parts fitted or unit swapped, with the old unit retained where applicable |
| Credential state | State before and after work when a credential was involved |
| Evidence | Photograph, reading or other record supporting the conclusion |
| Decision | Initial branch, severity, owner, later changes and approval |
Use the Escalation and Severity Levels for Installed Smart Locks: A Buyer and Operator Guide to distinguish an operational case record from informal email exchanges.
Work an illustrative branch comparison
An illustrative report states that an issued credential is not recognised on a door. A technician confirms that the door still opens through the normal authorised route and that no operational access loss exists. This belongs in the access-administration branch, with the observed door operability status recorded.
A second report uses similar wording, but the normal authorised route is unavailable and no alternative has been verified. The branch changes immediately to access continuity, and the site duty owner applies the approved procedure while the technician continues the evidence record. The reports describe different impact even though the initial symptom wording is identical.
These examples show why the symptom must not determine severity before access continuity is checked.
Ask for evidence instead of assuming support
CONFIRM-PER-SUPPLIER: Ask the supplier to confirm the evidence required for technical review or return authorisation, the scope of any authorised action and the records that must be retained; do not assume that attendance, replacement, freight or warranty handling is included.
CONFIRM-WITH-LOCAL-SITE-AUTHORITY: Confirm emergency-egress, accessibility, fire-safety and local access-control duties against the site's approved procedures and the relevant local authority; this runbook does not set those requirements.
When support is requested, provide the model and variant, the dated product-page reference, the ordered checks, the credential state where relevant and the evidence supporting the proposed branch. Avoid describing a general capability as a fact unless it is confirmed for the specific SKU.
Close the case without erasing the signal
A case is ready for operational closure when the door is operable again, the credential path has been checked where applicable, the field record is complete and any return or outstanding evidence has been recorded. Retain the original severity and the final severity as separate fields.
The practical counterpart to this point is the smart lock handle design. That is the same question escalation and severity levels decision tree has to answer here.Keep acknowledgement, attendance and resolution events distinct. Response time runs from report to acknowledgement, on-site attendance time runs from acknowledgement to arrival at the door, and resolution time runs from report to the door being operable again. Any mean time to repair is calculated across a stated population and period; it does not reveal the tail or doors that were never reported.
Use this closing checklist:
- Branch selected from door operability and access impact.
- Severity approved by the named authority.
- Checks and ruled-out outcomes recorded in order.
- Credential, parts and unit evidence attached.
- Changes logged rather than overwritten.
- Operable-again event captured.
- Supplier-dependent and site-dependent questions confirmed in writing.
For portfolio handover, ask Smart Lock Factory to map these branch labels, evidence fields and ownership rules into the buyer's approved support process. Keep every SKU-specific statement tied to the dated product page for that specific SKU.
A quote request turns the written requirement into something a supplier can price: request a quote.

