Track key fobs by number: list every fob the building owns with its number and access level, record one current holder per fob with the date it went out, and close that record with a return date or a lost mark before the fob goes to anyone else. The access system logs which credential opened a door. The custody record says whose hand it was in, and that is the question the building gets asked.

You know how many fobs the building bought, and the reader on the garage door logs which credential opened it, down to the minute. Both records are accurate for what they record. Neither holds whose hand that credential was in: the resident it was issued to, the relative who kept it after a visit, or the mover who walked out with it in March. A fob that is out and unaccounted for opens every door its access level allows, until someone turns it off at the reader.

Fob custody: whose hand each fob is in

Fob custody (fob tracking, at most desks) is the building's record of which numbered access fob each person holds, since when, and what happened to every fob that came back or did not. The access-control system knows credentials: it logs that fob 214 opened the garage door and decides which doors fob 214 may open. It does not know that fob 214 was issued to the resident of 1204 in March, lent to a contractor in June, and reported lost in September. Custody is the half a building has to keep itself, because the reader cannot.

The two records answer different questions: the access log, which fob opened a door and when; the custody record, who holds this fob, which fobs are out that should not be, and what was issued to the resident who is moving out on Friday. Fob custody is one of the six records a staffed desk keeps; Front Desk Operations for Residential Buildings maps the full set.

What a fob record should include

A fob record carries seven fields, and each answers a failure the desk has already had:

  • The fob number, printed or engraved on it: how the desk tells one from another.
  • The access level: resident, owner, staff, guest, management, or contractor, so a fob's reach is known before it goes out.
  • The facility code where the access system uses one, and the unit the fob belongs to.
  • The current holder, by name and by kind (resident, owner, staff member, contractor).
  • The issue date, and the return date when the fob comes back.
  • The status: active, returned, or lost. Lost is a status with a date, not a note in the margin.
  • Who at the desk issued or took back the fob.

A fob never issued still belongs on the list, because the inventory is what the count is checked against: fobs on hand plus fobs out should equal fobs owned, and the day the sum is short, a fob has gone missing without a record.

Issuing a fob: one holder, one open record

Issuance is where the record is made. A fob goes out against one named holder, with the date, and the record stays open until that fob comes back. Three rules keep it honest. The holder is a person on file, picked from the directory rather than written as the resident spelled it, so the fob can be found from the person as well as from the number. The fob goes out at the access level the person's role needs and no higher: a contractor's fob opens the service corridor and the floor the job is on, not the residents' lounge. And the note goes on at issue time (the replacement for a lost fob, the second fob for a unit, the fob lent for a renovation), because it is read months later by someone who was not there.

Returns: closing the record, and the fob that is still out

A return closes the record: the fob comes back, the date goes on, the status moves to returned, and the fob is on hand for the next issuance. The return is where the discipline bends, in an understandable direction. A mover hands in a bag of fobs at the end of a move-out, or a contractor leaves one at the desk with no name on it, and the instinct is to put it back in the drawer and issue it to the next person who needs one. The cost shows up in the record: the fob now has two holders and no return, or the old holder's record closes with a return date that is really an issue date, and the next time anyone asks who held fob 214 in August, the record answers with a name that was not holding it.

The rule that protects the record is short: a fob that is still out is returned, or marked lost, before it goes to anyone new. The return is recorded against the person who held it, with the date it came back; when nobody can say when it came back, that is a lost mark with a note, not a return. Then the fob is issued fresh, and each of the two records is true.

The lost-fob protocol

A lost fob is a credential in unknown hands, and the protocol exists to make the unknown short. The steps are software-neutral:

  1. Take the report the day it comes in, with the fob number, looked up from the holder's record if they do not know it. A fob reported on Friday and written up on Monday spent a weekend in unknown hands that the record does not show.
  2. Mark the fob lost in the custody record, with the date reported. That date is what stands between the building and an open question about who could enter it, and it is the date an insurer or a board asks for later.
  3. Deactivate the credential at the access-control system, so the fob stops opening doors. The custody record and the reader are two systems, and a mark in one does not switch off the other.
  4. Apply the building's replacement rule: the fee the lease, the bylaws, or the house rules set, invoiced to the holder, or waived where the rules allow.
  5. Issue the replacement as a new record, with its own number and date, against the same holder. The lost fob's record stays lost.
  6. Note the circumstances on the lost record: where the fob was last seen, whether it went missing with anything that names the building, and what happens if it turns up, which in most buildings is that it stays deactivated and goes back to inventory as a spare.
  7. Check the count. Fobs on hand plus fobs out plus fobs lost should equal fobs owned; a count that does not balance after a lost report means a second record is wrong.

Physical keys: the same record with a due-back date

