Front desk operations for residential buildings

A condo front desk should keep track of six things: who is in the building (visitors and their check-outs), what arrived for residents (packages and proof of pickup), who holds access (fobs and their history), what is assigned (parking and lockers), what happened (incidents), and who lives where (the resident directory). Each one is a custody record: it exists so the building can answer a question weeks later without relying on anyone's memory.

Saturday, 6:10 PM. The courier stacks 23 packages on the lobby cart while a visitor waits to be signed in for unit 1204 and a resident asks whether her replacement fob ever came in. The guard's shift ends at 7:00 PM, and everything he knows about this hour, who came in, what arrived, who asked for what, lives in two places: a spiral notebook and his head. One of them goes home with him.

What a condo front desk keeps track of

A front desk log is the building's custody record: who entered, what arrived, who holds what, and what happened. The table below maps what a residential front desk tracks, the record each item needs, and the question that record answers later, because each of these records exists to be retrieved, not just written.

Nothing on this list is exotic. What separates a well-run desk from a chaotic one is not what gets tracked but whether the tracking survives contact with a busy evening, a shift change, and six months of time.

Visitors: who is in the building right now

Visitor tracking answers a question nobody asks until it matters: who was here, when, and for whom. A useful visitor record carries the visitor's name, the unit and resident visited, the check-in date, a vehicle plate when one parks, and the guest space assigned to it. The other half of the discipline is the check-out. A visitor log where nobody ever leaves is a list of arrivals, not a record of who is in the building, and guest parking has the same shape: a space assigned at check-in should free up the moment the visit ends, or the lot slowly fills with ghosts.

Packages: custody from the courier to the resident

Package tracking is custody work. Between the courier's scanner and the resident's hands, the building holds the parcel, and the record exists to make that holding short and provable: what arrived (carrier and tracking number), for whom (resident and unit), when, and any note about where it was shelved. Proof of pickup is the half that settles disputes: who collected it, on what date, with a photo of their ID or a signature attached to the record. A package room full of arrivals with no pickups on file is a liability shelf. Statuses keep it honest: received, picked up, or returned to sender, with nothing allowed to sit in between unexamined.

Fobs, parking, and lockers: the assets on loan

Access fobs are the assets that walk away. A fob is small, anonymous, and opens doors, which is why fob tracking is really history tracking: which numbered fob, at which access level, is in whose hands, and every issue and return before that. Two disciplines matter more than the inventory itself. First, re-issuance: when a fob that is still active gets issued to someone new, the previous holder's assignment has to end at that moment, as a recorded fact rather than a mental note. Second, the lost fob: lost is a status, not a shrug, and the date a fob was reported lost is what stands between the building and an open question about who could enter it.

Parking spaces and lockers are the same discipline with larger objects: a labeled inventory, a type or size on each, and exactly one current assignee, whether that is a resident, an owner, or a contractor. The inventory is set up once; the desk's daily job is keeping the assignments true.

Incidents: when the desk becomes the record

Incident reports are the records a building hopes never to need. When something happens that involves police, fire, or a medical response, the front desk is usually the first place it gets written down: what happened, where, when, which residents were involved, and what evidence exists. The test of an incident record is external. Months later an insurer, a lawyer, or an officer asks, and the building either produces a dated report with photos and documents attached, or it produces an email thread and an apology. The desk's rule is simple: write it the day it happens, attach everything, and file it where it can be found by someone who was not there.

Where the paper log gives out

Most condo front desk procedures are sound. The binder has columns, the guard fills them in, packages get initials. The failure is not the procedure but the medium. A paper log is write-only: it records everything and retrieves almost nothing. Searching it means turning pages; proving something means hoping the right page was filled in, legibly, by the right shift. A staffed lobby produces hundreds of small handoffs a week, and nobody claps for a handoff that goes right; the record is the only witness it gets.

The deeper problem is where the log's index lives: in the staff. The desk knows the building the way a person knows it, and that knowledge leaves at shift change, goes on vacation in August, and resigns with two weeks' notice. When the custody record depends on who happens to be behind the desk, the building does not really have one.

How to set up front desk tracking for a building

Standing up a desk that keeps records is a one-time setup followed by daily discipline. The procedure:

