./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
5 August 2026 · Allan, Leo, Sheilla, Mae, Jade, Belle · auto-assembled from the Brain, then edited by you
Private · do not screen-share
What can this team do this morning that it could not do last Wednesday?
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.
Amendment 04 · effective today
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.
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.
| Since | Authority | Held by | State |
|---|---|---|---|
| 2026-07-22 | Outbound guest replies | Whoever is on shift | Live |
| — | Access and door codes | Jake | Queued, next |
| — | Refunds under a ceiling | Jake | Queued |
| — | Mid-stay and early check-in fees | Jake | Queued |
| — | Late checkout and over-occupancy calls | Jake | Queued |
| — | Listing edits and copy | Jake | Queued |
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.
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.
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.
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.
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.
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.
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.
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.
| Area | What | Open |
|---|---|---|
| Payroll | THE 07/27 PAYROLL BATCH IS NOT IN THE LEDGER, AND BELLE HAS NOT BEEN PAID SINCE 07/14 | day 110 |
| Fci | OWNER MICHAL IS NOT RECEIVING VRBO GUEST PAYMENTS | day 109 |
| Leo | PAY NOT CONFIRMED RECEIVED | day 109 |
| Reset | SEVEN JULY TURNOVERS WITH NO MATCHING CHECKOUT, HELD FROM PAYMENT | day 109 |
| Reset | HOLIDAY RATE CHARGED TO US WITH NO AGREEMENT ON FILE | day 109 |
| Payroll | MONDAY'S PAYROLL RUNS ON REMITLY, THE RAIL THAT FAILED FOUR PEOPLE AT ONCE, AND THE TEAM WAS NOT TOLD | day 103 |
This section is offline while it moves behind a sign-in.
Read the amendment back out loud so it binds. Confirm who owns what. Then the one question.
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.