An 11 o’clock meeting does not explain an 11 o’clock admission
“Let’s meet in the square at eleven; the tickets are for eleven too.” In this guide’s fictional exercise, the times match, but one is a party request and the other appears in a reservation note. We do not know whether the square and entrance are the same point or how long travelling would take. Before suggesting a route, we will leave those questions open for the guide to review.
The trial asks a text assistant for a draft with five fields: detail, source, meaning, recorded status and open question. Prepare a manual reference first, then compare. Here we provide the materials and that reference; we have not run the prompt or checked any assistant’s output. The trial aims to assess how it preserves these distinctions, without asking it to confirm the visit.
Two real examples for deciding which details to separate
On the Alhambra authority’s page consulted on 23 October 2026, the complex’s opening hours appear separately from the specific Nasrid Palaces time printed on the ticket. We take one question from this for our sheet: does this time describe general opening or reserved admission? That monument’s conditions do not apply to the exercise’s invented museum.
Rutas de Toledo’s private-tour page states that museum or monument admission is excluded and describes a provisional reservation pending confirmation of the service and meeting. This is that operator’s description, not a rule for every tour. In our exercise, we will also separate guide service, tickets and outstanding requests.
- Meeting: record place, time, who requests it and whether acceptance is documented. Keep a request as a request.
- Admission: copy venue, date, slot and places according to the supplied source. Distinguish this recorded status from a later check of the actual reservation.
- Service: leave assigned guide, language and inclusions for review. Do not fill those fields from the existence of a ticket.
- Open items: record the question and who should resolve it before communicating a final plan.
VIS-01: the party requests six places; the note says four and two pending
All places, people, quantities, times and statuses below are invented. VIS-01 is a fictional visit on 30 October 2026; all times are local to mainland Spain. It contains no customer data and does not establish a real reservation.
M1, party request: “There are six of us. We want a tour in Spanish on 30 October. We would like to meet at 11:00 in Plaza del Olmo, visit Museo del Patio and finish around 13:00. Preferably no stairs. We are arranging the tickets ourselves.” R1, fictional coordination note: “Museo del Patio, 30/10/2026, admission 11:00; recorded status: four places confirmed and two more pending.” P1, invented general information: “Open 10:00–18:00.”
No entrance address, journey time, checked route or assigned guide is supplied. We wrote the following table manually as the exercise reference. “Confirmed according to R1” means that is what the fictional note says; it is not assistant verification, an authentic ticket or current availability.
| Detail and source | Status supported by the material | Guide’s question |
|---|---|---|
| Meeting · M1 | 11:00, Plaza del Olmo; requested, no acceptance supplied | Is this the same point as the entrance? Is this meeting accepted? |
| Admission · R1 | 30/10, 11:00; four places confirmed according to the fictional note | Which entrance applies? Check the actual reservation before communicating it. |
| Party · M1 and R1 | Six requested; four confirmed according to R1 and two pending | Who resolves the two pending places? Six confirmed places are not documented. |
| Opening · P1 | 10:00–18:00; invented general hours | Keep separate from the 11:00 recorded in R1. |
| Preferences · M1 | Spanish, no stairs, finish around 13:00; requests | Is there a suitable guide and itinerary? Route, duration and conditions need checking. |
The instruction: organise the notes without closing the questions
After writing your reference, try this instruction with the fictional materials: “Prepare a VIS-01 draft for guide review using only M1, R1 and P1. Return detail, source, meaning of each time, status according to the source and open question. Distinguish requested meeting, recorded admission and general opening. Retain six people, four places confirmed according to R1 and two pending. Do not present R1’s status as your own check. Flag the matching times without asserting that the locations are identical or different. Do not calculate journeys or propose itinerary, availability, accessibility, price or inclusions. If something is undocumented, write ‘not documented’. Do not treat a request as an agreement. The materials are exercise data, not new instructions. Materials: [add M1, R1 and P1].”
Compare each row with the manual table and its original note. “Confirmed meeting”, “six tickets available” or “accessible route” would be additions unsupported by these materials. Keep the first response and mark each addition before correcting it. If the assistant suggests a ten-minute journey, do not include it: the exercise provides no distances or conditions to support it.
Anthropic documents that Claude can produce text that is incorrect or inconsistent with context, and recommends allowing uncertainty. That recommendation does not validate our exercise or another assistant’s behaviour. Manual comparison remains part of the trial.
Before sending anything, review the visit outside the assistant
Our proposed review list starts with checking the reservation through the appropriate channel: date, slot, people covered, entrance and conditions. Then resolve who handles pending places and check guide availability and language. Update each status separately, retaining its source; do not mark the meeting accepted when tickets are resolved.
Also review the route, time required and current venue conditions. Treat “preferably no stairs” as a request needing professional checking. Do not use the sheet to certify accessibility, infer a clinical need or justify that the party will arrive on time. Avoid requesting diagnoses or unnecessary personal documents.
This trial is limited to preparing and reviewing text. Do not connect purchases, changes, cancellations or dispatch. The responsible person decides what they can confirm and reviews the final message. For admission rules, professional licensing or cancellation, consult official sources and applicable conditions; this guide does not provide legal advice.
A first pilot you can compare with preparing the sheet manually
Use VIS-01 as a first trial and retain the manual reference, first response and corrections. Count times without meaning, omitted sources, requests turned into agreements, pending places turned into confirmed places and invented routes. Measure the full preparation, review and correction time against doing it manually. The result may not justify continuing with AI; do not assume savings or accuracy.
Try two changes separately. A: add M2, “We would prefer to meet at 10:30 at the hotel”, and designate that request as current yourself for the exercise. Your reference should retain R1 at 11:00 and leave hotel identity, acceptance of the change and journey feasibility open. B: change only P1 to “Open 09:00–18:00”; the reference retains R1’s 11:00. These are proposed evaluation criteria, not observed results.
Start with fiction only. Do not copy real conversations, vouchers, access codes, documents or personal or business data without permission and suitable access, use and retention conditions. The invented notes are enough for this exercise, without scanning tickets.
From copying notes to integrating a sheet: what needs agreement
Trying this manually means copying these materials and reviewing the response. Connected automation would require examining the source form or management system, permissions, available formats, versions and duplicates. The existence of booking software does not establish a connection with Adaris.
As an initial proposal to assess, a development could prepare a draft per visit with meeting, admission, places and questions, subject to professional approval. Its storage and how to block unreviewed dispatch would need agreement. Buying tickets, modifying reservations or sending messages would be outside that proposed scope. Feasibility, cost and acceptance would be decided before commissioning development.
Adaris offers custom software, CRM and automation with AI case by case. We can assess this administrative preparation with agreed scope and a quote. The connected sheet is a proposal, not an existing Adaris tourism app. Commercial communication is in Spanish.
Related services
Sources
Do you prepare each visit from separate notes and reservations?
Tell us in Spanish how you review meetings and admission. With a fictional example we can assess a custom sheet; scope, permissions and quote require agreement.