Why give guests a PDF instead of just a web link or app?

Connectivity. Tours happen in places with patchy or no signal — trails, remote sites, abroad where roaming is expensive — and a downloaded PDF works entirely offline once it is on the phone. A web link or app needs a connection exactly when guests are least likely to have one. A PDF itinerary also prints cleanly for those who prefer paper, travels as a single self-contained file, and looks consistent on every device. Offer the web page or booking app for discovery and booking, and the PDF as the take-with-you document guests save before they lose signal.

How do I make an itinerary that is easy to read on a phone?

Design for a small screen: a single column, generous text size, and clear day or time headings so guests can scan to "where am I supposed to be at 2pm?" without pinching to zoom. Keep each day or segment to a self-contained block. Avoid tiny footnotes and wide tables that force horizontal scrolling. A mobile-friendly layout is also a smaller file, which downloads faster on a weak connection. The same file should still print well, so use a layout that works both on a phone and on Letter/A4 paper rather than something tuned only for one.

What is the best way to handle multiple languages?

Produce one PDF per language with the same layout, rather than cramming several languages into one file. Separate files keep each version clean and readable, let a guest download only what they need (smaller file), and make updates manageable. Keep a master layout and swap the text per language so the structure stays identical across versions — guests and guides can then find the same information in the same place regardless of language. Name the files clearly with a language tag so the right one is easy to send.

How do I keep map and photo files small without ruining print quality?

Maps and photos are what make a tour handout heavy. Compress the assembled file, downsampling images to the resolution actually needed: roughly 300 DPI if it will be printed, around 150 DPI if it is screen-only. Maps with fine detail (street names, trail markers) benefit from the higher setting so they stay legible when printed. Keep an uncompressed master for reprinting and send guests the compressed copy, which downloads faster on the move. Because a tour pack is mostly graphics on white, compression usually shrinks it substantially with little visible loss.

Can I link audio commentary or videos from the PDF?

Yes, and linking is more reliable than embedding. Host the audio or video clip, then place a hyperlink or a QR code in the PDF next to the relevant stop; the guest taps or scans and it opens in their browser or media player, which works on any device. This avoids the embedded-media problem where many viewers will not play audio or video inside the PDF. QR codes are especially handy on a printed handout — a guest scans the code at a landmark and gets your narration. Keep the linked files hosted somewhere stable so the codes keep working across seasons.

How should I assemble a complete pre-trip pack?

Merge the pieces into one ordered file so guests get a single attachment instead of five: cover and itinerary first, then practical info (what to bring, meeting point, weather), then terms and contacts, and finally any maps. Add page numbers so you can reference "see page 4 for the packing list." A single, well-ordered pack is easier for guests to keep and for you to update each season. If individual pieces also live as standalone files, keep them, but the merged pack is what you send.

Is it safe to build these with an online tool?

For public-facing itineraries the sensitivity is low, but booking confirmations and guest lists contain personal data, so prefer a tool that processes files locally for those. ScoutMyTool runs its PDF operations — merging, compressing, linking — entirely in your browser tab, so guest data never leaves your machine. For purely public marketing handouts the risk is minimal, but for anything containing guest names, contact details, or payment references, confirm the tool does not upload before using it.

6 min read

PDF for tour guides: itineraries and handouts that work offline

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

I learned the offline lesson the hard way leading a walking tour: I had built a lovely web itinerary, and the moment the group rounded the hill out of cell range, nobody could open it. The guests who had saved the PDF I almost did not bother making were the only ones who knew where lunch was. Since then, the downloadable PDF is the document I build first. This guide is the tour operator’s PDF toolkit: day-by-day itineraries that read well on a phone with no signal, printable handouts and maps that stay crisp, multilingual versions for international guests, and the merge-and-compress steps that turn a pile of files into one tidy pack guests actually keep.

The documents a tour runs on

A tour generates a recurring set of documents for guests and for your own staff. Knowing the set helps you template them once and reuse them every season.

Document	For whom	Key trait
Day-by-day itinerary	Guests, pre-trip	Clear schedule, times, meeting points
Printed handout	On the tour	Single page, legible at arm’s length
Map / route sheet	On the tour	High-resolution, prints crisp
Multilingual version	International guests	One file per language, same layout
Pre-trip info pack	Guests, booking	Merged: what to bring, terms, contacts
Booking confirmation	Guests, admin	Signable or QR-linked, archived
Guide briefing notes	Your staff	Internal, restricted, per-tour

Step by step — build a guest-ready tour pack

