If you already know a route well — say Chengdu to Lijiang, or a week of eating across Guangzhou — an AI assistant can turn your notes into a tidy custom guide in an afternoon. The risk is drift. A model will happily fill gaps with plausible detail: a train that sounds right, a temple that closed, a noodle shop that moved. The method below keeps a small private guide useful by separating what you know from what the model guessed, and by giving yourself a way to re-check it later.
Start with the route, not the prompt
Write the itinerary skeleton yourself before opening any AI tool. List the days, the overnight stops and the transport legs in plain text. For a Yunnan route, that might be Chengdu, then a sleeper or high-speed leg, then Lijiang, then Kunming. If you need a reference for how such a route hangs together, this Chengdu to Lijiang and Kunming itinerary is a reasonable shape to compare against. The point is that the model edits your structure rather than inventing one.
Feed it sources, and label them
Give the assistant three kinds of input, kept apart:
Your own notes, marked as verified. These are things you have done, seen or booked.
Published references, marked with the page you took them from. Operator pages, city guides, timetables.
Open questions, marked as unknown. Write them as questions, not blanks, so the model does not answer them silently.
Ask for output that keeps those labels visible. A guide where every line carries a tag — verified, sourced, unconfirmed — is far easier to trust than one smooth paragraph. This is the single habit that prevents most drift.
Write the source notes into the document
A custom guide is only as good as its footnotes. For each factual claim, record where it came from and the date you checked it. Train times, ticket rules, miễn thị thực quá cảnh conditions and opening days all change, and none of them should sit in your guide as a bare statement.
For transport legs, note the operator and the booking channel rather than a train number, and check current times on the official page or app before you travel. The same applies to entry rules: transit and miễn thị thực arrangements have conditions attached, so point your guide at the official source and note the date you last read it. Our 240-hour visa-free transit checklist shows the kind of detail worth copying into your own notes.
Keep prices and hours out of the model’s hands
Do not let the assistant estimate costs, opening hours or journey durations. Either you supply the figure from a source you checked, or the guide says where to look. A line such as “check the operator’s page for current fares and departure times” is more useful than a wrong number, because it survives the next timetable change.
Set an update rhythm
Guides rot quietly. Pick a review point before you leave — two weeks out is workable — and go through the document in this order: entry rules, transport, anything with a date attached, then food and sights. Re-check each sourced line against its original page. Delete claims you can no longer verify rather than leaving them in with a soft wording.
If your route involves a cruise or a long rail leg, those sections deserve their own check, since schedules move. A Hướng dẫn hành trình thuyền sông Li and a rail reference are both worth re-reading close to departure rather than months ahead.
Keep it small and private
The best version of this is short. One file, one route, a handful of days, with your own notes doing most of the work and the model doing the tidying. Long guides invite padding, and padding is where invented detail hides. If you want to add a city, add it as a separate file with its own source notes rather than folding it into the main document.
When you share the guide with a travel companion, share the source notes too. Anyone relying on it should be able to see which lines are firm and which are still open questions.
Câu hỏi thường gặp
Can I trust an AI assistant to plan a China route from scratch?
Not for anything with a date, a price or a rule attached. Use it to organise and rewrite what you already know or have sourced, and keep the factual lines tied to a page you checked yourself.
How many sources do I need for a short guide?
Fewer than you expect. One official page per transport leg, one for entry rules, and your own notes for everything you have done before. More sources mainly add maintenance work.
What should I do when a detail changes?
Update the line and the date next to it. If you cannot confirm the new position, replace the claim with a pointer to where the reader should check, rather than guessing.
Is it worth writing source notes for a trip I take alone?
Yes, because you will reuse the file. A guide with dated sources can be refreshed in twenty minutes next year; one without them has to be rebuilt.
How do I stop the guide growing every time I edit it?
Set a length limit and treat additions as replacements. If a new note does not remove or improve an existing line, it probably belongs in a separate file.
Treat the guide as a working document rather than a finished product: short, labelled, dated, and re-checked close to departure. That way the model does the typing and you keep the accuracy.