The Front Desk Playbook: Running Concierge-Level Operations in Residential Buildings

Every other procedure in this playbook runs through the handoff. A package logged at 4 p.m. is only useful if the overnight concierge knows it's there. If a contractor signs in at 2 p.m. and leaves without signing out, the record still shows that person in the building, and the next shift has no way to know otherwise.

Most handoffs fail for ordinary reasons. The outgoing staff member is tired and ready to leave, the incoming one is getting settled, and the handoff turns into a 30-second conversation at the desk. Whatever didn't come up in that conversation leaves with the person who just walked out.

Hospitals have studied this problem closely. In its 2017 Sentinel Event Alert on hand-off communication (Issue 58), The Joint Commission cited a 2016 study estimating that communication failures in US hospitals and medical practices were responsible, at least in part, for 30% of all malpractice claims. Its recommended fixes translate well to a lobby: standardize what gets handed off, both spoken and in writing, do it face to face where you can, and use the same tools every time. The stakes at the front desk are lower, but the mechanics are the same.

A complete handoff has two halves. The narrative half covers what happened, what's in progress, and what someone promised. The inventory half covers everything physically open at the desk.

The narrative half should cover:

• Anything a resident was promised, such as "I'll call you when the plumber leaves."
• Changes in building status, such as an elevator out of service, a closed amenity, or a scheduled water shutoff.
• Incidents still in progress or still waiting on a written report.
• Front desk instructions that start or expire during the next shift.
• Anything unusual the next person should watch for.

The inventory half should cover:

• Packages and deliveries waiting for pickup, including perishables.
• Keys that are signed out and not yet returned.
• Contractors who are still on site.
• Items residents left at the desk for someone else to pick up.

Four rules make the handoff stick.

1. Write first and talk second. The outgoing staff member enters the handoff notes before the conversation, so the conversation confirms the record instead of replacing it.
2. Read the log before the outgoing person leaves. The incoming staff member asks questions while the person who knows the answer is still in the lobby.
3. Log every resident request that comes through the desk, including the ones staff resolve on the spot. If a promise to a resident isn't in the log, treat it as if it was never made. That rule protects staff as much as residents, because it turns "I told the night guy" into a record anyone can check.
4. Mark the end of every shift in the log. Anything logged after that marker belongs to the next shift.

In BuildingLink, the shift log is the electronic logbook for staff and management. Every note is stamped automatically with the date, time, and name of the employee who entered it. Notes can't be edited after they're saved, so a correction goes in as a new note. Staff can mark a note as high priority, which highlights it in red, and some properties use that flag to mark incidents. The end of shift note option adds a time-stamped dividing bar, which gives every shift a clean starting point.

Management can receive a copy of the shift log by email every night, or only the high-priority notes if they prefer a shorter read. Past notes are searchable by unit, text, date range, employee, and location, and you can export them to PDF or Excel. Non-management staff can't delete notes, and BuildingLink keeps a record of every note, including deleted ones.

The inventory half lives in the event log. Its open-event grid shows the events still open at the desk, including packages, keys that are out, and contractors who are signed in, so the incoming staff member sees the physical state of the desk in one view instead of rebuilding it from memory.

Template 1, the Shift Handoff Sheet, gives you the fields for both halves. If your team is new to structured handoffs, use it on paper for the first few weeks, then carry the same format into the shift log.

A front desk collects dozens of small permissions from residents. The dog walker comes on Tuesdays and Thursdays, a brother is staying for the weekend, and one resident wants a call before anyone goes up. Each of those is an instruction, and each one fails the relief test if it only lives in the memory of the person who took the call.

Decide which categories the desk will track before staff enter anything. BuildingLink's setup guidance suggests that most buildings start with these instruction types:

• Broker Access
• Housekeeper/Dogwalker
• Permission to Enter Temporary
• Permission to Enter Permanent
• Do Not Allow
• FD Instructions from Management, an internal type for staff

Common additions include Out of Town Instructions, Mail or Newspaper Hold, Internal Notes, Resident Preferences, and Caretaker. The exact list matters less than agreeing on it. If one concierge files a housekeeper under Permission to Enter and another files them under Resident Preferences, the next person searching won't find it.

Temporary instructions should always carry a start date and an end date. Permanent instructions need a review point instead, because otherwise nobody looks at them again. A housekeeper who stopped working for a resident 2 years ago and still has permission to enter is a security gap.

