Skip to content
Weezie

Field operations

Field evidence standard

Capture context that supports quality and handover.

Version 1.0

Evidence schema

Diagram connecting a field submission to its work package, network object, technician, location, timestamp, design baseline, validation result, and acceptance decision
A usable evidence record connects each photo, measurement, form, and geometry update to the work and network object it proves, so reviewers do not have to infer context from filenames or message threads.

Offline capture sequence

  • Open the assigned work package and cache its map, forms, assets, and evidence rules before travel.
  • Confirm the network object and activity before capturing geometry, photos, measurements, or material use.
  • Validate required fields and plausible values on the device without assuming connectivity.
  • Queue changes with stable local identifiers and show the technician what is waiting to synchronize.
  • On reconnect, reconcile conflicts explicitly and retain both the submitted evidence and the acceptance response.

Worked example: cabinet installation

Acceptance packet example

A cabinet installation packet contains the assigned asset identifier, captured position, enclosure and label photos, foundation measurements, installed materials, technician identity, timestamps, and the deviation from the approved route. Each item is attached to the cabinet and work package rather than uploaded as an unrelated file set.

Submission checks identify a missing internal label photograph before the crew leaves. After it is added, QA reviews the deviation, records the acceptance decision, and promotes the accepted position and asset state into the operational record.