Trip planning & itineraries

Trips, end to end

A trip in Really Focus is a single piece of context — flights, hotel, ground transport, costs, anything uncertain — that lives on your briefing until the trip is over. The assistant builds the plan, you confirm what's real, and the artefact is a PDF you (or anyone you forward it to) can read on a phone in 15 seconds.

1. Ask for a plan. "Plan me a trip to Berlin Sept 17–19 for the Hatch conference."
2. Save as a draft. The assistant gathers options and saves a structured trip draft to your briefing.
3. Mark booked. Once you've actually booked the flights and hotel, flip it from Draft to Booked — one tap on the briefing or one message to the assistant.
4. Get the PDF. Download it from the briefing card, or ask the assistant to email it to you.

The trip draft card

Drafts live on your dashboard for 30 days under a Trip draft chip. Once expanded, the card shows the full plan rendered from markdown — outbound, return, hotel, ground transport, totals, anything the assistant flagged as uncertain. Footer actions are the same on every card:

• PDF — downloads itinerary-{trip-title}.pdf immediately. The PDF is the same view you see in the card, formatted for print or for forwarding.
• Email me — sends the PDF to your verified account email as an attachment. No retyping; the draft / booked status carries through to the email subject line and footer.
• Mark booked — flips the card to Booked, stamps the date, and changes the chip to a solid badge so it stops looking like a tentative plan. Mark as draft reverts it.
• Discard — removes the draft. Use this for trips you decided not to take.

From Telegram

Telegram is the fastest path. Trip planning was built with travel weeks in mind — the kind where you're standing in a hotel lobby and need to forward your itinerary to a colleague before checking out.

• "Plan me a trip to Lisbon June 4–7 for the offsite. Direct flights only, hotel near the venue, max £400/night."
• "Mark the Berlin trip as booked."
• "Email me the PDF for the Lisbon trip."
• "Email me the itinerary for the Berlin trip and add a note saying 'forwarded for visa application'."

Last one is worth calling out: the assistant accepts an optional note when emailing, which lands as a short paragraph above the attached PDF. Useful for forwarding ("here's my flight info, see you Tuesday") without composing a separate email.

What ends up in the PDF

The PDF is a one-page A4 document, branded the same way as your timesheet exports:

• Status badge — either Booked with the date, or a Draft — nothing booked stamp.
• Trip title, destination, departure, and return dates pulled from the draft's metadata.
• Account if the trip is tied to a specific client (e.g. travel for the Acme engagement).
• Plan — the full markdown body rendered as headings, lists, and paragraphs. This is whatever the assistant wrote when it saved the draft.

Filename format: itinerary-{trip-title-slug}.pdf. Keep them in a client folder, attach to a project, or forward to a travel companion.

Tips

• Be specific in the prompt. "Sept 17 to 19, two nights, conference is on Wadenser Strasse, walking distance only" gets you a usable draft on the first pass. Vague asks get vague drafts.
• Tag the account. If the trip is for a specific client, mention them by name — the draft links to that account so the cost shows up in client context later.
• Update once, not twice. If your flight changes, ask the assistant to update the draft ("change the Berlin outbound to BA flight 09:00") and re-email. Don't edit the markdown by hand and then ask for a refresh — tell the assistant and it keeps everything consistent.
• Mark booked the day you book. A booked trip on the briefing is a different signal to a draft — the morning briefing treats booked trips as commitments to plan around, drafts as decisions to make.

What's next

• Connect Telegram — the channel most users plan trips through.
• Schedules — build a Sunday "what's the week look like, including any travel?" briefing.
• Back to Getting started