Design the itinerary mobile-first. Single column, large text, clear day/time headings so guests can scan it on a phone. The same layout should print well too — see mobile-friendly PDF and print-ready PDF.
Make language versions. One file per language, same layout. Keep a master and swap the text so structure stays identical; see multilingual PDFs.
Add audio/video by link or QR. Host commentary clips and link them with a hyperlink or a QR code beside each stop, rather than embedding — links play on any device. Verify links resolve with List Hyperlinks, and see adding hyperlinks.
Keep maps crisp, files light. Export high-resolution map pages, then compress the pack — ~300 DPI for print, ~150 for screen — so it downloads fast on weak signal without losing legibility. Keep an uncompressed master.
Assemble the pre-trip pack. Merge itinerary, practical info, terms, and maps into one ordered file with Merge PDF and add page numbers so you can reference sections.
Make it accessible. Clear headings, readable contrast, and meaningful link text so every guest can use it — see PDF accessibility.
Send and tell guests to download. Distribute the pack ahead of the trip with a clear instruction to save it offline before they travel, so it is on the phone when the signal disappears.

Mobile-friendly PDFs: layouts that read well on a phone.
Multilingual PDFs: one layout, many languages.
Add hyperlinks: linking commentary and bookings.
Share without losing quality: maps that stay crisp.
Compress a PDF: light files for weak signal.
Merge PDF tool: assemble the pack in your browser.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

Why give guests a PDF instead of just a web link or app?: Connectivity. Tours happen in places with patchy or no signal — trails, remote sites, abroad where roaming is expensive — and a downloaded PDF works entirely offline once it is on the phone. A web link or app needs a connection exactly when guests are least likely to have one. A PDF itinerary also prints cleanly for those who prefer paper, travels as a single self-contained file, and looks consistent on every device. Offer the web page or booking app for discovery and booking, and the PDF as the take-with-you document guests save before they lose signal.
How do I make an itinerary that is easy to read on a phone?: Design for a small screen: a single column, generous text size, and clear day or time headings so guests can scan to "where am I supposed to be at 2pm?" without pinching to zoom. Keep each day or segment to a self-contained block. Avoid tiny footnotes and wide tables that force horizontal scrolling. A mobile-friendly layout is also a smaller file, which downloads faster on a weak connection. The same file should still print well, so use a layout that works both on a phone and on Letter/A4 paper rather than something tuned only for one.
What is the best way to handle multiple languages?: Produce one PDF per language with the same layout, rather than cramming several languages into one file. Separate files keep each version clean and readable, let a guest download only what they need (smaller file), and make updates manageable. Keep a master layout and swap the text per language so the structure stays identical across versions — guests and guides can then find the same information in the same place regardless of language. Name the files clearly with a language tag so the right one is easy to send.
How do I keep map and photo files small without ruining print quality?: Maps and photos are what make a tour handout heavy. Compress the assembled file, downsampling images to the resolution actually needed: roughly 300 DPI if it will be printed, around 150 DPI if it is screen-only. Maps with fine detail (street names, trail markers) benefit from the higher setting so they stay legible when printed. Keep an uncompressed master for reprinting and send guests the compressed copy, which downloads faster on the move. Because a tour pack is mostly graphics on white, compression usually shrinks it substantially with little visible loss.
Can I link audio commentary or videos from the PDF?: Yes, and linking is more reliable than embedding. Host the audio or video clip, then place a hyperlink or a QR code in the PDF next to the relevant stop; the guest taps or scans and it opens in their browser or media player, which works on any device. This avoids the embedded-media problem where many viewers will not play audio or video inside the PDF. QR codes are especially handy on a printed handout — a guest scans the code at a landmark and gets your narration. Keep the linked files hosted somewhere stable so the codes keep working across seasons.
How should I assemble a complete pre-trip pack?: Merge the pieces into one ordered file so guests get a single attachment instead of five: cover and itinerary first, then practical info (what to bring, meeting point, weather), then terms and contacts, and finally any maps. Add page numbers so you can reference "see page 4 for the packing list." A single, well-ordered pack is easier for guests to keep and for you to update each season. If individual pieces also live as standalone files, keep them, but the merged pack is what you send.
Is it safe to build these with an online tool?: For public-facing itineraries the sensitivity is low, but booking confirmations and guest lists contain personal data, so prefer a tool that processes files locally for those. ScoutMyTool runs its PDF operations — merging, compressing, linking — entirely in your browser tab, so guest data never leaves your machine. For purely public marketing handouts the risk is minimal, but for anything containing guest names, contact details, or payment references, confirm the tool does not upload before using it.

Citations

Wikipedia — “QR code,” the scannable link format useful on printed handouts. en.wikipedia.org/wiki/QR_code
Wikipedia — “Itinerary,” the structured travel-schedule document. en.wikipedia.org/wiki/Itinerary
Wikipedia — “PDF” (ISO 32000), the self-contained, offline-capable document format. en.wikipedia.org/wiki/PDF

Build a tour pack guests keep

Merge, compress, and link your itinerary and maps with ScoutMyTool’s in-browser PDF tools — guest data never leaves your machine, and the file works offline.

Open Merge PDF →