Skip to main content

Evidence requests: collecting evidence from others

Written by Sven Poppelmann

Evidence requests collect specified files or photos. General external requests and in-app photo requests have different access rules: a photo request cannot be answered through the anonymous public upload link.

Creating a request on the web

  1. Open the relevant agreement or the farm's evidence-request controls.

  2. Use the request wizard to select items and configure the evidence needed. Catalogue-required evidence types start selected with quantity one; review them, any suggested types and the assigned parcels before proceeding.

  3. Enter a request name, instructions and any deadline, then create the request.

  4. Use the resulting share or invitation controls to send it to the intended recipient.

  5. Monitor the request and review received uploads. Use approval or rejection controls where offered.

External file uploads

For an open general request, the recipient can open its access-key link in a browser and upload to the requested items without a Farmwalk account. Treat the link as private. Do not assume it is single-use, expires after 30 days or automatically stops at the displayed deadline. Close the request when it should stop accepting evidence.

Responding to a photo request on iPhone

  1. Sign in, select the correct farm and open Photo requests from the farm hub when you have received a request, or follow a supported request notification.

  2. Open the request and read what to photograph and the target parcel.

  3. Tap Take photo to open photo capture. A new camera photo needs a usable device location. The photo-library picker can also use an existing image with its own recorded location; images without location are refused for this request. Check that the image actually shows the requested parcel and work.

  4. Check the upload and request status. Queued transfer and processing must succeed before the response is complete.

Notification and email links depend on farm selection, access and supported routing. Open the app and request manually if needed, or use the browser for general requests. Native Universal Links require external server AASA and Apple capability activation; operation should not be assumed.

Did this answer your question?