Table of contents
A vendor finishes a unit turn and leaves with the access badge in a toolbox. The badge stays active for weeks, and nobody notices until a resident asks who still has access. The work ended; the access did not. A badge return checklist keeps the end of the project as controlled as the start. It is short, and it prevents the most common access gap: a credential that was issued and never collected.
Start the checklist when the badge is issued
Record the badge, the vendor, the project, the issue date, and the expected return date. A return checklist that begins at the end has already lost the issue record. The expected date should match the project schedule. Name the person who will collect the badge and a backup. A collector who is on leave when the project ends is not a plan. The checklist should show who is responsible at the closeout.
Confirm the badge is physically returned
Check the badge and record the return date and the condition. A vendor's promise to return it is not a return. If the badge is damaged, record the damage and the replacement cost. If the badge is not returned on the last day, record the exception and the action. Deactivate the badge under the property's rule before the vendor leaves. Do not wait for a reminder.
Deactivate or reprovision the credential
Record the deactivation date and the person who did it. If the badge is reused for another vendor, record the reprovision and the new holder. A badge that is returned but still active is a risk. Check the access system, not only the physical badge. A badge may be returned while a mobile credential or a temporary code remains active. The checklist should include every credential the vendor held.
Reconcile keys and fobs
If the vendor held keys, fobs, or a lockbox code, record each item and the return. A badge-only checklist can miss a physical key. The property's access inventory should match the items returned. If a key is missing, follow the lock-change rule and record the approval. Do not issue a replacement key without changing the lock. A duplicate access path is a security gap.
Confirm the vendor's closeout
Record the vendor's final invoice or closeout note. A badge return is part of the closeout, not a separate favor. The record should show that the work, the access, and the payment are aligned. If the vendor is expected back for a punch list, issue a new badge or record the exception. Do not leave the original badge active for a future visit. A new visit should have a new issue record.
Review the checklist with the access owner
Ask the property's access owner to confirm the deactivation and the key reconciliation. Record the confirmation and the date. A checklist that is completed only by the vendor's contact is weaker. If the access owner is unavailable, record the alternate route. The confirmation should not wait indefinitely. The record should show who accepted the closeout.
Review the exceptions monthly
At the end of each month, review the badges that were not returned and the keys that were missing. Look for the vendor or project type that repeats. The pattern is more useful than a single exception. Change one step based on the review. A clearer issue record or a mandatory deactivation is often enough. Record the change and the date.
Protect the access record
The checklist can include vendor names, badge numbers, and key details. Keep it in the approved system and limit access to the property team. Do not circulate the access list in a broad channel. Set a retention period with the property's records policy. Keep enough to support an access review and no more. A badge log kept indefinitely creates risk without adding insight.
Keep the checklist at the access desk
The checklist should be available where the badge is issued and returned. A form stored in a folder nobody opens will be skipped at the end of a long job. Keep a printed or digital copy at the desk. Review the format after a month and remove fields that are never used.
Review the access list with the vendor
Before the job starts, confirm which credentials the vendor needs and which must be returned. Record the list and the expected return date. A vendor who knows the return expectation is easier to close out. The confirmation also prevents a badge from being issued and forgotten.
Key takeaways
- Start the checklist when the badge is issued, not at closeout.
- Confirm the physical return and deactivate every credential.
- Reconcile keys, fobs, and lockbox codes with the access inventory.
- Record exceptions and review the pattern monthly.
A badge return checklist is a small closeout control. It keeps access aligned with the work and protects the property after the vendor leaves. It also makes the next issue faster, because the access record is already current. For related workflows, see the common-area key inventory brief and the property management VA services overview.