Baltimore Leasing Records: Hand Over the Signed Version and Its Supporting Evidence
Homzora editorial team · Reviewed October 17, 2026
A leasing folder often contains drafts, attachments, email copies, and a signed document with similar filenames. Before responsibility passes to another staff member, identify the version that governs the current record and preserve the supporting history. A filename ending in final is not proof that a document was signed or accepted.
For Baltimore landlords, this recordkeeping task should remain separate from deciding whether the document satisfies legal requirements. Use qualified legal review for lease terms and applicable obligations. A software template or signature screen does not establish that a document is suitable for the property.
Create a document register
Give each document a title, property and unit reference, date, status, and location. Distinguish a draft from an executed document and a later amendment. Do not merge versions simply because their first pages look similar.
Record the source of the file and how it was received. If a signature service supplies a supporting record, preserve it using the service’s instructions and your retention procedures. Avoid promising that any one file type proves every legal issue.
Ask an authorized reviewer to resolve ambiguous status. If the system contains an unsigned attachment and an email saying agreed, keep both and ask what further review is needed. Do not manufacture certainty by renaming the attachment signed.
Keep property evidence distinct
A city licensing document, an inspection record, and a lease have different functions. Baltimore’s rental license prerequisites should be checked through the official sources. Attaching a license to a leasing folder does not replace reviewing the lease, and a signed lease does not demonstrate that licensing is complete.
Use separate labels that make those differences visible to incoming staff. If a document’s date or unit description conflicts with another, record the discrepancy and seek clarification. Preserve the original rather than editing the evidence to remove the conflict.
The handover should tell the next person which questions remain open and who is responsible for answering them. A folder with no visible questions can be misleading when the questions were simply left in someone’s inbox.
Control the transition between staff
Decide when the incoming person becomes responsible for communication and which tasks stay with the outgoing person. Provide the minimum access needed for the role and follow your organization’s process for changing permissions.
Keep passwords and entry codes outside broadly shared document registers. The register can identify where authorized access is managed without exposing the credential itself. A handover should reduce dependence on one person while preserving appropriate restrictions.
Ask the incoming reviewer to locate the current signed document and a related attachment without assistance. Then ask them to identify an unresolved item. This test reveals practical gaps better than simply asking whether they received the folder.
Handle a late revision visibly
Suppose a fictional amendment arrives after the initial handover. Record it as a later event, verify its status through the appropriate review, and notify the person who now owns the file. Do not silently replace the earlier document and leave staff using an old download.
Where a document changes a payment or operational instruction, confirm the implementation separately. Saving a file does not automatically change a billing schedule, access arrangement, or resident communication in another system.
The checks below connect document control with physical access and turnover coordination. Use only the parts relevant to your property, and obtain legal guidance when the content or authority behind an instruction is unclear.
Define the property and the authorized decision maker
Start with the full property and unit identifier. Record who is responsible for approving access and who is responsible for maintaining the register. If those are different people, make the handoff explicit.
Do not assume that possession of a key creates authority to enter. The register should record the basis for an authorized visit through the appropriate process, not merely the fact that someone has a physical object.
Keep the tenancy timeline separate from the maintenance schedule. A planned cleaning date does not by itself establish that possession has been returned or that entry is permitted. Confirm the relevant facts and seek appropriate advice where the situation is uncertain.
Separate credentials from general work orders
A work order may need an appointment time and contact without needing to display an access code to every user. Store credentials through an appropriate restricted process and share them only with authorized people who need them.
Do not place active codes in photographs, public notes, or broadly shared calendars. Review how your software exposes attachments and comments to residents, owners, and vendors. A field described as notes may not be private by default.
If a temporary credential is used, record its intended purpose and review date. Confirm how it is changed or disabled through the authorized system. Do not assume that deleting a message removes the credential from use.
Connect access to a specific task
For each visit, record the task, provider, proposed window, confirmation, and completion status. Keep access approval distinct from the work quote. A vendor can be approved to perform work without every access detail being settled.
Ask the provider to identify who will attend and how changes are communicated. If a different worker arrives, use the agreed verification process rather than handing over access based only on a company name.
Avoid collecting unnecessary personal information about workers. The aim is to verify the authorized appointment and responsibility, not to create a private database unrelated to the job.
Plan the sequence of turnover work
List tasks in the order they depend on one another. A repair that creates dust may need to happen before final cleaning. A delivery may require an entrance to remain clear. The access schedule should reflect the actual work sequence.
Record which tasks can overlap and which cannot. Do not promise the same restricted space to several providers at once without checking feasibility. If the sequence changes, notify the affected people through the agreed channel.
Keep a decision point for delays. Identify who will reschedule the next appointment if the earlier task runs long. That prevents each provider from assuming someone else has informed the incoming household.
Record the condition and documents at handover
Use the appropriate property process to document the handover, including the access items provided and any relevant condition record. Give the receiving person an opportunity to identify discrepancies through the agreed channel.
Do not use a key receipt to imply that unrelated disputes are settled unless the actual document and applicable advice support that interpretation. Keep administrative acknowledgment separate from broader legal conclusions.
Store the final signed or confirmed record securely. A photograph of keys on a counter may show objects but not the agreement about them. The useful evidence identifies what was transferred, when, and through which authorized process.
Test access controls in software
If using a property management platform, test the workflow with fictional records. Ask whether a vendor can see only the necessary job details and whether access information can be restricted. Review the current plan rather than assuming every permission feature is included.
TurboTenant and Buildium publish feature information that can help frame questions. Ask the provider to demonstrate your specific sequence, including a rescheduled visit and a completed handover. A generic task list may not address credential handling.
Keep a backup process for an outage that does not depend on sharing passwords broadly. The process should preserve appropriate authorization and privacy, not bypass them because the software is unavailable.
Review missing items and open exceptions
If an access item is missing, record the facts and contact the responsible property professional. Do not assume that a software entry saying returned means the item was physically received. Use evidence appropriate to the handover.
Any change to locks or credentials must follow the applicable authority, agreement, and legal requirements. This guide does not authorize a landlord to lock out a resident or change access during a dispute.
Keep the exception open until the responsible person records the action and supporting information. A clear unresolved item is better than a false completed status that leaves the next manager unaware of the issue.
Finish with a controlled handoff
At turnover completion, review the register with the person who will manage the tenancy. Confirm current holders, active credentials, completed visits, and unresolved questions. Remove access that is no longer appropriate through the authorized process.
Retain records according to the business’s legitimate needs and applicable requirements. Avoid keeping sensitive credentials in an archive after they are no longer needed. Preserve the history of actions without unnecessarily preserving a usable secret.
A restricted access checklist
Before a vendor visit, confirm the job reference, authorized person, approved access process, appointment window, and contact for a problem. Keep the actual credential outside the general checklist. The checklist should explain the process without becoming a convenient source of unauthorized entry information.
After the visit, record attendance, completion status, and return of any issued item. If a credential needs to be changed or retired, assign that action to the person authorized to do it and record confirmation. Do not assume the action happened because it appeared on a task list.
At the incoming household handover, compare the physical items with the prepared record. Correct the count before finalizing the administrative acknowledgment. If an item is missing or disputed, document the issue and follow the appropriate process rather than concealing it to finish quickly.
These checks should remain proportionate to the property. A small rental may use a simple secure register, while a larger building may require a dedicated system. In either case, clear authority and restricted information are more important than the number of software features.
Optional resource
Affiliate disclosure: Homzora may earn a commission if you purchase or sign up through these links.
Explore TurboTenant. Ask how the current plan handles document versions, permissions, and exports. Obtain appropriate legal review of the documents themselves.
Sources and further research
The official sources below support the local facts and service references. Worked examples and worksheets are planning suggestions, not market prices or guarantees.