Define the handover scope
A property management handover should start with a written scope that names the properties, the services, and the date the new manager takes over. List the staff, vendors, and owner contacts included in the transfer. State what is explicitly excluded, such as a renovation project or a separate rental program. A clear scope prevents the new manager from inheriting an obligation nobody agreed to transfer.
The scope should also name the person who will answer questions during the transition. That person needs enough authority to resolve a records gap or approve access. If the outgoing manager is leaving the company, identify a second contact who can fill in after the departure. The handover file should show both names and the dates they are available.
Inventory the live documents
Build a document inventory before copying files into a new folder. List the management agreement, the current lease or occupancy agreement, the property rules, the vendor contracts, the insurance certificates, and the latest inspection reports. Mark each document as current, superseded, or missing. A folder full of undated files is not a handover, because the next manager cannot tell which version governs.
Use one naming convention and one index for the handover set. The index should show the document title, the version date, the owner, and the location. Keep drafts and old versions in a separate archive rather than mixing them with the live set. If a document exists only in email, save a copy to the handover set and note where the original came from.
Record open vendor and maintenance items
The new manager needs a list of every open work order, the vendor assigned, the approval, and the expected completion date. Include the property, the scope, and the person who will confirm the work is finished. A vendor who has been paid but has not completed the work should appear on the list with a clear follow-up. The list should be current on the handover date, not copied from the previous month.
Separate routine maintenance from projects that need an owner decision. A leaking faucet is a routine repair, while a roof replacement or a landscape redesign may require a budget approval. Record the decision status and the next date for each project. The new manager should know which items can proceed and which must wait for the owner.
Summarize access and security arrangements
Access is one of the most common sources of handover failure. Record the keys, fobs, alarm codes, gate codes, and digital access assignments for each property. State who holds each item and how it will be returned or reassigned. Do not send a full code list to the entire team, because the handover file should limit access to the people who need it.
Include the security provider, the monitoring account, and the person who can authorize a change. Note any recent access incident and the action that was taken. For a property with staff or tenants, record the expected schedule and the rule for unscheduled visits. The new manager should be able to enter the property lawfully and explain the access rules to a vendor.
Reconcile the financial file
The financial handover should show the current rent roll, the security deposits, the open invoices, and the owner disbursements. Reconcile the bank records with the management ledger before the transfer date. A difference should be explained rather than carried forward as an unknown. The new manager needs a starting balance that can be defended.
List the recurring payments, the vendor terms, and the owner funding arrangements. Note any payment that is disputed or overdue and the person handling it. Keep the supporting statements with the reconciliation, not in a separate email folder. If a tenant or owner asks about a charge after the handover, the new manager should be able to trace it to a source.
Test the new manager's access
Before the handover date, ask the new manager to open the shared folder, the management system, and the key documents. Test the vendor contact list and the owner communication channel as well. A permission that looks correct in a settings screen may fail when the person actually tries to use it. Record the test and the date it passed.
If a system requires a new account, start the request early because approval can take time. Do not share a personal password or a former employee's login as a shortcut. Set the new account with the right role and remove the old access after the transfer. The handover is complete only when the new manager can work without borrowing someone else's credentials.
Run a joint walkthrough
A joint walkthrough gives the outgoing and incoming managers a chance to compare the file with the property. Visit the rooms with open work orders, the storage areas, and the access points that are easy to overlook. Confirm the meter readings and the condition of any item that will be listed in the handover record. Take dated photos and attach them to the file.
The walkthrough should produce a short exceptions list rather than a general statement that everything is fine. Record the item, the responsible person, and the date it will be resolved. Both managers should sign or acknowledge the list. A week later, review the exceptions again to confirm that nothing was lost during the transition.
Set the review window after handover
Keep a review window of thirty to sixty days, depending on the property and the number of open items. Schedule a short check at the end of the first week and another at the end of the first month. Ask the new manager which document was missing and which question took too long to answer. Those answers are the best guide for improving the next handover.
Update the template with the gaps that appeared, but do not rewrite the historical record. The property file handover and the vendor access log should use the same property identifiers and access rules. A documented handover protects the owner, the tenant, and the team that takes over. It also makes the next transition less dependent on one person's memory.