Pittsburgh Rental Turnovers: Keep a Clear Key and Access Register
Homzora editorial team · Reviewed October 17, 2026
A rental turnover can involve an outgoing resident, a cleaner, a repair vendor, a manager, and an incoming household. If access is coordinated through scattered messages, it can become unclear who has a key, which appointment is confirmed, and whether a temporary credential has been retired.
This guide provides an administrative method for a Pittsburgh rental property. It does not establish legal rights of entry, notice periods, lock change rules, or authority to exclude anyone. Those issues require the applicable law and agreement. The register described here is a way to document authorized access while protecting sensitive information and keeping the handover understandable.
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.
Inventory physical access items
List keys, fobs, remotes, and other access items by a neutral identifier. Avoid labeling a lost key with enough information to identify the property. Keep the mapping between identifiers and doors in a secure record.
Record how many items exist, who is authorized to hold them, and when they are issued or returned. If the count is uncertain, say so and investigate. Do not make the register appear complete by assuming that an unreturned item has been destroyed.
For shared building access, coordinate with the person responsible for that system. A unit manager may not control every fob or door in the building. Keep responsibilities clear so that a request is sent to the correct party.
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.
Use a fictional handover example
Imagine a hypothetical apartment where a repair vendor visits on Monday, a cleaner on Tuesday, and the new household collects keys on Wednesday. The register records a distinct authorization and status for each event.
If the repair is delayed, the cleaner’s appointment is reviewed rather than left unchanged automatically. The incoming key handover is confirmed against the actual readiness and applicable agreement. The example does not grant permission to delay possession or change legal obligations; it shows why operational dates must be tracked accurately.
At the end, the manager can identify which access items were issued, which were returned, and which actions remain open. That is more reliable than searching a message thread for a casual statement that everything is all set.
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 good Pittsburgh turnover register does not make entry lawful by itself. It helps authorized people coordinate work, protect information, and explain the handover. Those are practical benefits when several providers and households are involved in the same short period.
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 planning resource
Affiliate disclosure: Homzora may earn a commission if you purchase or sign up through this link.
Explore TurboTenant. Ask about the current document, task, and permission features for your workflow. Software does not determine whether entry or a credential change is legally authorized.
Sources and further research
These official resources support the local facts and service information above. The worksheets and examples are Homzora planning suggestions, not quoted prices or promises of service.