Saving a hotel, station or attraction does not mean its details will remain available without a connection. Before departure, do four things: save the exact addresses and confirmed booking records you need; download the map area covering the whole route; turn off Wi-Fi and mobile data, then close and reopen every essential file and the map; after any booking or route change, replace the old copies and repeat the test. Keep required original identification, tickets or other valid credentials with you: an offline backup does not replace them or prove that a venue or road is open now.
All example dates, places and filenames are invented placeholders, not real addresses, ticket codes or bookings.
1. Make one minimum information card
Do not begin with dozens of unrelated screenshots. Start with a short card containing the information you would need first:
- trip dates, version and last-check time;
- exact arrival, accommodation, main-activity and departure points, down to the entrance or terminal;
- local date and time for each fixed point, labelled pending, confirmed, changed or cancelled;
- a phone verified through an official source before departure (with country/region code abroad), plus a physical desk or meeting point; keep online links for reconnection;
- necessary journeys and checked fallbacks;
- required originals or valid credentials, plus the next online recheck time.
Copy this template:
TRAVEL CARD | version <v1> | checked <YYYY-MM-DD HH:MM>
Dates: <outbound date> to <return date>
Arrival: <station/terminal/exit> | <local time> | <pending/confirmed>
Stay: <invented hotel placeholder> | <full address checked against booking> | latest check-in time <time>
Main fixed point: <actual entrance> | <booking window> | <pending/confirmed>
Return: <station/terminal/entrance> | <local time> | leave previous point by <time>
Offline contact: <officially verified phone with country/region code if needed> | <physical desk/meeting point>
Offline files: <on-device folder> | map area <whole required route covered/retest needed>
Credentials: <original or valid credential required by operator>
No-signal fallback: <paper card location> | <companion's secret-free copy>
Recheck: <time and change trigger>Keep passwords, one-time codes, payment codes, full identity-document images and complete booking numbers out. Retain only necessary personal information, keep the device locked and never post files to a public group. Paper and companion copies should contain no secrets.
2. Store the essential files on the device
“Saved”, “sent in chat” and “in cloud storage” do not mean available locally. Export ordinary files to a folder reachable through the file manager. Check that each item is a real file, not a web link or online-only preview.
A simple folder can look like this:
Travel_Kit_YYYYMMDD/
00_Master_Card_v1.txt
01_Outbound_Confirmed_v1.pdf
02_Hotel_Confirmed_v1.pdf
03_Return_Confirmed_v1.pdf
04_Route_Hotel_to_Departure_Entrance_v1.png
Old_copies_optional/As an optional housekeeping step, name files by date and purpose so the current copy is easy to recognise. After a change, replace the copy you will carry and clearly separate any old copy you must retain. Keep the date, place and booking result, but do not collect unrelated identity or payment details.
Article 13 of the official China Railway passenger rules says that the itinerary information notice for a ticket bought through the 12306 website can be downloaded or printed, but cannot be used as the credential for travel. It helps offline checking but is not a universal boarding substitute. Follow each operator's current rules.
Check required fields as well as whether each file opens
A file opening successfully does not establish that every detail you need is present and legible. A missing exported page, a cropped entrance label or an unreadably small date can leave a local file unable to support the next action. Check your own copies before departure while stationary in a safe place. This does not replace credential checks, confirmation of booking status or testing the map's capabilities, and it does not require collecting more identity information.
Use the itinerary-planning guide to select the fields you actually need for the next part of the trip. Match each one to a verified original record and a page or location in the local file. The hotel-location guide explains the scope of checking an address down to the actual door. Keep “local file reopened” separate from “all listed fields legible”. Matching page counts, a v2 filename or seeing the first page cannot replace reading each field. If the original record itself lacks a required detail, verify it through the original trusted channel rather than filling the gap from memory.
The following example is entirely invented: one device, three local files and five chosen checks. Assume the verified original stay record F1 and return record F2 each have two pages, while F3 is a route image. These are not real bookings, typical page counts or five universal requirements. All three local files have reopened and passed the Section 5 no-signal test, but local F1 contains only the exported first page and F2's second-page image is cropped.
| Check | Detail to read clearly | Location in the invented original | Local observation and result |
|---|---|---|---|
| C1 | Address down to the accommodation's actual door | F1 page 1 | Legible and checked |
| C2 | Full local stay date and latest check-in time | F1 page 2 | Page not exported locally; pending |
| C3 | Full local departure date and time | F2 page 1 | Legible and checked |
| C4 | Actual departure entrance | F2 page 2 | Field cropped from the local image; pending |
| C5 | Origin and destination labels on the route image | F3 endpoint labels | Both legible and checked; this does not establish current access |
Files that reopen and pass the no-signal test: 3 of 3. Listed checks whose details are legible on this device: only 3 of 5, C1, C3 and C5. C2 and C4 remain pending. Do not turn three working files into a claim that the kit is complete. Legible endpoint labels do not establish map coverage, navigation capabilities or current access either. Other devices and paper cards still need separate acceptance under Section 6.
Restore missing details and retest the affected copy
Work from the missing detail, not a desire to complete every checkbox. These steps concern copies you are entitled to use. They do not change a booking, transfer permission to act or disable device security.
- Keep the file-opening result and each field's observation. Record a missing page, cropped text, text too small to read or an unconfirmed original detail rather than simply “broken file”. Do not mark unreadable details as passed.
- On a trusted device, export the required pages again from the original confirmed record, or save a complete, legible image. Ask the original channel to clarify a missing detail when necessary. Clearly mark and safely retain the old copy as superseded and give the replacement a new version. A forwarded guess or unfamiliar link is not the original confirmation.
- Reopen the replacement you will actually use and repeat the Section 5 no-signal test while safely stationary. Find the relevant fields page by page and check that the full date, time and entrance are legible and uncropped. Record the new version, page or location, actual observation and remaining task.
- If a paper fallback is the only available option, check each required field against verified information, then replace and check the card under Section 6. A paper card does not constitute a passed electronic-file test, a valid credential, permission to act or proof of current access. Pause an action that depends on a missing detail and seek a confirmed alternative; do not fix the kit while walking.
Continuing the invented example, F1 page 2 is exported again. The replacement local copy has reopened and passed the no-signal test; C1 is still legible and C2 is now legible too. F2's C4 has not been restored. Checked items increase from three to four: 4 of 5, not five of five. Record only this device's four results, without automatically signing off a companion's device or paper card as ready.
For each essential file, note where it is stored, whether it reopens without a signal, and whether the date, time and entrance you need are legible. If a detail is missing, return to the original trusted channel, replace that copy and test it again. A readable file does not prove that the information is current or that the service will be available.
3. Cover the whole journey and understand the map's limits
List journeys needing offline support, such as “hotel door → interchange → departure entrance”. Download the whole chain, not just the destination pin. The plan is incomplete if part lies outside the area or depends on a live transit service.
Google Maps Help for Android says downloads are unavailable in some countries or regions and the whole route must be inside the area. Offline transit, cycling and walking directions are unavailable; driving lacks live traffic and alternate routes. Downloads need updating. Apple Support limits its guidance to Maps in iOS 17 or later and select areas. It describes several direction modes, but downloads do not sync across devices. Neither page proves a particular phone or journey will work.
Test the app, device, region and mode you will use. Stored opening hours and roads are not proof of current conditions. Never use an offline map to enter a closed or restricted route.
4. Separate fallbacks for no power, a lost device and companions
Keep normal screen locks and security enabled. A secret-free paper card can hold the accommodation address, key points, an officially verified phone, and a physical desk or meeting point. Online links are for use after reconnection. Ask a companion to save and open the same card. Do not distribute complete documents, payment codes or recovery details.
If a device is lost, use a trusted device and official channels to protect it and the accounts, then use the secret-free copy. The kit is not proof of identity. Solo travellers can keep the paper card securely away from the phone.
When the person who booked leaves, distinguish information from permission
Opening a local copy is only one check; establish what the remaining traveller can actually do. This section covers adults able to travel independently who plan to separate or leave the group early. It does not cover an unexpectedly missing person, children travelling together or emergency response. A screenshot sent by the person who booked does not establish that a companion holds a valid admission credential, may change the reservation or may collect a refund. This is a handover checklist, not instructions for transferring named tickets, using another person's account or bypassing verification.
For each remaining booking, keep three separate records rather than writing “B takes over everything”:
- Readable information: B can open the actual entrance, full local date and time, current confirmed status, original official contact channel and last-check time on B's own device. A redacted internal booking label helps match records; it is not evidence the supplier must accept for a transaction.
- Confirmed tasks: Ask the supplier or original channel what B may do, which valid personal credentials or records are required and where to go. Check service use, changes, cancellation and refunds separately. Permission to enter does not establish permission to change a booking, and A's verbal agreement does not replace the supplier's confirmation.
- Who still handles an open task: Record anything A must still handle or verify through A's own account, the contact method agreed between the travellers and the next check. A leaving the group does not automatically transfer those tasks to B. Do not put account secrets into the copy to make the checklist look complete.
The following is an invented handover list. Every status is a teaching assumption:
| Internal booking label | B's local information | Supplier and personal-credential check | Open task |
|---|---|---|---|
| H01 stay | Address and remaining nights readable | Hotel has confirmed B's remaining stay and final-checkout process | A still checks the hold on A's card |
| T01 activity | Entrance and original booking window readable | B's required valid admission credential has been checked; permission for B to change the booking is unconfirmed | Neither the screenshot nor A's agreement establishes permission to change it |
| R01 return journey | Entrance and full local date/time readable | B's own required valid credential has been checked | Recheck current notices before departure; the kit does not guarantee an on-time journey |
All three rows being readable means information has been handed over. It does not resolve T01's pending change permission or H01's open financial record, so do not describe every booking as taken over or settled. Use the hotel-checkout guide for H01's remaining stay. Put each person's fixed arrival points and changes confirmed through the original channel back into the itinerary-planning guide; an old screenshot does not establish current status.
While stationary in a safe place, ask B to open each local record independently and read back the date, entrance, permitted tasks, required personal credential and open items. Test the files without a connection using the next section. The account holder uses a trusted device and original channel to complete any necessary action, then updates the copies with the non-sensitive confirmation. B must not fill a permissions gap by sharing passwords, forwarding login codes, taking control of A's phone or using remote-control software.
If a planned action still depends on A and A cannot be contacted, ask the verified supplier about a permitted process or alternative under the current rules. Until one is confirmed, leave the action pending and pause the activity that depends on it. Do not impersonate A or follow an unfamiliar “booking assistant” link. A physical desk, B's own identity document or a paper card does not automatically guarantee that the task can be handled; check this booking's actual requirements. Seek help under local safety guidance for a personal-safety concern. This is not a missing-person procedure.
Before the booker leaves, the remaining traveller should be able to open the date, entrance and official contact details on their own device. Ask the supplier which tasks that traveller may perform, which valid personal credential is required and which task still belongs to the original account holder. If permission remains unclear, pause the activity and ask the verified supplier for an allowed alternative.
The US Federal Trade Commission's account-verification-code advice warns against giving account login codes to others and recommends contacting an institution through a trusted channel. Its official body text was accessed on 4 October 2026 and is used only for that account-security boundary, not its comments or US advice as Chinese ticketing, hotel or refund rules.
5. Test without a network connection
Test before departure while stationary in a safe, well-lit place. Do not run the no-signal test while walking, driving, cycling or needing to watch your surroundings. Know how to reconnect, then turn off both Wi-Fi and mobile data. Flight mode with Wi-Fi enabled can make an online test look offline.
Open each essential file from the file manager, close it, then reopen it. Fully close and reopen the map app; check the downloaded area, places and intended offline feature. Confirm the companion or paper copy makes sense alone. Restore Wi-Fi and mobile data and confirm normal reconnection.
Invented pass: 00_Master_Card_v1.txt shows “Hotel A (invented) → South Station entrance (invented)”; hotel and return PDFs reopen; the area covers the whole journey; and a companion opens the secret-free card. Invented failure: the local folder has no complete hotel file, only a chat thumbnail or online preview, or the final route segment is outside the map. Export or redownload, then repeat the test.
6. Update and retest after a booking or route change
After any change to accommodation, transport, entrances or companions, update the card, file status and map area. Mark the old version superseded before saving the new confirmed file. Reconnect and check the latest booking details and notifications; never infer live status from an old screenshot.
After a route change, check the new origin, interchange and destination, then repeat the test. Confirm the download still exists and is current; another device may not have it under the same account.
After a change, verify every copy of the new version
Start only after the supplier has confirmed the accommodation, transport or activity change, and check the order status separately. Changing a document to v2 does not prove that the booking change succeeded. List only the copies your group will actually carry: for example, the main device's local file, a companion's local file and a paper card without sensitive details. For each copy, record the version, actual venue entrance or transport terminal, local date and time, an officially verified phone or service desk, and the last check. “Sent” or “read” does not mean usable.
Mark the old copy superseded and store it safely so it cannot be mistaken for the current version. On each device, open the new file from local storage, close it and reopen it, then repeat the Section 5 no-signal test before departure while stationary in a safe place. Ask your companion to open their copy on their own device. Check every paper-card field, replace the card, and clearly mark v1 as superseded rather than leaving v1 and v2 looking equally current.
Invented example: the main device's current copy reopens without a signal. The companion has received the new copy but has not opened it, and the paper card still shows the old plan. Before relying on the kit, ask the companion to open the file and replace the paper card.
Apple's offline Maps guidance gives one specific boundary: in select areas on iOS 17 or later, offline map downloads do not sync across devices. Checked on 26 September 2026 (25 September UTC), this does not establish how every file or app behaves. Test the copy on each device the group will actually carry.
Copyable receipt:
Copy: <main/companion/paper> | version: <v2>
Trip location: <actual entrance/terminal> | local time: <YYYY-MM-DD HH:MM>
Copy location: <local folder/paper location>
Official contact: <secret-free phone/physical desk> | last checked: <time>
Old version: <superseded> | electronic reopen/offline test: <pass/pending/not applicable to paper>
Paper fields/version check: <pass/replace/not applicable to electronic copy>
Next action and owner: <resave/replace paper/retest>On failure, reconnect, save again and retest, or prepare and check a paper fallback without identity numbers, passwords, payment codes or booking codes. Until a copy is confirmed usable, put any separate journey that depends on it on hold. These files do not replace the identification or valid tickets required by the operator; check booking status separately too.
7. Copy this pre-departure checklist
- [ ] Every address identifies the actual door, exit or terminal rather than only a city name.
- [ ] Essential bookings are ordinary local files, not cloud links or chat previews.
- [ ] Originals or valid credentials required by each operator are ready; a backup is not presented as a credential.
- [ ] The offline map covers the full necessary journey, and this device and travel mode have been tested.
- [ ] After both Wi-Fi and mobile data are off, files and the map still work after reopening.
- [ ] Paper and companion copies exclude passwords, payment codes, one-time codes and full identity documents.
- [ ] Connectivity is restored and live opening, road, booking and notice information is rechecked.
- [ ] After a booking, route or device change, the old version is superseded and the test is repeated.
The three official pages were consulted on 25 September 2026. They do not guarantee that an app, venue or transport service will be available for your trip. Before departure, recheck the rules for your device, region and booking.
Use the itinerary-planning tutorial to select essential checkpoints, then the hotel-location tutorial to verify the actual entrance and booking address. This page only turns confirmed information into a testable offline kit.