Physical keys travel beside the fobs in most buildings: the master for the mechanical room, the roof hatch key, the unit key a contractor needs for a repair. A key log (the key control log, or the key sign-out sheet) is the custody record for keys, and it carries one field a fob record does not: a due-back date. A fob is issued for the length of a tenancy; a key is usually signed out for a job, and the question is not whether it will come back but when. The key record names the key, the holder, the sign-out date, the date it is due back, and the return; a key past its due date is overdue, which is the word the desk reads at shift change. The lost-key protocol is the fob protocol with one heavier step, because a lost mechanical-room master is a rekeying decision rather than a deactivation, and the same rule applies: a key still signed out is returned, or marked lost, before it goes to anyone else.

How Scaalr keeps fob and key custody

Fob and key custody in Scaalr lives in two places: the inventory on each property's page, and the front desk that issues from it. The inventory lists every fob with its number, an access level (resident, owner, staff, guest, management, or contractor), an optional facility code, the unit it belongs to, and notes, with its current assignment and status beside it. The building's front desk workspace has a Fob Assignments tab with a live count of fobs out, and a fob is issued from there to a resident, an owner, a staff member, or a contractor, picked from the building's own records through a holder-type selector, with notes. Every fob keeps its issue and return history, per holder: active, returned, or lost.

A fob someone still holds has to be returned or marked lost before it can be issued again, so no holder's record is closed behind their back. Returning a fob stamps the date it came back. Marking a fob lost closes the record with the date and, in the same step, can invoice the replacement fee to the resident, owner, or contractor who held it; the invoice posts to the books like any other, as Property Management Invoicing: Residents, Owners, Contractors describes. Physical keys run the same way on the Key Custody tab: each key is listed with a label, a unit, and a description, signed out to a resident, an owner, a staff member, or a contractor with a due-back date, and a key past its due-back date is flagged as overdue on the list. Marking a key lost can invoice the fee the same way.

Open a resident and the Custody tab lists every fob and key they hold now, everything they have returned or lost, and the guest parking passes tracked against their unit, so the move-out conversation starts from a list. A fob or key taken out of service is retired, which drops it off the active lists while its history stays on every person who held it. Every issue, return, lost mark, and retirement is recorded with who did it and when, and a security guard's login, restricted to the front desk of the buildings they are assigned to, works the fobs and keys there.

Scaalr tracks who holds which fob, at which access level, with the history behind it; what each fob opens stays with the building's access-control system, where the protocol's third step happens. Fob and key custody is on the Growth and Scale plans: Growth is $99 for the first 50 units, then $1.49 per additional unit. The custody record sits in the same system as the rest of the desk, beside the visitor log that Visitor Management for Condos and Apartment Buildings covers and the package record that Package Management in Multifamily Buildings: Label to Pickup covers.

Key questions

What do we do when a resident loses a fob?

Mark it lost the day it is reported, with the fob number and the date, deactivate that credential at the access-control system, apply the building's replacement rule, and issue a replacement as a new record with its own number. The lost record stays lost even if the fob turns up; a fob that reappears goes back to inventory as a spare. The replacement gets its own record, because reusing the lost one erases the date the fob went missing.

Can we charge a replacement fee for a lost fob?

Usually, within what the lease, the bylaws, and local law allow: a lease or a condominium's rules set the fee, and tenancy law may cap it. British Columbia's Residential Tenancy Branch, for one, allows a replacement charge of no more than the actual cost of the key, a refundable fob deposit of no more than the fob's cost where the unit has more than one way in, and no key-related fee where the fob is the only way in (gov.bc.ca, updated March 4, 2026).

How many fobs should each unit have?

As many as the building's own rule says, written down, because it is what an audit counts against. Buildings set it by occupancy (one per resident on the lease, with a spare on request) or by unit size (a number per bedroom), and charge for fobs beyond it. The record per unit is what makes the rule enforceable: a request for a third fob is answered from the list of the two already out, not from memory.

How often should we audit the fobs?

At least once a year, and at every change of hands. A fob audit compares three lists, fobs owned, fobs on hand, and fobs out by holder, and chases every open record whose holder has moved out, whose job has ended, or who cannot produce the fob. Buildings that audit by asking residents to present their fobs find the ones that walked away; the record is what tells the desk whom to ask.

Should contractors get their own fobs?

Yes, issued to the contractor by name at the contractor access level, for the length of the job, and returned at the end of it. A contractor working on a borrowed resident fob or a spare staff fob leaves the record saying someone else was in the building. Where the work needs a key rather than a fob, sign the key out with a due-back date, so the day the job ends is the day the record expects the key.

Does marking a fob lost deactivate it?

No. Marking a fob lost closes the custody record with the date it was reported; the fob itself is deactivated at the access-control system, where the credential lives, and the protocol does both every time. A building needs both records: the access system to stop the fob opening doors, and the custody record to say who held it, when it was lost, and what replaced it. In Scaalr, the lost mark closes the record and can invoice the replacement fee in the same step.

← Visitor Management for Condos and Apartment Buildings All articles →