25:00
Moved to Monday 9:00 AM EDT · 9 PM Manila, unchanged
25 min target · 45 hard cap
This sheet is stale It was assembled for a session that has already passed. Run ./publish.sh before the call, or you will be reading last week's page at this week's meeting. That is exactly what happened on 29 July.

Xenia · Jake's run sheet

The Wednesday Run Sheet

5 August 2026 · Allan, Leo, Sheilla, Mae, Jade, Belle · auto-assembled from the Brain, then edited by you

Private · do not screen-share

The only measure that counts

What can this team do this morning that it could not do last Wednesday?

2 min

Open with what you owe them

First thing said, before a single ask. Three of this week's five problems are broken mechanisms, not careless people, and the owner found three of them before we did. If you open with corrections the room hears five scoldings for things that are mostly not theirs. Open here instead.

Say this first, before anything else"Before I ask anything of you, three things that are mine and have been sitting. One, Manuel Flores in 89-202 asked to stay through September on 13 August. I told the desk to push the modification to a 1 October checkout and I never ruled on whether our 29-night cap applies to him, so the extension never went into Guesty, and that is why an occupied room landed on Monday's turnover list. That was my loop, not yours. Two, Expedia has not been reliably delivering our messages to guests since the middle of August. Norman raised it on the 17th, Sheilla opened a ticket that same night, and I have not chased it to an answer. Every Expedia guest since then may have received nothing from us and we would not know. Three, Google reviews have had no owner since 9 August. Norman sent me a one-star to answer on the 9th, I drafted a reply for Nathan on the 17th, and neither has been posted. Those three sit behind most of what we are about to talk about."

Amendment 04 · effective today

Agreed date changes go into Guesty without asking me

Until now an extension, a shortening or a moved date waited on Jake before anything was entered. From today it does not. Whoever is on shift enters the change in Guesty the moment the guest confirms it, and tells Jake after. This is the direct fix for 89-202: a renewal agreed in a chat thread on 13 August never reached the calendar, so on 31 August the system correctly showed a checkout that was not real and an occupied room went out on the cleaners' list.

The boundaryDo without asking: enter an agreed extension, shortening or date move into Guesty as soon as the guest confirms it in writing on any channel, match the smart-lock schedule to the new dates, and post the change in the ops thread so the next shift sees it. Still bring to Jake: a change that pushes a guest past the 29-night continuous occupancy cap, anything that moves money (rate, refund, fee, deposit), an owner or advisory property, and a date change that collides with an existing reservation.
The error budgetA wrongly entered date shows on the calendar and is reversible in under a minute, so a wrong call inside the boundary is tuition and Jake is paying it. What costs something is a cleaner walking into an occupied room, which happened twice on Monday, and a guest whose room shows as vacant while they are asleep in it.
The reviewEvery date change is already visible in Guesty, so there is nothing extra to file. Jake reads them weekly, after the fact. The ledger has carried one live row since 22 July, which is six weeks without growth, and by the ledger's own test that means this meeting has been failing regardless of how well it ran.
Say it out loud, in the room"If a guest confirms a new date, you put it in Guesty. You do not wait for me. The 89-202 mess was not somebody reading the calendar carelessly, it was the calendar being wrong because I was the step in between, and I was slow. A date you enter wrongly I can see and undo in a minute. A date nobody enters at all sends a cleaner into an occupied room, and that is the one that actually costs us."
Standing

The handover ledger

AutoEvery authority that has moved off Jake's desk, and when. This list only grows. If it does not grow for four weeks running, the meeting has failed no matter how well it ran.

SinceAuthorityHeld byState
2026-07-22Outbound guest repliesWhoever is on shiftLive
—Access and door codesJakeQueued, next
—Refunds under a ceilingJakeQueued
—Mid-stay and early check-in feesJakeQueued
—Late checkout and over-occupancy callsJakeQueued
—Listing edits and copyJakeQueued
4 min

Rulings, each with its reason

A rule without its reason gets literal compliance, which fails on the first case the wording did not anticipate. A rule with its reason gets applied to cases nobody wrote down. That is judgment, and it is the thing we are short of. Sixty extra seconds each.

Early check-ins on Guesty lock homes

Euclid and every Xenia Guesty home with a smart lock. Starting now, whenever an early check-in is approved: 1) confirm the early check-in fee is paid, if one applies. 2) Open the reservation in Guesty and change the check-in time to the approved time. 3) Wait a few minutes, then open the reservation's Smart locks section and check that the code's start time shows the new time. 4) Only then tell the guest they can come early. If the early check-in is canceled, set the check-in time back.

Why: on Nov 10 a 247 guest paid for a 1:30 PM check-in and the door refused their code until 4 PM, because the code follows the booking's check-in time. Please confirm here once you've read this.

Your shift opens by closing what you inherited, not by filing your own

From today the first thing you do on shift is take the open loops the last person handed you and give each one a disposition: resolved, waiting on a named person, next shift, or escalated. Not read them. Dispose of them. A loop you carry forward without touching is one you are choosing to carry, and you say who it is waiting on. The report you file at the end is judged on what you closed, not on how well you wrote it up.

Why: this rule already exists twice in writing, as step 4 of the shift workflow and again in the shift report standard, and saying it a third time would change nothing. The gap is that the form makes you file well and never makes you close. It blocks a loop with no disposition, a waiting loop that names nobody, a completed line with no unit attached, and a shift with hours and no report. None of those four touch the list you were handed, so a perfect report can be filed by somebody who never opened it. Our own 14-day audit found ten reports from one person averaging half a forward action, and four carrying no open loops at all. The writing was never the problem.

The turnover list is only as true as what we put in Guesty