1. Inventory what the desk lends. List every fob with its number and access level, every parking space with its type, and every locker with its size, before anything is issued against them.
2. Load the directory. Enter residents and owners against their units with current contact details, so the desk can answer "who do we call about 1204" without a phone tree.
3. Set the visitor standard. Decide the fields every check-in captures (name, host unit, vehicle plate, parking) and make check-out part of the routine, not an afterthought.
4. Set the package intake standard. Log every arrival with carrier, tracking number, and recipient the moment the courier leaves, while the stack is still on the cart.
5. Set the proof-of-pickup standard. Record who collected each package with a photo of ID or a signature, every time, including for the faces everyone knows.
6. Define the incident protocol. Agree on what triggers a written report, who writes it, and the rule that evidence gets attached the same day.
7. Scope the logins. Give every person working the desk their own access, limited to what the job needs, so each entry carries a real name.

How Scaalr runs the front desk

Front desk software earns its keep when the record becomes cheaper than the binder. In Scaalr, the front desk is one workspace per building: pick the property and work in tabs for packages, residents, visitors, incidents, fob assignments, and owners, each with a live count, with the resident and owner directories built in for instant lookup. It runs in the browser and switches to stacked cards on a phone or tablet, so it works from the lobby floor as well as from behind the counter.

The daily motions are the ones this article just walked through. A visitor checks in with name, host, plate, and a guest space picked from the building's parking list; check-out is one click that timestamps the departure and frees the space automatically. A package can be logged by photographing the shipping label: Scaalr reads the label, fills in the carrier and tracking number, matches the recipient to a resident with a confidence level, and attaches the photo to the record. Pickup is captured with a photo of ID or an on-screen signature, and every package carries its status: received, picked up, or returned. Issuing a fob to a new holder deactivates the previous holder's assignment automatically, and every fob keeps its issue and return history. Incidents are filed with a type (police, fire, or medical emergency), the residents involved, and up to 10 attached files, and export as a clean, branded PDF fit for handing to an insurer or an officer. Every front desk action is recorded as it happens.

Two boundaries, stated plainly. The fob record is inventory and history, not door hardware: Scaalr tracks who holds which fob, and what each fob opens stays with your access-control system. And the security-guard role is deliberately narrow: guards get a restricted login that shows only the front desk, and only for the buildings they are assigned to, so the person working the lobby never needs to see the ledger to do the job.

The front desk is part of Growth and up: $99 for the first 50 units, then $1.49 per additional unit. It ships inside the same system as the cases, the work orders, the books, and the inbox, so the lobby's records live next to everything else the building produces; Property Management Accounting: The Complete Operational Guide covers the accounting end of that system, and AI for the Property Management Inbox: What Alex Reads, Flags, and Answers covers what Alex does with the resident email that used to interrupt the desk.

The same Saturday, on the record

Back to 6:10 PM. The courier's stack gets photographed label by label, and 23 packages are on the record before the cart is empty. The visitor for 1204 is checked in with a guest space that will free itself when they leave. The resident's replacement fob turns out to have been issued on Thursday, which the desk can say with a date instead of a shrug. At 7:00 PM the guard goes home, and for the first time nothing goes home with him.

Key questions

What does a condo concierge do?

A condo concierge (the staffed front desk role) runs the building's front of house: greeting and logging visitors, receiving packages and handing them over with proof of pickup, issuing fobs and guest parking, keeping the resident directory current, and writing up incidents. The security guard is the related role with a narrower brief: presence, access, and the log, usually overnight. In both cases the lasting output is the same thing: the record.

Do small buildings need front desk software?

No, not until there is a desk. A walk-up with no staffed lobby has nothing to run the software with. The tipping point is traffic, not unit count: once packages arrive in stacks, visitors need signing in, and fobs circulate, the handoffs outnumber what a paper log can prove, and the first disputed package makes the case for a searchable record.

Do security guards need their own login?

Yes. A shared login makes every entry anonymous, which defeats the point of keeping records at all. The guard also does not need the ledger, the leases, or the owner statements to work a lobby. In Scaalr, guards get a restricted login that shows only the front desk, and only for the properties they are assigned to; the rest of the system does not appear for them.

How long should a building keep visitor and package records?

There is no single rule; retention follows the disputes the records exist to settle, so align the horizon with your insurer's and counsel's guidance for liability claims in your market. In practice that means keeping front desk records for years, not months, which is the strongest argument against paper: a digital record costs nothing to keep and seconds to find, while a full binder gets boxed and effectively deleted.

Can the front desk run on a phone or tablet?

Yes. Scaalr's front desk runs in the browser, and every tab switches to a stacked card layout on phones and tablets, so a guard can log a visitor or record a pickup from the lobby floor rather than from behind a monitor. There is no app to install, and nothing for the desk to sync.