> For the complete documentation index, see [llms.txt](https://help.mywayroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mywayroute.com/guides/proof-of-delivery.md). # Proof of Delivery Visit tracking, Visit Confirmation, Proof of Visit, Delivery Status, Delivery Confirmation. The app provides several features for managing stops when you on route, such as taking photos, setting statuses, adding notes, collecting signatures, and more. These features depend on the app settings, particularly the “Proof of Delivery” option. ### Behavior of the “Done” Button The functionality of the “Done” button in route-following mode changes based on the “Proof of Delivery” setting: • **When “Proof of Delivery” is ON:** The “Done” button opens the Proof of Delivery screen. • **When “Proof of Delivery” is OFF:** The “Done” button closes the current stop and activates the next one. ### Proof of Delivery Features Multiple statuses are available, including: • **Arrived:** Automatically selected when marking “Success” or “Failed” for precise arrival tracking. • **Success:** Allows adding proof such as photos, signatures, and details. • **Failed:** Requires selecting a predefined failure reason or adding a custom reason. Customizing Arrived Status: If necessary, you can uncheck the “Arrived” status. This prevents the app from marking the stop as visited, which will impact the calculated travel distance.

You can quickly pick the "Proof of Delivery" status from route following mode by swiping stop to the right (see screenshot below) and picking the desired status.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.mywayroute.com/guides/proof-of-delivery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.