Smart Lock Commissioning & Handover Checklist for Projects
A practical smart lock commissioning and handover checklist for apartments, hotels and offices covering doors, users, gateways, accounts, emergency access and documentation.
segulock
10/8/202613 min read
Smart Lock Project Commissioning & Handover Checklist: From Installation to Operations
Installing the last smart lock does not mean a smart lock project is finished.
The hardware may already be on the doors, but the property manager may still not know:
Who owns the administrator account.
Which lock belongs to which room.
How temporary users are created.
Which doors depend on a gateway.
What happens when the internet is unavailable.
Where mechanical keys are stored.
Which spare parts belong to each lock model.
Who handles first-line troubleshooting.
What information should be collected before contacting technical support.
These are not minor details.
For apartment buildings, hotels, offices, rental properties and other multi-door projects, the transition from installed system to operational system should be managed through commissioning and handover.
A structured handover reduces confusion between supplier, installer, project contractor and property operator after the installation team leaves.
This guide provides a practical smart lock commissioning checklist for B2B buyers and project teams.
What Is Smart Lock Commissioning?
Smart lock commissioning is the process of verifying that the installed locks, access methods, software configuration, network architecture and operating procedures work as intended before the system is accepted for daily use.
Installation answers:
“Is the lock physically mounted on the door?”
Commissioning asks:
“Does the complete installed solution work correctly in the real project?”
Depending on the project, commissioning may include:
Mechanical operation.
Fingerprint access.
PIN codes.
RFID cards.
App management.
Gateway connectivity.
Remote functions.
User permissions.
Emergency access.
Administrator ownership.
Documentation.
Spare parts.
Staff training.
The exact checklist should match the product and project requirements.
A basic standalone fingerprint lock does not need the same commissioning process as a multi-building smart lock system with gateways and centralized management.
What Is Smart Lock Project Handover?
Handover happens when control of the installed smart lock system is formally transferred from the supplier, installer or project team to the organization that will operate it.
That organization may be:
Property management.
Hotel management.
Apartment operator.
Office administrator.
Facility-management team.
Building owner.
Distributor's local service team.
A good handover should transfer more than physical products.
It should also transfer:
control + information + documentation + responsibilities
Without this step, the project may depend on the installer long after installation has been completed.
Why Commissioning Should Be Planned Before Installation Ends
A common mistake is to wait until the final installation day before discussing handover.
By that point, important information may already be scattered between different people.
For example:
The installer knows which door required a special adjustment.
The supplier knows the firmware configuration.
The project manager knows which lock model belongs to each floor.
The property manager knows how users should actually be managed.
If these details are not consolidated, the operator receives a system without a clear operational record.
Commissioning should therefore be planned during the project rather than treated as a final administrative task.
A practical project sequence is:
Specification → Sample/Pilot → Production → Installation → Commissioning → Handover → Operation → After-Sales
If the project is still at the product-evaluation stage, complete a proper smart lock sample test before moving into bulk deployment.
1. Confirm the Final Door and Lock Schedule
Begin with a complete record of the installed doors.
Each installed lock should be identifiable.
A basic schedule may include:
FieldExampleDoor IDA-301BuildingBuilding AFloor3RoomApartment 301Lock modelApproved project modelFinishBlackMortiseProject-approved typePlatformTTLock / Tuya / otherGateway groupGateway A3Installation statusCompletedTest statusPassed / Action required
The naming format can be adapted to the project.
The important point is that the operator should be able to answer:
Which exact lock is installed on which exact door?
Avoid relying only on memory or photos.
For large projects, consistent door identification becomes extremely useful when troubleshooting begins months later.
2. Verify Mechanical Operation on Every Relevant Door
Smart lock commissioning should not begin with the app.
Begin with the door.
Check the physical installation.
Depending on the lock and door, checks may include:
Handle movement.
Latch movement.
Bolt movement.
Door closing.
Strike alignment.
Mortise alignment.
Spindle engagement.
Screw installation.
Panel stability.
Mechanical key operation.
The door should not require abnormal force to lock or unlock.
This matters because an electronic complaint may actually begin with a mechanical installation problem.
For example:
The fingerprint is recognized.
The motor activates.
But the bolt is rubbing against the strike.
The user may report:
“The smart lock motor is weak.”
The root cause may instead be door alignment.
Commissioning should therefore verify the complete installed door rather than testing the smart lock only while the door is open.
3. Test Every Access Method Included in the Project
Do not assume that because one access method works, the entire lock is ready.
Test the functions included in the approved project specification.
Depending on the model, this may include:
Fingerprint.
PIN code.
RFID card.
Mechanical key.
Bluetooth.
App unlocking.
Temporary PIN.
Remote unlocking.
Face recognition.
Palm recognition.
Other model-specific functions.
Create test cases around the actual operating scenario.
For example, an apartment project may need to test:
Administrator creates a user.
User opens the correct door.
Administrator removes the user.
Removed credentials no longer provide access where applicable.
Temporary access expires as intended.
Property staff can recover access through the agreed emergency procedure.
Commissioning should test workflows, not only individual buttons.
4. Verify the Correct App and Firmware Configuration
Two locks can look identical externally while using different software configurations.
Before handover, confirm the approved:
App platform.
Firmware configuration.
Language.
Lock model identification.
Gateway compatibility.
Supported access functions.
For B2B projects, software configuration should be treated as part of the approved product specification.
If the project ordered a TTLock-compatible configuration, receiving a different platform would not be acceptable simply because the physical lock looks correct.
SEGULOCK's smart lock quality control guide explains why firmware and software configuration should be controlled alongside mechanical and electronic components.
5. Define Administrator Account Ownership
This is one of the most important parts of handover.
The permanent project administrator should not depend on an installer's personal account.
Before project acceptance, confirm:
Who owns the primary account?
Which email or phone identity is associated with it?
Which organization controls account recovery?
Who can add administrators?
Who can remove administrators?
Who should have routine management access?
Who should have emergency access?
For commercial installations, use an ownership structure that remains with the customer organization rather than one individual contractor whenever the platform allows it.
If an installer initially created the system for testing, the permanent ownership arrangement should be confirmed during handover.
Do not discover six months later that the only administrator account belongs to a technician who no longer works on the project.
6. Define Administrator Roles
Not everyone needs the same level of access.
A project may involve:
Property owner.
Property manager.
Reception.
Maintenance staff.
Security team.
Installer.
Distributor support.
External service contractor.
Define what each role is allowed to do.
For example:
Property Administrator
May manage users and project settings.
Reception or Operations Staff
May issue guest or temporary access where required.
Maintenance Staff
May receive service access without full administrator control.
Installer
May have temporary commissioning access that is removed or restricted after handover.
The exact role structure depends on the software platform and project.
The principle is simple:
Operational access should follow operational responsibility.
7. Verify Gateway Deployment
If the project uses gateways, commissioning must include the gateway architecture.
Do not only check whether the gateway indicator shows that it is connected.
Verify the actual workflow.
Depending on the platform and lock configuration, confirm:
Gateway model.
Gateway location.
Connected locks.
Network connection.
Power source.
Required remote functions.
Lock-to-gateway communication.
Internet-dependent functions.
Recovery process after power interruption.
Replacement procedure.
Gateway planning should be based on the real building rather than only a theoretical distance.
Walls, doors, building materials and network conditions can influence actual deployment.
For TTLock projects, review the TTLock Gateway Guide when planning multi-lock connectivity.
8. Create a Gateway Map
Do not leave gateway locations undocumented.
A simple record may include:
Gateway IDLocationConnected AreaNetworkNotesGW-A1Building A, Floor 1Rooms 101–108Site Wi-FiUtility cabinetGW-A2Building A, Floor 2Rooms 201–208Site Wi-FiCorridor office
The project does not necessarily need this exact structure.
But the operator should know:
Where gateways are located.
Which doors they support.
How they are powered.
Who can access them physically.
This becomes particularly important when diagnosing remote-management problems.
9. Test Local and Remote Functions Separately
A connected smart lock can behave differently locally and remotely.
Therefore, separate the tests.
Local Test
Stand near the lock and test the required local functions.
Remote Test
Move outside the local Bluetooth environment and test the required internet-based functions through the intended architecture.
Do not treat successful Bluetooth communication as proof that remote management works.
Likewise, do not assume that every app feature is supported by every lock.
Confirm the exact functions of the installed model.
10. Test Network Failure
A project should not be tested only under perfect conditions.
Ask:
What happens if the internet goes down?
Depending on the lock and system architecture, test relevant scenarios such as:
Existing PIN access.
Existing fingerprint access.
Existing RFID access.
Mechanical key.
Local Bluetooth access.
Remote functions.
Gateway communication.
The purpose is not to make every function work without internet.
The purpose is to understand clearly which functions remain available and which do not.
Document this for the operator.
11. Test Gateway Failure
If remote management depends on a gateway, temporarily disconnect the gateway during commissioning where appropriate.
Then confirm:
Which local functions remain available?
Which remote functions stop?
What indication appears in the platform?
How is the gateway restarted?
How is connectivity restored?
Does replacement require reconfiguration?
This test gives the property team a realistic failure scenario before an actual service incident occurs.
12. Verify Emergency Access
Every project should understand its fallback procedure.
Depending on the exact smart lock, emergency access may involve:
Mechanical key.
Emergency external power.
Administrator procedure.
Other model-specific backup methods.
Confirm what applies to the installed product.
Then answer operational questions:
Where are emergency keys stored?
Who controls them?
How are they labeled?
Who can access them?
What happens if a battery is fully depleted?
What should staff do first when normal access fails?
Do not store the only emergency key inside the room that the key is intended to open.
Emergency access should be operationally usable, not only technically available.
13. Test Low-Battery Procedures
The property team should know what low battery looks like before encountering it in normal operation.
Confirm the model-specific behavior.
Depending on the lock, this may include:
Warning indication.
App notification.
Audible alert.
Display message.
Reduced-voltage behavior.
Emergency power option.
Then define:
Who checks battery condition?
Who replaces batteries?
Which battery specification should be used?
How frequently is battery status reviewed?
What is the escalation process if a lock repeatedly reports abnormal battery consumption?
Avoid publishing or training staff on one universal battery-life figure unless it is confirmed for the exact product and usage environment.
Actual battery performance can depend on configuration, usage and operating conditions.
14. Confirm Credential Workflows
Commissioning should test not only unlocking but the full credential lifecycle.
For example:
Create → Use → Modify → Expire → Delete
Depending on the project, test:
Permanent users.
Temporary users.
Staff cards.
Guest codes.
Maintenance access.
Administrator credentials.
For rental or hospitality environments, temporary credentials may be especially important.
For offices, staff onboarding and removal may matter more.
For apartments, the operator may need a clear process for tenant turnover.
Build the commissioning test around the actual business operation.
15. Define the User Naming Convention
Poor naming creates long-term confusion.
Imagine an administrator account containing users named:
John
John2
NewCard
Test
Guest
123
Manager
Six months later, nobody knows which credentials should still exist.
A project should establish a simple naming rule.
For example:
Building – Room – User Type – Identifier
or:
Department – Employee – Credential Type
The exact format is less important than consistency.
Good naming becomes even more useful when a system contains hundreds of doors or credentials.
16. Remove Temporary Installation Credentials
Installers often need temporary credentials during setup.
Before handover, review them.
Remove or disable credentials that are no longer required, including:
Test PINs.
Temporary fingerprints.
Installer cards.
Temporary administrators.
Demo users.
The final system should contain only authorized operational users.
Include this step in the acceptance checklist instead of assuming someone will clean it up later.
17. Verify Date and Time
Correct system time can matter for:
Temporary credentials.
Scheduled permissions.
Access records.
Troubleshooting.
Event history.
During commissioning, check whether the installed system shows the correct:
Date.
Time.
Time zone where applicable.
If several devices or platforms are involved, verify that records can be interpreted consistently.
Incorrect timestamps can make troubleshooting unnecessarily difficult.
18. Record the Installed Product Configuration
The property operator should know what was actually installed.
Useful information may include:
Lock model.
Finish.
Mortise.
Hardware version where relevant.
Firmware/version information where available.
App platform.
Gateway model.
Unlock methods.
Door thickness range used.
Key accessories.
Installation notes.
This record becomes valuable when ordering:
Replacement products.
Spare mortises.
Accessories.
Additional locks.
Service parts.
Without configuration records, a future maintenance team may need to rediscover the entire project from photographs.
19. Create a Spare-Parts List
The handover package should identify relevant spare parts.
The exact list depends on the project and lock model.
Potential items may include:
Spare lock units.
Mortises.
Strike plates.
Spindles.
Screws.
Mechanical cylinders.
Cards.
Gateways.
Other replaceable accessories.
Do not create a generic spare-parts ratio for every project.
Instead, evaluate:
Number of installed units.
Importance of the doors.
Local service capability.
Replacement lead time.
Component interchangeability.
Project risk.
The important question is:
If one unit requires service tomorrow, what can the local team replace immediately?
20. Build a First-Line Troubleshooting Procedure
Not every reported failure should immediately become an RMA.
The local team should know how to collect basic information.
For example:
Step 1 — Identify the Door
Door ID, room and building.
Step 2 — Describe the Symptom
Examples:
Fingerprint rejected.
Keypad not responding.
Motor activates but door does not open.
App cannot connect.
Remote function unavailable.
Gateway offline.
Step 3 — Check the Physical Door
Is the door aligned?
Is there mechanical resistance?
Step 4 — Check Power
Battery condition and contacts.
Step 5 — Check Local Access
Does PIN, card, key or fingerprint work?
Step 6 — Check Connectivity
Bluetooth, gateway or network where relevant.
Step 7 — Collect Evidence
Photo, video, app screenshot, door ID and configuration.
This gives technical support far more useful information than:
“Lock does not work.”
21. Agree on the Escalation Path
The operator should know who to contact.
A project may have several support layers:
Property Staff → Local Installer → Distributor → Supplier Technical Support
Define the responsibility of each layer.
For example:
Property Staff
Basic battery, credential and operational checks.
Installer
Door alignment, mortise, mechanical installation and local replacement.
Distributor
Product diagnosis, spare parts and technical coordination.
Supplier
Product-specific technical analysis and production-related support.
This structure prevents every minor issue from becoming a factory-level case while still giving difficult problems a clear escalation path.
22. Train the People Who Will Actually Operate the System
A technical demonstration for the project manager is not enough if the project manager will never use the system.
Train the people responsible for daily operation.
Depending on the project, training may include:
Creating users.
Deleting users.
Creating temporary credentials.
Managing cards.
Reviewing records.
Checking gateways.
Responding to low battery.
Emergency access.
Identifying the correct door.
Reporting problems.
Keep training practical.
The operator should be able to perform routine tasks without depending on the installation team.
23. Provide the Right Handover Documents
A useful handover package may include:
Project Information
Site name.
Project contact.
Installation date.
Supplier/installer contacts.
Door Schedule
Door ID.
Location.
Lock model.
Configuration.
Test status.
System Information
App/platform.
Gateway structure.
Administrator arrangement.
Device naming convention.
Operating Documents
User manual.
App instructions.
Credential procedures.
Emergency-access procedure.
Technical Documents
Installation instructions.
Relevant product specification.
Approved configuration.
Service Information
Spare-parts list.
Troubleshooting procedure.
Support contact.
Escalation flow.
Do not put sensitive passwords inside a widely shared handover document.
Account access should be transferred through an appropriately controlled process.
24. Complete a Final Acceptance Test
The final acceptance test should be based on the agreed project requirements.
There is no universal smart lock acceptance checklist that applies identically to every product.
However, a project may confirm categories such as:
CategoryAcceptance QuestionInstallationIs the lock securely installed?Mechanical operationDoes the door lock/unlock smoothly?FingerprintDoes the required function operate?PINDoes the required function operate?CardDoes the required function operate?Mechanical keyHas backup access been verified?AppIs the correct platform configured?GatewayAre required connected functions working?Remote functionsHave required workflows been tested?Network failureIs expected behavior understood?BatteryIs the replacement procedure understood?Emergency accessHas the fallback method been tested?User managementCan authorized staff create/remove users?DocumentationHas the operator received the required records?TrainingCan the operating team perform routine tasks?Spare partsHave required spares been identified?
Record unresolved items separately.
A project should not be considered completely handed over simply because most doors can open.
25. Create a Punch List Before Sign-Off
Some issues may remain after the main installation.
Instead of handling them informally through chat messages, create a punch list.
Example:
Door IDIssueOwnerActionStatusA-305Strike requires adjustmentInstallerRealign strikeOpenB-203Gateway connection unstableNetwork teamCheck Wi-FiOpenC-101Label incorrectSupplierReplace labelClosed
This creates accountability.
The project team can clearly distinguish between:
Accepted items and remaining corrective actions.
Smart Lock Commissioning Checklist
Use this checklist before handing a project to the final operator.
Physical Installation
Door closes correctly.
Lock is securely installed.
Mortise operates smoothly.
Handle returns correctly.
Strike is aligned.
Mechanical key has been tested.
Installed configuration matches the approved product.
Electronic Functions
Fingerprint tested where included.
PIN tested where included.
RFID card tested where included.
App operation tested.
Required alarms or additional functions tested.
Correct software platform confirmed.
Connectivity
Bluetooth operation confirmed.
Gateway connectivity confirmed where required.
Remote functions tested.
Gateway locations documented.
Network-failure behavior understood.
Gateway-failure behavior understood.
Administration
Permanent administrator identified.
Account ownership transferred.
User roles defined.
Temporary installer credentials removed.
Naming convention established.
Date and time verified.
Emergency Operation
Mechanical backup confirmed.
Emergency power procedure confirmed where applicable.
Low-battery behavior understood.
Emergency keys controlled.
Staff know the escalation procedure.
Documentation
Door schedule completed.
Lock models recorded.
Gateway map completed.
Manuals provided.
Configuration information recorded.
Spare-parts list prepared.
Support contacts provided.
Open punch-list items documented.
Training
Property staff trained.
User creation demonstrated.
User deletion demonstrated.
Temporary access demonstrated where relevant.
Emergency procedure demonstrated.
Basic troubleshooting demonstrated.
Common Smart Lock Handover Mistakes
Using the Installer's Personal Account
The permanent operator should have an appropriate long-term ownership arrangement.
Testing the Lock Only With the Door Open
Mechanical alignment problems may only appear when the door is closed.
Checking Bluetooth but Not Remote Access
Local communication does not automatically confirm gateway-based remote operation.
Forgetting to Test Offline Conditions
Operators should understand which functions remain available if the network is unavailable.
Leaving Test Users in the System
Temporary installation credentials should be reviewed before acceptance.
Not Recording Gateway Locations
Future technicians need to know where the network devices are installed.
No Door Identification System
Troubleshooting becomes much harder when nobody can identify the exact installed unit.
No Spare-Part Plan
A small hardware issue can create unnecessary downtime if the required replacement part is not locally available.
No Operating Training
A working smart lock system can still create complaints if property staff do not know how to manage it.
Treating Handover as a Folder of Manuals
Documentation is important, but handover should also transfer control, knowledge and responsibility.
Commissioning vs Installation vs QC: What Is the Difference?
These stages solve different problems.
StageMain QuestionSample TestingIs this lock suitable for the project?Production QCIs the approved product being produced consistently?InstallationHas the lock been physically fitted correctly?CommissioningDoes the complete installed solution work as required?HandoverCan the operator independently manage and support the system?After-SalesHow are issues handled during ongoing operation?
Treating these stages separately makes responsibilities clearer.
A lock can pass factory QC and still be incorrectly installed.
A lock can be correctly installed but incorrectly configured.
A system can function technically but still be poorly handed over.
Successful project delivery requires all three areas:
Product + Installation + Operation
FAQ
What is smart lock commissioning?
Smart lock commissioning is the process of verifying the installed lock, access methods, software, connectivity, emergency functions and operating procedures before the system enters normal operation.
When should commissioning happen?
Commissioning normally takes place after installation and before final project acceptance. Planning for it should begin earlier so documentation, accounts and testing requirements are ready before installation ends.
What should be included in a smart lock handover?
A handover may include the door schedule, product configuration, administrator ownership, gateway map, operating instructions, emergency procedures, spare-parts information, training records and unresolved punch-list items.
Who should own the smart lock administrator account?
For a B2B project, long-term control should normally remain with the responsible customer organization or authorized operator rather than depending permanently on an installer's personal account.
The exact arrangement depends on the software platform.
Should every smart lock project test internet failure?
If the project depends on connected or remote functions, understanding behavior when the network is unavailable is useful.
The goal is to identify which functions continue locally and which depend on connectivity.
Should gateway failure be part of commissioning?
If gateways are important to the project's remote-management architecture, test and document the expected behavior when gateway connectivity is unavailable.
What documents should a smart lock installer hand over?
Useful documents may include a door schedule, installation records, manuals, lock configuration, gateway mapping, operating procedures, administrator information, spare-parts list and support contacts.
The exact documentation depends on project size and complexity.
Is commissioning necessary for a small project?
The process can be simplified for smaller installations.
A five-door office does not need the same documentation as a 500-door apartment project.
However, even a small project should clearly establish administrator ownership, emergency access and basic operating procedures.
A Smart Lock Project Is Finished When the Operator Can Run It
The final objective of a smart lock project is not simply to install hardware.
The system should reach a point where the operating team can confidently answer:
Which lock is on each door?
Who controls the administrator account?
How are users added and removed?
Which functions depend on a gateway?
What happens if the network fails?
How is emergency access handled?
Which spare parts are available?
Who should be contacted when a problem occurs?
That is the difference between an installed smart lock and an operational smart lock system.
A better project workflow is:
Select → Test → Produce → Inspect → Install → Commission → Handover → Operate → Support
If you are planning smart locks for apartments, hotels, offices, rentals or other multi-door projects, prepare the project requirements before requesting the final system quotation.
SEGULOCK supports B2B smart lock buyers with product selection, project configurations and related lock hardware.
Review the SEGULOCK smart lock solutions, or submit your project type, required functions, door information and estimated quantity through the Catalog & B2B Quote page.
The earlier the handover requirements are defined, the easier it becomes to turn a smart lock installation into a system the customer can actually operate.
Get in touch
Address
Room 3060, Area C, No. 544 YaYun Avenue, Dalong Street, Panyu District, Guangzhou, Guangdong Province, China