Skip to content
LobbyExpress
Search

Analysis

What hybrid work did to reception

Reception was designed for a stable building: staff who were always there and visitors who were the exception. Where attendance varies by the day, staff start to look like visitors, desk booking overlaps sign-in, and some front desks go unstaffed.

By LobbyExpress Editorial

Photo: wocintech (microsoft) - 28 by wocintechchat.com, CC BY 2.0

The traditional reception desk rests on an assumption so basic that nobody writes it down: the building’s population is stable. Staff come in most days, sit at the same desks and badge through the turnstiles without reception noticing. Visitors are the exception, and reception exists to handle the exception.

Where hybrid working has taken hold, that assumption no longer holds. Who is in the building changes from one day to the next. Staff arrive who have not been in for weeks, do not have a desk, and are not sure which floor their team is on. Some days are busy enough to need two people on the desk; others are quiet enough that nobody is on it at all.

None of this is a crisis. But it changes what reception is for, and many front desks are still set up for the building they used to serve.

The week is no longer flat

In a building with fixed attendance, the busiest day and the quietest day look roughly alike. In a hybrid building they can look very different, and the pattern can shift as teams change their habits.

Illustrative example of a hybrid office weekAn illustrative bar chart, not real data, showing people on site from Monday to Friday in a hypothetical hybrid office. Monday is moderate, Tuesday to Thursday are high, and Friday is low. Two horizontal lines mark a reception staffing level set for the peak, which is idle on Monday and Friday, and a level set for the average, which is overloaded midweek.People on site through the weekILLUSTRATIVE EXAMPLE, NOT DATAMonTueWedThuFriStaffed for the peakIdle on quiet daysStaffed for the averageQueues midweek
Illustrative example only; the shape varies by organisation and over time. Neither a peak nor an average staffing level fits a week like this, which is why reception cover becomes a scheduling decision.

The practical effect is that fixed reception cover fits badly. Staff the desk for the busiest day and it is idle on the quietest. Staff it for the average and the midweek arrival rush queues out of the door. Organisations respond in different ways: flexible rotas, sharing reception across floors or tenants, leaning on self-service on quiet days. All of those depend on knowing in advance who is expected, which is exactly what booking data provides.

Staff are visitors in their own office

The more subtle change is in who needs reception’s help. In a fixed-desk building, employees are invisible to the front desk. In a hybrid building, an employee who comes in once a month may need almost everything a visitor needs: a booked desk, directions to a neighbourhood that moved since they were last in, a temporary pass because they forgot theirs, and a place on the evacuation list.

That last point matters most. A fire roll-call has always needed to account for staff as well as visitors. When staff attendance followed a stable pattern, managers could do much of that from memory. When attendance varies by the day, memory is a weak basis for a roll-call. Some form of record of which staff are on site — badge data, desk bookings or a sign-in — becomes part of the safety arrangements, and your fire risk assessor should know which one you rely on.

Two systems, one question

Desk booking and visitor management were usually bought separately, by different teams, for different reasons. In a hybrid building they turn out to answer the same question: who is expected here today?

Where desk booking and visitor management overlapTwo overlapping circles. Desk booking alone covers desks and rooms, team neighbourhoods and occupancy reporting. Visitor management alone covers identity checks and badges, site rules and agreements, and contractor documents. The overlap covers who is expected on which day, the host and floor, arrival at the front door, and inclusion on the evacuation list.Desk bookingVisitor managementBOTHDesks and roomsTeam neighbourhoodsOccupancy reportsID checks, badgesSite rules, agreementsContractor documentsWho is expectedand on which dayHost and floorArrival at the doorEvacuation list
The overlap is where duplicate data and conflicting answers come from. Decide which system owns the “expected today” list before integrating anything.

The market reflects this overlap. The LobbyExpress directory (98 products, October 2026) includes 24 workplace platforms that ship visitor management alongside desk and room booking. A visitor in those products is, in effect, an attendee who happens not to be an employee.

Whether you buy one suite or two separate systems, the design question is the same: which system holds the authoritative list of who is expected, and which one reads from it? Two lists that disagree are worse than one, especially when one of them feeds the roll-call. If you keep separate systems, map the overlap explicitly and integrate deliberately. If you consolidate, check that the visitor features are deep enough for your contractors and security requirements, not just for guests at a meeting.

When nobody is on the desk

Some organisations have responded to quiet days by leaving reception unstaffed, at least some of the time. That can work, but only if every task the receptionist used to do is consciously reassigned.

What replaces each reception task when the desk is unstaffedA two-column comparison of six reception tasks. Greeting and directions: staffed by a person; unstaffed replaced by signage, a kiosk and host meet-and-greet. Identity check: a person checking ID; replaced by pre-registration and kiosk capture, or not done. Badge issue: handed over; replaced by kiosk printing or mobile pass. Host notification: a phone call; replaced by automatic message, with escalation if the host does not respond. Deliveries: signed for at the desk; replaced by lockers or a designated drop point with logging. Judgement about someone who seems wrong: a person notices; replaced by nothing automatic, so needs a named contact and a clear escalation route.TaskStaffed deskUnstaffed: what replaces itGreeting, directionsIdentity checkBadge issueHost notificationDeliveriesJudgementA person at the deskChecked by eyeHanded overA phone callSigned for at the deskSomeone noticesSignage, kiosk, host meets guestPre-registration and kiosk captureKiosk print or mobile passAutomatic alert, escalation if no replyLockers or a logged drop pointNothing automatic: a named contactand a clear escalation route
Five of six tasks have a reasonable self-service replacement. The last does not, and is the one most often forgotten when a desk goes unstaffed.

Most of the visible work has a self-service replacement. Kiosks can capture details and print badges; pre-registration can carry identity checks; hosts can be alerted automatically. Deliveries need somewhere to go that is not an empty desk.

The work that does not automate is judgement. A receptionist notices the person who is not on any list, the contractor who arrived without their supervisor, the visitor who seems unwell. An unstaffed front door needs a named person who can be reached quickly, a clear way for a kiosk or a host to escalate, and an honest view of which buildings or times are not suitable for an empty desk at all. Schools, sites with safeguarding obligations and buildings with significant public access are obvious candidates for keeping a person on the desk.

Redesigning the front of house

Put together, these changes suggest a different layout and a different set of flows, built around the idea that anyone arriving — staff or visitor — may need help, and that reception may not always be there to give it.

Example layout of a reception designed for hybrid attendanceAn example floor plan of a reception area. From the entrance at the bottom, a staff lane runs straight to the turnstiles on the right. A self-service kiosk sits just inside the entrance on the left, next to the reception desk, which can be staffed or unstaffed. A waiting area and host meeting point sits on the left. A parcel locker bank sits beside the entrance. Numbered markers correspond to a legend on the right.ENTRANCEEXAMPLE123451Staff lane to turnstilesBadge or booking pass2Self-service kioskVisitors and forgotten passes3Desk, staffed or notContact number when empty4Waiting and host meetingVisible from the entrance5Parcel lockersLogged drop, not the desk
An example, not a template. The principles are what matter: staff who are expected walk straight through, everyone else has a self-service route, and deliveries never depend on someone being at the desk.

The principles are straightforward. Staff who have booked should be able to walk straight through. Anyone else — a visitor, a contractor, an employee who has forgotten their pass — should have a self-service route that does not depend on the desk being staffed. Deliveries should have a destination that is not the reception counter. And the desk itself should be designed to work both with and without a person, with a visible way to get help when it is empty.

Where to go next