Date and time on the photo.
Stamp captured photos with the date and time. Include GPS coordinates and a geocoded address according to your capture settings and company policy.
Evidence & verificationA clear record.
A clear record.
A checkable package.
Capture the work, preserve the package, and check whether the supplied files match its signed records—directly in your browser.
PHOTO TAGGING & VIDEO CAPTURE
Show when and where the work happened.
Date, time, coordinates, and an address give a photo the context a reviewer needs.
The address, with a manual correction.
Geocoding turns the capture location into an address. If the lookup fails or shows the wrong address, edit the address manually while taking the picture.
Photos and video. Both cameras.
Capture still photos or record video using either the front or rear camera. Choose the format that best documents the work.
Capture with context
Give the evidence a Work Order.
Capture before-and-after photos and video with either the front or rear camera. Stamp photos with the date, time, GPS coordinates, and the geocoded address. Correct an incorrect or unavailable address manually during photo capture, and add the work description to document the job. Company capture policy defines the requirements for the deployment.
Persistent sessions let technicians continue the job after closing the app or restarting the phone. Trusted-time-related metadata may accompany evidence; it should not be confused with independent proof of real-world capture time.
THE WORK ORDER PDF
A short report with the evidence in context.
What was done
A concise description of the work performed gives reviewers the context for the job.
What was captured, when, and where
Photo thumbnails, capture-time information, and recorded locations make the evidence easier to review.
Open the coordinates in Google Maps
Clickable coordinate links for photos and video open Google Maps at the recorded capture location. They show where the evidence was recorded; they do not independently prove the event.
How the supplied verifier works
From file fingerprints to package checks.
Fingerprint the files
SHA-256 fingerprints represent the exact bytes of package files. Changing a file changes its fingerprint.
Preserve signed package records
The package contains a manifest, signed media receipt records, and a public signing key. The verifier checks P-256 ECDSA signatures and consistency between those records.
Open the ZIP, folder, or package files
The browser reads the files locally, validates the signed records, and compares the supplied files with the manifest. No customer media is uploaded by the verifier.
Read integrity and completeness separately
An unchanged subset can receive a Verified result while missing signed files are listed as not included. Extra unsigned files and modified files are reported separately.
Do these files match?
Verification checks the supplied files against the signed manifest and media records. It identifies changed content, invalid records, and files outside the signature.
Is the whole record here?
Review the file count and missing-file list. A valid subset is not the same as a complete package. Missing required verification records prevent verification.
What does the key establish?
The signing key travels inside the package. That alone does not independently prove which company or authentic Field Bundle phone created it. Compare the fingerprint through a trusted channel when identity matters.
What is not established?
The supplied verifier does not query an independent server receipt or trusted device registry. It can display capture-time metadata, but that does not independently authenticate the time or the real-world event.
This is package-oriented verification. Keep the signed records with the files. A standalone photo without the required package records is not a complete verification input.
Local browser verification
Check the package. Keep the media local.
Open a Field Bundle ZIP or folder in the verifier. The verification page makes no network requests.