Yes, a residential building with a staffed desk should keep a visitor log, and each entry should record four things: who came in, which unit and resident they came to see, when they arrived, and when they left. The last field is the one most buildings skip, and the one that turns a list of arrivals into a record of who is in the building.
Your desk already signs people in. The book at the counter is honest as far as it goes: every name, in order, in the visitor's own hand, with the unit beside it. What it cannot tell you is who left. A time-in column beside an empty time-out column says everyone who ever came in is still upstairs, which is the answer you would hand a fire crew at the door, an insurer after a loss, or a resident asking who was let up to their floor. The record you kept is incomplete in the one place the question lands.
Why a building keeps a visitor log
A visitor log is the building's record of each person admitted past the lobby who does not live there: who they are, who they came to see, when they arrived, and when they left. The sign-in sheet at the desk (the visitor book, in older buildings) is its paper form. It exists to answer three questions, each asked at a different moment and none of them asked on an ordinary day.
The first is who is in the building right now, asked when the alarm sounds. The second is who was here, asked after the fact: a theft from a storage locker, damage in a corridor, noise from a unit whose resident was away. The third is who was let up to whose unit, asked by a resident, and it carries the most weight, because a resident who has asked the desk not to admit a particular person needs the desk to say, with a time, that it did not. A log of arrivals and departures answers all three; a log of arrivals alone answers the second, and only partly. The visitor log is one of the six custody records a staffed desk keeps; Front Desk Operations for Residential Buildings maps the full set.
What a visitor log should include
A visitor log should include seven fields, and most entries fill five of them. Each field exists to answer one failure, which is the test for adding anything else:
- The visitor's name, as given at the desk: the entry's identity, and the first thing a resident or an officer asks about.
- The unit and the resident visited, chosen from the resident directory rather than written from the visitor's spelling. The host is what makes an entry a visit, and a visitor naming a unit with no resident of that name has told the desk something worth knowing.
- The check-in time, which places the visit on the day.
- The check-out time, which ends it. This field answers who is in the building, and the paper book almost never gets it, because leaving is not a transaction: nobody stops at the desk on the way out.
- The vehicle plate and the space, when the visitor parks. The plate ties an unfamiliar car to a name and a host; the space tells the next arrival what is taken.
- A note, when the visit is not social: the contractor's trade and job, the agent's showing, the delivery carried up to a unit.
- Who at the desk logged it, so a question weeks later goes to the person who made the entry.
What the log leaves out is as deliberate as what it keeps. A phone number, a home address, and an ID document's number add nothing to any of the three questions and add a great deal to what the building holds about a stranger. The log exists to prove who was admitted and when; the fields above are what that proof takes.
Check-out: the half that makes it a record
Check-out is the discipline that separates a visitor log from a guest book. Every name in a book with no check-out column is still in the building as far as the book knows, so the book cannot say how many people are inside, when a visit ended, or whether a guest space is free. Arriving is a transaction: the visitor stops, gives a name, waits to be announced. Leaving is not. The visitor walks past the desk with a wave, or leaves by the garage, and the row stays open.
Buildings that get check-out right make it cheaper than skipping it. The desk closes the row when it sees the visitor leave, without asking them to stop. Residents call down when a guest is on the way out, because the building asked them to. And every shift ends with one fixed task: read the open rows, and for each one either confirm the visitor is still upstairs or close it with a note of when they were last seen. A log swept at every shift change is never more than one shift wrong. A log never swept is wrong by its whole history.
Guest parking: the visitor's car
Guest parking belongs in the visitor log, not beside it, because the car is part of the visit. A plate recorded at check-in turns the unfamiliar car in a reserved stall from a towing dispute into a phone call: the desk knows whose guest it is and which unit to ring. A space recorded at check-in tells the next arrival which guest spaces are taken without a walk to the garage. And a check-out recorded when the visitor leaves is what gives the space back, which is why a lot full of guest cars that left hours ago is a check-out failure wearing a parking problem's clothes.
A visit that outlasts an afternoon needs more than a space on a line: a guest staying several nights, a contractor's van for the length of a renovation. Those stays run on a pass with a stated window, a permit on the dash a patrol can read, an overstay flagged when the window closes rather than when someone complains, and a cap on passes per unit, so the guest spaces stay guest spaces instead of becoming a second assigned stall for the units that ask most.
How to run visitor check-in, step by step
The procedure below is software-neutral; it is the discipline the record depends on, whatever holds the record:
- Take the visitor's name and the resident they are here to see, and find the resident in the directory rather than writing down the name as the visitor says it.
- Confirm with the resident before admitting anyone the resident has not already announced, and anyone the building's rules say to confirm regardless.
- Record the check-in: name, unit, resident, and the time, in the log and not on a notepad to be copied later.
- Record the car when there is one: the plate, and the guest space assigned from the building's list. Issue a pass instead for any stay longer than a visit.
- Note the purpose when it is not a social call: the contractor and the job, the showing, the delivery to the unit.
- Check the visitor out when they leave, as one action with a time on it, without asking them to stop at the desk.
- Sweep the open rows at the end of every shift, and close each one with a confirmation or a note, so the log handed to the next shift is a record of who is in the building and not of who has ever been in it.
How Scaalr keeps the visitor log
Front desk software earns its keep at the two moments the paper book fails: the check-out, and the question weeks later. In Scaalr, the visitor log is one tab inside each building's front desk workspace, with a live count on the tab. A visitor is checked in with their name, the unit, the resident picked from the building's directory, the check-in date, the vehicle plate, a parking space picked from the building's parking list, and a note. Every visitor carries one of two statuses, active or checked out, and check-out is one click that timestamps the departure. Every check-in and check-out is recorded with who at the desk did it and when, so the question about an entry has an answer and an author.
The workspace runs in the browser and switches to stacked cards on a phone or tablet, so the guard checks a visitor out from the lobby floor rather than from behind the counter. A security guard's login is restricted to the front desk of the buildings they are assigned to, and the resident directory is built into the workspace, so the desk confirms who the visitor is here to see against it before anyone goes up. The visitor log, with the rest of the front desk logbook, is on every plan from Starter up. Growth ($99 for the first 50 units, then $1.49 per additional unit) adds the Reports tab and the guest parking passes.
The Reports tab prints an evacuation list of who is on site, built from the visitors still checked in, and runs a visitor analytics report over any date range you choose: how many visitors came, on which days of the week, and how many of them parked. Guest parking passes are issued for a stated window with a printable PDF permit for the dash; expiry and overstays are flagged automatically, violations land in a log, and passes are capped at 4 per unit per month, so the building's guest spaces stay available to guests. The desk's whole record, visitors and parking included, sits in the same system as the packages, the fobs, the incidents, the cases, and the books.
Key questions
Do visitors have to show ID at the front desk?
Only where the building's own rules say so. Most residential desks admit a visitor on a name and a host, confirmed with the resident, and reserve an ID check for contractors, agents, and anyone the resident has not announced. Where ID is checked, record that it was checked and the name it showed, not the document number; the log needs to prove who was admitted, not to hold a copy of their identity.
Do contractors and delivery drivers go in the visitor log?
Yes, anyone who goes past the lobby is logged. A contractor working in a unit or a common area is checked in with the purpose noted and checked out when the work ends. A driver who carries a delivery up to a unit is a visitor for the length of the trip. A courier who hands a parcel to the desk and leaves is package intake rather than a visit, and belongs in the package log instead; Package Management in Multifamily Buildings: Label to Pickup covers that record.
Is a visitor log a privacy problem for residents and their guests?
It can be, in two ways: when it collects more than admitting a visitor needs, and when later visitors can read earlier entries. Record the name, the host, the times, and a plate when a car is parked; leave out phone numbers, addresses, and document numbers. Keep the record where only the desk and management can read it, and keep it only as long as the building's written policy says. Where privacy law applies to your building, your counsel reads the law; the log's design is the operational half.
What happens to the visitor log in an evacuation?
It becomes the headcount. Every entry with a check-in and no check-out is a person the building believes is still inside, which is what the fire crew asks for at the door. A paper book has to be carried out and read in the stairwell, and a book nobody checks out of names everyone who ever visited. In Scaalr, on the Growth and Scale plans, the Reports tab prints an evacuation list of who is on site from the visitors still checked in.
Is a visitor log the same as an access control system?
No. Access control is hardware: readers and fobs deciding which doors open for which credential, and logging the credential, not the person holding it. A visitor log is a record of people a human admitted past the lobby, with a host and a reason. A fobbed building still needs the log, because visitors carry no fob. Scaalr keeps the visitor log and the record of who holds each fob; the doors are the building's own hardware.