Part of AI
From a trek's name to a full draft
Writing a new trip page by hand takes most of a day: fourteen days of villages, altitudes and walking times, then inclusions, a packing list and answers to the questions travellers always ask. On the Trips screen, Draft with AI does the first version for you. Give it the trip's name, and if you like its length, type and region, and it researches the route on the web, writes the trip and saves it.
Prices, group sizes, dates and named hotels are never invented. If your notes give a price per person in your company's currency, it's used; otherwise the price stays empty for you to fill in. The same goes for departure dates, which you add afterwards.
- Overview, summary, highlights, grade and fitness notes
- Itinerary with altitudes, distances, walking hours, ascent and descent
- Acclimatisation and spare days marked as such
- Included and excluded lists, essentials, packing list and FAQs
- Overnight stops and landmarks such as peaks and passes, placed on the map
Your knowledge comes first
The box called What you already know is the most useful part. Paste the route variant you actually run, your price, your group size or the itinerary from your old brochure. The AI treats your notes as the authority and only fills the gaps from what it finds. A company that starts Annapurna Base Camp from Nayapul instead of the newer road heads gets its own version, not the average of the web.
What it won't do for you
The draft is a strong first version, not a finished page. It has no photos, because pictures of someone else's group on Larkya La don't sell your trip; add your own from the media library, or search Unsplash, Pexels and Wikimedia Commons from the trip's Photos tab. It adds no departures, since only you know which Saturdays you'll run. The route map stays switched off until you've looked at it. And the facts it found on the web, altitudes, walking times and permit rules above all, need the eye of someone who has walked the trail. Fees change every year, so the draft says so in the way your guides would, rather than quoting a figure that may be out of date by spring.
Stops placed where they really are
AI is often a few kilometres out on the position of a village. After writing, TripNerve looks up each overnight stop and each landmark on OpenStreetMap and moves it to the matching place, as long as that place is within 30 km of the estimate. A namesake village in another district is ignored and the estimate stays, so check stops that look wrong on the route map before you switch the map on.
Changing a trip in plain words
Any trip, drafted by AI or written by hand, has Update with AI. Say what should change, such as "make it 15 days with a rest day in Samagaon" or "add FAQs about permits and altitude sickness". The AI checks facts on the web only when the change needs them, then shows every change: added lines, rewritten lines and removed lines, section by section, with the current text a click away. Nothing is saved until you choose Apply changes, and prices and group policies are never part of an AI edit.
Both jobs run in the background on TripNerve's server. You can leave the page or close the tab, and the draft or the proposed changes are waiting when you come back. Ask AI and connected apps such as ChatGPT and Claude can start the same jobs for you.
Worked example
Drafting the Manaslu Circuit
A Kathmandu company adds a 14-day Manaslu Circuit Trek for spring 2027. In the notes it writes: start and end in Kathmandu, USD 1,390 per person, 2 to 12 people, teahouses throughout.
| Part of the trip | What the draft had | What the office did |
|---|---|---|
| Itinerary | 14 days, Larkya La (5,106 m) on Day 11 | Swapped one lunch stop |
| Price | USD 1,390, taken from the notes | Kept it |
| Map | 13 overnight stops and 6 landmarks, 11 stops moved onto OpenStreetMap | Checked the 2 left at the estimate |
| Practical | Included and excluded lists, 6 essentials, 8 FAQs | Added its own porter policy |
| Photos | None | Added 10 from its own library and free photo search |
The draft arrived about two minutes after the owner clicked Draft trip. The facts that come from the web, altitudes and walking times above all, were checked against the guide's own notes from last autumn. Two stops had no OpenStreetMap match within 30 km and kept the AI's estimate, so the office dragged them into place on the route map before switching it on.
A week later the lead guide asked for a second acclimatisation day. The owner opened Update with AI and wrote "make it 15 days with a second rest day in Samagaon". The proposal showed 1 day added, the later days renumbered and rewritten, the trekking days and highlights updated, and nothing touching the price. She applied it, added the trip's spring departures and published it.
Common mistakes
Publishing without checking numbers
Altitudes, walking times and permit rules found online can be wrong or out of date. Read the draft as a guide would before it goes live.
Leaving the notes empty
Without your route variant, price and group size, you get a generic trip. Two lines of notes make the draft yours.
Skipping the route map check
A stop with no nearby OpenStreetMap match keeps its estimate. Look at the map before you turn it on for travellers.
Starting two jobs at once
Each company runs one trip draft or trip edit at a time. Let one finish before you start the next.

