The audit log every owner will eventually ask for
At some point in the first 90 days of running an agent in production, the owner — or the GM, or the auditor, or the corporate legal team — will ask: "Show me exactly what the AI did, when, for which guest, and how that compares to what a human would have done." If you cannot answer that question in five minutes with a screen-shareable log, the project loses budget. The audit log is not a nice-to-have; it is the artifact that defends every euro of agentic investment.
What goes in the audit log
How to make it queryable
A log is useless if you cannot search it. The audit log should be queryable by: guest name or confirmation code, reservation ID, date range, agent decision type, and outcome (success / partial / failed / overridden). The minimum viable implementation is a Postgres table with these as indexed columns. The more mature implementation is a logging service like Datadog, Honeycomb, or Logfire with structured fields. Either works; do not start without one of them.
What the owner will actually ask
Three questions, in this order. First, after 30 days: "Show me the runs where the agent did something different than a human would have." This is the calibration question. Second, after 60 days: "Show me the runs where a guest complained, and what the agent did versus what we wish it had done." This is the failure-mode question. Third, after 90 days: "What does the agent cost us per run, and what would a human FTE cost us for the same volume?" This is the ROI question. The audit log answers all three; the absence of an audit log fails all three.
The retention question
How long do you keep audit logs? Hospitality-specific answer: at least as long as you keep PMS records (typically 7 years in EU jurisdictions for tax compliance), and for any run that touches a payment, follow the PCI DSS retention guidance. The cost of storing structured logs at this scale is tiny — €5-20 per month per property for the volumes we are talking about. The cost of not being able to produce a log for a regulatory question is enormous.
At the property in Krakow, the owner asked to see the audit log for every agent action involving a corporate client during a six-month period. We produced 1,840 runs in a queryable spreadsheet within 20 minutes. That document defended the budget for the following year.