Keep the underlying location
A screenshot can help someone recognise an area, but it may omit the exact address, zoom level or link needed to identify a place reliably. Keep the confirmed location record alongside the image. Do not let a cropped circle or arrow become the only instruction in the transport request.
If you add an annotation, explain what it represents. “This is our hotel” and “We hope to meet here” are different statements. The first describes a destination; the second proposes an arrangement that may still need to be checked and agreed.
Do not infer access from the picture
A map view does not confirm where a vehicle may stop, which entrance is in use or whether the proposed point suits the party’s walking needs. Ask for the practical collection arrangement to be confirmed. Avoid describing a visually close point as guaranteed door access.
This matters when a family member chooses a location remotely. The image may make two points appear adjacent while leaving out the route a traveller must actually use between them. Describe any practical requirement instead of assuming that distance on the screen answers it.
Share one agreed version
After the meeting point is confirmed, send the usable instruction to the lead traveller. Keep the image as an aid, but preserve the accompanying text or link. If the arrangement changes, label or replace the earlier screenshot in the working plan so that it does not resurface at collection time.
Ask the traveller to explain where they expect to meet, using the current instructions. If their description differs from the booking record, resolve the mismatch before departure rather than collecting more screenshots of the same uncertainty.
A good map image supports an agreement. It does not create one by itself. Keeping that distinction clear makes visual planning useful without turning a convenient illustration into an unverified transport promise.
Explore Pilgrim Taxi journey options · Read The Pilgrim Edit