What this guide covers

A property-manager lock-service handover should show what was authorized, what was completed, and what remains. “Locks done” is too vague when a job covers several units, common entrances, or different credential systems. This checklist creates a clear record that another manager can understand without reconstructing the visit from messages.

Use an opening identifier throughout the job. Connect each door to its hardware, approved action, testing result, and keys or credentials issued. Keep authorization records and user details private; the working summary should contain only the information needed by responsible parties.

Set the boundaries before you begin

Name the management approver, site contact, and person who will accept completion. If they are different people, agree how decisions and handover notes reach the approver. A receptionist who can admit a technician may not be authorized to approve additional work.

Distinguish private doors, common hardware, landlord systems, and equipment managed by another provider. Record permissions and dependencies before the visit. Shared-access administration may remain separate from a physical lock-service appointment.

Capture the approved scope

For every opening, record the original condition and intended result: authorized entry, a changed key arrangement, repair, installation, or another supported service. Include known management-key or master-key requirements for review. Identify any requested work not yet assessed or approved.

Keep additions to the scope traceable. If an on-site assessment identifies a separate door or frame issue, record who approves it and who will perform it. Do not let a conversation about an extra opening silently expand the completed-work record.

Record hardware and access changes

Identify the components serviced or supplied, with make and model information where available. A cylinder change, full assembly replacement, and strike adjustment are different descriptions. Document the actual work in language a later manager can connect to the opening.

Record the resulting key groups and any electronic credential action separately. Mechanical service should not be assumed to revoke a shared fob or app account. If another administrator performs that change, capture the confirmation and responsible party as its own item.

Accept through useful tests

Use the opening’s normal operating sequence to confirm the agreed outcome with the authorized representative. Test the supplied key groups and any intended access exclusions. Where special door functions apply, have the responsible qualified parties verify the requirements for that actual installation.

Record the tester, date, and result. If a function could not be tested, state why and name the follow-up owner. A photograph of new hardware is useful identification, but it does not replace a functional handover record.

Issue access and close remaining tasks

Count the keys or credentials supplied and record recipients through the property’s private process. Do not include key cuts or usable codes in the general job report. If keys are held temporarily by management, identify custody until they are issued.

List unresolved work with a responsible person and next action. Include separate trade repairs, pending administrator changes, or an unserviced door. Close the job’s completed scope without describing the whole property as finished when dependencies remain.

Copy and use this worksheet

Use one record for each opening, vehicle, user, or project item covered by this guide. Write “unknown” where information is missing, rather than guessing. Keep this working record private; it is an administration aid, not a place to publish combinations, usable access codes, photographs of key cuts, or personal identification documents.

  • Property, job reference, and service date: ____.
  • Approver, site contact, and handover recipient: ____.
  • Opening ID and private/shared responsibility: ____.
  • Original symptom and approved intended result: ____.
  • Serviced/supplied hardware and model information: ____.
  • Agreed key group or management-access requirement: ____.
  • Functional tests, tester, date, and result: ____.
  • Keys/credentials supplied, custody, and recipient acknowledgment: ____.
  • Separate digital administration confirmation: ____.
  • Remaining work, responsible party, and next review date: ____.

Complete the review and keep a useful record

Compare the completed record with the approved opening list before filing it. Ask for clarification where a description is too broad to identify the work. Keep manufacturer instructions, permitted photographs, and component identifiers with the record so future service starts with reliable information.

Connect the handover to the apartment-turnover checklist and the commercial door inventory as applicable. A well-maintained record prevents new staff from confusing key custody, technical work, and pending property decisions.

A handover record should explain partial completion

A hypothetical opening entry might state D-02; compatible cylinder rekey completed; two approved keys supplied; normal lock operation tested by the manager; existing closer symptom remains outside the completed scope; closer assessment assigned to a named contact. It records the useful completed result and the continuing dependency in the same place.

A second opening may be unserviced because authority or identification is still unresolved. Keep its status separate instead of adding it to the completed key count. The next manager should be able to tell which doors can be accepted now and which still require a decision or visit.

Where electronic administration is involved, record the actual confirmation from the responsible administrator. A new mechanical cylinder should not become an indirect claim that a former user’s fob was removed. Distinct completion records make the property handover more accurate without requiring a long narrative.

Related service information

For the work discussed here, review apartment access turnover and commercial door inventory. Describe the actual situation to the team before choosing a service scope.