Practical questions.
Clear answers.

It is the storage destination selected and controlled by your company for evidence files. Field Bundle can upload directly to that destination rather than act as the permanent media repository.

Yes, when it exposes the required S3-compatible operations over valid HTTPS. Compatibility depends on the endpoint and configuration. Validate the complete upload and review workflow before rollout.

It is a service address that implements the required S3 storage operations. The service may be hosted by a provider or run on your own infrastructure; S3-compatible does not necessarily mean public cloud.

R2 and Spaces are specific hosted storage services. Custom S3 lets you configure a compatible endpoint, including self-hosted infrastructure. Provider configuration, permissions, limits, and costs differ.

In the direct-upload workflow, evidence goes to your selected customer-controlled storage. Field Bundle does not need to keep a permanent media copy. Account, device, Work Order, and operational records are separate from the media.

Yes. With storage connected, users can browse Work Order folders in the Company Portal and download them as ZIP files. Keep the signed package records with the evidence for verification.

Create the Work Order in the Company Portal, add instructions, a reference image, and customer/site details, then assign a company phone. That phone receives a push notification.

Yes. Reassign Work Orders from phone to phone. A technician can also return a Work Order to the office with a note, such as “This job is rescheduled for Friday.”

No. Evidence location stamps and requested tool-location sharing are supported, but Field Bundle does not run background GPS monitoring.

When the phone gets back online, uploading continues. If upload fails, share the evidence package as a ZIP using Android’s native share menu. Evidence photos are not placed in the technician’s personal gallery.

Yes. Capture the before photos, completely close the app, and reopen the same persistent Work Order session after the work to take the after photos. Add the work-performed notes, then upload the package.

Yes. Assets support assignment and custody, technician responsibility, availability, maintenance, and out-of-service states. Issues and reminders support related follow-up work.

Yes. After a connectivity interruption, the phone continues uploading files when it is back online.

Yes. Add a reference picture showing what needs fixing, enter the instructions or description when creating the job, and include the site/end-user name, street address, building number, and phone number. The technician can then record what was done in the field.

Tap the phone number to open the dialer with the number filled in; you choose when to start the call. Tap the address to open maps, then start directions to the job location.

The asset record shows which phone holds the tool. Send its holder a push notification requesting location sharing. When the location is shared, view it on a map. This is not continuous background tracking.

Yes. Schedule service or other reminders months in advance and select an email alert to the company before the event.

No. Evidence photos remain within the Field Bundle workflow rather than the personal gallery. If uploading fails, the package can be shared as a ZIP using Android’s native share menu.

The browser verifier checks SHA-256 fingerprints against signed package records, validates signatures and record consistency, and reports unchanged, modified, missing, and extra files. The check runs locally without uploading media.

Not necessarily. An unchanged subset can be marked Verified while omitted files are listed as not included. Review completeness separately. Required verification records must be present.

The supplied verifier is package-oriented. It needs the required signed records; a standalone photo without those records is not sufficient.

No. The public key is supplied inside the package, not independently anchored to a trusted device registry by this verifier. Integrity checks do not establish that the depicted event is true or independently prove capture time.

Yes. Both the front and rear cameras support photo and video capture.

A short summary of the work performed, photo thumbnails, capture-time information, and recorded locations. Click the photo or video coordinate links to open the location in Google Maps.

The date, time, GPS coordinates, and a geocoded address provide capture context. Stamping follows app settings and company policy.

It converts the capture location into a readable address so reviewers can see the address alongside the GPS coordinates.

Yes. If geocoding fails or returns the wrong address, you can edit the address manually while taking the picture.

Yes. Company Seats provides device activation, seat usage, available seats, and replacement or removal controls in the Company Portal.

Use the company device-management controls to replace or remove the old phone and activate the replacement. Review seat allocation and outstanding Work Orders during the handover.

Yes. Company users can have Administrator, Dispatcher, or Office roles. Server-side permissions determine the access available to each role.

Company capture and evidence policies can set those requirements for company devices. Configure them to match the work and your company’s obligations.

You can select email notifications for Work Order uploads. Daily or weekly KPI emails list phones and the number of Work Orders uploaded by each phone.

Use the Get Android App page to request current access instructions by email. The supplied website does not include a public Play Store download link.

They list the phones and the number of Work Orders each phone uploaded. Choose a daily or weekly reporting cadence.