Motor Not Driving: Contract Clauses that Make It Work
Use this ops runbook when a smart lock is reported with the motor not driving and the buyer needs motor not driving contract support before a technician arrives. The agreement should turn a broad repair request into a controlled sequence: capture the reported symptom, preserve evidence, authorize the next action and prove when the door is operable again.
Direct answer. The short answer is that motor not driving contract support is not one decision. It is a sequence. This article takes motor not driving contract support from motor not driving contract support through motor-not-driving to the record you keep. A motor not driving contract support covers the period after handover. It names the owner. motor not driving contract support is the interval that makes motor not driving contract support visible before it becomes a complaint.
The term motor not driving contract support carries one meaning throughout this article. It is the one given in motor not driving contract support. That is a working definition of motor not driving contract support, and the buyer still has to check it against the dated product page.
The field service runbook below is written for a facility manager coordinating post-award operations. It connects the at-door fault tree to the contract schedule without presenting diagnosis, attendance or replacement as a promise. For broader installed-base context, use Motor Not Driving for Installed Smart Locks: A Buyer and Operator Guide.
Start with the motor not driving contract support clause map
The clause map should sit beside the service schedule and identify who owns each decision. Draft each row as a question that the agreement must answer, rather than as a claim about what a supplier has already agreed to do.
| Clause topic | Question the agreement must answer | Evidence attached to the gate | Result recorded |
|---|---|---|---|
| Support scope | Which reported faults enter the support lane? | Door ID, fault tag, report time | Shared intake scope |
| Fault evidence | What must accompany a dispatch or return request? | Ordered checks, observations, readings | Complete or incomplete packet |
| Site access | Who provides access and confirms the work area? | Named requester, access route, constraints | Access-ready status |
| Diagnosis | Who may inspect, test or change the lock? | Work order and change record | Repair or swap recommendation |
| Authorization | Who approves a repair, unit swap or return? | Fault packet and approval entry | Authorized action |
| Closure | What proves the door is operable and the case is closed? | Operable time, test result, disposition | Closed or reopened |
Name a role rather than leaving the clause open to interpretation. The same role may hold different duties at intake, dispatch and closure, but each transition should produce a record. A support contract that defines only an outcome leaves the parties reconstructing the decision later. The catalogue side of this is the smart door locks.
CONFIRM-WITH-LOCAL-COUNSEL: Confirm the final clause allocation, notice method and delegated-authority wording against the buyer’s governing agreement and applicable local requirements.
Define what enters the motor not driving support lane
A reported symptom and a confirmed fault are different events. The contract should state that “motor not driving” opens an investigation lane without proving that the motor, gearbox or electronics have failed. It should also define when a door is considered operable, because the repair branch may end with intended access restored rather than a particular component replaced.
| Contract term | Definition to use | Operational consequence |
|---|---|---|
| Reported symptom | The reporter’s description of the fault | Opens the intake record |
| Observed condition | What the technician or system records | Supports branch selection |
| Confirmed fault | A conclusion supported by the ordered checks | Supports repair, swap or return |
| Door operability | The intended opening and securing method works | Provides the closure test |
| DOA boundary | The agreed point between pre-service and in-use failure | Selects the relevant contractual route |
Any instruction about an override, indicator, app, cylinder, fingerprint reader, battery pack or emergency input must remain conditional on the specific lock. Confirm on the dated product page for the specific SKU before a technician relies on that feature or treats its absence as a fault.
The contract should also define which door identifier the parties use. Use the object schedule rather than a room number alone, because rooms can be renumbered while the installed asset remains the same.
Run the door-side fault isolation before invoking the repair branch
The support request should ask for an ordered diagnostic record, not a collection of disconnected observations. Each check needs a recorded result and a statement of what it ruled out. The order prevents a convenient replacement from displacing evidence.
flowchart TD
A[Reported fault] --> B[Lock safe access and door state]
B --> C[Run ordered fault isolation]
C --> D[Manual path works]
C --> E[Manual path does not work]
D --> F[Review drive power and electronics]
D --> G[Review credential path]
E --> H[Record mechanical obstruction]
F --> I[Complete fault evidence]
G --> I
H --> I
I --> J{Action authorized}
J -->|Repair or swap| K[Restore door and record closure]
J -->|Return| L[Record RMA disposition and closure]
| Order | Check at the door | Record | What it rules out or separates |
|---|---|---|---|
| 1 | Confirm the locked or unlocked state and whether the handle is free | Door position, handle movement | Alignment, closer force and latch preload |
| 2 | Turn the handle by hand; use a manual override only where fitted | Result and any obstruction | A seized gearbox when movement is free |
| 3 | Read the indicator and app, where present | Exact message or no-response state | Low-power, jam and no-response branches |
| 4 | Test cells or the pack, plus an emergency input only where fitted | Reading and connection result | The power branch |
| 5 | Compare physical and recorded controller states | Both states | Configuration or synchronisation mismatch |
| 6 | Test the cylinder or fingerprint reader, where fitted | Credential response | The credential layer |
| 7 | Compare the fault fingerprint with another door of the same model | Affected-door list | A possible shared configuration, firmware or supply-batch issue |
| 8 | Replace or return only after the earlier branches are documented | Approval, action and retained unit | Unexamined branches |
If the same fingerprint appears on two doors of the same model, the contract should trigger a common-cause review before further unit swapping. That control preserves evidence without treating the similarity as proof of a configuration, firmware or batch fault.
CONFIRM-WITH-LOCAL-SITE-OWNER: Confirm which site procedures govern safe isolation, manual operation and temporary access before a technician tests an installed door.
Package smart lock fault evidence as a usable packet
The phrase “the lock does not work” is an opening statement, not a diagnosis. The agreement should identify the minimum fault packet that supports dispatch, repair authorization and any return request. The same checklist should govern all branches so that the reader can compare records without reconstructing them later.
| Packet field | Required entry | Why the clause needs it |
|---|---|---|
| Door or unit ID | Object-schedule identifier | Connects the fault to the installed asset |
| Model and variant | Label or catalogue identification | Confirms the correct service path |
| Reported times | Date and time reported | Starts the buyer’s service measurement |
| Symptom | Technician’s words plus measured observation | Separates narrative from evidence |
| Checks | Order run, result and what each ruled out | Shows the decision path |
| Parts or unit | Item fitted or swapped | Establishes what changed |
| Credential state | Before and after, where involved | Separates access-layer faults |
| Supporting proof | Photo, reading or retained unit | Supports the conclusion |
Draft a clause that lets intake mark a packet complete or incomplete against these fields. If the packet is incomplete, the record should state the missing evidence rather than imply that the fault has been disproved.
The evidence packet should identify the dated source used, while avoiding assumptions about features or serviceable parts.
Route intake through one controlled channel
Use motor-not-driving as an intake tag, then connect it to the door ID and contract case reference. The tag helps organise the record; it must not replace the individual fault observations. Define one authorised route for reporting and one route for evidence corrections so that parallel calls do not create competing histories.
| Stage | Required action | Record produced |
|---|---|---|
| Report | Log the door, symptom and reporter | Intake entry |
| Review | Compare the packet with the fault-tree fields | Complete or incomplete status |
| Dispatch | Authorise the inspection or further evidence request | Work instruction |
| Work | Record actions, changes and test results | Technician entry |
| Close | Confirm operability and required dispositions | Closure entry |
The clause should define acknowledgement, dispatch and completion as distinct events. It should identify the source record for each event. The Motor Not Driving: Decision Tree for Field Teams can support the technical branch, while the contract determines who receives its output and who may act on it.
Avoid promises about attendance or repair outcomes. Instead, specify the information required at each gate and the evidence that moves the case to the next gate.
Assign site access responsibility without leaving a grey zone
A technically correct diagnosis can still stall when nobody owns access. The agreement should identify the role that requests support, the role that authorises entry, and the role that maintains continuity while the affected door is unavailable. Use a request form that captures the access contact, door location and any site constraints.
An Office Smart Lock Site Survey may establish the survey fields before installation. For an existing installation, Smart Lock Retrofit Site Survey can help identify whether door condition, hardware variation or an incomplete survey affects the service record. Those records support the fault ticket; they do not replace the on-site observation.
Access responsibility should cover safe isolation, the work area, temporary entry arrangements and communication with security or the occupant. If an insurer or internal security policy affects temporary measures, request written direction for that site.
CONFIRM-WITH-LOCAL-INSURER: Confirm any site-specific insurer, security or access requirement that affects temporary door arrangements or work on an installed lock.
Define lock repair authorization as a decision ladder
The contract should not leave “repair”, “replace” and “return” as interchangeable terms. Each action changes the evidence, the installed asset or the commercial record. Define who may authorize each level and what must be present in the case file.
| Action level | Authorisation basis | Required evidence |
|---|---|---|
| Evidence review | Pack received against the checklist | Intake status |
| On-site diagnosis | Work instruction issued for inspection | Access confirmation |
| Component intervention | Service procedure permits the named action | Parts and test record |
| Unit swap | Earlier branches completed and swap approved | Old and new unit details |
| Return | Local diagnosis closed or repair route unavailable | Return authorisation details |
For a motor-not-driving event, emergency authority should be clear without becoming blanket permission to replace equipment. Define which actions can begin immediately, which require retrospective approval and which remain outside the technician’s authority. If work is delegated, the record must identify the person who accepted the delegated task.
The agreement should also say how commercial treatment is recorded without embedding assumptions about coverage. Ask for the applicable route, required evidence and named decision-maker in writing.
CONFIRM-WITH-LOCAL-COUNSEL: Confirm delegated repair authority, evidence-retention duties and approval wording against the buyer’s contract and applicable local requirements.
Control the replacement unit record and return route
A replacement is not closed when the new unit powers up. The replacement unit record should connect the old unit, the affected door, the authorization, the tests performed and the final door status. Where safe and agreed, retain the old unit so later review does not depend on memory.
| Record element | Entry |
|---|---|
| Removed unit | Identifier, variant and physical condition |
| Replacement unit | Identifier, variant and fit confirmation |
| Transfer state | Door and credential state before the change |
| Post-work state | Operability test and remaining restriction |
| Disposition | Retention, return or other agreed handling |
| Authorization | Named role and case reference |
Define RMA as the authorised return route, including what may be shipped, what supporting material must accompany it and what disposition is required when the unit returns. State commercial responsibilities without assuming which party bears freight or other costs. The returned unit and its evidence should remain linked to the affected door.
Any action involving a serviceable component must follow the procedure for the specific SKU.
Trigger supplier escalation without repeating completed field work
Supplier escalation should begin when the evidence packet is stable and the next action falls outside the current role. It should not restart the fault tree unless new evidence invalidates an earlier conclusion.
| Trigger | Evidence required | Escalation outcome |
|---|---|---|
| Same fingerprint on two doors of one model | Affected-door comparison | Common-cause review |
| Evidence conflicts with device output | Readings, photos and checks | Technical disposition |
| Authorised repair does not restore operability | Work record and post-test | Revised action path |
| Return is proposed | Complete packet and authorisation | RMA decision |
| Possible shared configuration or batch issue | Cross-door evidence | Controlled containment and review |
Draft a clause requiring a written escalation disposition that separates observed fact, suspected cause, decision and required corrective action. The record need not use a fault code to be valid, but every code should map to a defined meaning and owner.
Do not use escalation to bypass site access or repair authority. If the case depends on another party’s evidence, keep that dependency visible and record the date and channel of the request.
Keep door status and operational continuity explicit
The affected door has a service condition as well as a technical condition. The agreement should define the status names used in tickets and the transition that each one requires. This prevents a repair request, a temporary workaround and a completed repair from appearing as the same event.
| Door status | Record entry |
|---|---|
| Reported inoperative | Reporter, symptom and reported time |
| Temporarily accessible | Workaround and responsible role |
| Diagnosis underway | Assigned work and access status |
| Repair authorised | Action, approver and retained evidence |
| Operable under test | Test result and outstanding work |
| Service restored | Operable time, closure evidence and open actions |
For occupied or controlled doors, define who confirms the temporary access arrangement and who receives an update when the condition changes. The communication clause should identify triggers rather than use vague instructions such as “keep the supplier informed”.
A change in door status does not automatically prove that the root cause is known. Keep operational continuity and technical closure as separate fields in the record.
CONFIRM-WITH-LOCAL-SITE-OWNER: Confirm the approved temporary-access and communication process for each affected door or security zone.
Close the case with an auditable record
Closure requires evidence that the door is operable again and a record of what remains open. The agreement should identify which timestamp starts each buyer-computed measure, which population is included and where the source record sits. It should not publish a supplier commitment disguised as a metric.
| Measure | Definition | What it does not show |
|---|---|---|
| Response time | Report through the agreed channel to acknowledgement | Whether anyone attended |
| On-site attendance time | Acknowledgement to a person being at the door | Whether the door was fixed |
| Resolution time | Report to the door becoming operable again | Why the interval occurred |
| MTTR | Mean resolution interval for a stated population and period | Tail performance or unreported faults |
| Availability | Operable time divided by scheduled time for a stated population | Whether the population matters |
| First-time fix | Visit ends operable with no repeat visit for the same symptom | Whether root cause was found |
| Repeat rate | Failures returning within a stated window | Severity of each failure |
The buyer computes these measures from its records. The supplier’s contractual role should include timely source records and a process for correcting them. Close only the technical actions that are complete; leave root-cause investigation, return disposition or corrective action visible if they remain open.
Convert repeat faults into contractual corrective action
A repeat fault needs a different record from a one-door repair. When the same fingerprint appears on two doors of the same model, the clause should suspend routine unit swapping until the buyer reviews shared configuration, firmware or supply-batch possibilities. The review is an evidence activity, not a declaration of cause.
Ask for a comparison across affected doors, configuration records, installation records and the checks already completed. The output should state what changed between affected and unaffected doors only where evidence permits. Unresolved differences should remain open items.
The Motor Not Driving: The Evidence a Motor Not Driving Record Needs provides the evidence view. The contract should connect that record to a corrective-action owner, verification method and closure condition. A return route without an outcome record does not close a recurring fault.
Audit motor-not-driving support through sampled case files
Contract review should test the process with actual records rather than committee interpretation. Sample closed and open cases, then follow each case through the clauses. Look for missing authorization, duplicated timestamps, unsupported conclusions and closures that lack a door-operability test.
| Audit test | Passing evidence | Contract gap |
|---|---|---|
| Intake consistency | Same identifier and symptom across records | Missing case reference |
| Diagnostic order | Checks and ruled-out outcomes are sequenced | Undefined evidence standard |
| Access ownership | Requester and authorising role are visible | Grey-zone access clause |
| Decision authority | Repair, swap and return each carry approval | Undefined delegated authority |
| Closure quality | Operability and remaining actions are recorded | Premature closure |
| Repeat-fault control | Similar faults trigger common-cause review | No recurrence rule |
Record each gap as a change request with an owner and an agreed route. Do not rewrite the operational history to match the clause. The sampled record may instead show that the clause is workable but was not followed, which is a different finding from an unclear clause.
The practical counterpart to this point is slk g200 for single glass doors. That is the same question motor not driving contract support has to answer here.The Common Mistakes in Motor Not Driving checklist can help the audit avoid relying on intuition during review.
CONFIRM-WITH-LOCAL-COUNSEL: Confirm how audit findings, corrective-action records and contract amendments will be handled under the buyer’s governing documents.
Attach the ready-to-use support schedule
Place the following items in a post-award service schedule. Ask the supplier and internal owners to complete the blank fields rather than adopting generic promises.
- Support scope: Define the reported events, fault tag, exclusions and affected-door identifier.
- Intake route: Name the reporting channel, authorised requester and case-reference format.
- Evidence packet: List every required field, including what each ordered check ruled out.
- Access responsibility: Assign access approval, safe-work conditions and temporary-access communication.
- Fault order: Set the minimum diagnostic sequence before repair, swap or return.
- Repair authorization: Define the action ladder, delegated roles and approval evidence.
- Replacement and RMA: State unit identification, old-unit disposition, return contents and commercial responsibilities.
- Door closure: Define operability, the operable timestamp, credential state and remaining actions.
- Service measurement: Specify the buyer’s record source, population, period and computation method.
- Escalation and change control: Set repeat-fault triggers, escalation inputs, corrective-action ownership and amendment route.
Give the completed schedule to facilities, security, procurement and supplier support. Run one historical case through it as a tabletop: the record should reveal missing owners, evidence fields and approvals before a live door is affected. Keep unresolved fields visible in the agreement rather than hiding them in a technician’s local practice.
CONFIRM-WITH-LOCAL-COUNSEL: Obtain final review of the support schedule, local notice methods, access conditions and authority provisions before the schedule becomes operative.
Ask for the offer against the same requirement: request a quote.