Good review points include the resident's move-out, an annual review of all permanent instructions, and any time a resident reports a change in the household. In rental communities with frequent move-ins and move-outs, the move-out review does most of the work.

A Do Not Allow instruction usually signals a sensitive situation. Decide who can create, edit, and remove these instructions, and make sure the desk knows to escalate any attempt by that person to enter instead of handling it alone. Chapter 5 covers where that call goes.

The most reliable instruction is the one the resident writes. When your property enables front desk instructions for residents, they can view, add, edit, and expire their own instructions from the resident portal, and the resident app includes a shortcut for submitting one. That turns a phone call someone has to transcribe into a written record in the resident's own words, with the dates they chose.

Depending on your instruction type settings, staff can add instructions on behalf of residents by selecting the unit, the instruction type, the instruction text, and the start and end dates. Staff can capture or upload a photo with the instruction, which helps the desk recognize an authorized dog walker or caretaker on sight. To cancel an instruction, staff set it to expire immediately.

When a regular visitor such as a dog walker arrives, staff can log the visit straight from that resident's instruction, and BuildingLink fills in the unit number and the instruction text. Managers and security officers can also set automatic notifications that go to staff or residents when certain instruction actions are taken.

Template 2, the Instruction Type Worksheet, lists each type with who can create it, whether it needs an end date, and when it gets reviewed.

Three kinds of people come through the lobby who don't live there, and each one needs a different check.

• Guests visit a resident. The desk's job is to confirm that the resident expects them.
• Standing service providers, such as housekeepers, dog walkers, and caregivers, visit on a schedule. The desk's job is to match them to a current instruction.
• Contractors do work in a unit or a common area. The desk's job is to confirm the work is approved, track their time on site, and track anything they're given, such as a key.

For guests, check front desk instructions first. If a current instruction covers the guest, log the visit and send them up according to your policy. If no instruction covers them, call the resident. Your written procedure should say what happens when the resident doesn't answer, so new staff aren't left to improvise.

Standing service providers are the reason instructions need photos and end dates. A standing authorization is only as good as the desk's ability to confirm two things: the person in the lobby is the person on the instruction, and the instruction is still current.

A contractor visit has three key moments, and each one needs a rule.

1. Before arrival: confirm that the resident or management has authorized the work, and confirm that anything your community requires before work starts is on file, such as a certificate of insurance for alterations.
2. On arrival: sign the contractor in, capture what your policy requires, issue a badge if you use them, and sign out any keys.
3. On departure: sign the contractor out, collect any keys, and note any unfinished work that someone needs to follow up on.

The departure step is the one that slips. A contractor who leaves without signing out stays open in the record, and the next shift has no way to know whether that person is still in the building.

Keys follow the same logic. Every key that leaves the desk should stay an open item until it comes back, which is why keys belong in the handoff inventory.

Visitors, contractors, and keys all run through the event log, alongside packages. BuildingLink's recommended setup groups them into event groups: a people group with event types for visitors and contractors, and a keys group with separate types for keys coming in (a resident leaves a personal key for someone else to pick up) and keys going out (a key kept at the desk goes to a resident, contractor, or vendor).

Each event type can require a signature, a photo, or an ID before the event is saved. Visitor types typically require a signature on arrival and close automatically, so no one has to sign the guest out. Contractor types often require a signature and a photo, and properties with a label printer can print a contractor badge. Any event type set to open status stays on the open-event grid until staff close it, so setting the contractor and keys-out types to open puts them in front of the next shift.

The event log keeps a permanent history of every event, open and closed, so management can check a contractor's recorded time on site against the invoice. For properties that want automated key control, KeyLink is BuildingLink's add-on key management system, with fingerprint authentication and an audit trail.

Template 3, the Visitor and Contractor Rules card, puts all three flows and the key rule on one page the desk can keep within reach.

Packages are a high-volume task at most staffed desks and a common source of resident frustration. The carrier's app says "delivered," the resident comes down, and the item has to be found. A good intake process makes that moment uneventful. Package handling breaks into four steps: receive, log, store, and release.