Build the daily list from Guesty, and treat any date agreed in a chat thread as not real until it is in Guesty. If you agree an extension, you enter it (see today's amendment). If you see a date discussed in a thread that you cannot find on the calendar, that is an open loop with your name on it before the list goes out, not a detail for later.

Why: two occupied rooms went to the cleaners on Monday and the instinct is to say check the list against the calendar before sending. On 89-202 that would have confirmed the error, because Guesty correctly showed a 31 August checkout: the renewal to 1 October had been agreed on 13 August and never entered. Checking the output twice does not fix an input nobody filled in. Say this plainly so nobody leaves thinking Monday was carelessness at the desk.

We ask for a review only from a guest we can already see was happy

Norman's rule, set 31 August. Before the review request goes out, read the stay's own message thread. Send it when the guest told us during or after the stay that they were happy. Skip anyone with an open recovery case, an unresolved complaint, or a stay we know went badly, and skip means skip rather than send later. Google is the surface we want most, Expedia counts too, and the review window closes 14 days after checkout, so the ask runs as a rolling sweep over everyone who checked out in the last fortnight rather than one message per departure.

Why: in Norman's words, if the guest was not happy we do not want to invite the public review at all. Roughly 30 percent of guests review whatever we do, 30 percent never will, and the middle 40 percent review if reminded. That middle group is the entire reason the ask exists, and reminding an unhappy guest converts a private disappointment into a permanent public one. Our own SOP already says never chase a review from a guest with an unresolved issue. Norman's addition is the positive test: not merely no complaint on file, but visible evidence in the thread that they left happy.

4 min

What I am giving you this week

Tools, access, fixes and documents. The half of this meeting that is a transfer of capability rather than a transfer of authority. If nothing is in this block, that is a finding too.

FixThe Expedia message channel, owner named todayExpedia has masked guest phone numbers since late March, so a Guesty flow set to SMS, email or WhatsApp cannot reach an Expedia guest and fails silently. Only flows set to Booking Channel Communication get through. Six [EXPEDIA] flows were built for exactly this, three for 52 and three for 89, and all six were configured on the OLD property IDs before Norman's July rebrand onto a new account. Nobody has confirmed they were re-applied to the new IDs. That is the first thing to check and it is a twenty-minute job inside Guesty.
FixA delivery test, not an assumptionBefore we tell anyone the channel works, one live Expedia guest thread gets a test message and someone confirms the guest received it. Until that is done, treat every Expedia arrival as unreached and call them.
AccessGoogle Business ProfileGoogle has been a review and message surface with no owner since 9 August. Jake is asking Norman for profile access today so it can sit with the desk instead of with him. One person owns it from the moment access lands.
StandingArrivals sweep, today and tomorrow, every channelTwo checks per arriving guest: that they actually received check-in instructions, and that they completed the Guest Check-in Form. No form means no access code, so an incomplete form is a locked door. Anything missing, resend and call to confirm it landed. James Murphy scored us 2 out of 10 on 89-205 because he could not get in, and Norman let the 52-302 guest in himself on Sunday when the code failed.
ToolShift report opens with your inherited loopsThe form at ops.xenia.host/shift/report changes so the loops handed to you come first and each needs a disposition before it will let you file. Until that ships, do it by hand at the top of your report.
8 min

Questions I am putting to you

AutoNot a status round. One specific question per person, named, asked out loud, answered live. Type the answer straight into the line; it saves as you go and feeds the recap. A question nobody answers carries to next week and shows how many times it has carried, because an unanswered question asked three times is a finding about the meeting.

AllanWednesday midday is yours alone again from today. What breaks first if a guest issue lands at 12:30, and what would you want in place before next Wednesday?
LeoFrom today every shift opens by disposing of the loops it inherited. What is the first loop you would refuse to accept from the shift before you, and how would you say so without it landing as a complaint?
SheillaYou opened the Expedia support ticket on 17 August and nothing came back. What do you do differently to get an answer out of them this time, and what do you need from me to do it?
MaeAn extension is agreed in a chat thread. What has to happen before you would call it real?
JadeYou build the daily turnover list. What would have to be true for you to trust it without checking it twice?
BelleA guest tells you they never received their check-in information. What are the first three things you check, in order?
Reference

Money in motion

AutoRead before the call, not during it. Here so the numbers are shared rather than held by one person. Nothing about an individual's pay is ever discussed in the group; that is one-to-one, always.

AreaWhatOpen
PayrollTHE 07/27 PAYROLL BATCH IS NOT IN THE LEDGER, AND BELLE HAS NOT BEEN PAID SINCE 07/14day 110
FciOWNER MICHAL IS NOT RECEIVING VRBO GUEST PAYMENTSday 109
LeoPAY NOT CONFIRMED RECEIVEDday 109
ResetSEVEN JULY TURNOVERS WITH NO MATCHING CHECKOUT, HELD FROM PAYMENTday 109
ResetHOLIDAY RATE CHARGED TO US WITH NO AGREEMENT ON FILEday 109
PayrollMONDAY'S PAYROLL RUNS ON REMITLY, THE RAIL THAT FAILED FOUR PEOPLE AT ONCE, AND THE TEAM WAS NOT TOLDday 103
Brain

This week, from the Brain

▾

This section is offline while it moves behind a sign-in.

2 min

Close

Read the amendment back out loud so it binds. Confirm who owns what. Then the one question.

Before anyone leaves

What can this team do this morning that it could not do last Wednesday?

The team does not see this page, so the recap is their only artifact. Build it, read it once, then paste it into Xenia | HQ.

Assembled from the Xenia Brain, then edited by Jake. Private: the team receives the recap, not this page.

Training and case files: training.xenia.host