Workwitness
A contractor-controlled receipt workspace that binds authorized work orders to source-preserving field evidence, reviewer acceptance, payment requests, operator acknowledgments, settlement states, disputes, and correction under an openly versioned schema.
The research confirms field-photo and mobile-form products, content-provenance standards, signing infrastructure, and improving device support. It found no standard assertion for work performed. Content provenance can describe an image's capture and edit history within scope, but it does not prove who did the work, where the device really was, that the task met specifications, that a customer accepted it, or that payment is due.
Workwitness should create a portable evidence bundle, not an automatic settlement instrument. A paying network must explicitly contract to accept a schema version, evidence class, review process, authority, exceptions, dispute rights, and payment trigger. Device attestation, geolocation, time, asset scan, photos, measurements, technician statement, supervisor review, and customer acknowledgment remain separate observations.
The contractor keeps an export and controls reuse, while customer, occupant, site, and bystander privacy is minimized. A receipt can be corrected or superseded without erasing history. It never becomes a worker-performance score, universal credential, lien waiver, safety certificate, code compliance proof, warranty, or guaranteed payment.
Field-service networks, contractors, insurers, property operators, and marketplaces that need mutually accepted completion evidence and a portable dispute trail.
Device provenance and signing support make portable evidence more practical now.
Networks and contractors handling disputed field completion are specific.
Several evidence, closeout, claims, and worker-owned credential neighbors support the direction.
The field network buyer, portable schema, accepted evidence class, contractor ownership, and payment-state separation are concrete.
Acceptance is a two-sided adoption problem, provenance does not prove work, privacy and fraud are difficult, existing platforms can add exports, and contractual settlement semantics vary.
Discussion
No comments yet — be the first to weigh in.
