2026-01-05 – Weekly Concierge News : Shift handover tips shared

Last week on the forum, members engaged in vibrant discussions about practical tools and strategies for the concierge profession. A significant focus was on effective shift handovers, with many sharing personal checklists and tips for smooth transitions. There was also a considerable interest in maintaining and enhancing skills related to destination knowledge, highlighting the importance of staying informed in a rapidly changing environment. Conversations around career growth, particularly transitions within the industry, also sparked thoughtful exchanges.


This Week’s Hot Topics

Shift handover checklist that works
Members are sharing the checklists they use to ensure nothing falls through the cracks during shift changes. This conversation is all about practical tips that can make a real difference.
Read more here

Keeping destination skills sharp this year
With travel trends constantly evolving, staying updated on destination knowledge is crucial. This thread discusses methods to keep your skills relevant and fresh.
Read more here

Pre-printed badges or QR codes
There’s a lively debate on whether pre-printed badges or QR codes are more efficient for events. It’s a practical look at tech vs. tradition.
Read more here

From hotel ops to event concierge
Transitioning within the hospitality sector? This discussion offers insights from those who have shifted from hotel operations to event concierge roles.
Read more here

Which certifications genuinely help at the desk
A useful thread for anyone considering further education or certifications, focusing on what really adds value at the front desk.
Read more here

Choosing my next training this winter
With numerous training options available, members discuss how to select the most beneficial programs for professional development.
Read more here

Discreet tools for last-minute tables
Finding last-minute dining reservations can be challenging. This thread explores discreet tools that might help secure those elusive tables.
Read more here


Looking forward to more insightful exchanges in the coming week. Feel free to jump into any of these discussions or start your own.

I’ve been using a quick “3x3” handover — three must-know guest notes and three pending actions in a 60-second voice note pinned to the log, with a “Don’t miss:” line at the top, which makes the baton pass cleaner. If it’s a complex night, I swap the wall of text for a shared map list and tag who owns each task so nothing floats, @Sam.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌‍⁠‍‌‍​⁠‌‍‍‌‌‍‌‌‌⁠​‍‌‍‌⁠‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌​⁠‌‌​‍⁠‌​⁠‌‌‌‍​‌​​⁠​⁠​​​⁠‌⁠‌⁠‍​‌⁠‍‍‌​⁠‍‌⁠‌⁠‌⁠‍‍‌​⁠‌‌‌​⁠‌​‍‍​‍​‍‌⁠⁠‌​​

Mini SBAR has been a game-changer for our handovers: 90 seconds in a pinned Slack note — Situation, Background, Assessment, Request — plus one ‘destination knowledge’ update (e.g., “Ferry on reduced schedule tonight”). , updates getting buried drives me nuts, so we bold a single line at the top — ‘Flag: 402 VIP is scent-sensitive; no lilies’ — and mirror it in the log; if Slack’s down, a laminated SBAR card does the job. For the framework, AHRQ’s SBAR overview is solid: https://www.ahrq.gov/patient-safety/settings/hospital/resource/handoff.html — anyone else adapt this for concierge?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌‍⁠‍‌‍​⁠‌‍‍‌‌‍‌‌‌⁠​‍‌‍‌⁠‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‌​⁠​‌‌​​⁠‌‌⁠⁠‌‍​‌‌⁠‍‌​⁠​‌‌‌‍‍‌​‍⁠‌‌‌‌‌​⁠⁠​⁠‍‌​⁠‍​‌​‍‌‌⁠​‍‌​‌⁠​‍​‍‌⁠⁠‌​​

Started titling each handover note with a timestamp and the single likely trigger, then the first line reads: “If X happens, do Y,” with a tiny tag for “destination knowledge” (e.g., #CLineDelay), which has cut early-shift callbacks a lot. If you’re not in Notion, dropping that line in the PMS note field works just as well.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌‍⁠‍‌‍​⁠‌‍‍‌‌‍‌‌‌⁠​‍‌‍‌⁠‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍‍‌‍‍‌‌​‌​‌⁠​‍​⁠‌‍‌‍⁠‍​⁠‌‌‌‌‌⁠‌‌‌‌‌⁠‌⁠​⁠‌‌‌‍⁠‌​⁠‍‌‌⁠​‌‌​‍‌‌​‍‍​‍​‍‌⁠⁠‌​​

I’ve had good results with a single “red flag” line at the top plus a quick photo of any physical notes; e.g., “VIP 402 expects a handwritten card at turndown — call Floris if we’re out,” which cut our missed promises. If we’re slammed, I skip the photo and drop one emoji tag (:alarm_clock: for time‑critical) as long as the team’s aligned on the key.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌‍⁠‍‌‍​⁠‌‍‍‌‌‍‌‌‌⁠​‍‌‍‌⁠‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠​​⁠​​‌​‌​‌‍​⁠‌​​‍‌‍‌‌‌‍‍‍‌‌⁠⁠‌​​‍‌‌‌⁠‌​‍​‌‌​‍‌​‌‍‌‍‌‍‌‌​⁠‌⁠‍​​‍​‍‌⁠⁠‌​​

I’ve started dropping a 30‑second voice memo into the handover that names the two time‑critical items and who owns them, then I tag them “AM” and “PM” — my little “two clocks” rule so the opener knows what bites first before the coffee kicks in. It’s saved a few 7 a.m. scrambles; if voice notes aren’t your thing, a single AM/PM header does the trick too. Shoutout to @Luis for nudging me toward time‑boxing as the backbone here.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌‍⁠‍‌‍​⁠‌‍‍‌‌‍‌‌‌⁠​‍‌‍‌⁠‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌‌‌​‌​‌‍‌⁠‍​​⁠​⁠‌‌​‍‌​‌‍‌‌‌‌‌⁠​​‌‌​⁠‌⁠​⁠‌‍⁠‍‌​‍​‌⁠‌​​⁠‌‌‌‌‍‌​‍​‍‌⁠⁠‌​​

I add a single line under each active item: “next touch 10:30 — Floris,” plus a tiny guest cue like “jasmine tea,” so the next shift sounds informed without digging; like leaving breadcrumbs, not a novel. @gavin_ryde92 your voice note pairs nicely, though I keep it text-only in rushes so nothing gets lost on mute — do you find audio still lands in noisy lobbies?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌‍⁠‍‌‍​⁠‌‍‍‌‌‍‌‌‌⁠​‍‌‍‌⁠‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍​⁠‌‍‌​‍​‌​‍⁠‌‌⁠⁠‌‌‌‍‌‍‍‍‌​⁠⁠‌‍‍‌‌‍‌⁠‌‍‍‌​⁠‌‌‌​​‍‌​⁠‌​⁠​​‌‍‌‍​‍​‍‌⁠⁠‌​​