Skip to content

Verification

A green tick that means something.

“Completed” is a claim by the party with the most incentive to make it. Bolvido checks that claim against the workflow you defined, and tells you when it does not hold.

Watch a job get verified.

“Completed” is a claim by the party with the most incentive to make it. Bolvido checks it against the workflow you defined — and sometimes says no.

Standard Clean at Acme HQ

Verified
  • Checklist complete3 of 3 items
  • Photos captured3 of 3 required
  • Location proof12 m from site
  • Customer signaturesigned at hand-off

Checking 4 of 4 requirements…

Verified

Checked against the workflow. 4 of 4 requirements satisfied.

Without Bolvido

  • “It’s done” — from the person paid to say so
  • Photos in someone’s camera roll
  • A phone call to ask if the crew arrived
  • Paper forms in a van
  • A dispute you cannot settle

With Bolvido

  • A verdict from evidence, against the workflow you defined
  • Photos bound to the job, hashed, immutable
  • Location captured once, at the site, as proof of presence
  • A signed hand-off, attributed to a named person
  • An audit trail you can hand to the customer

Four conditions, and only one of them is proof.

Field work happens out of sight of the office and the customer. Every tool on the market can record the third rung. Bolvido exists for the fourth.

1

Assigned

The office’s intent

Work has been given to a crew. Nothing has happened.

2

Executed

The worker’s activity

Tasks are underway. Evidence is being captured.

3

Completed

The worker’s assertion

The crew says it is finished. This is a claim.

4

Verified

The system’s corroboration

The claim held up against the workflow’s requirements.

Evidence is generic. Requirements are yours.

The engine does not know what a cleaning photo is. It knows an immutable, provenance-bearing item that satisfies a requirement. That is why a pest-control chemical log and an HVAC sensor reading run through the same code as a photograph.

Photos

The visual state of the work.

thumbnail · captured-at · content hash

Video

The process, not just the outcome.

duration · poster frame · hash

Location

Someone was at the site.

coordinates · accuracy · distance from site

Worker signature

The worker attests to the work.

signed-at · the person who signed

Customer signature

The customer accepts the work.

signed-at · signer name

Forms

A structured reading or a pass/fail.

field values · units · tolerance

Provenance is not metadata. It is the evidence.

A photograph proves that something was photographed. The same photograph, captured by a named person, at 09:14, twelve metres from the site, during the “confirm unit serviced” step of a specific job — that is proof. Strip the provenance and you have a file.

The audit trail is the deliverable.

A dispute with a customer is not settled by an opinion. It is settled by a verdict, the requirements that produced it, the evidence behind each one, and the name of the person who captured it. Bolvido keeps all four, permanently, and can hand them over.

  • Every state change of a job, with its timestamp.
  • Every requirement, satisfied or not, and by which piece of evidence.
  • Every evidence item, hashed at capture and never rewritten.
  • Every verdict, with the reason it was reached.

Questions we get asked.

Does a human have to review every job?

No. Deterministic requirements — “three photos”, “this checklist”, “a customer signature” — are evaluated automatically the moment a job completes. Judgement calls can be routed to a person, but most jobs never need one.

What happens when a job fails verification?

It is rejected with the reason, in the product’s own words: “requires 1 customer signature, got 0.” The job returns to the crew, and every piece of evidence they already captured stays attached to it. Nothing is discarded.

Can a worker verify their own work?

No, structurally. The actor who performs the work never judges it. That separation is what gives the verdict any worth.

Does Bolvido track workers between jobs?

No. Location is captured once, at the site, as proof of presence for a job that asked for it. There is no background tracking, no route history and no fleet view.

Can evidence be edited after the fact?

No. Evidence is append-only and hashed on capture. A correction is a new piece of evidence, not an overwrite. Proof you can edit is not proof.

Stop taking “done” on trust.

Define the workflow. Capture the evidence. Let Bolvido decide whether it holds up.