A BETTER WAY TO SHARE THE WORK
Create a travel briefing that separates bookings from possibilities
One useful page for the trip, with clear answers about what is booked, what is optional, and what still needs checking.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How do you turn travel notes into a reliable briefing?
Use an agent to organize supplied booking details and trip notes into a dated HTML briefing. Separate confirmed arrangements from tentative ideas, label local times, and include gaps and fallback options. Verify changeable details with official sources before travel, remove sensitive booking information, and share only with the intended audience.
01 / SEE THE DIFFERENCE
A weekend briefing with honest uncertainty
A fictional weekend trip. Locations and activities are placeholders; the example makes no claim about real transport, hours, or availability.
Arrive Friday, maybe visit the gallery, dinner somewhere near the hotel. Saturday could be a walk if the weather is good.
- Confirmed
- Friday arrival and two nights of accommodation are recorded in the private booking confirmations. Reservation codes are not included here.
- To verify
- Check the current arrival time and the accommodation’s check-in instructions with the providers before departure.
- Tentative
- Friday gallery visit is an idea, not a reservation. Opening hours, travel time, and ticket availability still need checking.
- Fallback
- If the outdoor walk is unsuitable, consider an indoor activity after checking current availability and accessibility.
- Group decision
- Choose a dinner option after confirming arrival plans. No restaurant booking has been made.
02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Separate fixed commitments from ideas
Start with confirmed transport, accommodation, and reservations from the supplied sources. Put possible activities in a different section. Ask the agent not to fill an empty afternoon with invented opening hours or availability. A useful briefing shows the plan’s gaps instead of making a draft look fully booked.
Make each day easy to navigate
Group the plan by local date and label times clearly, especially when a journey crosses time zones. Include the location and the next movement, but distinguish a verified journey duration from a planning estimate. Leave room for transfers and uncertainty rather than presenting every minute as guaranteed. Link to official information when supplied.
Add useful fallbacks
For a weather-dependent or unconfirmed activity, explain the alternative and what would trigger the change. Note which choices still require agreement or booking. Do not treat a suggested fallback as available until it has been checked. Keep emergency and sensitive personal information in an appropriate private place rather than a broadly shared trip page.
Verify, redact, and share
Review current schedules, addresses, restrictions, and reservation status with the relevant official providers. Remove booking codes, identity documents, payment data, and unnecessary precise personal whereabouts. Apply your saved style if available with clear day headings and status labels. Test the page on a phone and confirm access before sharing. Keep essential confirmations available separately if connectivity fails.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Create a practical travel briefing as static HTML from the booking details, official source information, and preferences I supply. Organize it by local date. Separate confirmed arrangements, tentative ideas, planning estimates, and outstanding checks. Include locations, clearly labeled local times when known, transfer assumptions, and fallback options without implying availability. Do not invent reservations, opening hours, prices, travel durations, restrictions, or official advice. Link only to supplied sources and show when changeable details were checked. Remove reservation codes, payment details, identity documents, and unnecessary personal information. Apply my saved artifact style if available and make it easy to read on a phone. No scripts or forms. Return a draft for verification; do not publish or change access until I approve.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Is every booking distinguished from an idea, estimate, or item that still needs verification?
- Have dates, local times, addresses, and changeable details been checked with official providers?
- Are booking codes, identity and payment data, and sensitive personal details excluded?
- Can travelers access essential confirmations separately, and is the page’s sharing audience appropriate?
When HTML fits
A readable group briefing for a reviewed snapshot of the trip, with official links and explicit uncertainties.
When another format fits better
A live flight tracker, booking system, navigation service, or source of official entry and safety requirements. Do not assume a hosted page will be available without internet access.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Will the page update when a booking changes?
No. A static briefing reflects the details used to create its latest reviewed version. Check provider messages and update the page when needed. Tell travelers about important changes directly rather than assuming they will reopen the link before acting.
Should I include reservation numbers?
Keep them in a suitable private location rather than a broadly shareable briefing. Include only the detail this audience needs. An unguessable link is not a substitute for choosing appropriate access, and anyone with access may copy the information.
Can the agent recommend activities too?
It can help organize and compare options, but treat suggestions as unverified until current official details are checked. Keep confirmed plans visually separate from ideas. The briefing should never turn an attractive suggestion into a claim that tickets, transport, or access are available.