One email per hotel, addressed to that hotel's GM, with only his property's questions and ownership on copy. Below are the three real emails as they render right now off the Tuesday 08/19 close. These are the actual output of the email generator in non-sending mode, not mockups.
Rendered 2026-08-20 by scripts/daily-ops-email.mjs in dry-run mode · data from RevParPro production (night audit, adjustment entries, Homebase timecards, AP board) · nothing was sent
How it works today
audit pack → AI brief → Zabir → GM
One portfolio email lands with Zabir. He reads four hotels' worth of detail, works out which line belongs to which GM, and reaches out. The GM hears about a problem only if that relay happens.
What these samples do
audit pack → each GM directly
Each GM gets his hotel only, with the questions already addressed to him. Ownership is copied for visibility, not for dispatch. Nobody has to route anything.
The yellow PREVIEW bar inside each email is real and deliberate. Until you approve GM distribution, the generator sends only to you and Alyssa and says so in the body. Flipping the audience to the GM addresses above is a one-line policy change, not a code change.
What these three emails asked this morning
HOURP: 6 questions found, top 5 shown. Includes 7 invoices ($13,728.36) awaiting GM approval with 3 past due ($11,083.47), a $93.95 refund whose only stated reason was "error", 11 rooms out of order with no room list in the feed, and all 22 timecards unapproved.
HOUZN: only 3 questions. 6 invoices ($5,406.97) with 2 past due, one $139.47 refund to confirm, 18 timecards unapproved. A quiet night produces a short email, which is the point.
HOUUS: 8 questions found, top 5 shown. 23 invoices ($12,935.15) with 14 past due ($9,183.88) and the oldest sitting 23 days, plus four guest refunds and adjustments to document.
How this differs from the brief Zabir forwards
Addressed, not broadcast. Each question carries an owner role (GM, AGM, engineering, front desk) and goes to the property that owns it.
It remembers. Every ask is written to a ledger in RevParPro. Unanswered items come back the next morning with their age, day 3 copies ownership, day 5 moves to a weekly review. When a person does the routing, that person's memory is the tracking system. Remove the person and the system has to hold it.
Action items close themselves. The timecard question closes when Homebase actually shows the cards approved, not when someone replies "done".
Capped at five. HOUUS surfaced 8 candidates and asked the 5 that mattered by dollars. The rest wait rather than pile on.
What is still missing, honestly
No rate-code exceptions or folio balances. Zabir's pipeline parses those out of the Hyatt and Hilton packs; ours does not yet. That is the gap that would have caught his Alacrity finding (6 folios, $5,787.20, against $75 authorizations).
The four DFW hotels are not covered here. RevParPro holds their night audit through 08/19 and adjustments for the two Hiltons, but no Homebase labor and none of the rate or folio detail. They would get a thinner email than these three today.
Cash, chargebacks, and incidents have no data feed and stay as three yes/no confirms until we can reconcile deposits against a bank feed.