How Bolvido works.

Bolvido has one job: to turn a worker's “done” into evidence a customer can see. Everything you configure serves that.

1. Add your sites — the places work happens.
2. Add your people. Login is optional; a subcontractor can be assigned work without an account.
3. Define a workflow: the checklist, the required evidence, who signs.
4. Create a job from that workflow, assign a crew, and name a Lead.
5. The crew executes. Verification runs the moment they complete it.

Two surfaces, one engine. The dashboard is where the office manages work: schedule, assign, verify, report. The worker app is where it is performed: start, do the tasks, capture, complete.

The separation is deliberate. A worker completes; a verifier judges. Whoever performs the work never decides whether it passed — that is what gives a verdict any worth.

A workflow describes what a kind of job requires: its checklist items, which evidence is mandatory, and who must sign. It is the mechanism of industry specialisation — a pest-control chemical log and a cleaning photo are the same thing to the engine, and differ only in what a workflow demands.

Workflows are immutable in use

Every job copies its workflow at creation. Editing a template changes what the next job requires; it never rewrites a job that has already run. A job verified last March is still judged by March's rules.

A job is a unit of verifiable field work at a site. Its state moves through scheduled → assigned → in progress → completed → verified, with rejected as the branch that matters.

Exactly one Lead

A crew can share the work and the evidence. Exactly one person is the Lead: they start the job, complete it, and sign it. Participants can view the job and capture evidence but cannot transition it. “The crew did it” names nobody, and a signature needs a signatory.

People do not need logins

A Person is an operational identity. Login is a separate, optional capability. A day labourer is dispatched, appears on the crew, and is credited with the evidence they capture — without ever signing in.

Evidence is a typed, immutable, provenance-bearing item that substantiates a step of a job. Photo, video, location, worker signature, customer signature, form, note.

Provenance is constitutive

A photograph alone proves almost nothing. The same photograph, captured by a named person, at 09:14, twelve metres from the site, during the “confirm unit serviced” step of job J — that is evidence. Strip the provenance and you have a file.

Append-only

Evidence is never altered or deleted in place. It is hashed with SHA-256 at capture. A correction is an addition. Proof you can edit is not proof.

Records and attestations

Any assigned person may capture a record — a photo, a note. Only the Lead may produce an attestation: a signature, or the completion location proof. An attestation names its affirming party; a record does not need to.

When a job completes, its evidence is evaluated against the job's own copy of the workflow. Deterministic requirements resolve automatically. If they all hold, the job is verified. If one does not, it is rejected, with a reason in the product's own words: requires 1 customer signature, got 0.

A rejected job returns to the crew and keeps every piece of evidence it already had. Nothing is discarded. A verifier that cannot reject is a rubber stamp.

Staffing never enters a verdict. A job planned for three people and executed by two, with every requirement satisfied, passes. Headcount is not evidence.

Field work happens where there is no signal. The worker app captures to the device first and holds the work until the server acknowledges it — write before confirm, retain until acknowledged.

A worker who loses one completed job stops trusting the app forever. That is why this is expensive by choice, and why the device is temporarily authoritative for its own jobs.

The worker app is where evidence is captured: today's jobs, the checklist the workflow defined, photo capture, signature, completion. It is built for one hand, in daylight, wearing gloves.

A worker sees only the jobs they are assigned to, and only the requirements their workflow asked for. There is no inbox to triage and nothing to configure on the device.

The office view. Jobs, sites, people, workflows, and the verification result behind each completed job — with the evidence, and who captured each piece.

What it deliberately does not contain: a leaderboard, a jobs-per-worker ranking, a utilisation percentage, or a map of where anyone is. Bolvido measures units of work, never the diligence of a person.

Does Bolvido track workers?

No. Location is captured once, at the site, for a job whose workflow asked for it. There is no background location, no route history, no fleet view.

Can a manager override a rejection?

A rejected job can be reworked and re-verified. It cannot be silently marked as passing — the verdict and its reason stay in the audit trail either way.

Is Bolvido an invoicing or payroll system?

No, deliberately. It records what was done and what was consumed, and hands that to the systems that bill and pay. It computes no charges, taxes or wages.

Direct access to the people who build it. Write to our contact page or report a vulnerability under Security.