Skip to main content

Uploading evidence from the field

Written by Sven Poppelmann

Capture evidence while doing the work, then check that the correct file, agreement and parcel were saved. The web browser and native iOS app use different workflows.

Web browser

  1. Open the relevant agreement action or item and choose Add Evidence.

  2. Choose Upload New where offered. Browse for a file, or choose Take Photo; the browser/device decides which camera or file-picker options appear.

  3. Wait for the upload to complete. Uploading saves the file but does not automatically select or link it.

  4. If the farm's Require approval setting applies, ask an authorised reviewer to approve the uploaded record first. An Awaiting approval or Not approved record cannot be linked. Then select the approved saved file in the evidence dialog and choose Add. Check any linking error and the resulting evidence record.

You can also upload through Records, then return to the agreement to link the file.

Native iOS app

  1. Choose the correct farm. For a specific agreement item, open its detail and tap Add evidence; this opens Capture with that item already selected.

  2. In Capture, choose Photo, Video or Audio and allow the permissions needed for that mode. The photo-library button selects existing images; it is not a general PDF/document picker.

  3. Capture the evidence. General captures may offer an agreement-link suggestion or Link to... selection; item- or task-seeded captures already carry that target.

  4. Check the upload queue. Saved on the phone is not yet uploaded. Linking happens after the file upload succeeds, and can still fail.

You can also start from the Capture tab or a task's Capture button. Check which target that entry point selects.

Location and parcel checks

Location depends on permission, a usable GPS fix and available parcel geometry. The iOS app can attempt parcel matching, including cached geometry offline, but may leave a capture untagged when it cannot obtain a trustworthy match. Check the parcel rather than assuming it is correct. Specific photo-request flows can require coordinates and refuse a capture without them.

Existing photos may lack trustworthy location or capture time. A device location obtained during upload is not necessarily where an older photo was taken. Metadata supports a review; it does not independently prove where, when or how the work was done.

The in-app camera adjusts its preview and saved photo/video orientation as the phone turns, where the camera connection supports it. Check the saved image. Image rotation is separate from GPS location or compass direction, which may be unavailable.

Tips

Capture context and detail, keep the originals, and check upload, linking and approval status once you have a connection.

On the web, an eligible approved record's preview also offers Log as evidence to select scheme codes and parcel or works-stage context. Verify the saved links and review status. If an action is missing from the native Link picker, check the agreement on the web rather than assuming it does not exist; the picker loads active agreements with limits and can omit items when a request fails.

Did this answer your question?