1. Receive. Check that the label matches a current resident before accepting the package. Decide in advance what happens to packages for former residents, misdelivered packages, and items that need special handling, such as perishables, pharmacy deliveries, and flowers.
2. Log. Log each package when it arrives. The most common failure is the pile: a delivery comes in during a busy stretch, and staff set it aside to enter later. Later turns into the next shift, and the pile turns into a search. When a large drop arrives, log it as a batch instead of setting it aside.
3. Store. Record where each package is stored, especially if your property uses more than one area, such as a package room and an overflow space. A logged package that no one can find isn't helpful.
4. Release. Confirm who is picking up and capture whatever your policy requires at release. Close the item in the system the moment it leaves the desk, not at the end of the shift.

Set a rule for reminders on packages that sit, and another rule for what happens to packages that no one claims. Outgoing items, such as returns waiting for a carrier or items a resident leaves for someone to pick up, need the same treatment as incoming ones, because they cause the same kind of dispute when they go missing.

Packages run through the same event log as visitors and keys. BuildingLink's suggested event types include an incoming deliveries group, with carrier types such as FedEx, UPS, USPS, and DHL, plus types for perishables, pharmacy deliveries, and flowers. An outgoing items group has types for laundry pickup, items left for someone else to pick up, and package returns. Staff record the unit, the event type, and who to notify.

BuildingLink recommends a short, descriptive comment on each event. For packages with tracking numbers, staff can scan the barcode, which captures the tracking number so the package is easy to find later, and the record multiple events option handles a large delivery in one pass.

Event locations let staff record the area where an item is stored. At release, event types can be set to verify pickup with a signature or a photo. Once contactless package pickup is enabled for an event type, residents can authorize the release of their items in the resident app, and staff see a time-stamped confirmation. If a resident can't use the app, staff can authorize the release on the resident's behalf at their request.

For packages that sit, staff can email reminders to residents whose items have gone unclaimed for a set number of days. BuildingLink adds a note to the shift log recording who sent the reminder and when.

Properties that use ImageR, BuildingLink's smart label reader in the GEO app, can log and close packages by holding a phone or tablet camera over the shipping label. Residents can see their pending deliveries in the resident app, and BuildingLink integrates with Luxer One, Package Concierge, and Snaile package lockers. To see the full feature set, visit our package management system page.

Your package standards fit on one page. Use the table in this chapter as the outline, fill in your property's rules, and post it at the desk.

The front desk usually sees a problem first. A water stain on a hallway ceiling, a resident locked out, a stranger following someone through the door, and a noise complaint at 1 a.m. all start at the front desk. The question is where each one goes next.

Without a written path, staff make that call on instinct. Some call the manager about everything, and the manager stops picking up. Others handle everything alone, and the manager finds out on Monday. Both are reasonable responses to having no rule.

Sort situations into four tiers and write down which situations belong in each.

1. Tier 1, handle and log. The desk resolves it and records it in the shift log. Examples include a routine noise complaint, a resident locked out who shows valid ID, and a delivery driver at the wrong entrance.
2. Tier 2, notify the manager this shift. The desk handles the immediate step and sends a message the manager will see the same day. Examples include a package dispute, a contractor who left without signing out, and a repeated complaint about the same unit.
3. Tier 3, call the manager now at any hour. The situation needs a decision the desk isn't authorized to make. Examples include an active leak, an elevator going out of service, and a person on a Do Not Allow instruction attempting to enter.
4. Tier 4, emergency services first. The desk calls 911, follows your emergency plan, and then notifies the manager. Examples include a fire, a medical emergency, a person trapped in an elevator, and any threat to someone's safety.

An escalation path that says "call the manager" fails at 2 a.m. when the manager is unreachable. Write down a name and a phone number for each tier, add a backup, and update the list whenever staffing changes. Do the same for vendors the desk may need to reach after hours, such as a plumber, an electrician, or the elevator service company.

Tier 4 situations belong to your community's emergency plan, and the front desk's part in that plan should be explicit: who calls 911, who meets responders at the door, and who notifies residents. BuildingLink's emergency broadcast sends voice and SMS messages to residents' phones. By default, only users with security officer authority can send one, but properties can grant that permission to other users as well. Decide ahead of time whether the overnight desk can send a broadcast, because the middle of an emergency is the wrong time to find out it can't.

Template 4, the Escalation Matrix, maps each tier to examples, names, phone numbers, and backups, with a section for after-hours vendors.

The shift log is a running account of the day. An incident report is a formal record of one event that may have consequences, such as an injury, property damage, a security issue, or a dispute that could come back later. Keeping the two separate keeps the shift log readable and the formal record complete.

