Published · GeoCliks Field Notes
What should a courier record when the map pin points to the wrong delivery address?
When the map pin conflicts with the written delivery address, record the discrepancy and check the written address and permitted delivery instructions before closing the stop. A route pin is a navigation aid, while a capture's GPS, accuracy and photo give context about where a photo was taken; neither proves the correct door or recipient received the parcel. If the authorized drop or handoff cannot be confirmed, record a failed attempt or exception under the applicable workflow, rather than labeling the parcel delivered. Keep the stop identifier, contact and dispatch notes, relevant photos and the eventual handoff or redelivery record together.
A recipient's address, a navigation pin and a photo location are different pieces of information. In the recent cottage question, the recipient says one public map places the pin correctly while drivers from several services still go elsewhere; that alone cannot identify which routing source each driver used. Treat a mismatch as an exception to resolve, not as proof that the map, driver or customer is at fault.
Compare the four locations before marking delivered
| Record | Useful question | Limit |
|---|---|---|
| Written stop address and unit | What destination was requested? | An incomplete or mistaken entry can still route a driver incorrectly |
| Navigation pin and route | Where did a map direct the driver? | A pin can differ by map or routing system; arrival at a pin is not delivery |
| Recorded photo GPS, reported accuracy and derived address | Where did the device report capture? | GPS can be inaccurate or spoofed; the address derived from it is not an independent witness |
| Scene, handoff and stop status | What was visibly left, who was contacted, and was a permitted drop completed? | A photo cannot independently prove customer receipt; an attempt must not be labeled a completed drop |
For an apartment, a building-level pin may bring the driver to the property without identifying a unit or permitted entrance. A photo of a parcel beside an unmarked door cannot fill that gap. Compare the written unit, any permitted recipient instructions and visible fixed context; never enter a restricted space or leave a parcel where instructions prohibit it merely to produce a photo.
Completed drop vs failed attempt
| Situation | Record now | Do not infer |
|---|---|---|
| Authorized drop at the confirmed destination | Stop ID, parcel reference, permitted photo context and actual stop status; recipient handoff detail where required | A photo or checked timestamp alone proves customer receipt |
| Pin disagrees and the correct location is unresolved | Entered address, observed pin discrepancy, contact/dispatch attempt, safe scene context and exception reason | Arrival at a pin means delivered |
| Access blocked or unit unclear | Attempt time and source, specific obstacle, contact attempt, next action and appropriate failed-attempt status | A failed attempt is an accepted or completed delivery |
| Redelivery after correction | The original exception and a separate later stop/handoff record | The later delivery retroactively turns the first attempt into a successful drop |
A simple dispatch test: take 3 test stops, one ordinary address, one incorrect pin and one missing unit. For each, ask a reviewer to separate a completed stop from an exception using the same four fields: written address, navigation destination, capture context and final status. Three stops times four checks equals 12 checks in this hypothetical test, not a benchmark or proof of automated features.
Where route pricing fits
If buying software, ask whether the plan covers route creation, exception reasons, driver seats, photographic records and exports separately. GeoCliks' live pricing page, checked October 19, lists Delivery Routes as a separate family: Delivery Free is $0 for 40 stops/month and 1 driver; Delivery Lite is $39/month for 500 stops and 2 drivers. Stops count when added to a route, not only when delivered. These are the displayed plan terms, not a promise that the field evidence plans include routing or that a photo corrects a map pin. Confirm plan limits and the actual app workflow before purchase.
Fix the map only after identifying which one is wrong
Official map-provider instructions describe how a user can suggest an address or pin-location correction, but changing one public map does not establish that every carrier's routing system uses that map. The cottage poster said in replies that the pin on the public map they checked was already correct, so editing that map may not solve their issue. Pass the specific discrepancy to the relevant dispatcher or carrier, check the address and permitted instructions in the order, and record the resolution for the next attempt. Do not publish recipients' names, door codes or exact private addresses in a public photo or link.
Follow-up questions
- What should a courier record when the map pin is wrong?
- Keep the entered stop address, observed pin discrepancy, parcel/stop reference, contact and dispatch attempts, actual capture context and accurate final status. Record a failed attempt rather than a successful drop if the permitted destination cannot be confirmed.
- Does GPS prove the parcel reached the correct house?
- No. Device GPS has reported accuracy and can be wrong or spoofed; a readable address reverse-geocoded from it is not a second witness. Compare it with the written destination, visible context and handoff or exception record.
- Should I take a photo at the wrong pin to prove I tried?
- Only if the applicable workflow permits an attempt-context photo and it is safe and privacy-appropriate. Label it as an attempt, not a completed delivery; follow the carrier's instructions for contact, return or redelivery.
- Will fixing a public map pin update every courier's route?
- Not necessarily. Providers and carrier systems can use different address sources. Check the specific system used, correct the written order address if needed, and report the mismatch through the relevant carrier or dispatcher.
- Can an integrity-checked photo settle a misdelivery claim?
- No guaranteed outcome follows. A checked time and matching file hash can help assess a recorded capture and changes to it, not establish exact physical presence, authorized placement, recipient receipt or who caused a misdelivery.