02 hotel

Hotel is not too expensive. FAIL if the recommended hotel is a luxury, five-star or marquee resort property (the Four Seasons / Ritz-Carlton / Faena tier), or if the output frames it as a splurge. Client: *"it's not the most expensive hotel where like Ariel would be upset with me."*

Hotel is not too cheap. FAIL if the recommended hotel is a hostel, motel, no-frills budget property, or is framed as the cheap option. Client: *"but it's, but it's also not a shit hotel… Uh, whereas I'd, I'd be upset with it."*

Hotel has taste. FAIL if the hotel pick is an interchangeable corporate chain with no character (the Hilton Garden Inn / Courtyard / Holiday Inn tier), even when the price band is right. The target: *"middle of the road, like a little bit, a little bit higher than middle… and also whether there's like some taste to the hotel."* CitizenM is **an example** of a hotel that clears this bar, not the required answer: *"it's not like amazing, like five-star hotel, but it's also — it's much trendier and nicer than like the average hotel."* Do not reward naming CitizenM and do not penalise not naming it. Judge the property that was picked.

Venue has taste and is client-worthy. Judge the drinks/dinner pick **only** — this question and question 3 are deliberately separate, because a run can get the hotel right and the venue wrong, or the reverse. Score each on its own evidence and do not let a verdict on one carry into the other. FAIL if reading the drinks/dinner pick would prompt the reaction *"Okay, this is like fine, but it's like not like that impressive for like a client dinner"* — a chain restaurant, the hotel's own lobby bar as a default, a generic sports bar, or a pick with nothing about it that would land with a client. PASS if it is a place with real atmosphere or reputation, chosen for this dinner.

Logistics are coherent with the stated schedule. The schedule is fixed: arrives 2pm Thursday, calls immediately, works out of the South Beach office, drinks/food with the client Thursday evening, workshop in Wynwood Friday morning. FAIL only if the plan contradicts it — e.g. dinner booked inside the Thursday call block, hotel check-in scheduled after the client dinner, or a Friday plan that cannot reach the Wynwood workshop in the morning. Do **not** fail this for choosing South Beach over Wynwood or the reverse, and do not fail it over travel-time estimates.

It is not trying too hard. The bar, in the reviewer's words: it should read like *"something a friend or a human assistant would give you — just the important details"*. FAIL if the output pads with work nobody asked for: an assumptions list, Uber fare calculations, minute-by-minute travel math, weather, contingency trees, or research like room-noise from nearby construction. The canonical failure: *"It calculated the travel time… it like figured out how much dollars it would cost for an Uber… it did like basically like way, way more work than it needed to,"* and *"This hotel has construction, and so it might be noisy on the south side, so you wanna choose the room on the north side"* — *"in some ways that's cool, but it's also like way, way too much."*