Escalation and Severity Levels: Contract Clauses that Make It Work
After award, a smart-lock fault is an operating event, not just a support ticket. The agreement should say how the first severity is assigned, who receives it, what evidence can change it, and what closes the record. For a facility manager, escalation and severity levels contract support is the control point between a door report and a defensible action trail. Use the Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey to define the door population and site constraints before assigning routes.
Direct answer. Short version — escalation and severity levels contract support is treated here as escalation and severity levels contract support first. escalation-and-severity-levels comes second. The evidence for escalation and severity levels contract support is named in the sections below. An escalation and severity levels contract support covers the period after handover. It names the owner. escalation and severity levels contract support is the interval that makes escalation and severity levels contract support visible before it becomes a complaint.
Severity levels tied to operating consequence A settled spec
| Level | Contract trigger | Initial route | Evidence at opening |
|---|---|---|---|
| Critical | The door cannot meet the site's documented continuity procedure | Incident lead and site duty owner | Door state and impact note |
| Major | The primary access path is impaired and no approved workaround is recorded | Support owner | Observation and workaround check |
| Standard | A localized impairment has a recorded workaround | Case queue | Symptom and test result |
| Administrative | There is no operating interruption, only a record or configuration discrepancy | Administration owner | Before-and-after record |
Build the smart lock severity matrix around verified operating consequence rather than blame, diagnosis, product age or contract value. State that the opening level is provisional and linked to the original report; a later diagnosis must not rewrite what the facility team knew at intake. The range this procurement eventually buys from is the smart door locks.
Clause fields that make routing executable
A practical clause set for escalation and severity levels contract support should contain:
| Contract field | Draft requirement | Audit proof |
|---|---|---|
| Definition | Covered events and explicit exclusions | Versioned scale |
| Trigger | One named intake channel | Report reference and receipt timestamp |
| Clock | Defined start and end events | Timestamp fields |
| Owner | One accountable role for each level | Role roster |
| Authority | Who may change a level | Approval record |
| Closure | Required evidence and sign-off | Closed record |
| Audit | Retained history and review access | Reviewable record |
Define contract escalation routes for every level, including a fallback when the first owner does not acknowledge. Use the Escalation and Severity Levels Worksheet You Can Fill in on Site to collect the fields, then attach the completed scale as a versioned contract schedule.
Define clocks before targets
| Service term | Definition | Supporting record |
|---|---|---|
| Response time | Report received through the agreed channel to acknowledgment | Receipt and acknowledgment timestamps |
| On-site attendance time | Acknowledgment to arrival at the door | Arrival timestamp and door record |
| Resolution time | Report received to the door becoming operable | Receipt and operable-again timestamps |
| MTTR | Mean resolution interval across a defined population and period | Filtered records and calculation method |
The plan sets targets; the records supply observations. Keep arrival and repair evidence separate so acknowledgment cannot be reported as a fix. The Measuring Escalation and Severity Levels: What to Record companion sheet can standardize the evidence without replacing the agreement.
Gate the first classification
At intake, record the door, symptom, observed consequence and available evidence. Routing is then a gate rather than an opinion: escalation means movement to the accountable role, while severity describes operating consequence. Use the Escalation and Severity Levels Triage: The Branch to Follow First to test each hand-off.
flowchart TD
A[Report received] --> B[Record initial severity]
B --> C{Required evidence present}
C -->|Yes| D[Route to accountable owner]
C -->|No| E[Request missing evidence]
E --> B
D --> F{Door operable}
F -->|Yes| G[Close and verify record]
F -->|No| H[Escalate and keep open]
Treat controlled reclassification as an append-only decision. Maintain a severity-level change log containing the original level, new level, evidence, approver, effective time and reason. Require named authority for a downgrade, and preserve the original receipt time even when later evidence narrows the impact.
Keep decision authority separate
- The facility manager owns the door facts, observed impact and accuracy of the initial report.
- The support owner acknowledges the report, requests missing evidence and routes it without rewriting site facts.
- The authorized approver accepts severity changes and records the supporting reason.
CONFIRM-PER-SUPPLIER: Ask the supplier to confirm in writing which remote checks, attendance, replacement handling and evidence it can provide for the contracted scope.
Capture the evidence at the door
Retain the field service evidence record as the evidentiary base of every severity decision:
- Door or unit identifier from the object schedule.
- Model and variant taken from the label or catalogue row.
- Report and operable-again timestamps.
- Symptom in the technician's words and the measured observation.
- Checks performed in order and what each check ruled out.
- Parts fitted, unit swapped, and old-unit retention or disposition.
- Credential state before and after where credentials were involved.
- Supporting photograph, reading or other retained evidence.
Each check must state what it ruled out; a list of actions is not diagnosis evidence. Where a model-specific capability affects the route, confirm on the dated product page for the specific SKU. Preserve original files with the report rather than reconstructing them later.
The practical counterpart to this point is smart lock old lock replacement. That is the same question escalation and severity levels contract support has to answer here.
Reclassification decision table
| Decision | Classification action | Contract control |
|---|---|---|
| Evidence narrows operating impact | Downgrade the level | Authorized approver and both levels logged |
| Door is operable but cause is unknown | Record operability separately | Keep the cause-investigation state open |
| Same event is submitted twice | Merge the working records | Retain both sources and one original clock |
| Wrong door or site is named | Correct the target | Preserve the original entry and correction |
Most reclassification disputes arise from mixing impact with cause. The agreement should state separately whether the door is operable, whether the cause is known, and whether the underlying condition may recur.
Audit pack before signature
Before signature, require the operating record to demonstrate that the current level is visible, each change can be reconstructed, the service clock can be reproduced, the accountable owner and fallback are named, and supplier commitments are confirmed in writing.
For a multi-site agreement, use the Escalation and Severity Levels: From One Site to Twenty structure to apply one scale without erasing site-specific consequences. Clause priority, site access and retention provisions should be reviewed for each operating site.
CONFIRM-WITH-LOCAL-LEGAL: Confirm the priority, access and record-retention provisions that apply to each site before signature.
Use this datasheet as the agenda for a clause workshop with the supplier and internal operations team. Leave the meeting with a versioned scale, named role map, clock definitions, evidence schedule and written supplier confirmations; unresolved fields should remain visible assumptions rather than hidden operating rules.
Close the loop with requesting a quote.

