How to Automate Pruvan

Photographs are what a preservation contractor gets paid for

Pruvan is order management and proof of work software for people whose job only counts once it is documented. It is now part of Verisk.

Property preservation is the clearest case. A mortgage servicer needs a vacant property secured, winterised, mowed, cleaned out or boarded, and the order reaches a contractor through a national field service company. The work might take an hour. Whether it gets paid depends on photographs taken in a particular order, before and after each task, with timestamps that survive a challenge a year later.

The same shape turns up in roof and property inspections, in home services and delivery, and in lending and insurance work. Somebody goes to a location, does a thing, and the evidence is the deliverable.

So Pruvan is built around the field app, the forms it puts in front of a technician, and the certified photos and videos that come back.

The order is done and the file is not

A crew can finish everything on the property and still not be finished.

The order needed a before and after photo on each task and one is missing, which nobody notices until the client's QC team rejects the batch and sends back a reason and a deadline. An estimate came in over the client's allowable with no approved bid, so it returns as a chargeback three months later. A signature was never captured. A note field is empty.

Meanwhile the queue keeps moving. New orders get assigned and sit unseen because nobody refreshed the portal. Vacant properties fall due for their recheck and the list was on a whiteboard. Bids wait on client approval and nobody knows which turned green this morning.

None of that is difficult. It is a person refreshing screens all day, and it is the difference between getting paid and arguing about getting paid.

Workflow Builder shapes the form, the client still owns the scorecard

Pruvan covers the field side about as well as anything does, and a contractor should use all of it.

The mobile app collects results from the field in real time. Workflow Builder builds custom forms and pushes them to web or mobile, so the questions one client insists on get asked the same way on every job. Certified Results produce tamper-proof photos, videos and forms, which is the entire point when a client disputes a charge. The online portal is where work is assigned and adjusted, the invoicing tools cover bids, expenses, payment reconciliation and client-specific pricing, and results can be shared straight to a client or an integrated partner system.

That is a complete loop from assignment to payment.

The ceiling is that Pruvan holds what happened, not what somebody else makes of it. A required photo missing from a task is visible in the record, but the record does not raise a hand. A rejection lands on the client's system with a reason and a deadline. An allowable limit belongs to the client rather than the order. A bid changes status when their approver gets round to it.

A crew can leave the property with the file already complete

The gap between doing the work and being paid for it comes down to who checks the file, and how often.

Completed orders checked for the required before and after shots on every task, with anything missing posted while the crew is arguably still nearby, not after a rejection comes back. Estimates compared against the client's allowable limit before submission, because an overage with no approved bid is a chargeback with a delay on it.

Newly assigned orders picked up every quarter of an hour and posted with the address, order type, due date and contractor, so nothing sits unseen. Orders due in three days gathered into one list. Vacant properties due for a recheck pulled out on Monday, not remembered on Friday.

Then the things that turn into money. QC rejections collected with the reason and deadline against each one. Bids watched for a status change, with a go-ahead drafted the moment one is approved. And when a chargeback arrives, the timestamped photos and notes supporting your side gathered and filed, so the dispute is a draft rather than a scramble through old orders.

Messages stay drafted. A contractor who missed a photo and a client who rejected one both need a human tone.

The proof exists, somebody just has to look at it

All of that already happened. The photos were taken, the estimate written, the bid submitted, the order assigned. What is missing is somebody comparing what is there against what was required, every day, across hundreds of orders.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens Pruvan, reads the order queue, the photo sets, the bid statuses or the rejections the way your coordinator would, files what it gathers where you keep it, and posts the exceptions to whoever can fix them.

It runs on your schedule, limited to the sites you allow. Anything going to a client or a contractor is drafted and waits: a status update to the company that feeds you work should not go out unread.

The workflows below are already built, and each one names what it opens.