Write down which situations require an incident report. A reasonable starting list includes any injury on the property, any damage to the building or a resident's property, any police or fire department response, any security breach, and any dispute that a resident or vendor is likely to follow up on. When staff aren't sure, the rule should be to file.

Good incident reports are factual, specific, and written the same day.

• Record what staff saw and heard, not what they concluded.
• Include the date, the time, and the exact location.
• List everyone involved, including witnesses and staff.
• Attach photos and documents while they're still available.
• Note what the desk did in response and who was notified.

Staff should finish the report before the end of the shift. Details fade quickly, and a report written the next day from memory is weaker than one written an hour after the event.

Someone with the authority to act on an incident report should review it. That review turns a write-up into a decision, whether it's a repair, a follow-up with a resident, or a change to procedure. Reviewing reports by type every month also shows patterns that a single report won't, such as a side door that keeps getting propped open on weekends.

The incident reports module is built for properties that want staff to complete specific fields when incidents occur, and BuildingLink Support can turn it on. Staff choose an incident type defined by your property, mark the incident as minor or severe, and enter the date, time, locations, and a description. They can add the people associated with the incident, notes, photos, and documents, and then submit the report for approval.

By default, front desk and maintenance staff can submit reports, and security officers or management approve and finalize them, which mirrors a manager signing off. A finalized report can't be edited, though staff can still add notes to it. A link in the dashboard summary shows reports waiting for approval, and you can set email notifications for new submissions, with different recipients for specific incident types. Any report can be saved as a PDF, and an Incidents link at the top of the shift log gives staff a shortcut to the module.

Template 5, the Incident Write-Up Guide, gives staff a checklist to follow for every report.

A playbook only works when it's trained, used, and kept current. Three habits keep it that way.

1. Train on the procedures, then the software. New front desk staff should learn your handoff format, instruction rules, visitor flow, package steps, and escalation tiers in their first week, with the system as the tool that carries them. BuildingLink's front desk training covers adding packages, reviewing permission-to-enter information, and entering requests on behalf of residents.
2. Review the playbook on a schedule. Once a quarter, read through the templates with your desk leads. Update names and phone numbers, retire instruction types nobody uses, and add anything the last quarter's incident reports taught you.
3. Keep the front desk running when the internet doesn't. A desk that depends on an internet connection stops working during an outage.

ConciergeLink is a front desk console and database you install on a Windows computer, and it lets staff handle the bulk of front desk operations without an internet connection. It covers packages, instructions, maintenance, units, shift notes, parking management, and amenity reservations. It syncs with BuildingLink when the connection returns and you log in again, or every 30 minutes while a connection is active, and staff can log in offline with a PIN or an enrolled fingerprint.

Staff who step away from the desk can use the GEO staff app to track packages, look up permission-to-enter instructions, and add shift log notes from a phone or tablet. Managers and security officers can also restrict front desk logins to specific, authorized computers.

Concierge-level service looks personal from the lobby, but behind the desk it runs on procedure. The desk that remembers every resident's preferences, finds every package on the first try, and knows exactly who to call at 2 a.m. has usually written those things down and put them in a system every shift can see.

Run the relief test on your own front desk. Pick one procedure from this playbook, hand it to someone who doesn't usually work that shift, and see what they can do with what's written down. Whatever they have to ask about is your first edit.

Complete Part A before the handoff conversation. The incoming staff member reads it, reviews the open-event grid for Part B, and both initial the bottom.

Part A: Narrative

Part B: Inventory

The rows below are suggested policy defaults, not system settings. Adjust them to your property's rules, add your own types in the blank rows, and train staff on the finished version.

Fill in the bracketed items, then print this page for the desk.

Use names and direct numbers, not titles. Update this page whenever staffing changes.

After-hours vendors

Staff authorized to send an emergency broadcast overnight: ____________________

File a report when:

• Anyone is injured on the property.
• The building or a resident's property is damaged.
• Police or the fire department respond.
• Someone gains or attempts unauthorized entry.
• A resident or vendor is likely to follow up on a dispute.
• You aren't sure. When in doubt, file.

Include every time:

Write facts, not conclusions. Describe what a person said or did instead of labeling them. "The visitor raised his voice and refused to sign in" is a fact. "The visitor was aggressive" is a conclusion.

Finish the report before your shift ends, submit it for approval, and note in the shift log that a report was filed.

Reviewer for incident reports: ____________________