Features
Everything between the job and the proof.
Bolvido is one engine. What changes between a cleaning company and an HVAC contractor is the workflow, not the software.
Workflow engine
Every company runs its jobs differently, and the difference is the business.
You describe what a kind of job requires — checklist items, which evidence is mandatory, who signs. Every job copies that workflow at creation, so editing a template never rewrites a job that has already run.
Job templates
Define once. Every job inherits the requirements.
Immutable in use
A running job keeps the workflow it started with.
Required vs optional
Only required steps gate a verdict.
Configuration, not code
A new vertical is a workflow, not a release.
Verification
“Completed” is a claim by the party with the most incentive to make it.
When a job completes, its evidence is checked against the job’s own copy of the workflow. Two required photos and one arrives, and the job comes back with the reason. A verifier that cannot reject is a rubber stamp.
Automatic evaluation
Deterministic rules run without a human.
Rejection with a reason
“Requires 1 customer signature, got 0.”
Rework loop
A rejected job returns to the crew, evidence intact.
Independent of the worker
Whoever performs the work does not judge it.
Evidence
A photo alone proves almost nothing. It could be old, staged, or from somewhere else.
Every piece of evidence carries who captured it, when, and where, bound to the job and the requirement it satisfies. It is hashed on arrival and never edited in place — proof you can rewrite is not proof.
Append-only
Never overwritten, never deleted in place.
Tamper-evident
Fingerprinted at capture. A later change cannot hide.
Attributed
Bound to the person who captured it.
Typed
Photo, video, location, signature, form, note.
People and assignment
Two people share a job. “The crew did it” names nobody.
A job has one accountable Lead, who starts it, completes it and signs it, plus any number of participants who can view it and capture evidence. Login is optional: a subcontractor is dispatched and credited without ever holding an account.
Exactly one Lead
Enforced by the database, not by convention.
Collaborative capture
Participants add evidence; only the Lead attests.
Login is optional
Assignment does not require an account.
Transferable
Leadership can move mid-job, and the change is recorded.
Offline
The van has no signal, and the worker has finished the job.
Work is captured on the device and held until the server acknowledges it. A worker who loses one completed job stops trusting the app forever, so this is expensive by choice.
Write before confirm
Nothing is acknowledged until it is durable.
Retain until acknowledged
The device keeps it until the server has it.
Queued uploads
Media lands when service returns.
Conflict handling
A late sync never resurrects revoked authority.
Multi-company
One platform, many companies, and no acceptable failure mode.
Every record belongs to exactly one company, and isolation is enforced beneath the application rather than by code that has to remember. Ask for data without saying which company you are, and you get nothing — never somebody else’s work.
Isolated by default
Separation is the floor, not a filter someone applies.
Fail closed
The safe answer to an ambiguous question is no answer.
Per-company workflows
Your configuration never leaks to another company.
Audited access
Any read that spans companies is an explicit, reviewed path.
Your operation will not look like this list
Stop taking “done” on trust.
Define the workflow. Capture the evidence. Let Bolvido decide whether it holds up.