Make a destination card
| Field | Use | Check |
|---|---|---|
| Venue name | The name used by the venue | A translated nickname may not identify it. |
| Address | Original spelling and script | Keep building and unit numbers intact. |
| Map pin | A saved link or clearly labelled map | Check that it points to the intended building. |
| Entrance | The venue’s own directions if supplied | A rear entrance can differ from the main address. |
| Request | One short task such as “Please take me here” | Keep the task separate from the address text. |
Use the confirmation card to present a value clearly. The card copies your entry; it does not validate an address or translate an arbitrary sentence.
Preserve the text that identifies the place
Do not replace a person’s name, building name or local script with a guessed translation. If your booking supplies both a local address and a romanized version, keep them labelled. A person reading the local script may find it more useful than a phonetic approximation.
Fictional example: a hotel confirmation includes a street address and “Entrance on the courtyard side.” Put the address on one line and the entrance note on another. Do not merge the courtyard instruction into the official street name.
Check spoken and written understanding separately
- Show the destination while you make the request.
- Ask the other person to identify the same place on the map.
- Resolve a branch, building or entrance mismatch before moving on.
- Keep any new meeting point distinct from the original address.
A translator can produce a plausible sentence while still substituting a place name. Read the name and numbers on screen. If you cannot read the destination script, compare it with the original source rather than editing it from memory.
Show only the detail needed
A destination screenshot does not need your full booking code, passport details or private messages. Prepare the card while you have time, then keep the original booking available if authorised staff need it. Read the privacy checklist for deciding what to enter into a translation service.
Sources and scope
For taxi travel in Japan, JNTO recommends keeping the destination written in Japanese, especially for a less familiar place. The destination-card fields, entrance example and privacy checklist here are editorial preparation guidance; the source does not validate an address, map pin or universal travel procedure.
Practical examples are editorial exercises, not recordings, measured app results or claims about a currently released feature.