Log household key, fob and access-card handovers

A key handover log is a shared, dated record of each time a household access item is issued, returned or passed from one person to another. Items can include unit keys, building fobs, access cards and mailbox keys. Each entry records what moved, who gave it, who received it, whether a return date was agreed, and whether both people acknowledged it. When a fob stops working, someone moves out, or the building asks who holds a card, the household can check the log instead of relying on memory.

There is no single required format. The same set of columns works as a spreadsheet, a printable form or a short handover letter, so you can choose whichever your household will actually keep up to date. The template below is an original, illustrative starting point. Add or remove columns to fit your household.

What the log is for, and what it is not

The log is an administrative record of handoffs that are already authorized. It does not grant anyone permission to hold, copy or transfer a building's access items. That permission comes from whoever manages access to the building or unit, such as a landlord, property manager or building operator. Before recording a new issue or transfer, confirm with that person or office that the handover is allowed, and note who confirmed it.

Keep the log focused on access items. Some published key handover receipt templates, including FileIt's, limit their scope to the listed handover and keep it separate from property-condition and deposit records. Following the same separation keeps a key log short and avoids mixing an access record with questions about money or damage.

Fields to include

The fields below are suggestions. Use the ones that serve your household's purpose. The notes column explains entries that people often fill in inconsistently.

Field	What to write	Notes on ambiguous entries
Event ID	A short running number, such as H014	Lets a return entry point back to the original issue.
Date and time	When the item actually changed hands	Use the handover time, not the time you typed the entry.
Household or unit reference	A neutral label, such as Unit A	Avoid writing a full street address in a shared file.
Event type	Issue, return or transfer	Issue: an item goes out to a person. Return: it comes back. Transfer: it passes directly between two holders.
Item type	Unit key, building key, fob, access card, mailbox key	Record each type on its own line instead of grouping them.
Agreed item reference	A label everyone recognizes, such as Card C2 or Blue-tag key	Use the number printed on a card or fob if there is one. Otherwise agree on a tag or color.
Quantity	How many of that item	Matters most for identical keys, such as two mailbox keys.
Giver	Who handed the item over	Use the name the household normally uses.
Recipient	Who received it	For a return, the recipient is whoever now holds it for the household.
Authorization confirmed with	The role that approved the handover, such as property manager	Write the role, not private contact details.
Agreed return date	Only if the handover is temporary	Leave it blank for ongoing holders. Do not guess a date.
Acknowledgment	Initials or a short confirmation from both people	Both the giver and the recipient should confirm.
Unresolved follow-up	Anything still open and who will check it	Example: card not activated yet, Lee to ask the front desk by Friday.

Housing providers' own forms show how item types are often split. Manitoba Housing's keys and access cards distribution form, for example, lists access cards, main-entry and laundry keys, unit-door keys and mailbox keys separately. It records the holder, the card or key identifier, issue or activation dates, return dates and signatures or initials, plus a quantity for mailbox keys. That is one agency's form, not a universal requirement, but splitting items by purpose this way makes a household log easier to check.

Copy-ready template

Paste this header row into the first row of a spreadsheet, or use it as the column headings of a printed table. In a spreadsheet, each column becomes a field and each handover becomes a new row.

Event ID | Date/time | Unit ref | Event type (issue/return/transfer) | Item type | Item reference | Qty | Giver | Recipient | Authorization confirmed with | Agreed return date | Acknowledged (giver/recipient) | Unresolved follow-up

Illustrative sample entries

The following hypothetical entries show a temporary card loan and its return. The return is logged as its own event linked to the original, rather than as an edit to the first row.

H014 | Nov 6, 5:00 p.m. | Unit A | Issue (temporary) | Access card | C2 | 1 | Morgan | Lee | Property manager | Nov 8 | Morgan ✓ / Lee ✓ | None
H015 | Nov 8, 7:30 p.m. | Unit A | Return (links to H014) | Access card | C2 | 1 | Lee | Morgan | Property manager | — | Lee ✓ / Morgan ✓ | None

Choosing a format: spreadsheet, printable form or letter

• Spreadsheet (such as Excel or Google Sheets): best when several people need to see the current record. You can filter by item reference to find an item's latest event.
• Printable form or PDF: useful when a handover happens in person and both people want to initial a paper copy. Keep the printed columns identical to the spreadsheet so entries can be transcribed later.
• Short handover letter (Word or PDF): suits a single, more formal handover, such as a household member moving out and returning every item at once. Use the same fields written as sentences.

An illustrative handover letter built from the same fields might read as follows. Replace the bracketed placeholders.

Access item handover – [Unit reference]

Date and time: [date, time]
Event: [Issue / Return / Transfer]
Given by: [name]
Received by: [name]
Authorization confirmed with: [role, e.g. property manager]

Items:
  - [Item type], reference [ID], quantity [n]
  - [Item type], reference [ID], quantity [n]
Total items: [n]

Agreed return date (if temporary): [date or "not applicable"]
Open follow-ups: [description and who will check, or "none"]

Giver initials: ____    Recipient initials: ____

FileIt's receipt template follows a similar structure. It distinguishes the giver from the recipient, describes each item, gives a total count, and includes an optional return date for temporary handovers.

Steps at each handover

• Confirm that both people agree to the handover and that whoever manages building access permits it.
• Count the items together and match each one to its agreed reference.
• Record each item type on its own line, with quantity.
• Agree on a return date only if the handover is temporary.
• Have both people review the entry and add their acknowledgment.
• Note anything left unresolved and who will follow up.
• Save the entry to the household's single shared version of the log.

RentRight's suggested handover workflow follows the same order. It identifies the event, unit, participants and their roles, counts items by purpose, records unresolved items with agreed follow-ups, and keeps one common version that everyone works from.

Keeping the record accurate over time

• Agree who can view and edit the log, and keep it in one place so there are no competing copies.
• Fix mistakes by adding a dated correction line that references the original event ID, rather than deleting or overwriting the earlier entry.
• Reconcile by item reference from time to time. Every issue should have a matching return, or an open entry showing who currently holds the item.
• If an issue has no matching return, ask the listed holder and, if needed, the building's access contact a factual question about where the item is. Do not assume it is lost, and do not treat the log as permission to change or deactivate access.

What to leave out

Do not write door codes, alarm codes, gate PINs or similar access codes in the general log. RentRight's guidance recommends keeping sensitive codes out of the shared record, because a log that many people can read is a poor place for anything that grants entry by itself. Record that a code was shared or changed if it matters, without the code itself, and keep property-condition notes and deposit matters in their own separate records.